@Mark-Stewart Are you still using the Pycom firmware? Have you tried Nebra’s? https://support.nebra.com/support/solutions/articles/24000083168-getting-started-with-pycom

@Julia-Steiwer As you should have noticed, Pycom Inc ceased it's operation, and there is no service any more for Pycom products, be it hardware or software like Pymakr. The latter should still work with the older VSCode versions. So if you want to use PyMakr, you have to stick with an working combo of an older VSCode version and PyMakr.

@robert-hh Thank you

Hi Jonathan I have the same issue. Did you find an alternative?

@Jaco-Pretorius In RC1, there is a duty cycle limit at 1%, measured per hour. This means you can send at most 6 messages per hour (6 messages taking 6 seconds of airtime each = 36 seconds per hour = 1%, so one message every 5 minutes is not possible. Not sure how or why you then only get 2, but it may be related to how the duty cycle limit is implemented. Regarding the antenna, a larger antenna is not necessarily better, what makes a difference is antenna gain (a bit, but watch out for EIRP limits!) and line-of-sight. You can try to test outside, in an area with no obstacles around (buildings, trees, hills), on a high point, to see if that makes a difference. But change your interval first, set it to 10 minutes or more to see the result.

Now it seems to be back up.

@Omer-Mughal I would not do a fresh start with Pycom products. The company went bankrupt a year ago, the products are discontinued by the follow-up company, and there is no support anymore by Pycom. Only the web sites are still online. But yes, making distributed measurements is a good application for LoRa, and Pycom products had a good support for LoRa. But there are many others. Look at the TTN pages.

@Christo-Vorster and @Vin883 where do you get to buy that kind of numbers? I'm searching a lot, but everywhere is out-of-stock!

@Elias-Tapia Assuming you have the LOPY4 attached to some kind of USB/Serial interface, like an expansion board, the Updater should always work. You can try to force the ESP32 into update mode by pulling P2 to GND an pushing Reset. You msut as well verify that you use the proper Serial port on your PC.

@robert-hh said in Pymakr 1.1.13 does not work with VSCode 1.60.0: @jchernandez mpremote has a --help option. For copying files, you have to use the cp subcommand. So as example for copying a file to the board: mpremote connect /dev/ttyUSB0 cp myfile.py :myfile.py or just mpremote connect /dev/ttyUSB0 cp myfile.py : for using : as a shortcut for the baord's local directory and . for the PC's one. Copying back similar as: mpremote connect /dev/ttyUSB0 cp :myfile.py myfile.py or mpremote connect /dev/ttyUSB0 cp :myfile.py . The device names at Windows are similar COM3, COM4, .... Shortcuts are: u0 for connect /dev/tty/USB0 Unfortunately the mount command of mpremote does not work with the PyCom version of MicroPython. That version is too old. To run a local script without copying it to the board use the run command. If you do not enter a command after the connect, mpremote opens a REPL session cat mario And before I forget it: With Pycom devices and WiFi active you can always use FTP for copying files. A good FTP client is FileZilla. But some file managers allow using FTP paths as well. User name is micro, password is python. you can review the .py file, i think it has that problem

I think there could be several causes for this problem. It could be because your network connection is unstable. Or your time like the date and time on your device is set wrong. It could also be because you are trying to register more devices than the device registration limit.

@Dale-Fletcher Which firmware version do you use? The time window for receiving a OTAA join confirmation is small (~10 ms after 5 or 6 seconds) and the PyCom (ESP32) device have not You could try to join with a lower data rate or init Lora with a higher spreading factor. That will increase the time window for receive. Edit: Do you see the join request in the TTN gateway console?

I am having the same problem. Is there a solution?

@Danny-Helwegen I understand, but that was not the intention of my question. You could try the following: Disconnect the device from the GPy and measure the current that flows from either output of the device to GND of GPY, with the other device output floating and the GPY's USB port connected to your PC. The current should be 0. If not, the device has internal connections to GND, which can have the effect you see.

@SanOls When you look at the file, do you see any lines with coordinates with values null or 0 or something similar? I think you need to add more logs, including: Timestamps, ideally before and after send, coordinates and recv Logs of the return value of coordinates in all cases Logs of any retries (which I believe would happen if recv returned something other than 'bob' What is the duration of each good/bad phase? Looks like about 8 to 10 points, which should be 15-20 seconds each, is that the case? What is the range of the RSSI values?

@jcaron MERCI DANKON THANG VIELENDANK

Have a look at the docs on Github: https://github.com/pycom/pymakr-vsc#readme especially: https://github.com/pycom/pymakr-vsc/blob/next/GET_STARTED.md https://github.com/pycom/pymakr-vsc/blob/next/WHATS_NEW.md Hope it helps!

@firemonkey Did you have success with this? I'm having issues where the pygate drops off the network (usually when the router loses power) and it never reconnects.