fogleman / axi

Library for working with the AxiDraw v3 pen plotter.
MIT License
274 stars 42 forks source link

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

Open nestcodehouse opened 7 years ago

nestcodehouse commented 7 years ago

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'"

fogleman commented 7 years ago

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

nestcodehouse commented 7 years ago

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

fogleman commented 7 years ago

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

oskay commented 7 years ago

Outdated firmware?

oskay commented 7 years ago

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.

nestcodehouse commented 7 years ago

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

fogleman commented 7 years ago

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

nestcodehouse commented 7 years ago

No , I am using the firmware it came with

fogleman commented 7 years ago

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

oskay commented 7 years ago

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

jvolker commented 4 years ago

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