When the GPy is on the total consumption is stable to 300mA (I use only the WiFi at the moment, the LTE module not yet). The other electronic parts are low power, can not absorb peaks of 300mA. Now I'am update the GPy firmware and then I'am updating the LTE modem firmware.

That would be nice. Hopefully it solves many of the little issues that I have seen with the current chip.

@John-Baird Interesting observations/experience with IOT in Aus. I have been working with Vodafone and have found them very supportive.

@kjm Obviously yes.

@PeterB Ah, there is the difference. Due to the low power requirements of our device we only use deepsleep(), hence the flush was enough for us. Glad you're on the right path now.

I ended up using Atom on my windows pc and was able to talk on the port no problem. I'm not sure why the port was closed on the fedora pc. Hopefully this helps someone in their setup.

...and I figured it out. I had a try...finally block that had machine.reset() in the finally block. Removing the try...finally restored the trackback output.

Found my problem. I had commented the single line in a while statement, like so: while True: #someFunction()

@SiMoS-IoT I improved the way the GPys were handling network failures and ended up implementing a function that manages delays between retries. So if the device can't connect it keeps waiting longer and longer to save power... Delays between attempts : {1,1,1,2,2,2,4,8,16,32} in minutes. You get the idea. Unfortunately I had to ditch all pycom boards for now and find an alternative solution. We faced major issues about 9 months ago, and did not get a prompt reply/support. See this thread: https://forum.pycom.io/topic/3390/potential-device-lockdown-network-providers/37 The Sequans modem is (STILL) not supported by Telstra : https://www.telstra.com.au/content/dam/tcom/business-enterprise/machine-to-machine/pdf/telstra-m2m-certified-devices-modules.pdf

@notf0und said in Programming GPy using USB to serial converter: 3.3.3.114 I only tried with the default windows driver and did not manage to get it working. I guess it is a driver issue. I will test again with other driver version, including the one you propose.

See documentation, there is an accesspoint example: https://docs.pycom.io/firmwareapi/pycom/network/wlan.html from network import WLAN wlan = WLAN() wlan.init(mode=WLAN.AP, ssid='wipy-wlan', auth=(WLAN.WPA2,'www.wipy.io'), channel=7, antenna=WLAN.INT_ANT) Johan

@robert-hh I used this link https://software.pycom.io/downloads/GPy.html and the pycom firmware update wizard. I can now include LTE. Thank you very much for your help.

@jcaron it's a big help thank you for your answer

That's the problem, I tried to use sockets but the wrong way. I think I should be trying for a UDP broadcast? So the diagnostics go out regardless of the phone being connected or not import socket; import time addr = socket.getaddrinfo('0.0.0.0', 80)[0][-1] s = socket.socket(); s.bind(addr); s.listen(1) print('listening on', addr) while 1: cl, addr = s.accept() print('client connected from', addr) cl.send('a diagnostic print \r') time.sleep(2) cl.send('another diagnostic print \r') time.sleep(2) cl.close() If the phone looses the adhoc wifi connection the program just sits there waiting for a client to connect.

Spot on with the cl.makefile('wb') Eric, although I can't tell how you figured that out from that doc page. No matter it works now! If I change 'import socket' to 'import usocket as socket' it runs the same so the pycom library must have both?

How to receive a Bulk text message to a phone that has a Programmable Wireless SIM <?xml version="1.0" encoding="UTF-8"?> <Response> <Message to="sim:YOUR_SIM_SID_HERE" from="{{From}}"> {{Body}} </Message> </Response>

@Fin another good way to reduce overall power usage while being able to use the GPS is to keep the GPS on as long as an acceleration has taken place in the last 3 or so minutes. That way you can sleep the GPS while your device isn't moving and is on long enough to collect acceleration data while you are on the move.