mcs1xapwire polling - 1 out of several sensors is slow

[ksdehoff]

Michael:

I'm wondering if you have any troubleshooting steps for mcs1wire - like increasing logging level or something like this. I have about 30 devices on this 1wire network now and one of them, the AAG wind instrument direction indicator updates very infrequently - once or twice day. The indicator next to it is green which leads me to believe mcsxap1wire thinks its healthy - but is there anyway via logging to confirm this?

Thanks Much
Ken

[Michael McSharry]

The info going to the IO Window for raw communications can be replicated to the reporting mechanism. If the debug checkbox is checked then the info goes to a file in the \data subfolder. If not checked then it goes via xap using the Homeseer.Event schema.


Edit your xapmcs1wire.ini file to add the following in the area where the debug key is located
ShowRawData=true

The green indication means that the device has acknowledged its 1-wire address and when queried it reported status without errors at least once since the last wildcarded polling. Anytime the device the reported status is invalid it wil go red. If the device never acknowledges its address then it will be yellow. Wildcarded polling occurs on startup and each time the Poll Devices button is used. If you use the Poll Devices button and the status remains green then the 1-wire DS2450 to PC interface is good. If your direction is not updating then you likely have a bad resitor connection on the input to the DS2450 or other similiar hardware failure on the sensor side. If the status changes from green then you likley have a problem with the wiring from the PC to the DS2450 on the instrument.

[ksdehoff]

Thanks much for posting that - I've got the raw data being logged and not seeing an obvious problem - can you see anything - I've cranked up the polling rate to 6 sec for troubleshooting and it appears all data is being returned correctly.

Thanks again!
Ken

7/3/2009 5:37:51 PM | xapmcs1Wire DS9x9x Port COM4: Port=COM4:7E00000004CBE61F:0 Address=D600000001067620 Family=DS2450 Voltage=0,0,0,3.58216403448539, 0
7/3/2009 5:37:51 PM | xapmcs1Wire DS9x9x Port COM4: Port=COM4:7E00000004CBE61F:0 Address=DB0000000159C21D Family=DS2423 Counter=629203/629214 0
7/3/2009 5:37:58 PM | xapmcs1Wire DS9x9x Port COM4: Port=COM4:7E00000004CBE61F:0 Address=D600000001067620 Family=DS2450 Voltage=0,0,3.5815390249485,3.5603668268864, 0
7/3/2009 5:38:05 PM | xapmcs1Wire DS9x9x Port COM4: Port=COM4:7E00000004CBE61F:0 Address=D600000001067620 Family=DS2450 Voltage=0,0,0,2.64324345769436, 0
7/3/2009 5:38:06 PM | xapmcs1Wire DS9x9x Port COM4: Port=COM4:7E00000004CBE61F:0 Address=DB0000000159C21D Family=DS2423 Counter=629284/629295 0
7/3/2009 5:38:11 PM | xapmcs1Wire DS9x9x Port COM4: Port=COM4:7E00000004CBE61F:0 Address=D600000001067620 Family=DS2450 Voltage=0,0,0,2.64293095292592, 0
7/3/2009 5:38:18 PM | xapmcs1Wire DS9x9x Port COM4: Port=COM4:7E00000004CBE61F:0 Address=D600000001067620 Family=DS2450 Voltage=0,0,0,2.64058716716259, 0
7/3/2009 5:38:21 PM | xapmcs1Wire DS9x9x Port COM4: Port=COM4:7E00000004CBE61F:0 Address=DB0000000159C21D Family=DS2423 Counter=629390/629401 0
7/3/2009 5:38:25 PM | xapmcs1Wire DS9x9x Port COM4: Port=COM4:7E00000004CBE61F:0 Address=D600000001067620 Family=DS2450 Voltage=0,0,0,2.64214969100481, 0
7/3/2009 5:38:31 PM | xapmcs1Wire DS9x9x Port COM4: Port=COM4:7E00000004CBE61F:0 Address=D600000001067620 Family=DS2450 Voltage=4.40631723506523E-02,0,0,2.60347722590982, 0
7/3/2009 5:38:37 PM | xapmcs1Wire DS9x9x Port COM4: Port=COM4:7E00000004CBE61F:0 Address=DB0000000159C21D Family=DS2423 Counter=629466/629477 0
7/3/2009 5:38:38 PM | xapmcs1Wire DS9x9x Port COM4: Port=COM4:7E00000004CBE61F:0 Address=D600000001067620 Family=DS2450 Voltage=0,0,0,2.60300846875715, 0

[Michael McSharry]

The analog readings from the DS2450 look to be changing as if the vane is moving. Are you not getting any changes in the xAP message or on the browser page for wind direction?

[ksdehoff]

The browser interface is what I have been looking at - it will update once or twice per day.

Thanks again
Ken

[ksdehoff]

To update this - I am observing the wind direction in mcsxap1wire and mcsdatabase and xapmcshub. None of these shows any updates eventhough the raw data logging from mcsxap1wire shows the direction changing. Is there something I need to tweak - significant digits or some such thing?

Thanks again for your help

[Michael McSharry]

The obvious thing to check is the "A"ccept checkbox for this sensor. There is also a debug option that will provide data to a log file in the \data subfolder.

[ksdehoff]

[Michael McSharry]

The segment you are showing is for the DS2450 third set of data which is the voltage reading for the first A/D.

7/14/2009 9:09:44 PM | xapmcs1WireDebug Format Analog D600000001067620=2.84379339284352E-02, port=COM4, accept=True, Channel=2, Type=20 0


What is of interest is the Channel=0 equivalent of the above. Channel=0 corresponds to the Wind Direction measurement. When the DS2450 is setup in the xapmcs1Wire browser the first in the sequence will give you the option to select Wind Direction, ph or Delete. This will be the one were the Wind Direction is selected.

[ksdehoff]

This is looking more like an instrument issue than anything else. I may come back here in a few days but need to see if the instrument is providing the right data, now that we've established it is providing data. It appears now that the data its providing doesn't line up correctly with the lookup table for direction.

Thanks again

Ken

[ksdehoff]

Difference between my working hub connected USB device and direct connect serial

The differences that I see are that the serial port is only attempting to poll Channel 5, while the USB port scans channels 2, 3, 4 and 5.

Any clues here!?
Ken

Serial
7/20/2009 6:08:24 PM | xapmcs1WireDebug GetSensorData D600000001067620, Hub=3200000004CBDE1F 1 20
7/20/2009 6:08:24 PM | xapmcs1WireDebug ProcessSensorQueue(1) D600000001067620, DoNow=True, Hub=3200000004CBDE1F 1,SelectedHub=3200000004CBDE1F 1, HubMod=3 0
7/20/2009 6:08:24 PM | xapmcs1WireDebug ProcessSensorQueue(2) Skip=False, Device=D600000001067620, Hub=3200000004CBDE1F 1,SelectedHub=3200000004CBDE1F 1, HubMod=3 0
7/20/2009 6:08:24 PM | xapmcs1WireDebug DS9x9x Port COM4 Device = DS2450 D600000001067620 0
7/20/2009 6:08:24 PM | xapmcs1WireDebug GetDS9097Data for port COM4 0
7/20/2009 6:08:24 PM | xapmcs1WireDebug Format Analog D600000001067620=2.65191546501869, port=COM4, accept=False, Channel=5, Type=20 0

USB
7/20/2009 6:11:45 PM | xapmcs1WireDebug PollTimer 1, Counter=0 0
7/20/2009 6:11:45 PM | xapmcs1WireDebug GetSensorData D600000001067620, Hub= -1 20
7/20/2009 6:11:45 PM | xapmcs1WireDebug ProcessSensorQueue(1) D600000001067620, DoNow=True, Hub= -1,SelectedHub= -1, HubMod=1 0
7/20/2009 6:11:45 PM | xapmcs1WireDebug ProcessSensorQueue(2) Skip=False, Device=D600000001067620, Hub= -1,SelectedHub= -1, HubMod=1 0
7/20/2009 6:11:45 PM | xapmcs1WireDebug DS9x9x Port USB1 Device = DS2450 D600000001067620 0
7/20/2009 6:11:45 PM | xapmcs1WireDebug GetDS9097Data for port USB1 0
7/20/2009 6:11:46 PM | xapmcs1WireDebug Format Analog D600000001067620=4.54530373083085, port=USB1, accept=False, Channel=2, Type=20 0
7/20/2009 6:11:46 PM | xapmcs1WireDebug Format Analog D600000001067620=4.56006958113985, port=USB1, accept=False, Channel=3, Type=20 0
7/20/2009 6:11:46 PM | xapmcs1WireDebug Format Analog D600000001067620=4.5752260624094, port=USB1, accept=False, Channel=4, Type=20 0
7/20/2009 6:11:46 PM | xapmcs1WireDebug Format Analog D600000001067620=2.38378637369345, port=USB1, accept=False, Channel=5, Type=20 0
7/20/2009 6:11:46 PM | xapmcs1Wire DS9x9x Port USB1: Port=USB1::-1 Address=D600000001067620 Family=DS2450 Voltage=4.54530373083085,4.56006958113985,4.5752260624094,2. 38378637369345, 0

[Michael McSharry]

Data is updated in HS (FormatAnalog) only when there is a value change. This indicates that the first 3 A/D readings did not change and the 4th did for the Serial case. Just noise should cause differences in the raw analog readings in a normal scenario. The USB case included the 4 A/D readings as the last line posted. You should be able to confirm by looking at the same data for the serial case.

[ksdehoff]

I'm running the driver that gets installed when the mcsxap1wire app runs the first time. I believe it is 4.00. There is a 4.0.2 on the vendor website - should I try this? I'm running out of ideas, with the driver and the actual device being the only things I haven't swapped out yet....

Ken

[Michael McSharry]

I know the more recent drivers from maxim-ic willnot work at all unless you are running from .net and xapmcs1wire is vb6.Another thing I observed isthat when ds2405 is connected to ds9490d - usb the voltage is held up at the device so it maintains its state when the drivers are logically switched to another adapter. Wnen ds9097u - com is used then the ds2405 looses its state.. It does not help you, but it does indicate that there are differences based upon the interface.

[ksdehoff]

I've had a breakthrough of sorts on this.

Using the 1 wire viewer I was able to inspect the 2450 in the working mode (usb/hub) and compare to the non-working mode.

I identified what appears to be missing initializations as the culprit.

The differences are in the A/D control and Status and also A/D calibration

Non-working:
A/D Control and Status = 08 8c 08 8c 08 8c 08 8c 08 8c
A/D Calibration = 00 00 00 00 00 00 00 00

Working:
A/D Control and Status = 00 0d 00 0d 00 0d 00 0d
A/D Calibration = 00 00 00 00 00 00 00 cb

I manually configured the working parameters in the serial hub (non-working) configuration and have the 2450 reporting reasonable values now.

The next question I guess is to drill down on the initialization to understand why initialization works on these 2 PCS with usb/hub and not with the serial hub.

Any suggestions!?