@jarat @jcaron So i tried your second option, and i saw a drop in current consumption to about 70 mA from 77mA. And this option did NOT turn of the LoPy. And i further tried to read from the I2C to get the GPS coordinates while it was off and i got an error. So i might think that the second option worked, but a drop of 7 mA is maybe a bit too little to come from the GPS? The datasheet of the GPS says that the gps should use around 29 ma. So i should have measured a current consumption around 50 mA?

@soren simpy use BSS138 to level shifting or bigger model 2N7000

@herbv said in Where is ticks_diff()?: @sakis What is the status with this. I've come to the same point. with missing "utime.ticks_add" and "utime.ticks_diff" it is quite useless to use ticks for calculating deatlines. Please go ahead, tx, Herbert Well, if you can read ticks itself you can write your own ticks_diff. It takes time, memory, etc. but may work as 'Plan B'.

You could connect by telnet, after configuring the WiFi of your WiPy as access point (AP) or station (STA).

@soren OK, So despite the no project, I tried uploading and it behaves really strange. It says "Connected" above the console despite the console saying "Connecting on COM4..." at the same time.. how does that make any sense? Here's a snippet of my log: Uploading project (main folder)... Reading file status Failed to connect (Error: Writing to COM port (GetOverlappedResult): Operation aborted). Click here to try again. Failed to read project status, uploading all files [1/5] Writing file boot.py Connecting on COM4... ** and here it will stay forever, while at the same time displaying "Connected".....

@rdixey If you didn't need the speed of SPI, then you could have used I2C (IIC) for both devices (as long as they different addresses), as IIC supports 127 (from memory) device addresses. "OLED: https://www.adafruit.com/products/938 #Using as SPI by Default but can be configured for I2C.", rdixey

The MAC address printed on your beacons is just a nicely formatted version in hexadecimal of the 6 byte address. What you get from Python are the actual 6 bytes themselves (hence the b' at the start) and when you print them they get turned into the correspond ASCII characters for that value (or \xYY if it's not a printable character) You can use the binascii.hexlify function to turn each of those bytes into hexadecimal and make a string which is closer to what you have. For example your b'FS\xbd\x8c\xd2\x11' >>> import binascii >>> binascii.hexlify(b'FS\xbd\x8c\xd2\x11') b'4653bd8cd211' So this address is 46:53:bd:8c:d2:11 Of course you can split into pairs, add the colons and make all letters uppercase too using standard string manipulation.

ouch... In Pycom's webpage, the last version of DFU that is writen is pytrack_0.0.4.dfu and I do not download because it's the version that I have now: "The latest firmware is v0.0.4. The DFU file can be downloaded from the links below:" But, if open the link, the version is 0.0.6.... Sorry, it's my fault! Works again!

@soren did you add code that affects the antenna switch? This is on GPIO16

@kots Even it that is true, it does not sound reasonable. G2 is used for the REPL communication. You might use another GPIO port for switching, but G2 seems to be an odd choice, as well as driving a step-up converter power input with a GPIO port, especially if a single transistor switch or digital gate is sufficient for the purpose.

@snehasg95 I had the same issue with Atom not installing Pymakr plugin however this has been resolved in a new patch. I strongly recommend trying again to install Atom with the Pymakr plugin.

@seb I've tried you're code, it is better but in my opinion it's harder than the first one (I don't really know but the sintax " if rec=='Ping' "didn't work so I've tried yours :"if rec !=b' ' " that's just fine) @jmarcelino at a distance of 15 meters I had accuracy of almost 40% ( from 100 messages sent from LoPyPC only 40 came back from the other LoPy )

@helalbr You can use a serial connection via UART in combination, to be safe, with level shifters, which are widely available, e.g. from adafruit. Since you only need to send from the Lopy to the Arduino, only the connections TX(Lopy) to RX(Arduino) and GND to GND are required.

Hi, I just updated the firmware on the LoPy and PySense, following this guide: https://docs.pycom.io/chapter/gettingstarted/installation/firmwaretool.html Thanks

@robert-hh That worked great. I'm now able to build the FW with our frozen bytecode. Next step is to figure out the OTA

@hansjorg2 Ampy is a a python program. You'll find it here: https://learn.adafruit.com/micropython-basics-load-files-and-run-code/install-ampy