@kjm Obviously yes.

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

@jetatomic I see this is an old post but wanted to response. That is correct. The Gateway is LoRa enabled and backhaul (when using GPy) allows for cellular use or Wi-Fi. Using the POE adapter will give you Ethernet backhaul in addition. Thanks

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.

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.

@reidfo The issue is that an unsupported band is being used by the modem and causes it to crash and reboot. It's a bit more involved but that is the gist. I got a revised firmware that appears to have resolved it. I suppose I could PM the fw. Not sure if pycom would frown upon sharing. I would expect this is resolved in the next release after 1.18.2.r3.

@Paul-Thornton Have you found any update/change on Vodafone's rollout in the UK in the last 1 yr? It will be highly appreciate if you share your knowledge on this issue.

Same problem with the latest 1.18.2.r2. An SPI device that normally worked with 1.18.1.r7 does not work after 1.18.2.

@paul-thornton @ChangedDaily this is now reset. go ahead and re flash the firmware.

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>

@aventri My guess is that you haven't installed the drivers to allow you PC to see the Expansion Board com port? When I was starting with GPY, I found this tutorial from Core Electronics in Australia, to be very helpful.. https://core-electronics.com.au/tutorials/pycom-gpy-getting-started.html It is Windows centric, but there are others to be found as well

@fedonman Depends on the sensors really. What bus (i2C, SPI, etc) or other port you need. Other factors are the power supply required and any other such factors. My practice is to extend the bus/es from the sockets Expansion/Pytrack board to a protoboard, so I am able to connect more than one device, power supply, level shifters, pull up/down resistors, capacitors etc if required. Makes it easier to work on and follows on with making a custom PCB later on..

Ideally the external headers if the pins match your usecase.

@smoochypea You can achieve 5 minuite send intervals easily enough by sleeping for 5minuites - however long execution took. (read the time at the start and end of executing. run time is end - start sleep for 5 minuites - runtime as long as recording and sending data takes < 5 minuites you'll end up with a nicely timed 5 minuite loop) That said. without knowing more about what the rest of the datacollection code does it's rather hard to make recommendations.

@robin Have you tried forcing the use of the internal antenna, either via the appropriate WiFi setting, or directly by controlling P12?

@nadvorvo said in T-Mobile NB-IoT in the Netherlands? [SOLVED]: Could you comment, please [AT] 939910, [AT-OK] +9509 I do not know meaning. [AT] 939910 means an AT command was submitted at timestamp 939910 [AT-OK] +9509 means an OK response was received after elapsed time 9509 both values are in milliseconds

@shedaim I'd agree with @robert-hh. Such "test points" are often incorporated into a PCB for automatic testing during production. Most boards pass through an automatic testing stage during manufacture and at that time it can be "pressed down" onto a jig that makes contact with these test points and allows for full testing and quite often the loading of any boot code required. Here are some similar looking test points inside, of all things, and electric toothbrush. Note that they have helpfully labelled a lot of the test points on the silkscreen (Hint hint, Pycom)