We have now discovered that even sending the "AT+CFUN=4" does not solve the problem. Yesterday we had a GPy stuck in a mode where it would not return the ICCID even after power on/off, modem reset command, and the AT+CFUN=4 command. The only thing that resolved the issue was to send a dummy attach command lte.attach(apn='unknown'). Then the lte.iccid() command worked from that point forward (even through power on/off and resets). We do not know what causes the GPy to get in this crazy mode; however, it seems to be related to low signal situations.
Another issue with Pymakr was discovered yesterday. If you install Visual Studio Code on a newly installed Windows 10 and add the Pymakr extension, it will not communicate with the GPy until Node is also installed on the computer.
@mylescai the nanogateway opens a socket connection to the TTN server. So you just have to attach and connect the LTE link, and the go on with connecting to TTN.
Edit: To be more specific. In nanogateway.py, function start(), at about line 140 the wifi is set up. At that place you can instead set up the LTE connection.
Hi @hiyasbie, I'm having the same issue on my MacBook Air. Were you able to update your firmware using your MacBook Pro or was your workaround solution just use your friend's laptop w/Window's to update your expansion board?
@Jordan-Reyes Technically speaking Fipy (Fi as five perhaps...) is a 5G module. LTE-M and NB-IOT are inside 5G scope network. But if you have in minds higher data bandwith we must be wait some years i guess.
I wanna pick up where this thread from a year ago left off since it seems similar:
We have a +25% failure rate on making our prototypes, and it seems that the OEM module gets damaged.
Upon powering up everything seems normal, but the OEM module get really hot in a few minutes. It seems to be the bottom right portion of the L04 that we used now.
And on programming the Flash memory seems to be unresponsive. See programmer screenshot with a test program below:
The oven reflow profile has been measured and seems to match the profile of the OEM.
This is the OEM's profile:
with alpha OM-338 paste.
Did you manage to help @Tom with this issue or did you have other issues like this? Any help is greatly appreciated!
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