@mms117 There are also libraries available. Some are probably able to use other GPS modules with very little changes to the code, as long as you stick to standard NMEA format (as opposed to brand-specific formats).

@robert-hh Thanks for the info. Always rescued it via software. Will test it with machine Deepsleep

I agree with @jcaron that it's not usually appropriate to write directly to a remote database from an IoT sensor. Most instead use a protocol such as MQTT to communicate, as it was designed for this type of application. You can use an MQTT broker (such as Mosquitto) to receive messages and write them to your mysql database.

@robert-hh Ok. I will do it. Thanks.

Hi @robert-hh , Both Lopy and Fipy have firmware release='1.18.2.r1'

@stanschultz Also very useful: https://github.com/zsquareplusc/mpy-repl-tool

@changeddaily said in Wipy3 Low power modes: rwble.c Sorry, I cannto find the file either. It is only referenced in the libraries.

@alexpul said in Turn GPS back on after pytrack.go_to_sleep(gps=False): I am using pytrack.go_to_sleep(gps=False) in the lib/pycoproc.py define your own funcion: def gps_state(self, gps=True): # enable or disable back-up power to the GPS receiver if gps: self.set_bits_in_memory(PORTC_ADDR, 1 << 7) else: self.mask_bits_in_memory(PORTC_ADDR, ~(1 << 7)) easiest way is for you to search for "def go_to_sleep(self, gps=True)" in the file, and place your custom function above or below it :-) ... and then you can execute it (Turn on): pytrack.gps_state() and (Turn off): pytrack.gps_state(gps=False) good luck 👍🏻

Update: It seems I am getting the crashes only when I have my pysense/wipy connected via USB. I have around 12-15 units running in various setups; those running standalone (battery connection only) seem to do fine, those with USB fail regularly.

While the official MicroPython has "wlan.status('rssi')" to to retrieve the RSSI of the AP signal (when you are in STA mode connect to the AP), Pycom firmware >= 1.20.0.rc0](https://forum.pycom.io/topic/4099/new-firmware-release-candidate-v1-20-0) has a new function : wlan.joined_ap_info() Returns a tuple with (bssid, ssid, primary channel, rssi, Authorization method, wifi standard used) of the connected AP in case of STA mode. Tested it with firmware 1.20.0.rc4 on LoPy4 and it works. So no need to call 'wlan.scan()' when there is already a connection to an access point. Also note that the same firmware 1.20.0.rc0 brings new features (for example, to filter by ssid or bssid) to 'wlan.scan' : wlan.scan([ssid=NULL, bssid=NULL, channel=0, show_hidden=False, type=WLAN.SCAN_ACTIVE, scantime=120ms])"

I confirm that wlan.antenna(WLAN.EXT_ANT) works with Pycom firmware > 1.18.1.r1.

@rafaelsolano So is 192.168.1.1 the IP address of your router? I'm askign because that is a typical router address. The, you could follw the example from the documentation https://docs.pycom.io/tutorials/all/wlan.html, under the heading "Connecting to a Router".

We dont have anything official for this at the moment.

@alvaroav Hey glad its working. I've raised it in the team so hopefully the fixes will get ported into the next pybytes firmware release.

@crumble Pictures of the larp kit please :P Ill dig mine out in return ^_^ @arthurlutz Thats super cool. good work.

@brossingo FWIW, I managed to get such a display running with the development release firmware (version 1.20rc4) in combination with the write_data() change that robert-hh mentioned. This newer release is required in order to be able to make use the framebuf class. Here's a post with my notes: https://forum.pycom.io/post/24819