"Failed to Configure radio" "bad response" #2
Comments
|
Try running with |
|
Ran with --debug pi@Pi3_misc:~/lorapipe/target/release $ sudo socat EXEC:'pppd nodetach file /etc/ppp/peers/lora,pty,rawer' \
I then ran lsusb then ls /dev/ttyU* pi@Pi3_misc:~/lorapipe/target/release $ lsusb pi@Pi3_misc:~/lorapipe/target/release $ ls /dev/ttyU* pi@Pi3_misc:~/lorapipe/target/release $ I connected to the Lostik via terminal and ran mac reset mac pause I went into /src/lorastik.rs and commented out the mac reset statement and reran cargo then removed the mac reset statement in init-fast.txt and re-ran. Same error pi@Pi3_misc:~/lorapipe/target/release $ sudo socat EXEC:'pppd nodetach file /etc/ppp/peers/lora,pty,rawer' \
|
|
Interesting. I found the reference for your device over at http://ww1.microchip.com/downloads/en/DeviceDoc/RN2483-LoRa-Technology-Module-Command-Reference-User-Guide-DS40001784G.pdf and apparently it requires either I don't know which band you're using, but can you try adapting the |
|
Just did that very thing..... 8-) Ther is one error showing at the beginning pi@Pi3_misc:~/lorapipe/target/release $ sudo socat EXEC:'pppd nodetach file /etc/ppp/peers/lora,pty,rawer' \
|
|
Well, adding the band set works but still not sign of TCP/IP traffic. Strangely enough if I run a network command such as ping or traceroute, whilst the commands bomb out there IS back and forth activity in the debug screens. I am running this off two Raspberry Pi's "Pi"_4 and "P3_misc" Two screenshots First showing the two devices running lorapipe in debug mode, minimal activity Second screenshot is when I run traceroute, activity showing on both but the traceroute bombs out They have IP addresses 10.10.10.3 and 10.10.10.4. I run traceroute from .4 to .3
|
|
So there's a lot that could be at play with TCP/IP. Let's start simple, and first verify that the two lorapipes can talk to each other: run one with the ping command, and the other with pong. If that works, then how are you configuring TCP/IP? |
|
FWIW, I documented the |
|
It's ALIVE...... 8-) Just fired up ping and pong, screenshot of the activity and the outputs including RF quality below. Command line used ./lorapipe --debug --readqual /dev/ttyUSB0 pong > pi3_lora.txt ./lorapipe --debug --readqual /dev/ttyUSB0 ping > pi4_lora.txt
TCP/IP was fired up using the PPP settings in the lorapipe documentation, then SSH'd. (There was an extraneous # in my original script that buggered it up) Memories of classic dial up and Compuserve days..... with the speed..... Thanks so much for this..... now I get to play. Have you thought about porting this to Arduino..? The TTGO Lora32 or T-Beam devices would lend themselves particularly well to this as self contained, all in one devices as well as plugins for PC Wintel and *nix devices including repeater and re-broadcast as well as IoT functionality |
|
Hah, another old CompuServer! Yes indeed, the speed brings back memories of modems... I've done very little in the Arduino space, mainly thanks to the Raspberry Pi being roughly the same cost and far quicker to get going. I run lorapipe on a pi and it works great. I haven't had the time to tinker. |
Hi,
Looking to set up some remote connectivity, working with LORA (2 x LoStik's) via TCP/IP, connecting to two Raspberry Pi's so thought your code would be perfect.
I have complied the Rust code, no errors, the firmware for the LoStik from "sys get ver" is RN2483 1.0.5 Oct 31 2018 15:06:52
When I try to run the code, I have to run it first using sudo
sudo socat EXEC:'pppd nodetach file /etc/ppp/peers/lora,pty,rawer'
goes to > OK , I then run
EXEC:'./lorapipe --txslot 2000 --initfile=init-fast.txt --maxpacketsize 100 --txwait 120 /dev/ttyUSB0 pipe,pty,rawer'
error message throws as below.
thread 'main' panicked at 'Failed to configure radio: Custom { kind: Other, error: "Bad response from radio during initialization" }', src/main.rs:112:5
note: run with
RUST_BACKTRACE=1environment variable to display a backtraceLooking at the init-fast.txt the "radio set pwr" statement appears incorrect as the max pwr setting is 15 not 20. as per the init.txt and init-fast.txt both edited and set to 15, same error on run.
Any idea where the problerm may lie..?
The text was updated successfully, but these errors were encountered: