Hi Brian, thanks for the reply, the auto detect doesn't do anything for me, the popup that shows in your video, nothing also there is nothing happening in that small info window either like it does in your video. I made a video
here to show whats not happening
I am using 10.37S B130.
I have been having issues ever since my baro in the Envoy gave in, i.e, If i want to adjust any mainscreen items, when i goto Settings/Advanced-Misc/Mainscreen etc to enable customise, as soon as i do that, some images on the mainscreen change in size (back to default sizes) and no matter what i try, i cannot resize them. I have to restore registry to get it back, it just happened again when I was making sure I was writing down the correct names of each stage...
I think it stems from restarting WD so many times when trying to troubleshoot the baro issue that a conflict has gotten in there.
Something also happened yesterday too when I was trying to troubleshoot this WLL setup issue, restarting WD a few times as i tried to see if unplugging the WL USB would help, then reboot WD, then see if WLL would auto detect, on one of the WD restarts, the mainscreen background colour went black (assume to default), and i had to use a backup file to restore that.
I can do a video of the above issues if required, well, not the black background cause I'm not sure how to produce that one, but the mainscreen one i can do.
EDIT: keeping reading please and see how I got it working...
This is the error, I see in the WLL cron when i click on auto detect, now that I've manually started the program
ERROR: Access violation at address 00000000 in module 'crondaviswll.exe'. Read of address 00000000 at time/date 08:30:22 16/09/2021
WD wont start the WLL cron
manually ran the cron, opened the cron window, clicking auto detect in cron still doesn't do anything
manually adding the IP in the cron window and clicking test does work ok
I then clicked enabled. saved, closed WD, the cron didn't close automatically.
I kept that cron open, ran wd, the cron was working, ie something was happening
I then closed WD, this time the cron closed, so opened WD again and the cron opened ok
So I closed WD again, unplugged the WL USB, opened WD, the cron auto opened and showed it working,
closed that and WD is now grabbing data ok from WLL.
Weirdly though...
Soil moisture hasn't worked in about 2 years or more, its always been at 200, its now at 187.2 and dropping so not sure whats going on there.
The Leaf wetness is at 0.1, never seen that before, its always been 0 to 15, no decimal place
I still see that access violation error when I click auto detect, yeah, I know, no reason to click it anymore
but just thought you'd want to know