@robert-hh Hooray! I've got it! Signal wire was broken between pin and GPS. Thanks.

@robert-hh So a remote raw lora receiver with a lot of nodes sending it is just inevitable that collisions happen? My current "solution" is to send and wait for it to send back an acknowledge, if not just wait a random period of time.

@tschili Imho, if you trigger the wake-up just when the transmission starts, you'll have the issue that the GPY needs to little bit of time to wake-up and initialise, and you will most certainly lose and data received during that time. So you would need the SIM800L to wait until the GPY is ready to receive before it start sending the data, and some other way to wake up the GPY.

@jmpratt I cannot believe that you have the same code on both WiPy's. Please reload the code to both devices, reset them and try.

@hopkapi If you connect G24 aka P3 -> 7 G11 aka P4 -> 6 GND -> 8 GND Vin -> 2 (5V) and run the LoPy from USB. then the electrical conditions shoul be OK, and the device shoudl be accessible via UART 1. SOmetimes the definition of Tx and Rx are reversed, so you may swap P3 and P4. That should not cause any harm to the devices. The UART setting according to the data sheet is baud rate: 9600, databits: 8, stopbits: 1, parity: no Some test code would be like: from machine import UART uart = UART(1, 9600) # init with given baudrate uart.init(9600, bits=8, parity=None, stop=1) # init with given parameters while True: data = uart.readall() if data is not None: print(data)

@livius Thank you so much!!! That works for me! Not sure how long it would have taken me to properly use brackets [ ].

@bitvijays the default rx buffer size us 512. But you can set it when instantiating the uart object with the parameter rx_buffer_size=nnn Whether that can be set to a value like 40000 has to be tested.

Per comments from @robert-hh & @timh , I used a MAX3232, RS232 to TTL converter chip to resolve the issue.

@jimpower ok, so why do you get no module found when you call urequests.post now when you didn't before. I can't see all your code, just snippets. The vaious sample bits of code are being changed. Oh I see now what the problem is, when you import urequests you are importing as requests hence the module not found error. You will need to change the sample to requests.post Also as an aside why do you execfile('/flash/Wi-Fi/Wi-Fi.py') rather than importing. This seems odd thing to do.

@fsergeys I'm not familiar with Qi chargers, but isn't there a chance the electromagnetic field generated when you transmit data may "trigger" the charger somehow? Since those chargers are designed to be inserted into phones it shouldn't be an issue, but you never know...

@matamune you can turn automatic gc on gc.enable() and also you can do manual gc.collect()

@livius i did already.. still the same problem.. Now i connected my lopy to raspberry pi through usb0 and putty.. the data bieng sent by raspberry pi is showing on the terminal instead of in uart.readall()...

Hello guys, The issue fixed in the IDF is definitely affecting us. We will merge that patch and will be available for our next release this week. Cheers, Daniel

Any News?

@livius It features a MAX3421E USB host controller chip and USB-A port. We created this board to communicate with existing serial-over-USB (CDC, or communications device class) devices. Adding support for other USB "drivers" is a matter of understanding the USB endpoints and writing the implementation in MicroPython. Update: Check out the First look: USB Host Expansion Board by Semireg

thanks but i was looking for how you can use it instead of Wifi forwarding he messages that normally are forwarded through Wifi to loraserver using Uart i think i'll need to design also a process on the other side to read uart and push it to loraserver I'll try to do it and see

@leo_sol Looking at your initial post it seems that UART1 may still available on both units. the default config collides with the SD card pins, but you can assign UART1 to other pins.