Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
nestcodehouse opened this issue Mar 2, 2017 · 11 comments

Comments

@nestcodehouse
Copy link

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
Copy link
Owner

fogleman commented Mar 2, 2017

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

@nestcodehouse
Copy link
Author

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
Copy link
Owner

fogleman commented Mar 3, 2017

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

@oskay
Copy link

oskay commented Mar 4, 2017

Outdated firmware?

@oskay
Copy link

oskay commented Mar 4, 2017

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
Copy link
Author

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

@fogleman
Copy link
Owner

fogleman commented Mar 4, 2017

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

@nestcodehouse
Copy link
Author

No , I am using the firmware it came with

@fogleman
Copy link
Owner

fogleman commented Mar 4, 2017

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

@oskay
Copy link

oskay commented Mar 5, 2017

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

@jvolker
Copy link

jvolker commented Jul 2, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants