Created Date: December 22,2019

Created by: Gizmobreaker

Hi PLC Geniuses,

I am using a BRX BX-DM1E-36ED13. I have 3 servo motors connected to the hi-speed outputs which run Horizontal, Vertical, and Rotation axes. I configured them using 3 AXCONFIGs and I can jog them using 3 AXJOGs. I need to run sequential operations so I am attempting to use AXSCRIPT. For testing, I am running several commands in 1 AXSCRIPT for just the Horizontal motor and then I run several more commands in another AXSCRIPT for just the Vertical motor. Here's the question: When I run the program in the PLC, I can monitor the motor positions on screen and work through the entire program. However, if I use the simulator, the only thing that happens is that the 1st AXSCRIPT turns on the error bit as soon as it is enabled. As soon as I switch from Term to Run, the ERR messge is "Unable to access module in AXCONFIG @00000097 ". Then, if I trigger the script, the ERR changes to "Unable to access module in AXSCRIPT @0000013E ".

Am I doing something wrong? Is this normal? I don't think that the PLC can detect the motors so that is not the issue.

Thanks, everyone, for taking a look at this. I appreciate the interest and any help I can get!

Created Date: December 22,2019

Created by: Gizmobreaker

I should add that there is a Warning flag. When I open the dialog, there is 1 Warning Message and 3 Last Errors. The Message is "Device Driver Error - $DriverError(ST143) " and the Errors are all "Unable to access module in AXCONFIG @00000097 (AXCONFIG at $Main@52) ", "Unable to access module in AXCONFIG @00000097 (AXCONFIG at $Main@34) ", and "Unable to access module in AXCONFIG @00000097 (AXCONFIG at $Main@15) ". Those addresses fall in the AXCONFIGs for the 3 motors, in $Main.

Created Date: December 22,2019

Created by: Gizmobreaker

BobO, I don’t think that I have a module configured and one does not appear in the PLC image. How can I tell if I configured one if I cannot see it?

Tinker, that might be right, though a bit of a disappointment. If it does not simulate the HSIO, does that mean that it will not step through the AXSCRIPT, either? Since I use the Success bit, if the script does not parse, that bit won't ever get set.

Created Date: December 22,2019

Created by: Gizmobreaker

Yes, I am using a hardware BRX BX-DM1E-36ED13. The program works on that. However, it will soon be installed in the real world and I would like to be able to work on the logic when I do not have access to the hardware PLC. That's why I am asking about the Simulator.

In terms of the "yes, I did it " response, that is not what I am seeing. The first time I enable the AXSCRIPT in Simulator, it sets the ERR bit and turn on the yellow warning flag at the bottom of the window. That pretty much halts operation as I cannot step through the commands in the AXSCRIPT and, therefore, cannot get a Success bit turned on. Maybe this is just not possible? Do you know if these kinds of exceptions are documented, anywhere?

Created Date: December 23,2019

Created by: BobO

Yes, I am using a hardware BRX BX-DM1E-36ED13. The program works on that. However, it will soon be installed in the real world and I would like to be able to work on the logic when I do not have access to the hardware PLC. That's why I am asking about the Simulator.

In terms of the "yes, I did it " response, that is not what I am seeing. The first time I enable the AXSCRIPT in Simulator, it sets the ERR bit and turn on the yellow warning flag at the bottom of the window. That pretty much halts operation as I cannot step through the commands in the AXSCRIPT and, therefore, cannot get a Success bit turned on. Maybe this is just not possible? Do you know if these kinds of exceptions are documented, anywhere?

Sorry, I misunderstood.

The simulator is a full implementation of the PLC engine, minus the specialized hardware required for HSIO, motion, and interrupts. In general, our way of handling stuff the simulator doesn’t support is to just claim it did it. AXSCRIPT is a bit more specialized because half of what it does is handled by the PLC and half by a special coprocessor. The copro isn’t there, and the PLC is fussing about not being able to talk to it. It could probably be handled cleaner.