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

Can write to gauges but not text #1

Open
VegaDeftwing opened this issue Jun 19, 2019 · 2 comments
Open

Can write to gauges but not text #1

VegaDeftwing opened this issue Jun 19, 2019 · 2 comments

Comments

@VegaDeftwing
Copy link

VegaDeftwing commented Jun 19, 2019

Running selftest.py The gauges all move and everything is fine and dandy, but I can't seem to write text, instead I get a bunch of:

...
Error I2C Write block: [Errno 121] Remote I/O error. Register:0x74 command: 0xf3 data:0x7
Error I2C Write byte: [Errno 121] Remote I/O error. Register:0x74 data:0x90
Error I2C Write byte: [Errno 121] Remote I/O error. Register:0x74 data:0xaf
Error I2C Write byte: [Errno 121] Remote I/O error. Register:0x74 data:0x40
Error I2C Write byte: [Errno 121] Remote I/O error. Register:0x7c data:0xe2
...
Warning Try to write some text 3 times without success

any ideas?

Currently my best guess is the addresses for registerDialControl/Data are incorrect on my nimbus, I could try brute forcing them, but thought I'd see if you have a more elegant solution

@VegaDeftwing
Copy link
Author

Update: I tried brute forcing, no dice.

@VegaDeftwing
Copy link
Author

Looking at http://blog.arcnor.com/quirky-nimbus-hacking-part-2/ and in mynimbus.py nimbus_init() I finally noticed that it mentions wifi needs to be on, implying the original Imp needs to be in place and in working order. As that isn't the case for me it's clear that is the cause. I'm only updating this issue with progress in case anyone else ever stumbles upon this repo. At least as of now it appears that either a new special sequence would need to be sent to the PIC on the daughter board or that there's an enable pin that gets brought high/low when wifi is on, which is very possible given the number of pins on the ribbon cable implies a lot more than just bi-directional communication and power (even with multiple voltages). As my IMP was destroyed in removal I'm unable to take a logic analyzer to it and there is a strong chance any further attempts to find a solution would either damage the pi or result in the complete destruction of the Nimbus and I don't think it's worth it to bypass the main board as it would necessitate a new power supply and much, much more work.

Thank you so much for this repo Nechry, and to any other who wind up here I wish you the best of luck.

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

1 participant