[Kilian1234]

Hi,

I'm working with an Epson robot. I'm using the the connect to Robot feature with the EpsonDriver.py on RoboDK.

When I initially press Connect I get this error:

Code:

Connecting to robot 192.168.1.5:5000
Unexpected length of status_flags (10, expected 10) or error_code (4, expected 4

When I go into Command and click Reset, the robot shows ready, but if I use any other command I get an error like this 

Code:

Custom command: POWER LOW
Sending command...
Waiting...
Unexpected error: Traceback (most recent call last):
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 34, in <module>
Unexpected error: RunMain()
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 1845, in RunMain
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 1384, in RunDriver
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 1719, in RunCommand
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 1033, in set_low_power
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 590, in execute
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 470, in get_status
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 168, in __init__
Unexpected error: ValueError: Unexpected length of status_flags (10, expected 10) or error_code (4, expected 4"

I'm using the remote ethernet connection in RC5.0+ with the CRLF terminator. I looked inside the EpsonDriver.py file and it have the CRLF labelled as default.

RoboDK is able to ping the controller. When I try "Send program to Robot", it says "No connection could be made because the target machine actively refused it". This program works when I export it and put it directly into the RC5.0+ software.
The reason I'd like to be able to connect directly from RoboDK is that I'd like to be able to program the robot from Python so I can use a Raspberry Pi as a vision system.

I think it may be a driver issue because of all the errors that are thrown. I made the .robot file myself using a step file and the manual, as well as copying the existing Epson G6-651s in the RoboDK library.

If anyone has any experience with these issues I'd appreciate any help. Let me know if there's any more details I can give that would be helpful.

Best wishes,
Kilian


  Epson-G6-451s_Fixed_Base.robot (Size: 690.93 KB / Downloads: 17)

[Albert]

It looks like the robot controller fails to get the status flags or error flags when you connect or set the low power mode.

Can you try connecting to the robot without sending any previous commands?
Are you using the latest version of RoboDK?
Can you share the connection log?

[Kilian1234]

Hi Albert,
I have updated RoboDK from 5.9.2 to 5.9.4 and I am having the same issue.

Code:

Driver for RoboDK 5.9.4.25471
Disconnected
Process stopped
Stopped
Starting robot driver: C:/RoboDK/api/robot/EpsonDriver.py
Using RoboDK RoboDK v5.9.4
Starting...
Using Python version: sys.version_info(major=3, minor=10, micro=10, releaselevel='final', serial=0)
RoboDK Driver: C:/RoboDK/api/robot
Command RESET: Reset errors
Command CJNTALL: Current position
Command POWER HIGH: Set High Power
Command POWER LOW: Set Low Power
RoboDK Driver for Epson robots v2.0.4
Disconnected
Sending command...
Number of axes: 4
Using IP: 192.168.1.5
Using port: 5000
Using password:
Connecting to robot 192.168.1.5:5000
Unexpected length of status_flags (10, expected 10) or error_code (4, expected 4
Custom command: RESET
Sending command...
Working...
Ready

Is this the log you're looking for? When I connect it gives  "Unexpected length of status_flags (10, expected 10) or error_code (4, expected 4". The only command that works is Reset.

If I send a different command I get something like this for each one:

Code:

Custom command: POWER HIGH
Sending command...
Waiting...
Unexpected error: Traceback (most recent call last):
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 34, in <module>
Unexpected error: RunMain()
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 1845, in RunMain
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 1384, in RunDriver
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 1717, in RunCommand
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 1042, in set_high_power
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 590, in execute
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 470, in get_status
Unexpected error: File "C:\RoboDK\api\robot\EpsonDriver.py", line 168, in __init__
Unexpected error: ValueError: Unexpected length of status_flags (10, expected 10) or error_code (4, expected 4

[Albert]

Yes, this is the log I was referring to.

We just updated RoboDK including a new version of the Epson driver to provide better error reporting. For now you should simply see more details about what's going on (more details error flags or status flags).

You can take the latest version of RoboDK for Windows here:
https://robodk.com/download

Could you repeat your test and send us the log? It will allow us to better understand this issue.

[Kilian1234]

This is the new log:

Code:

Driver for RoboDK 5.9.4.25484
Disconnected
Process stopped
Stopped
Starting robot driver: C:/RoboDK/api/robot/EpsonDriver.py
Using RoboDK RoboDK v5.9.4
Starting...
Using Python version: sys.version_info(major=3, minor=10, micro=10, releaselevel='final', serial=0)
RoboDK Driver: C:\RoboDK\api\robot\EpsonDriver.py
Command RESET: Reset errors
Command CJNTALL: Current position
Command POWER HIGH: Set High Power
Command POWER LOW: Set Low Power
RoboDK Driver for Epson robots v2.0.4
Disconnected
Sending command...
Number of axes: 4
Using IP: 192.168.1.5
Using port: 12499
Using password:
Connecting to robot 192.168.1.5:12499
Unexpected status flags (0100000001, expected 10)

[Albert]

Great, this helped. We just published another update again:
https://robodk.com/download

This time it should work. It looks like you had the correct number of status flags. It was raising an exception without a real issue.

Let us know if this solves the issue or not.