@tttadam said in LTE init error: lte = LTE(debug=True) Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: extra keyword arguments given Concerning this error, please update to the latest stable firmware (1.20.2.r4) as the 'debug' keyword is not supported in the version you're using. Let me know if it happens again, generally the issue is solved by either machine.reset() or a power cycle

How to compile .py @micropython.native code into .mpy?. .

@Akshay-Khushu You can use every SIM card provider offering either NB-IOT or LTE-M. Just go for the one offering a good service in your region.

@D-S are you using pymongo on micropython?

Just an update, this project got parked for a while, but have tried it this morning and your code did work. Appreciate the assistance!

@jcaron Search for "Lacuna space" and "TinyGS"

Some further info on this. I have dumped the NMEA messages from the GPS to a file and I can see that the pytrack isn't picking up any satellites. I have tried with antenna jumper on/off, external and internal antenna, same result. Could the shield be defective? $GPVTG,0.00,T,,M,0.00,N,0.00,K,N*32 $GPGGA,004345.864,,,,,0,0,,,M,,M,,*44 $GPGSA,A,1,,,,,,,,,,,,,,,,1*03 $GPGSA,A,1,,,,,,,,,,,,,,,,2*00 $GPGSV,1,1,00,0*65 $GLGSV,1,1,00,1*78 $GPGLL,,,,,004345.864,V,N*76$GPRMC,004346.864,V,,,,,0.00,0.00,060180,,,N,V*37 $GPVTG,0.00,T,,M,0.00,N,0.00,K,N*32 $GPGSA,A,1,,,,,,,,,,,,,,,,1*03,M,,*47 $GPGSV,1,1,00,0*65,,,,,,,,2*00 $GLGSV,1,1,00,1*78 $GPGLL,,,,,004346.864,V,N*75

@Gijs I think it should be here: https://pycom.io/webshop-2/services/cellular-services/faq-for-vodafone-pycoms-nb-iot-services/ or maybe somewhere around here: https://docs.pycom.io/tutorials/networks/lte/ I believe it's also important to highlight that the modem firmware may need to be updated and modified to the NB-IoT version, since I took some to realise that as well... my FiPys come with the LTE-M version installed.

@Alex-Dew note that the L76-L only supports GPS and Glonass, not Galileo.

@Lokefar Can you post the final working code for this sensor with lopy 4?

Thanks for the help again. I disabled pybytes on boot and downgraded to the current stable firmware. It's running now.

Hi @SciWax , thanks for your help! When I started working on this project, I checked the map and saw that the only LTE-M provider was Orange. However, after contacting different providers they told me that the map was out of date and other companies (for example Telefonica) are now offering coverage too. In my particular case, I finally choose a global SIM provider who is working with Telefonica in Spain, but I'm unable to connect to a suitable cell. I'm running the tests in Vitoria-Gasteiz, a city in the north of Spain, so I should have good signal. Anyway, I couldn't get any official map from the provider to confirm that. After this experience, I wanted to know if any user have got a successful LTE-M connection in Spain and use the information to buy a new SIM card. Naroa

I'm at a dead end with this. As mentioned earlier I am required to stick to only an older firmware, but that has a WLAN() bug. I detail the issue more here: https://forum.pycom.io/topic/7029/anyone-using-google-cloud-not-on-pybytes?_=1620435408202 Thanks for attempting to help!

Hey @panda are you still out there? What firmware version did you test this on? I can't get any other Google IoT libraries to work due to various firmware bugs and want to try your implementation.

Looking at the infographic here: https://github.com/tetrodoxin/chirpstack-ns, and reading about the purpose of the Chirpstack Network Server The responsibility of the Network Server component is the de-duplication of received LoRaWAN frames by the LoRa® gateways and for the collected frames handle the: Authentication LoRaWAN mac-layer (and mac-commands) Communication with the ChirpStack Application Server Scheduling of downlink frames Im not sure if its actually possible, as the Gateways are supposed to connect to the Application server, which in turn communicates the LoRaWAN packets with the Network server. Though Im no expert in the whole Chirpstack and maybe there's a work around

@jcaron Yes, i know that many infos are lost then. But i have suppoesd that there is currently a way from python code but only i miss it ;-) here is good overview of modes: https://lastminuteengineers.com/esp32-sleep-modes-power-consumption/ and this one about what to modify to take hibernation https://esp32.com/viewtopic.php?t=3083

For more resolution, there is the ADS1220, a 24 bits ADC using SPI, 4 channels, 2 ksamples/s, gain 1-128 : https://www.ti.com/product/ADS1220 It is easy to buy break-out boards with ADS1220, e. g. : https://www.aliexpress.com/premium/ads1220.html https://www.tindie.com/products/whitchurch/ads1220-24-bit-4-channel-low-noise-breakout-board/

There's several ways of collaborating currently available, but Im not aware of your level of remoteness If your teammate is not in the same location / building, you can work on the same code in for example a GitHub repository, and one of you has to push it to the device. If both of you have access to the same Pybytes account with the device attached, you should be able to use the remote project upload as well, though note it is still in beta and not all features (like collaboration) are fully operational yet. Moreover, it might be hard to figure out who uploaded which version of the code last, and what is running on the device, making testing somewhat harder. If you are both in the same room / connected to the same network, you can approach the device through a Telnet or FTP connection to upload code, using Pymakr or an FTP client respectively: https://docs.pycom.io/gettingstarted/programming/ftp/. An issue in any scenario might be testing code that breaks the WiFi connection, which in turn also closes the Pybytes / Telnet / FTP connection