My LR4Sample programs(eg LRsimple) log data at whatever interval I set in the LRDemo app.
In WD despite the fact that the Dallas1wirereader.exe sees the Fluke 414Dand data is actively being sent from it I do not see any flowing data into the Dallas1wire reader screens, the WD main screen snow section or in updated customtext.txt or customtext.php files
There is an issue with the data NOT flowing into the Dallas1wirereader.exe (I should see it in one of the boxes?)and subsequently the WD app.
I have tried many suggestions but am stuck using an HP PC Stream 14 Laptop running Windows 10. Devices and drivers all show that they are working fine in Device Manager.
By the way I can take manual snow depth measurements and log them…it just does not happen automatically.
this suggests to me that the latest hardware has changed somehow to make it not work anymore
so that means what I need to do is make a new .exe program to see if I can get that to read the data
I will need testers
it wont be a new dallas1wireader program (I lost the source code for that with a hard drive crash)
but a new cron program just to read the lazer snow sensor data
(and so option in WD to use that )
Why not read from the log file. Set lrtimelog to read once an hour. Have wdisplay read the log file and subtract the last reading from the first reading to get the snow depth. You should be able to extract cm’s per hour etc from that as well. The file is in the following format.
2017-12-03 15:42:43.161, 107.6 cm
Probably not that simple but it should do away with having to use the 1-wire.
yes, I know about the forum certificate error
I am not the forum admin, so I can not help with that, sorry
re vid/pid hex
simply run windows device manager, then see the usb/hid devices, find your device (the lazer sensor) and it should show the vid/hid values there (properties)
I am including two devices as supposedly the Fluke 414D may be recognized as a keyboard in the Dallas1wire…I am not certain I am giving you the correct devices.
Found under HID device:
Device HID\VID_0417&PID_DD03&MI_00\9&14cb3d3&0&0000 was configured.
Driver Name: input.inf
Class Guid: {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}