Running 1.20.1r1 I am impressed of the boot performance.
But in combination with a pytrack there are a lot of i2c errors. I am not amused to figure out new timings which may result in less errors, but will never remove them all.
Additionally I run now into i2c that can only be resolved by cutting the power suply. Would be great, if the PIC has a watchpig function. So I can track down with less efford, if this is caused by the LoPy or the Pytrack.
@JeanJean Hi, can you send us the whole output you got from Pymakr (when device boots up and send a signal), please?
It's possible that your device got disconnected from Pybytes, but then if you restart your device, won't that work?
I'm trying to figure out how to abandon a function call after 5s if the function hasn't returned a value by then.
import _thread, time
def _function(this, that):
print('waiting for _function'); time.sleep(9); print("don't want to see this message")
_thread.start_new_thread(_function, (1, 2))
Running C:\Users\Kris\Google Drive\My Documents\Pycom\main\test.py
waiting for _function
Pycom MicroPython 1.18.1.r7 [v1.8.6-849-d1c5ea9] on 2018-12-17; GPy with ESP32
Type "help()" for more information.
>>> don't want to see this message
isn't forcing the function to exit after 5s. Can someone show me how to achieve this?
I'm using this library at the moment, I can attach and connect to the network, but my efforts fail when I want to do some actual calls to servers. I don't seem to have http-traffic:
@thinginnovations You should expect that the LoPy4 firmware will only work on the L04 module (SX1276 chip) and the LoPy1 firmware will work on the L01 module, making however use of the larger RAM and flash. Similar to the WiPy firmware which works on both WiPy2 and WiPy3.
For a client, I'm looking for a senior Micropython/embedded developer (freelance/contractor) that preferrably has experience with Pycom modules. I have been working as developer for the client myself, but they need extra help.
You will be working on the software for a new iteration of the (Pycom-based) device that the company is developing. You will be working most of the time on the Micropython code that runs on the devices. You will also need to be comfortable with embedded C in order to analyze and fix problems in the Pycom firmware when they arise and extend the firmware in case a feature cannot be implemented in Micropython.
You can work remotely, but occassional visits to the company headquarters in Noord-Brabant are desired.
Developer Experience Profile
Embedded C + GNU command line toolchain (gcc, gdb, binutils)
Inter-IC Protocol knowledge: I2C, SPI, 1Wire, etc.
Analyzing/Debugging hardware issues using a logic analyzer
Development of device drivers and other low-level code (both in Micropython as well as C)
Unit testing (esp. Python) is a plus
TypeScript & React experience is a big plus, but not a must
Bluetooth experience is a plus, but not a must
The company is active in the smart building and real-estate space. It has many Pycom-based products deployed in a number of large buildings in The Netherlands. The team working on the products and services is very small so you will have a lot of influence on the product. The company is based in Noord-Brabant, The Netherlands, easily accesible by car or public transit.
Please contact me at:
post AT martijnthe DOT nl