The number of digital I/O points is normally set under program limits setup under a controlled start:
As to your other issues, is $IO_AUTO_CFG set to true?
The number of digital I/O points is normally set under program limits setup under a controlled start:
As to your other issues, is $IO_AUTO_CFG set to true?
Changing the mount angle will affect collision detection sensitivity, which should be good in this case. I am kind of surprised it's not throwing false alarms as is.
It can also affect the axis limits, but that varies by mechanical model. That information can be found in the mechanical unit operator's manual.
If you put in an accurate payload, does the issue go away?
Is it a position register that you are touching up?
It's probably being overwritten by your code. If you could post your code, that would really help.
Do your tool and user frames match between the simulated and real robot?
Look at the summary.dg file.
You do know that will completely wipe the robot, correct?
Yes, once the register is read on the robot you will then use the same group output from the PLC to to set the load number, the layer, the unit...
PLCPART uses a combination of complimentary DI/DO and GI/GO signals.
The digital in and out are a request to send output and ready to receive input on the robot side.
The group input is used to send the data, and then the group output is used to echo the data back to the PLC for error checking.
Cause:
The specified program is not paused.
Remedy:
Pause the program.
You can only use one motion instruction to the same PR. You need to use registers and math to adjust that PR.
I don't see a way not to use PR[i,j].
Is there an active payload? Can you post a picture of the payload schedules?
You need to use only one PR, but cannot change the individual elements of the array?
That doesn't make sense.
Could you maybe post the actual question as it is written?
Is your payload properly set?
Have you had any hard crashes lately?
After the fault code, does it list a program name and line number?
Your hold signal is off because it got mapped to the cable when you turned on auto I/O assignment.
Do you have a backup from before you started this? It might be easier at this point to load a backup of DIOCFGSV.IO and start over without $IO_AUTO_CFG turned on.
Are you actually using the UOP's? Some of your UOP's are mapped to rack 35, slot 1, which is the internal always on rack.
No, you run it from windows. Just open the device in windows explorer and double-click on apverify.bat
Sounds like you got a bad re-burn.
Have you run apverify.bat?
It's in the root directory and can be run to verify all of the files are present. If successful, it will just terminate. If it fails, it will post an alarm.
DCS is a paid option. You would specifically need DCS Cartesian position check.
It is safety rated and runs continuously on a separate processor. It monitors all robot movement, either manual jogging, or automatic motion.