1-Wire .NET xAP Connector

Michael McSharry · #1 October 7th, 2009, 03:33 PM

Version 3 of xapmcs1wire has been posted at [http://board.homeseer.com/showthread.php?t=101056]. This is a .NET implementation that no longer requires the Microsoft JVM. It is based upon the .NET framework and uses J# libraries and the latest 1-wire drivers from Maxim-ic. It has been tested with Vista X64 and XP32.

If you do not already have the prequesites installed they can be found as the following links:
The .NET framework 2.0 needs to be installed http://www.microsoft.com/downloads/d...displaylang=en
The .NET J# 2.0 redistributable needs to be installedhttp://www.microsoft.com/DOWNLOADS/d...displaylang=en
The 1-wire drivers need to be installed http://www.maxim-ic.com/products/ibu...tmex/index.cfm

For those upgrading I suggest that you install the V3 xapmcs1Wire in a new folder by expanding the zip file. Copy the old xapmcs1wire\config folder to the new location. Everything is backward compatible with the only issue I had was the new drivers identify the DS9097U differently so you will get " Desc=Specified adapter name "{DS9097U}" is not known Line 100 Specified adapter name "{DS9097U}" is not known " message. You can correct this by using the Search for Ports button. The name the new drivers gave for my adapter is DS9097U_DS9480 and I no longer had a default port (i.e. no < and > bracket in the Comm Port(s) box.

Multiple adapters are now fully supported.
The Comm window is now browser rather than form so is can be remotely viewed
A messages page is available from the tray for hard copy of the errors that are also delivered via xAP Homeseer.Event schema.

The browser display contains a set of links at the top. These are read from the \HTML\xapmcs1wire\Links.htm file. You will need to edit this file to put the links of interest to you. My links can be used as an example. The option to use Homeseer Header was not tested as my 1-wire environment is not on the same computer as HS2.

While we are progressing by moving from MSJVM to the .NET J#, Microsoft has elected to voluntarily discontinue J# with the last release associated with the .NET 2.0 framework. This means someday the same issues that we now have with MSJVM will exist with MS J#. This is again a Dallas Semiconductor (Maxim-ic) decision to use J# as it was to use MSJVM.

Pete · #2 October 8th, 2009, 06:13 AM

Michael, I am currently running two instances of XaPMCS1Wire. One is located inside of the HS directory and the other one is outside. Are you stating that both of these (new version) should be running outside (autonomously) of the HS directory?

Michael McSharry · #3 October 8th, 2009, 01:44 PM

My suggestion is that each xAP application have its own folder to avoid any issues of the same file being overwritten by two applications and to make maintenance update configuration control easier. It is only a suggestion.

mloebl · #4 October 8th, 2009, 08:27 PM

Hi Michael,

I like the new version and happy to see no more of the MS legacy Java (was a pain to always try to hunt down the MSJavaVM after a rebuild.) One issue though, last night it started out ok, but then started giving me the following error in the logs:

Code:

10/8/2009 7:24:01 PM  mcs.OneWire.MIKEHOME>xapmcs1wire  setupds2408 line 30 object reference not set to an instance of an object.

Then it would no longer consistently send updates (only about 2 of my devices would update.) Any thoughts on what it might be and what I could send you to help debug it? I've gone back to the last version of the VB6 plugin and it's ok for now.

Thanks again!

-Mike

Michael McSharry · #5 October 9th, 2009, 02:43 AM

The DS2408 code is a special case as it talks directly to the adapter rather than going through the Java library. I did not have any of these in my system when testing. Can you give the attached a try.

mloebl · #6 October 9th, 2009, 06:08 PM

Hi Michael,

Thank you for the quick response, but getting a new location where it's failing now:

Code:

10/9/2009 6:06:45 PM  mcs.OneWire.MIKEHOME>xapmcs1wire  setupds2408 line 80 object reference not set to an instance of an object.

-Mike

bachelet claude · #7 October 11th, 2009, 09:00 AM

Hi mikael,
i am now using V3.0.0.2 on a FIONO 330 with Windows 7 64 bits and it is workink perfectly.
Also, it seems the new Xap plugin isn't going deaf anymore.

Thanks for all the good work.

Claude

Pete · #8 October 11th, 2009, 11:39 AM

I switched over to the new XaPMCS1wire browser yesterday. All working well. Thanks Michael!

mfisher · #9 October 11th, 2009, 05:33 PM

Updated to v3.0.3 from 2.7.6 as outlined in your post:

Uninstalled DS9490 using Device Manager
Uninstalled Maxim 402beta driver
Installed J#
Installed Maxim 402 driver
Unzipped xapmcs1wireNet to a new dir
Copied the following ini files from orig Config dir to new Config dir:
- includes.ini
- includes.ini_bck
- mcsXap1Wire.ini
- mcsXap1Wire.ini_bck
- mcsXap.ini
- mcsXapDevices.ini
- mcsXapDevices.ini_bck
Ran xapmcs1wireNet
Fiddled around with ports and finally got it to read my devices.

However, 3.0.3 ignores the 2.7.6 ini settings for Cal, rev and Poll ms.

Two screen shots are included below for your review: the first is v2.7.6 just before the upgrade and the 2nd is v3.0.3 after getting it 'working.'

After reviewing the ini files from both versions, I decided to try from scratch. I removed all files from the Config dir and started xapmcs1wire. After finding the 'com' ports and searching for devices, I saved and restarted. All of these initial settings 'stuck' and a review of the new ini confirmed that the device info was saved.

I then changed the Cal and Poll ms settings for several devices, saved and restarted - these settings did not 'stick' and reverted to 0!

I did verify that the Cal and Poll ms values are being written to the ini file, but they don't seem to get read from the ini on startup...

Any help would be appreciated!

Michael McSharry · #10 October 11th, 2009, 06:24 PM

Did the Messages page show you anything that may indicate why the settings was not being restored. It looks like it got part way though init and then raised an error which should have shown on the Messages Page.

mfisher · #11 October 11th, 2009, 09:12 PM

Only messages shown are:

Code:

10/11/2009 6:03:31 PM | 10/11/2009 6:03:31 PM | Using xAP port 2346 
10/11/2009 6:03:31 PM | 10/11/2009 6:03:31 PM | InitINIVariables Line 20 An item with the same key has already been added.

Then, if I change the Cal value for a device and save I get this:

Code:

10/11/2009 6:04:34 PM | 10/11/2009 6:04:34 PM | Status ClientRequest Line 1500 Collection was modified; enumeration operation may not execute.

I've attached two ini files:
v2.7.6 (before upgrade)
v.3.0.3 after 1 run, change Cal & poll for 1 device, save then close