axi icon indicating copy to clipboard operation
axi copied to clipboard

ValueError: invalid literal for int() with base 10: "!8 Err: Unknown command 'QS:5153'"

Open nestcodehouse opened this issue 8 years ago • 11 comments

axi goto 10 10 Traceback (most recent call last): File "/usr/local/bin/axi", line 9, in load_entry_point('axi==0.1', 'console_scripts', 'axi')() File "/Users/jojiabraham/code/axi/axi/main.py", line 34, in main device.goto(x, y) File "/Users/jojiabraham/code/axi/axi/device.py", line 97, in goto px, py = self.read_position() File "/Users/jojiabraham/code/axi/axi/device.py", line 124, in read_position a, b = map(int, response.split(',')) ValueError: invalid literal for int() with base 10: "!8 Err: Unknown command 'QS:5153'"

nestcodehouse avatar Mar 02 '17 01:03 nestcodehouse

Is this AxiDraw v3? Have you gotten any commands to work?

fogleman avatar Mar 02 '17 02:03 fogleman

Yes , it is AxiDraw3 , only when I issued "axi on" I heard some noise from the AxiDraw , Any command that involves movement failing with this error

nestcodehouse avatar Mar 03 '17 07:03 nestcodehouse

@oskay any ideas? My code only sends QS but this error says !8 Err: Unknown command 'QS:5153'

fogleman avatar Mar 03 '17 15:03 fogleman

Outdated firmware?

oskay avatar Mar 04 '17 04:03 oskay

The QS command was only added in 2.4.3 (very recent) and isn't used in any of the software that we're publishing.

oskay avatar Mar 04 '17 04:03 oskay

so is it recommended to update the firmware to fix this issue or remove the usage of QS from the axi python module ?

nestcodehouse avatar Mar 04 '17 21:03 nestcodehouse

@oskay Did any AxiDraw v3's ship with older firmware? @nestcodehouse Did you change the firmware on your device?

fogleman avatar Mar 04 '17 23:03 fogleman

No , I am using the firmware it came with

nestcodehouse avatar Mar 04 '17 23:03 nestcodehouse

I'm suspicious of the ":5153" part, but I have no idea where that would be coming from.

fogleman avatar Mar 04 '17 23:03 fogleman

Try running the firmware update, and see if that helps.

oskay avatar Mar 05 '17 00:03 oskay

I had the same issue using an Axidraw V2. Updating the firmware fixed it for me.

jvolker avatar Jul 02 '20 14:07 jvolker