@colateral Hi, i am using 1 gateway that only with pymaker opened while the node i using the power bank to power up. I have try both in vice versa yet no result showing out.

@robert-hh Awsome! Thank you

I just want to share my experience. I think this can happen if your power supply voltage is not sufficient. For example the device we are working on will handle most commands but when it tries to write to memory and voltage is below 3 V it will stall and output this kind of message. I have had this issue on two GPys and could replicate that the problem was solved by merely upping the voltage and rebooting the device.

@Jurassic-Pork I have an AMT2301/DHT21 sensor. Google says that it is similar to the DHT22 and should work with the same code. However, your library with DHT22 as the set sensor does not work. Do you know anything about if the sensor is supported or are you planning to add it in the future?

@gertjanvanhethof said in LoPy as LoRaWAN Basestation?: @bmarkus Yes that is correct. Only a LoRa Nano-Gateway is possible. This is not compliant with LoRaWAN. But for development and without a full compliant gateway this is ok. So you can develop LoRa Nodes which connects to your own Nano-Gateway. It is OK, but the original subject of the topic is "LoPy as LoraWAN Basestation?" Using LoRa radio layer you can make great things with other protocols, see http://www.waziup.eu/ as an example building network with SX127x devices and gateways only. But not LoraWAN.

@camdenkrupala You can already set an APN manually by doing lte.send_at_cmd('AT+CEREG=2') time.sleep(2) lte.send_at_cmd('AT+CFUN=1') time.sleep(1) lte.send_at_cmd('AT+CGDCONT=1,"IP","YOUR_APN_HERE"') time.sleep(2) while lte.isattached() == False: time.sleep(1) lte.connect() while not lte.isconnected(): time.sleep(1) print("connected")

I have done more testing and the call is actually working, I'm just not able to catch the confirmation reply. @jcaron Thanks for the suggestion with the PMTK353. I changed these around and discovered my antenna is not reading anything but GPS. When I turn on Glonass only, I get nothing returned, so I must have a hardware issue.

@wghirakawa The issue is that socket.connect() and SSL handshake will not timeout also in case the socket timeout is set and hang the application forever. https://forum.pycom.io/topic/3985/new-lte-firmware-releases-v1-18-1-r4-stable-1-19-0-b5-development-nb-iot-firmware-40343/45

@Pesien @mfalkvidd I mage a PR for inverted UART signals, based on the release candidate version. The ony changes file is mods/moduart.c, so it's easy to use it for the master branch too: https://github.com/pycom/pycom-micropython-sigfox/pull/310

@monersss At the moment, with my example, that happens when you get a timeout. But again, that would require some "out-of-band" signaling, meaning: in addition to the "payload", the jpg file, some control information must be exchanged. And that is part of a protocol. That could be pretty simple. If I grab one out of the air, it could be: Define record types, where the first letter defines the type of the record, followed by 3 bytes record length, followed by the payload, like: 'fnnn': filename (of length nnn) 'd128': data 'x000': done You would first receive 4 bytes, decode type and length, and then receive further 'length' bytes. And for every record received, your LoPy would send a confirmation, like the three bytes: "ok!" or "bad", in case of errors (or just a single byte). That would implement flow control and the EOF signal. It does not have other elements like check sums and sequence control. But you might not need that.

Voting for "@micropython.native/viper/.asm_xtensa" decorators on PyCom MicroPython, so we can optimize the speed of important code.

@danielm Thanks! Anything about band support?

@seb Thanks, I found them and was able to start playing with the new calls.

@robert-hh Okay yeah that is a fair point, there is a known bug in this ones firmware with sending RST signals or something. I'll throw it in the bin and try a different one with a FTDI chip.

I don't think pycom would refuse to promote pybytes as there entry into service business.

@szyba91 What do you mean with: does not work? The copying or the script? For copying Filezilla also support a upload option with the right cick on the file. SImple Double-Click also copies. Did you set the number of transfers to 1 in the settings? The ftp server in the xxPy devices is pretty limited. I had never problems using ftp for file transfer, but I'm using FireFTP, which is a Firefox plugin. That is convenient because I have firefox open anyhow almost all the time.

@daniel I understand Telstra connectivity issue should be resolved. I don't see how to test it myself, Sequans firmware being unavailable at the moment. Did you get positive feedback in this forum?

@livius regarding your problem trying to connect 2 WiPy's together, please check my reply in: https://forum.pycom.io/topic/376/interim-update/6 Thanks. Cheers, Daniel

@tttadam I think it because there may be values in the read buffer, which are discarded when you init the device. You could try to call tou.read() to flush the buffer instead of re-initing the UART. if that does not work, it's no big harm. Reestablising the UART does not harm.