@btaillandier The tarball is at https://github.com/robert-hh/Shared-Stuff.git. It's name is: LoPy4-1.20.2.rc11_invert.tar.gz You call the inversion with e.g. from machine import UART uart=UART(1, 1200, invert=UART.INV_RX) there is also UART.INV_TX, UART.INV_CTS and UART.INV_RTS, to be or'ed if required.

I think its a very interesting idea! Ive suggested a feature to the FW team to make pycom.rgbled() return the current value of the led if no color value is given, such that you can reset the color after each function call. Now to make this a good library, I would suggest a nonblocking function that handles the setting of the led, and creates a timer of sort to reset the led at the end, to not keep the main program busy.

The most common issue here is using a USB charging cable that does not support a communication link. Make sure you have a USB cable with all conductors present :-) Next to that you can check the device manager to see if the COM port is created correctly, sometimes (rarely) Windows will have driver issues where the board gets assigned the wrong driver. Let me know! Gijs

Yes, sorry, my mistake! Ill fix it, thanks! Gijs

Ok Thank you. Richard.

@ric2498 said in Pygate and Fake GPS: "fake_gps": true, "ref_latitude": xx.xx, "ref_longitude": yy.yy, "ref_altitude": z This works! You have to add it inside the "gateway_conf" object. The gateway will print the following: [535347552] lorapf: INFO_ [main] Reference latitude is configured to 5.000000 deg [535347560] lorapf: INFO_ [main] Reference longitude is configured to 4.000000 deg [535347567] lorapf: INFO_ [main] Reference altitude is configured to 2 meters [535347574] lorapf: INFO_ [main] fake GPS is enabled

@ProfFalken I have a Pygate + LoPy4 sucessfully talking to Chirpstack server over WiFi. Have you been able to resolve this? Maybe I can help.

@peterp Thank you, Peter :)

The best way to calibrate a magnetic compass is outside. As concrete and metal objects will affect the magnetic field orientation, and thus the sensor output. Also, keep the sensor level, as rotation around other axes will require additional calibrations (you could use the accelerometer in the device to account for this ). i believe there are many examples on the internet using this or similar sensors :) Gijs

@wituwitu According to the answer from @lmo, you can only set the characteristic once you actually have a client connected. You'll get an error if you try to set it when there's no client.

I believe this has to do with OTA versioning.. The OTA server will create a manifest for which version the device has to update to a new one. If you delete the current OTA version folder in the servers' file structure, the manifest will (Should) upload all files from the new version. You can check this yourself by asking for the manifest described in this section: https://docs.pycom.io/updatefirmware/ota/#how-to-use. If you enter a non-exisiting current version, it should only display 'new' files.. Im not a big fan of the current OTA updating system as its confusing and not really user friendly in my experience, Please do let us know what you would like to see improved! Best, Gijs

@randomrnti Just curious, which NB-IoT network would be that? Is it via PyCom Vodafone NB-IoT sim? or you have setup a MQTT Server on a dedicated server and made that server reachable from Vodafone NB-IoT SIM?

Hi @Gijs, Fixed! I have now started getting GPS fixes! Thanks so much for your help! One last thing - I am interested in getting cold fixes to measure the time difference between cold fixes and warm fixes. I'm not sure if you're familiar with writing to the L76 chip, but I'm trying to use L76GNSS.write() and the relevant NMEA message to get the chip to perform a full cold restart where it has no information on the last location whatsoever. Does this command look correct? It doesn't throw up an error, but the L76 is fixing immediately afterwards so I know it isn't performing a full cold fix. [image: 1597160030340-screenshot-2020-08-11-at-16.33.48.png] Otherwise, do you know of another way to perform a full cold restart on command? Regards WilkinsSq

@kiltedpython There is also size_check.sh, application.mk. You have to create board subdirectories and change the respective partition map files to get actually space for larger images. For WiPy3, you can use e.g. LoPy4 as template.

Many thanks to @jcaron and @robert-hh, it now works. I found I had to specify the terminator as a byte string (a variation I had tried before but always got a type error, as robert-hh noted), but I had never tried making the command string a bytes field as well, in fact I didn't know that was possible. If I'm totally honest I was only vaguely aware that there is a difference between byte strings and strings. I had to Google it, and I'm still not sure I entirely get it, but moot point right now. Anyway, thanks again. ;-)

@jcaron you are right, thanks.

@robert-hh with uart.readline() you have to be sure, that the receive buffer is sufficiently large. You can increase that when creating the UART object with the parameter rx_buffer_size=nnn. Since the sample JSON object of your post is 352 bytes, you could try to use a buffer size of 1024 or even larger, which will cope with delays during forwarding the content. Edit: The default size is 512.

It can happen to the best of us! I missed the ssl line in your example as well when typing it over. Great to hear it got solved