GPIO Offline Task - Not resetting properly

Hey,

having xArm5 and the corresponding AC Control Box.
Robot Model: xArm5
Robot SN XF130308B22B05
Firmware: 2.3.0
Studio: 2.3.0
Control Box SN: AC130303A3009C

We are launching multiple BLockly Tasks via Modbus TCP. Works fine as intended.

For Identification we have one Output set to Blockly Offline Task Running (in our Case CO5). This is read via the SPS, if the Blockly task is still running, despite having Wait commands inside the Blockly.

Sometimes this Output gets stuck, when the Blockly Task ends. The COBOT sends Normal, no motion and no error. But the Output is still set. The Output gets reset, when we push the STOP Button on the Web Page.

This might not be the intended behaviour, and i cannot find any systematic issue, since this only happens from time to time. Also on different Blockly Programs…

We “could” change from the fixed Output Setting to user-defined GPIO Command in each Blockly Program, but this is much work to do… Since we have 40+ Programs and multiple if-statements ect.

Do you have any advice, why this happens so random?

Hi Sir,

Do you mean the CO5 will keep at a high level even when the offline task is finished? At that time, can you switch it to a low level via ‘Settings-Externals-Controller IO-IO State’?

I think you enable the option in ‘Settings-General-Advanced Settings-Clear IO output when the robot is stopped’, this way the IO will be reset when you push [STOP] button.

When the output gets stuck in high level, please enter into the Blockly module, and see if you can run any Blockly project normally. What does the icon below look like at that time?

If you can provide the Blockly offline task project for our test, that would be great, please send it to support@ufactory.cc.

Best regards,
Minna

Hey,

Yes, the CO5 stays on High level. I cannot change the Setting manually through the Externals Interface (on this Screenshot, everything is fine)
:

The Setting is not activated:

I will create some Screen Dumps the next time this happens. And which Blockly Program was ran right before that. I will try to run a different, simple Blockly Program through the Modbus TCP interface and through the Blockly Website.

I will answer to this Topic, when i have further Information.

Hi Sir,

Thanks, wait for your further feedback.
Please provide specific steps for us to reproduce the problem.

Best regards,
Minna

Hey,

the error just happened again, but this time it stops within a blockly task without doing whats intended.

This has been launched. Name: 2002

20204_07_01_COBOT Stop Error.py (14.1 KB)

This Program does the following:

  • Move to defined Position (344 | 8.5 | 150)
  • Activate Vacuum Gripper
  • Register Event for Move Command
  • Move in Z-, slowly
  • Event Trigger: When something has been picked up, stop the Z- move command, move up
  • Timeout: Move up, Write Information to Modbus TCP Register 256 && 257
  • Move to defined Postion (either HOME or continue with next Step)

Hi Sir,

Would you please share the Blockly project to support@ufactory.cc?
Not quite understand, What is the expected behavior?
I didn’t see any code in your py script to set CO5.

Best regards,
Minna

Hey,

i am getting Email Notification as undeliverable… So i cannot send you an e-mail with the files.
We have configured the IO Function the following:

Hi Sir,

Please upload the file to the Google below.
temp - Google ドライブ

Best regards,
Minna