1-Wire .NET xAP Connector

[Michael McSharry]

I see, the Program icon and not the tray one. It was the quotes in the .ini file that caused the problem. I uploaded the full version 3.0.0.6 and that should take care of the issues. Thank you for persisting.

[mfisher]

Windspeed units for mph, km/h and knots are now all working correctly.
Hey, program icon fixed - cool!
Should I remove the quotes from all params in the .ini file or just leave them alone?

Thanks again for the awesome support!

[Michael McSharry]

Thanks for the confirmation. The quotes are fine there. I just was not previously looking for them.

[ksdehoff]

Michael:

I tried an upgrade to this new version and ran into a couple issues. I've gone back to the previous rev for now but I'll try again over the weekend.

In my first attempt I tried to migrate using the existing config files. I hit an interesting problem in that the only sensors that were 'red' were the ones I had accepted. Any sensor I rejected (like individual voltage readings) was green.

So I then tried a new config. In this mode I see all my devices and they were green. Unfortunately after saving my config and restarting the driver the configuration was empty.

I'm working other issues at the moment so I'll hang on and see what other folks come up with and try again in a couple days

Ken

[Michael McSharry]

The Message page should be viewed when thngs are not as expected. This page is also a .txt file in the \Data subfolder path. It only persists between restarts.

[Michael McSharry]

I tested the .NET version with a DS2408 AAG LCD and all was working as expected. What was not working was the xapbsc.cmd recognition so the only way to command outputs was locally. This was fixed in V3.0.0.7.

I also noticed that the heartbeat only happened once. This should have the effect of the application being only able to transmit and the xAP hub will stop trying to forward messages to it.

I will upload it later as the upload site is not accepting things now. It is temporarily attached here.

[mloebl]

Hi Michael,

LCD is working perfectly, thank you! However still having the same problem with certain devices not updating when it hits HS. The Barometer is working perfect... and if I look the UI for xapmcs1wire, it's definitely updating the values there.
I think I did find the problem however, did you change it in the new version to respect spaces in strings? Here's what I found:

.NET:
mcs.OneWire.MIKEHOME:xapmcs1Wire_Bedroom Temperature.4A0008008B693710.Temperature

VB6:
mcs.onewire.mikehome:xapmcs1wire_bedroomtemperature.4a000800 8b693710.temperature

I found that by watching the xFx message viewer that the messages were indeed different. My devices in MCSXap1wire did have spaces for devices that seemed to stop working. I went in, removed the spaces, and like magic it started working

-Mike

[Michael McSharry]

I did not do anything intentionally, but if I recall the xAP spec does not allow spaces in the address so I should be removing spaces automatically. I will look and update to assure there are no spaces in the address.

[CouchPotatoe]

Michael - you're right that originally we prohibited spaces in addresses but after several people questioned why this was necessary we relaxed this for v1.3 and it is now permitted. As you're running as a xAP v1.3 application you can happily use spaces should you wish.

Mike - a source name that does include a space will of course be different to one without and would cause the issues you mention

[mloebl]

Thanks guys for the clarification I let out a groan when I realized how simple it was with the spaces when I looked at the viewer... I should have known better, but was spoiled by using them in the past. Since at some point, some version had detected it and relayed it with the spaces back in 2008, I didn't seem anything new coming in to MCSXap so didn't see anything unusual.

In any case great job Michael, I really appreciate all the hard work and quick help responses that you do!

-Mike

[mfisher]

xapmcs1wire crash

It looks like the issue began at 00:17:45 and then errored two entries later (last entry.) Here's the comm data:

15 00:16:52 | Port=USB1 Address=F4000000B16DD626 Family=DS2438 Temperature=72.64845 Humidity=27 Voltage= 5.04 1.66 0 6 | 
15 00:16:53 | Port=USB1 Address=DC0000019C815628 Family=DS18B20 Temperature=24.875 | 
15 00:16:54 | Port=USB1 Address=C90000019C96AB28 Family=DS18B20 Temperature=24.0625 | 
15 00:16:55 | Port=USB1 Address=AF0000019CA03128 Family=DS18B20 Temperature=9.75 | 
15 00:16:57 | Port=USB1 Address=82000000B1628726 Family=DS2438 Temperature=72.45475 Humidity=0 Voltage= 5.03 5.7 0 6 | 
15 00:16:58 | Port=USB1 Address=6100080154E84010 Family=DS1920 Temperature=25.0625 | 
15 00:16:59 | Port=USB1 Address=480008015517C710 Family=DS1920 Temperature=9.9375 | 
15 00:16:59 | Port=USB1 Address=2B00000009F8491D Family=DS2423 Counter=259/259 | 
15 00:17:03 | Port=USB1 Address=39000000B16DCF26 Family=DS2438 Temperature=48.8875 Humidity=56 Voltage= 5 2.6 0.1 26.56631 | 
15 00:17:04 | Port=USB1 Address=7700000009F30A1D Family=DS2423 Counter=20799824/20799850 | 
15 00:17:16 | Port=USB1 Address=7700000009F30A1D Family=DS2423 Counter=20799835/20799861 | 
15 00:17:31 | Port=USB1 Address=7700000009F30A1D Family=DS2423 Counter=20799849/20799875 | 
15 00:17:45 | Port=USB1 Address=C9000000037B1F29 Family=DS2408 | 
15 00:17:46 | Port=USB1 Address=F4000000B16DD626 Family=DS2438 Bits= | 
15 00:18:16 | Port=USB1 Address=F4000000B16DD626 Family=DS2438 Bits= F4000000B16DD626 Not Present / OneWireContainer26-Bad CRC during read.107 Temperature=72.64845 Humidity=0 Voltage= 0 0 0 13 |

No indications of the failure in xapmcs1Wire.txt:

False 11/11/2009 9:14:02 AM | 11/11/2009 9:14:02 AM | xapmcs1Wire Using xAP port  1028

A restart of xapmcs1Wire resolved the issue.

[Michael McSharry]

If no more messages appear in the comm log after what you posted then you have use the mcsXap Trigger to detect the loss of messages from xapmcs1wire and then take action such as restarting it. If this does reoccur then some additional logic can be added around the DS2408 processing to get some hints as to what may be happening.

[mfisher]

This crash occurred again last night. It seems that if there is an error on the 1-wire bus, xapmcs1wire crashes. The U/I is still functional and it looks like xapmcs1wire continues to send xAP packets (as I only get one xapmcs trigger when this occurs), but no 1-wire processing occurs and all the devices remain in their last state.

Would it be possible for xapmcs1wire to re-init the 1-wire bus and driver if a serious error is encountered?

[Michael McSharry]

I know it is not unusual for me to see verify errors as I switch the hub channel and these are transient. Based upon your experience what would you consider to be a serious error? I suspect it will involve some category of errors that persist.

With the older COM drivers I know I had to be careful when using the Visual Studio degugger. If I stopped the application for debugging without gracefully releasing the connection to the driver my only recover option was a reboot of the computer.

The current design attaches to the adapter at startup so it will not support an environment where multiple applications want to attach. What I have been considering is to make it more dynamic and only attach when actively used. This approach may also overcome the problem you are seeing. The problem with it is that it introduces complexity when the adapter is in use at the time the polling is scheduled.