L76GNSV5 Library OSError: I2C bus error
Well, I am using the L76GNSV5 library and I am having some troubles. When I try to upload it, it appears the same error:
File "main.py", line 14, in <module> File "/flash/lib/L76GNSV5.py", line 38, in __init__ OSError: I2C bus error
Sometimes it lets me upload it (maybe 1 each 20), and as you can understand, it is a terrible situation if I am constantly changing the code. I also tried with the V4 version and nothing. Also have the latest firmware both Lopy and Pytrack.
Hope you can help me! Thanks!
Don't care about power right now. I like to see version chaos for the pytrack as well. Why do they only improve the expansion board and don't place a better antenna and a plug on the pytrack? And a battery plug which is more common in my area?
Version chaos now!
And a wiki in which user can keep the documentation/examples in snyc with the firmware. Yes, it is a risk, but Pycom seems to small for keeping the documentation actual - and the forum is not the best place for user collected best practice and workarounds.
@robert-hh what a great thing... So cool to use with battery
robert-hh last edited by
The thing is that with 1.20.1 firmware, the board consumes 120 mA
Because is starts all the PyBytes stuff in the background. <irony> You should be lucky to have all these unwanted services around. They keep your device busy and power-hungry. </irony>.
@crumble Thanks. The thing is that with 1.20.1 firmware, the board consumes 120 mA when it should consume 40 mA, don't kmow why.
Use the latest firmware, IDF 3.2 fixed a lot of I2C/timing issues.
If the GPS fails on init: reset it. You can use deepsleep method of the pytrack to switch of the power supply for a second.
Someone got something? Still having the problem
ferfersan6 last edited by ferfersan6
@oligauc I am using USB just to upload the program and then a battery to operate.
oligauc last edited by
@ferfersan6 Are you using the USB or battery to power the device ?
Latest version show up a lot of I2C errors in your combination. Try to delay the first I2C call. Use the watchdog. You will see the I2C quite often.