@Clemens Thank you Clemens to pointing this out for me , Actually the Maximum Payload is 64B for the Lopy . i was thinking that packets were cut internally but not. Nice to see that no one had this problem before. I have already bypassed the problem by cutting the packets. Thanks again .

@jmarcelino can you help me please? I was able to connect my NanoGateway to TTN, then I connected a node and i no had problems, however, now I am having problems to connect the node, when I start the node the following messages appear in the NanoGateway: [ 884.453] Received packet: {"rxpk": [{"data": "ABeYANB+1bNwQfHGnEnVs3BtML tNbMI=", "time": "2018-02-14T15:38:34.160580Z", "chan": 0, "tmst": 860755474, "s tat": 1, "modu": "LORA", "lsnr": 5.0, "rssi": -20, "rfch": 0, "codr": "4/5", "fr eq": 903.9001, "datr": "SF7BW125", "size": 23}]} [ 884.710] Push ack [ 887.718] Pull ack [ 889.710] Pull rsp [ 890.633] Sent downlink packet scheduled on 866.755, at 923.299 Mhz using SF12BW500: b' yZ\xe2\xb8 \x 191\xc3NL\xc7/\xba+\xf4\xc4' but the node is still getting "not joined yet", I am using the 915 Mhz.

@stef Hi Stef, This is working. Thanks

@mkharibalaji Thanks for the explanation. Currently the Bluetooth stack only supports Bluetooth LE. You'd have to change your mobile app to use this instead. Bluetooth Classic is planned but I'm not sure when, it's not even on the low-level toolchain yet.

@robert-hh Pick it apart :).

hi all, thx for all the responses, i've got the exp. board (in combination with the lopy) working. the vcp driver did the trick :) thx :) :)

@bmarkus I don´t really know because I have not chosen one yet. I am thinking about using Loriot or the Semtech Network Server. I have to look for one with multicast downlink support in order to use LoRa. If it is supported, would the Lopy module support it too? Thanks for your answer

@bucknall I have watched the webinar and still have some problems with understanding how to send data between two Lopys. Should both of them be connected to a computer? If so do I need to use two computers to do that? How can I send the data without connecting Lopys to computer? I believe these are very easy questions but i am a begginer here...

I think so. I did not find any pin that could be hold low during deepsleep mode. @daniel can you show us some light here? Thanks a lot, Pablo

@chumelnicu Still on my to-do list I'm afraid, but maybe try iotmaker's code? https://forum.pycom.io/topic/1453/i2c-sensor-with-wipy2/11

Ok.. Solved: from machine import I2C import time ADDR = 0x70 CMD = 0x51 configure the I2C bus i2c = I2C(0, I2C.MASTER, baudrate=250000) i2c.writeto(ADDR, bytes([CMD])) time.sleep(0.5) dist = i2c.readfrom(ADDR, 2) total = (dist[0]*255)+dist[1] print(total)

@jmarcelino Thanks for the quick reply. Yes, I'm in US915, and setting it to 3 does solve the issue. Now to figure out how to view what I'm sending from the LoPy to the mLinux Conduit gateway... :-/

@dchappel bit left shift << same for bit right shift >>

@pascal probably you are connected to board by COM port from different program. You can not be connected to board bye e.g. pymark, putty. Updater tool must have exclusive access to com port (UART). Is this the case? also look here https://forum.pycom.io/topic/763/firmware-upgrade-troubleshooting-checklist-procedure

Hi @vervoortraf, you should not need to pass any arguments to the uart.readline() function. Just run uart.readline() and it should detect the '\n' in any of the messages sent to your LoPy via UART. https://docs.pycom.io/pycom_esp32/library/machine.UART.html#machine.uart.readline Let me know if this helps! Thanks, Alex

@Jan-Burkhardt said in Power saving with new machine.deepsleep functions !: machine.deepsleep([60000]) In documentation brackets [] show optional arguments you can run machine.deepsleep() or machine.deepsleep(60000) But remember that first is currently not wake up able We must wait for pin wakeup support And about 13 mA - it is already know by @daniel and he say that it is under investiagtion.

@robert-hh Thank you for the answer! I searched around the forum but its sometimes confusing when then documentation and forums are not synced because of the ever changing updates :) I'll keep an eye out the in the patch notes.