I’ve been reading this thread and can only provide my 2 cents worth that my “cronlazersnow” is running perfect and I have no issues. It ran great all through last season and is running great now. I’m very happy with the program and don’t want to download any modified versions as the current version is fine (at least for me). “If it isn’t broke don’t fix it”. Maybe there is some other related file that is missing or corrupt?
Perhaps some of the other 8 or 10 users can comment on their current experiences when the snow arrives at their locations.
HI Brian
Looks like 2.9 is working correctly. I checked the 2 boxes in WD “Setup/Advanced Misc” “Enable” USB Laser sensor and “use cronlaser.exe”, “Save & Exited” WD and when I restarted it “cronlasersnow” and “LRTimelog” started normally. I’m taking 5 minute readings now and they are correct. Also the logging in “Input Daily weather” “Snow Input” is updating correctly.
Dennis check to see if you have the file “HID.dll” located in your Weather Display folder. If so, copy and save this file to another location in case you need to reinstall it. Then delete this “HID.dll” file from your Weather Display folder and see if the program will run correctly. Just a thought … Worth a try.
Check out this forum link. Maybe helpful, maybe not …
What’s strange, is I haven’t really changed my configuration since everything was working last winter. Other than an occasional WD & Win10 update. I just plugged in the sensor and attempted to start cronlazersnow. and was baffled when it wouldn’t run. Which I now believe was due to that version of cronlazersnow not able to handle the error I’m getting.
Also, all of the Porcupine util’s work with no errors/problems.
And WD may actually be working without cronlazersnow showing it. Ive been busy with visiting relatives so I haven’t paid close attention. But it looks like cronlazersnow starts LRTimeLog which appears to be feeding the measurements to WD’s snow input screen.
I’m not sure if cronlazersnow.exe can run standalone (including AtUsbHid.dll) without a WD installation, but I tried it on another Win10 PC and got the same symptoms; cronlazersnow runs posting the error, but when started, runs LRTimeLog like it should.
I’m hoping to be able to spend more time with it tomorrow.
Dennis, I’m just grasping at straws but is your LRDemo program set on “centimeters” and set to read “continuously”? If this doesn’t resolve your problem maybe MikeyM or some other cronlazersnow user can chime in with some ideas for you to try.
Brian; Yes I have rebooted the PC, even tried cronlazersnow along with AtUsbHid.dll and LRTimeLog.exe in the same folder on another computer, not sure if that is a valid test. But got the same results, error in cronlazersnow.
Jeff; For me LrDemo starts up in Single Measurement Mode and that setting is not “saved” unless “Save to Rangefinder” is pressed. I was hesitant to write to the rangefinders nonvolatile memory, however being desperate, I saved the Continuous Measurement Mode. But it didn’t help.
Note; I have also written to Richard at Porcupine Labs asking for help.
In your WD folder there should be a file called “AtUsbHid.dll”. What is the date/time of this file and what is the size of the file? Mine and MikeyM’s is dated 6/20/14, 10:22 pm and is 72 KB in size.
I received a reply from Richard of Porcupine Labs.
From the relative lengthy description of my situation I sent, he does not feel there is anything wrong with my LR4 rangefinder. Quite frankly, I have to agree with him as all his utilities run and work properly.
Although Jeff’s suggestion to send a link to this forum was a good one, I did not as I had already sent my email. And I’m not sure it would help as Richard would have no idea as to the internal workings of cronlazersnow, which is primarily what this discussion is about.
there might be another way
where the LRTimelog.exe is run to output the data to a file (which WD reaeds in) instead of to the console
if you run that program from a command DOS prompt and use
LTTimelog.exe → outfile.txt