Closed Addy771 closed 4 years ago
@Addy771 Thanks for opening an issue. Could you make a PR with your fix? That way I can share it with other users.
Thanks! -Liam
I tried to, but I think I can't, due to the way that I pulled and merged pyvesc.
Here's the commit where I made this fix: https://github.com/Addy771/VESC-logger/commit/c103f6eb220ea13cee3a49bc7514d0afa06ecafc
Maybe you could just make the change and reference this issue.
Sounds good, I can add this.
Background:
When I try to encode a GetValues request, I get an exception:
I was able to avoid this error by modifying VESCMessage in protocol\base.py. I added this line to the VESCMessage constructor:
cls.can_id = None
With that change, pyvesc is working and I get correct data with GetValues.