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
I just got out an old laptop that I haven’t updated Windows 10 since May of 2018 and cronlazersnow runs properly.
It is Windows 10 Version 1709 Build 16299.125.
I cannot use this laptop as my as my Weather PC but I can use it to test cronlazersnow.
My thought is to now update this laptop to the current version of Windows 10 to confirm my cronlazersnow issue is due to an update. Is there information I should gather to assist troubleshooting before doing the update?
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
I guess I was hoping that now that you know there is a problem between your cronlazersnow and the current version of Windows 10, that you might be able figure out how to fix/update cronlazersnow.
In response to your “there might be another way”, I don’t understand how to pursue this.
How do I get WD to input outfile.txt especially since it’s output is formated differently.
It’s my understanding, that a file from a programs redirected output remains open by the OS until the program ends, so this output file is unavailable until LRTimeLog is ended. So I would have to start/stop LRTimeLog for every reading.
LRTimeLog creates its on log file however this, also, is not available until LRTimeLog ends.
Please attempt to update cronlazersnow to be compatible with Windows 10.
Please attempt to update cronlazersnow to be compatible with Windows 10.
Windows has made breaking change
I can’t actually perform miracles
what was working, was the ability to be able to share the usb connection, i.e cronlazersnow was piggy backing on the LRTtimelog incoming data flow
windows has it looks like stopped that USB sharing ability
by the looks
and there is not much I can do about that
there might be some setting somewhere in windows (USB settings or similar) that can be tweaked
maybe google?