If we takeout the RAK4270, you should at least see set to OTAA because of the line print("set to OTAA").
Is the Rpi PICO working properly? Can you check via an oscilloscope or logic analyzer if there’s a UART output going to RAK4270? Also, can you try to test first the RAK4270 via USB-Serial converter?
I do receive “set to OTAA” with or without the RAK4270 connected. I tried with a second new Pico and still nothing. No response using a USB to serial converter either. Thanks Carl
Success! Nothing like swapping out bad jumpers for more bad jumpers… I opened a new pack of jumper wires and now everything is working perfectly. I would never have guessed it was a bad wire(s). Thanks for your help!
Can you try first a UART loopback test on your RPI Pico? Or try to connect it to a PC via USB-UART converter and replicate the module? Also, is the RAK42xx working well if you use a USB-UART converter?
The problem it isn’t the rak module because i’ve tried to change it and the error still remain, i don’t think the RPI Pico is broke or other because when i connect it to a PC the machine and Thonny recognize the board, maybe the cables i used for connect the module and the RPI are damaged?? like @RGS problem?
Currently, for WisBlock Core module, it is the RAK4631.
We also have a core based on RAK3172 but the custom firmware support (RUI V3) is not yet released (probably Q2/Q3) but the board is already available. At the moment we are not selling the RAK3172 based Core as independent product.
Ok, I have seen it. Based on STM32 it looks very interesting. Now I will start with RAK4631 without BLE to reduce power consumption. Also, I will replace M5Stack ENV.II unit with RAK1902 as there sensor can go into sleep mode. I am curious about the runtime of the LoRaWAN node with a transmission cycle of 30 min. I hope that the solar support is helpful.