ISSRx not working, but WxReceiver is (kind of)? about vptools

[kobuki]

Yeah, I know it works, I've been in contact with him while he made the changes to his fork. His code works perfectly fine but it's harder to reuse or customize. Eventually I'll need to fix mine too for the US band (possibly other bands as well).

[kobuki]

Hi. The ISSRx sketch is a simple demo to show how to use the library. I don't plan adding functionality or fixing it in any way. Consistency with WxReceiver is not expected nor aimed. The problem you describe is in the lib itself, as it currently has problems properly syncing to all packets of the US frequency band (while it works perfectly on the EU band). I'm yet to get to the bottom of this, but will eventually, soon. The fact that I don't have transmitters on the US band makes it pretty hard to debug. If you have an incentive to try and fix it, be my guest. The syncing algo is the same, but somehow it misses every other packet. Other folks reported the same on the US band.

[poblabs]

Understood on ISSRx, it seems I have a baseline with it now, so I'll keep molding it.

I was going to ask why I was getting a packet every 5 seconds - and you mention that US band is missing every other packet so I think that answers that question.

As for the lib issue, I'm happy to help. I don't have experience in RF algo debugging, but am happy to load sketches onto my Moteino that may help move things forward.

My Davis ISS is brand new and sitting on my bench. I haven't had a chance to install it yet due to the snow storms we've been receiving.

[amm042]

Pat, I ported this code to the adafruit feather M0 last year and in the process rewrote the scheduler so it works for the US bands. You can take a look to see if this code helps: https://github.com/HydroSense/FeatherM0_Davis_ISS_rx Alan

…

On Tue, Mar 13, 2018 at 8:50 PM, poblabs ***@***.***> wrote: Hi there, I'm about a days worth of tinkering into it, and I'm trying to get this working, but can't. I have been using my own weewx driver so I'm trying to get the ISSRx working and then will change it to suit my needs. Basically it's a socket server, so Moteino will hand the data to a NodeMCU which will upload to the socket. Anyways, ISSRx is not receiving any packets from ISS. I uploaded the WxReceiver sketch and it eventually got some packets. I've since rebooted and both of them are failing, but I can't figure out why ISSRx isn't working. I see some inconsistencies with ISSRx, such as the blink function is not being called from anywhere. So I'm sure it could use some updates; and I'm happy to take a stab at it, but right now I'm totally lost. I have 1 station, changed the band to FREQ_BAND_US and I'm not getting any data anymore. I didn't see a FAQ or anything so that's why I'm making the ticket. Any guidance is appreciated! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGJwumub-R7-oaN02eq8TpsAvsJNfPkLks5teGlOgaJpZM4SprHi> .

-- Alan Marchiori | Bucknell University | Breakiron 268 Assistant Professor of Computer Science Calendar: https://calendar.google.com/calendar/embed?src=amm042%40bucknell.edu <https://calendar.google.com/calendar/embed?src=amm042%40bucknell.edu&ctz=America%2FNew_York> Appointments: https://calendar.google.com/calendar/selfsched?sstoken=UUNGd08xclV2MHphfGRlZmF1bHR8YzAzMzU2NzgwYmQ1MDBjNmFkYTgxZjQzODgwNTIzZDQ

[poblabs]

@amm042 Thanks! I tried it out but I wasn't getting anything on serial monitor - not even the Boot complete!. I'm a bit new at this, and not sure what I'm doing wrong.

[kobuki]

@poblabs thanks. Don't worry about the scheduler (packet timing algo), it's not closely related to the RF part or settings. Davis devices transmit packets at fixed intervals; the interval is calculated as (41+ID)/16 seconds, where ID is what you set on your SIM panel in the ISS, for example. The packets are transmitted on a hopping frequency sequence, looked up in the various tables in DavisRFM69.h. If you have any questions about the algo in my code, just ask here.

[poblabs]

@kobuki Okay interesting, so it is about 2.5 second transmit interval and I'm seeing about 5 seconds right now on the serial monitor. Not sure where to begin with helping since I don't know C++, but I'm happy to help in some capacity

[kobuki]

Well, without some moderate C/C++ knowledge it would be hard. There's another repo, based on mine, from MCrossley - maybe you can try that, too.

[amm042]

@poblabs Thinking back, my board has a different pin connection to the radio. You can try replacing the line:

DavisRFM69 radio(8, 3, true, 3);

with

DavisRFM69 radio;

This will use the default values, which should match your hardware.

[poblabs]

@amm042 That worked! I'm seeing packets every 2.5 seconds, and it looks like on all sequential channels.

raw:50-00-80-FF-71-00-59-A7-FF-FF, station:0, packets:1/0/100.00, channel:0, rssi:-73, batt:ok, windv:0, winddraw:128, windd:179, rainsecs:-1, fei:-21, delta:0
raw:40-00-80-00-01-00-84-19-FF-FF, station:0, packets:2/0/100.00, channel:1, rssi:-76, batt:ok, windv:0, winddraw:128, windd:179, uv:0.0, fei:-20, delta:2559732
raw:80-00-80-29-79-00-A3-8E-FF-FF, station:0, packets:3/0/100.00, channel:2, rssi:-73, batt:ok, windv:0, winddraw:128, windd:179, temp:66.3, fei:-16, delta:2560772
raw:E0-00-80-81-01-00-69-5B-FF-FF, station:0, packets:4/0/100.00, channel:3, rssi:-81, batt:ok, windv:0, winddraw:128, windd:179, rain:129, fei:-16, delta:2560760
raw:50-00-80-FF-71-00-59-A7-FF-FF, station:0, packets:5/0/100.00, channel:4, rssi:-75, batt:ok, windv:0, winddraw:128, windd:179, rainsecs:-1, fei:-17, delta:2560772
raw:90-00-80-00-01-08-A1-A5-FF-FF, station:0, packets:6/0/100.00, channel:5, rssi:-75, batt:ok, windv:0, winddraw:128, windd:179, windgust:0, fei:-20, delta:2559732
raw:80-00-80-29-79-00-A3-8E-FF-FF, station:0, packets:7/0/100.00, channel:6, rssi:-80, batt:ok, windv:0, winddraw:128, windd:179, temp:66.3, fei:-17, delta:2560776
raw:E0-00-80-81-01-00-69-5B-FF-FF, station:0, packets:8/0/100.00, channel:7, rssi:-80, batt:ok, windv:0, winddraw:128, windd:179, rain:129, fei:-16, delta:2560780

but it was short lived. I now have all missed packets

47906400: missed packet from station 0 channel 12
50473924: missed packet from station 0 channel 13
53041408: missed packet from station 0 channel 14
55608924: missed packet from station 0 channel 15
58176400: missed packet from station 0 channel 16
60743928: missed packet from station 0 channel 17

Finally received a Station is lost message and it went into search mode. It found 2 more packets and now they're lost again.

After the 2nd Station is lost message it seems stuck in searching mode.

Not sure where to go from here. It looked promising though.

Edit: After several minutes it found another 10 packets, and now the packets are lost again.

[amm042]

@poblabs that's promising, on my station it was working good enough. There were occasional drops but only a handful per day (24 hrs) and it does correctly resynchronize (eventually). It looks like you seeing more issues. Is the station near your receiver? Rssi in the -70's should be good (I think high 80's to low 90's is the lowest you can receive at).

[kobuki]

Sorry guys, but I'd like to keep discussions related to my own repo here. Could you please continue with the discussion of amm042's in his own bug tracker? Thanks in advance.

[poblabs]

@kobuki Will do. If you have any sketches you'd like me to test to improve your repo, please advise.

[kobuki]

The problem most probably lies with DavisRFM69.cpp, that's the one I need to debug. Any suggestions or ideas are welcome.

[poblabs]

@kobuki Just FYI - I tried out the fork that you recommended from MCrossley... it's working pretty well. I let it run overnight (11 hours so far) and I'm getting packets on all 0-50 channels and as of right now I see 15529 received and 60 packets lost with the percentage of 99.62%. Maybe there's something in that DavisRFM69.cpp that did the US band magic? I also saw a different timer library being used too.

Thought I'd mention my findings since you recommended it and it's working.

Thanks again for the help