DavisGetLPSandLOOP: CRC BAD
Renew HiLows
FLsunshine
WiFilogger has no communication with the console.
Cases:
1. Baud rate in the console is not 19200. 19200 baud rate is required to obtain communication.
2. The console was not fully disabled while logger mounting. The AC adapter and batteries must be removed. Because a console is recognizing logger on startup, the time when a console is beeping.
3. Logger can be not pushed firmly enough into the socket. Sometimes socket/plug is extreme tight, user has to use some force to push it into the socket in the batteries compartment. Ofcourse a console has to be powered off while putting/removing datalogger.
4. WiFilogger is damaged. Can happen, but this is extreme rare.
As I had mentioned in a previous post, I was going to remove the WFL2 so I could do a thorough inspection of the WFL2 as well as the connector pins on both the WFL2 & the console. This would be the first time I would be removing the WFL2 since the day I first installed it. Following breakfast this morning I accomplished that task and found nothing that look suspicious. All the solder joints on the WFL2 were exceptionally well flowed and none exhibited any evidence of being cracked or "cold" solder, additionally all the piins for the connector (male & female) were in good shape. I reinserted the WFL2 and this time took exceptional care to make sure it was firmly inserted into the console connector.
At this point let me respond to the question that was posted by davidmc36...my method for testing for the baud rate was to simultaneously press the "DONE" button and the "-" button and then cycle through the various setup options. Using this method the option for setting the baud NEVER appeared.
Upon power up the first thing that I observed was that the Real Time Data was now for the first time showing data being displayed for all the sensors in my instrument suite. Also based upon the posting from WiFiLogger I once again went looking for the Serial Baud Rate setup option and now it is available and is set to 19200.
So it now appears that both the console & the WFL2 are working as designed. I can only assume that the final step that got things working properly was the removal of power from the console followed by the removal of the WFL2 and then the replacement of the WFL2 followed by a power up.
Additionally, I started up the WeatherLink software Ver. 6.0.5 and entered the IP address in the Communications Port setup screen. The WeatherLink software immediately started to communicate with WFL2 and was displaying all my sensors.
And one last task which was for me the real important item. From my Raspberry Pi I issued a curl command to the WFL2 (curl 192.168.1.11/wflexpj.json) and got back a complete status display of all sensors including WFL2 setup parameters...happiness is a totally functional wifiLogger2.
I want to thank all the posters for their assistance with my issue which in the end appears to be some unique quirk associated with getting the Davis console into the proper state to allow it to communicate with WFL2.
Now I'm off to start working on the software needed to display my weather data on my website.
Ed Finn
https://thecore.com/efinn/wx/wx.html