Ta. Fair comment. Shouldn't be needed but I'll try it.
In the post on the new version of firmware it was suggested that the Python code does not send the proper lead in code to address a memory chip. It is just generic code which is guaranteed to fail.
The 24LC512's I use demand an A1 or A0 for read or write then the address then the data.
I read all the PyCom/Python doc I could find and assumed it was the same as Arduino Wire library which works.
A poster showed me a command variation that allows "stop" to be conditional which would allow exaclty what I need to create the correct addressing.
I'll try that tomorrow - gotta leave for the day.
Thanks for the comments and taking an interest. I've used I2C memory chips for last 18 years and quite like them. We've found them to be very robust and reliable and low current though capacity is low by modern standards and somewhat slow.
Ah... I think my machine.SOFT_RESET might have had something to do with it. When I hit the reset button on the unit it reloaded and reconnected to my wifi correctly I believe, because I started ntp_sync()ing correctly. Thanks.
I use a WiPy 2. I use Atom on windows. Various firmware revisions in the WiPy.
I found that simple code examples for scanning BLE advertisements crashed after a few minutes to a few hours. Fiddling with gc made a difference, not always good, but did not fix it. The thing locks up.
The cure I found was to scan for 10 seconds. Then when it stops scanning, you can detect that, de-init the module then start it scanning again. That worked very well for 6+ days.
Yours is a different module and a different application etc... worth a try. Stop the BLE then restart it. Just a guess. Hope it works.
If you have an expansion board I really suggest using it.
I've not been able to use the Pytrack with the firmware update utility, for one because it's not easy to ground P2 pin to put the board into update mode but also the serial drivers seems to lack something needed by the update tool.
@daniel I think the 2.8uA of video is due to a little part of current drawn from pullup resistor of serial connection instead from the power supply. Without serial connection I think the current rise up 6uA (5uA for ESP32, like in Espressif documentation, and 1uA for LoRa module in sleep mode). what do you think about it?
@Emmanuel-Goudot Yes, the interrupts are currently connected to the onboard PIC of the Pytrack, which makes it a bit more difficult to manage regarding simply connecting the accelerometer to the ESP32 interrupts. We're working on this and will let you know when it's ready!
Thank you for the hint.
In fact we work with pymodbus, or I should say we use it. I'm not very deep in Modbus and new to Micropython, this is why I currently do not want to go into it deeper. But there are quite a few devices that talk modbus.
What I meant is, I haven't planned to cover Poland as a specific country. I will cover it under the various Mobile Networks Operators. At the moment I don't have much specific to go by other than I know Deutsche Telecom is rolling NB-IoT out in cites across Poland through 2017. I am trying to understand via our contacts what Orange is doing specifically in Poland and will come back to you as soon as I have the information.