Can everyone explain me how is pwr_en works? Can I wakeup the board over pwr_en and gnd from deepsleep? Can I force a reset over this pin? Pycom doc confuse me 😊

@pmb_nl Yes it works without any problems the last few weeks so far

@rubencg195 The pull/push ack messaage show the communication via Internet to the TTN server. Independent of that, the LoRa device is always listening, except when it is sending itself. But that would only happen after an uplink message has been send and it was told by the server so deliver a downlink message. It might only happen, that if there are many nodes around sending, then the gateway may have started to listen to another message. A few notes. always use the software from the git repository. Do not copy it form the documentation. Use the latest firmware version with the software from the git repository. The nanogateway is listening on a single channel only. If you do not configure the node accordingly, the node will send on different channels. The examples for abp_node and otaa_node shoudl cater for that. Besides that, I have a comibinatin of a LoPy as nano-gateway and FiPy as nodes running, and they never seem to miss a packet.

Hi @dda socket.connect doesn't take a domain name, you need to resolve it first into a tuple like this - (family, type, proto, canonname, sockaddr) - which you can obtain from socket.getaddrinfo() In your case doing: s.connect(socket.getaddrinfo(addr, port)[0][-1]) should do what you want. There currently isn't a way to obtain your assigned IP address.

@jmarcelino Any update on the fn to enable LOW power LTE option?

@jmarcelino I am still in need of a way to use NB-IoT on fipy. Is there a way to achive it? As I can see others have the same problem as me, so can we have some update on the state of the matter?

@jmarcelino I'm getting the following error: Traceback (most recent call last): File "main.py", line 13, in <module> AttributeError: 'RTC' object has no attribute 'irq' MicroPython v1.8.6-849-83e2f7f on 2018-03-19; FiPy with ESP32 Type "help()" for more information.

That worked perfectly. Thanks, Zac

@smbunn It's still a single step to change the LoRa region but now you can either fix it in firmware configuration, or use the region= parameter. I recommend always the region parameter going forward. The firmware method was added more so existing code without the region parameter wouldn't break.

@matthew said in Relay and solenoid valve: e if i can power the relay using the 5v o The "5V" label of the expansion board v. 3 is in reality the voltage input value. It can be around 5V when the board is connected with USB cable (if attached to a 5V source), but it is not when is power is sourced by the LiPo battery. On board there is a TPS2115A, that switches from one source to the other when, for example the battery is connected and we plug the USB cable. The Vin can be from 3.5 to 5.5 V. Solenoid valve control You can use many different options to control the solenoid valves as well as ways to power the solenoid valves and mechanical relay or equivalent driver. I personally prefer isolated solutions like optocouplers, solid state relays (photo MOSFET) (price went down in last years), ... An alternative can be, if You need to drive more than one, darlington transistor arrays like ULN2003, the low voltage ULN2003LV, or the newer equivalent TPL7407L. You can easily found mechanical relay boards with onboard optocoupler. You need to heck the datasheet to look for the mA at 3.3V that they sink.

@jmarcelino Yeah, all up to date to the latest firmware. We are working them pretty hard, I guess they are reaching somewhere into the 45+ degrees C

@jmarcelino I've tested this now (removed lte = LTE() and lte.deinit() ) and the peak is still there. The device goes into deep sleep, but like before the current rises quickly to about 200 mA for a couple of seconds before it goes into deep sleep. I also find it strange that it doesn't happen the first time the device goes into deep sleep, but all consecutive runs. The first time now, since I don't deinit() LTE the current is at about 200 mA and drops down to deep sleep. Then when waking up it is around 60-70 mA when measuring and then peaks to 200 right before deep sleep.

@livius Thank you i will try immediately

hi @Matthew, First, you should not have anything plugged in the Expansion Board, no Lopy/Fipy. On Windows, the fact that went up to 96% and stopped, means there are USB problems(lots of retries and timeout). Try changing something, USB port, cable. We had lots of problems with poor USB cables. Maybe try to remove other USB peripherals, from your PC. On Linux, please, check if board is in dfu mode, looking at lsusb output, 04D8:EF99 should be visible. It's not clear from dfu-util error, Cannot open DFU device 04d8:ef99, if the device is not enumerated or you don't have rights. As wild try, maybe you should keep just RX and TX jumpers, on Expansion Board. <later edit>: FYI, the Expansion board 3 has already the latest firmware, we released just once

@jmarcelino And on retrying the firmware upgrade again, this time I am getting a different error once and back to the same AT+SMSWBOOT failed error <<< Welcome to the SQN3330 firmware updater >>> Entering recovery mode Resetting. Starting STP (DO NOT DISCONNECT POWER!!!) Traceback (most recent call last): File "main.py", line 2, in <module> File "/flash/lib/sqnsupgrade.py", line 114, in run NameError: local variable referenced before assignment MicroPython v1.8.6-849-83e2f7f on 2018-03-19; FiPy with ESP32 Type "help()" for more information. >>> <<< Welcome to the SQN3330 firmware updater >>> Entering recovery mode Traceback (most recent call last): File "main.py", line 2, in <module> File "/flash/lib/sqnsupgrade.py", line 98, in run OSError: AT+SMSWBOOT=3,0 failed! MicroPython v1.8.6-849-83e2f7f on 2018-03-19; FiPy with ESP32 Type "help()" for more information. >>> I have not done any changes to my code or file since the last error: OSError: AT+SMSWBOOT=3,0 failed!

I'm getting this error whenever I try to compile anything for the GPy: [15975] Error loading Python lib '/var/folders/57/hyd6ntr1233_x_brscxdp8480000gn/T/_MEI7xbrkg/libpython3.8.dylib': dlopen: dlopen(/var/folders/57/hyd6ntr1233_x_brscxdp8480000gn/T/_MEI7xbrkg/libpython3.8.dylib, 10): Symbol not found: ____chkstk_darwin Referenced from: /var/folders/57/hyd6ntr1233_x_brscxdp8480000gn/T/_MEI7xbrkg/libintl.8.dylib Expected in: /usr/lib/libSystem.B.dylib in /var/folders/57/hyd6ntr1233_x_brscxdp8480000gn/T/_MEI7xbrkg/libintl.8.dylib I have just re-installed Python 3.9. Anyone know how to fix this?