Run hookup test in rslogix 5000

Run a Motor and Feedback Test. Applying the Commutation Hookup Test Run a .. Logix ™ Controllers Motion Instructions Reference Manual, publication MOTION- .. RSLogix ®, version. or.
Table of contents

• Hook up test rslogix 5000
• Scripting must be enabled to use this site.
• 11 posts in this topic
• Servo hook up test | glohi.xsrv.jp
• Create an account or sign in to comment

I have a couple questions that I am hoping you may be able to help me figure out as I have been struggling to get the results I am looking for. I am using Logix Version The first question is probably pretty simple, but I haven't been able to find the answer and have searched through this forum, as well as, the AB Knowledgebase. Unfortunately, it works differently as it is looking for input and return parameters to go along with the instruction. Upon downloading the program to the controller, it shows that it is linking all of the routines, but when trying to execute an output from routines other than the MainRoutine, I get no response.

The second question I have is a tad more complicated, at least for me, as this is the first time I've jumped into servo motion control.

I have no issues when testing and tuning each axis, which is probably the easiest part of the process. Upon initial trial of jogging my indexing motor, it immediately errored. I realized that I hadn't turned the servo drive on with the MSO instruction prior to attempting the move. It would engage, then go done, and withing 2 seconds engage itself again.

I'm not sure where I'm going wrong and have not found an answer. I have looked at some sample code from the Knowledgebase, but it is all for earlier versions. I'm hoping I might be able to get a little insight into my problem from the experts in this forum.

I have also attached a copy of my program for you to critique. Again, I am new to fairly new to RSLogix so don't be too harsh. Share this post Link to post Share on other sites. You need to use the JSR instruction to execute the other routines, just like in Logix Leave the input and return parameters blank, they are optional.

When I insert the JSR instruction, it doesn't usually display those fields anyway. Perhaps it's the way I enter it. As far as the servo control itself, I'm not sure I follow your description. Or is it just the MSO command that is cycling? I've attached a routine that I built for manual servo control that includes and initialization sequence for reseting and turning the servo on, as well as jogging, etc. Try adapting that to your use to see if that helps. You can import it into your project as follows: Extract the file, will have an L5X extension.

Right-click on the "MainProgram" folder and choose "Import Routine". Find the L5X file and select it, then follow the prompts. You'll have to adapt some of the logic for your purposes, but I've used this on the L33ERM with Kinetix , so it should get you started. You can also do testing without logic by using the Motion Direct Commands right-click the axis to find the option.

This lets you send motion commands directly to the axis without writing logic. This can be helpful for figuring out what commands to use, troubleshooting, etc.

11 posts in this topic

Thanks for the reply Jross. I insert the JSR identical to how I do it in I've tried leaving the input and return parameters blank, but when I go to verify the program, it gives me errors for leaving those parameters blank. The servo is following the logic in engaging and disengaging.

As soon as I put the controller into remote run mode, this takes place. I'm not asking the drive to execute the move until I press the Jog button, but it is engaging and disengaging itself. I'm not getting any movement out of the servo, atleast not that I can see, but it is cycling.

• .
• Logix5000 and Kinetix 6500 Motion.
• definition of radioactive carbon dating.
• dating in your late twenties.
• dating a southern girl.

The drive shows cycles between running and stopped. Also, thank you for the sample logic, I will definitely take a look at it and learn from it. If you leave the '? Be sure to highlight any and all characters in the fields then backspace or delete. They should disappear upon hitting the enter key.

Blown Fuse Bus Loss. A blown fuse was detected in the power structure. Call your Rockwell Automation sales representative to return module for repair. Motor Feedback State Error. The number of illegal state transitions of the AQB encoder signals has exceeded a factory limit. The motor feedback wiring is open, shorted, or missing. Aux Feedback State Error. The auxiliary feedback wiring is open, shorted, or missing.

The number of illegal state transitions of the AQB encoder signals has exceeded a user limit.

Create an account or sign in to comment

The number of consecutive missed or corrupted serial data packets from the feedback device has exceeded a factory set limit. Communication was not established with an intelligent encoder. Motor Fdbk Serial Comms. The number of consecutive missed or corrupted serial data packets from the feedback device has exceeded a user set limit. Aux Feedback Serial Comms.