The Things Uno is based on the Arduino Leonardo, yes I know a bad name choice , confusing because its totally different then an Arduino UNO.
Connecting should be done like you connect a Leonardo to your computer.
The TTN UNO uses a software UART while the original UNO uses a hardware UART.
So if you have the board connected and you goto Tools-> Serial Port -> you must be sure that the board is connected to the right port.
If you don’t see the port you can :
Upload a sketch (for example blink) and press the reset button of the board during compiling.
Thanks. I’ve checked the COM-port and I’m sure it is set correctly, as I can see it as well in device manager showing up with the name “Arduino Leonardo (COM11)”.
But just to make it clear - I haven’t tried yet to compile and upload a sketch as I wanted to use this standard pre-installed app. But since it does not seem to be installed, I wonder if I can get it to upload it in my Things Uno.
ah… well then compile/install device info from the examples and open the terminal… write down the info you get from the board because you’ll need it later
Yes, that’s right. New UNO, nothing happens.
If no one from TTN can share the app, I’ll do it the “Quick Start” way.
Thanks for trying to help @BoRRoZ It’s much appreciated.
I think I found the issue : my Uno gets stuck in the function ttn.showStatus(). It never returns.
I can see that from the serial output, after uploading a new sketch (using DeviceInfo as a start point) and putting some delays so I get time to start the serial monitor.
Is that a known issue? I’ll do some research in the forum, perhaps I find an answer there.
Do you mean that it is normal behavior that the function ttn.showStatus() does not return if there is no gateway?
I tested the Things Node last week, and it never got stuck, even though they was no gateway available.
After some hours in reading, understanding and testing, I found out that the issue is the RN2483, being mute, never answering to commands! Is it sleeping, dead?
I verified this with 2 sketches.
With DeviceInfo, the method ->readBytesUntil never returns a message (only 0).
With PassThrough, function loraSerial.available is never true -> nothing to read from RN2583, even though command “mac get deveui” is sent.
Any suggestion on what to do next? Any way to “wake up” the module, sending some control control char, hard reset, upload of new firmware (I doubt this will work).
Thanks.
Update : I downloaded the Microchip LoRa Dev utility, but it does not detect any device (PassTrough used, correct COM port detected).
Thanks, but cable is working fine (I have 2 and both works with a Things Node and other Wemos projects). Sending and receiving from the PC to the Things Uno works fine, the problem in receiving from the RN2483.
(I think it is USB 3.0 yes, but again, the problem is not between the PC and the Things Uno, but between the Uno and the RN2483).
Is the hardware documentation / wiring available somewhere? Can’t find it. Thanks.
PS: for the Things Node, not for the standard Leonardo nor the RN2483.