1-wire reader & laser sensor

does that mean you got it to work?

No. It is not working.

Not working how exactly
Any error message now?
The more info you can provide the better
Saying it does not work does not help

Hi.
You also need to tick “enable to calculate current snow depth” in the dallas 1 wire reader vers 5.7, as i remembered.
this for auto reading, from, also try set lr4 program to every 10 sec only for test.

Also when it worked for me no dallas driver was nessesary to install.

Good luck.

See also some info here:


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.

Thanks for your time and consideration

I need to rely on others who have one for input
do others see a data stream flowing in the dallas1wirereader?

Not me, seems I’m in the same boat. Data flows from the sensor but not into the 1 wire.

rick

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

Count me in as a volunteer tester of new dallas1wirereader.exe versions.

Again please note that previous forum contributors had a similar problem using Windows 7 and things were fixed following their upgrade to Windows 8.1

Now it seems to be a problem with Windows 10.

Also you may remote in to my PC anytime using TeamViewer or Google Remote Desktop.

Thanks

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.

Rick

try this test program
http://www.weather-display.com/downloadfiles/cronlazersnow.zip
to see if the raw data flows

Thanks, I’ll try this evening.

Tom

It finds it but no data flow.

Devices found 0417 DD03
Lazer snow connected 0417 DD03

Using lrtimelog.exe to read the sensor on win8.1

I will need to use a different HID USB component then by the looks

I will then hold off until your next version is released…Thanks.

I need to know the hex value of the PID and VID using windows device manager

I do not know how to find the hex value of the PID and VID using windows device manager.

I apologize for my ignorance.

Also please be aware something has changed in your website’s security certificate.

The connection warning I received is attached and it is occurring no matter where I log in and despite using multiple platforms.

Thanks.


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}

Driver Date: 06/21/2006

Driver Version: 10.0.14393.82

Driver Provider: Microsoft

Driver Section: HID_Raw_Inst.NT

Driver Rank: 0xFF1004

Matching Device Id: HID_DEVICE_UPR:FF00-FFFF

Outranked Drivers: input.inf:HID_DEVICE:00FF1005

Device Updated: false

Parent Device: USB\VID_0417&PID_DD03&MI_00\8&27c7df8b&0&0000

Found under Keyboard:
Device HID\VID_0417&PID_DD03&MI_01\9&280bb056&0&0000 was configured.

Driver Name: keyboard.inf

Class Guid: {4D36E96B-E325-11CE-BFC1-08002BE10318}

Driver Date: 06/21/2006

Driver Version: 10.0.14393.0

Driver Provider: Microsoft

Driver Section: HID_Keyboard_Inst.NT

Driver Rank: 0xFF1003

Matching Device Id: HID_DEVICE_SYSTEM_KEYBOARD

Outranked Drivers: input.inf:HID_DEVICE:00FF1005

Device Updated: false

Parent Device: USB\VID_0417&PID_DD03&MI_01\8&27c7df8b&0&0001