You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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:
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
The text was updated successfully, but these errors were encountered: