Hi, I'm just getting to assemble the Lead Acid version - I dont have skyweather in it yet, I just wanted to get it running for other projects first. I see testing with a raspberry pi on what looks to be a remote link, but see the micro-usb connector on the board itself. is there any docs / support on "talking" to the processor directly? I see reference to using an FTDI to USB to connect it, but wasn't sure where on the headers to connect it. Or, is there a spec or schematic/interface dwg for the board showing header definitions and potential upgrading of the code from the Arduino IDE?
Thanks! I discovered the issue - i had skipped a step on the grove connection and wasn't getting power to the board. it powers up ok and is running....
Unfortunately I have a new problem - on the raspberry pi "test" side. I'm not using Sky Weather and ran testWXLink.py but get a message "WXLink Not Found" after about 2 seconds. I double-checked the connection to the pi grover runs from the LORA to the Serial Interface connector. I also verified via an FTDI that the Mini is running and the yellow LED is blinking. Attached is the output from the console. It appears the statement "if state.ll.setOpModeSleep(True,True):" is throwing the except
Any thoughts on what I should be checking? I have the serial communications enabled on the Pi. I verified 4.9V across the VCC and GND on the Lora board so I know it's powered up.. .. Are there other pins on the Lora I can check or any kind of debug in the testWXLink or libraries I can enable?
Last Edit: Mar 22, 2020 18:37:45 GMT -8 by riffelrw
I've connected the Lora via a PiGrover per the attached picture. I've also copied the configuration showing no serial port enabled, and the console. I also tried some troubleshooting today:
1) I changed the Grove cable to another - no change 2) I removed the PiGrover and went with headers right to the RPI - no change 3) I moved the SD Card to a Pi Zero from my Pi 3B - no change 4) I swapped the Lora cards - no change (and the Mini still transmitted with the "old" one 5) I have a LiPoly version and it came with WXLink so I tried another Lora card (different from the other 2) - no change. 6) I downloaded SkyWeather just to be sure there weren't any drivers missing, rebooted, tried again - no change.
This must be something in the SW configuration somewhere? But I'm running out of things to try.
I also attached a listing of the devices found on the Pi. This was the Pi 3.
Thanks, that makes sense. I re-enabled the console and tried again, but still no luck. I did swap the Lora's back to the original configuration (put the remote one back on the mini, and vice versa). Attached are the two images, it looks like the it should be working - i can't figure out what could be wrong.
I also swapped out the 3B and put the PiGrover and SD Card into a Pi Zero but same answer. The only thing I haven't swapped out is the pi grover, but I dont think there is any logic on the card, just straight pin to pin connection, correct?
I ordered a spare Grover just to be sure, but it's not here yet.
Is there any standalone commands you can think of for me to talk to the Lora itself, from the remote station, and verify it's actually there? I couldn't find anything on the SEEED site beyond standard arduino code with the radiohead library. I'm guessing it's not a serial connection to the lora radio itself that i could poke at via a terminal to see its alive?
My other thought is just do a loopback TX to RX and console program so that i can verify the serial port on the RPI is functional. I'm guessing it's not even though it's enabled, although its strange I get the same behavior on both platforms... Probably something right in front of my face I cant see.....
Thanks for your thoughts...
Last Edit: Mar 29, 2020 17:32:11 GMT -8 by riffelrw
OK, I was able to figure this out with help from your FB feed on the SD site - it was suggested to disable the serial console access while leaving the serial port enabled and it worked. I'm assuming the serial console enabled over-rode and locked the port (maybe because I'm headless?) so when I disabled the console it worked.
Might be helpful in a future rev of the documentation to point out the configuration, at least in the "test this with a raspberry pi" option.