I maybe got a clue to what's going on https://forum.pycom.io/topic/4915/gpy-pytrack-modem-won-t-attach-after-firmware-upgrade/7 with responses to print(lte.send_at_cmd("ATI"))
My one working GPY responds SEQUANS Communications VZM20Q UE184.108.40.206d whereas the dead ones reply PYCOM FiPy UE220.127.116.11d God knows how a cereg cmd makes the lte modem think its FiPy?!
I'm having the same problem right now. From what I've figured out so far, there's an interrupt on P#9 which can be configured through the py.setup_int_pin_wake_up(False) method. I haven't gotten it working so far, though. I have also created another topic asking a similar thing.
Alternatively, you can sleep through the machine.deepsleep method and configure any GPIO as wakeup pin for that. YMMV though, as I am experiencing extremely high sleep current with the machine deepsleep.
hi everyone, sorry for the delayed answer.
We're taking steps towards open-sourcing main part of Pymesh (maybe keeping the Pybytes connection as close-source).
The pdf license was a temporary solution, to allow us to make this split, and offer you, our community, to freely build your Pymesh solutions.
I just tried the same process on my side. It worked fine.
I've opened the Pycom firmware updater and pasted the activation token.
Then firmware updater wrote the Pybytes device config to a device and updated the firmware.
Then the device restarted and was connected to Pybytes. The last connection time was updated.
I tried pymakr and I can evaluate expression in REPL
rst:0x1 (POWERON_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
mode:DIO, clock div:1
Initialized watchdog for WiFi and LTE connection with timeout 1260000 ms
WiFi connection established
Pybytes connected successfully (using the built-in pybytes library)
Pybytes configuration read from /flash/pybytes_config.json
Pycom MicroPython 1.20.1.r2 [v1.11-06dfad0] on 2019-11-30; FiPy with ESP32
Pybytes Version: 1.3.0
Type "help()" for more information.
It's strange that it is not working for you.
Can you to change the Wifi network in your device profile and then try to provision it again?
Also, enable debugging, maybe you spot something there
import pycom; pycom.nvs_set('pybytes_debug', 6)
You can also try to completely erase a device with erase_all command
Beware that after doing erase_all device will not boot up properly until you the flash firmware (doing the firmware update with firmware updater)
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