xapmcs1Wire - 1 Wire (DS9097U / DS9490D) xAP Node

[Michael McSharry]

The DS2450 is now structured as
0) Wind Directiion
1)
2) Voltage/Switch
3) Voltage/Switch
4) Voltage/Switch
5) Voltage/Switch
6)

I believe the best way to do this is to make a new pH type and allow the first DS2450 value be selectable as either Wind Direction or pH. When selected as pH then the first channel A/D voltage (V) will be computed using the equation

pH = 14 - (V*4) + Calibration

Please confirm this is what you want. If you are planning on using the hobby-boards HVAC monitor then the scaling will not be correct. Are you going to use it or some other A/D input device such as a DS2438 variant?

[mloebl]

The DS2450 is now structured as
0) Wind Directiion
1)
2) Voltage/Switch
3) Voltage/Switch
4) Voltage/Switch
5) Voltage/Switch
6)

I believe the best way to do this is to make a new pH type and allow the first DS2450 value be selectable as either Wind Direction or pH. When selected as pH then the first channel A/D voltage (V) will be computed using the equation

pH = 14 - (V*4) + Calibration

Please confirm this is what you want. If you are planning on using the hobby-boards HVAC monitor then the scaling will not be correct. Are you going to use it or some other A/D input device such as a DS2438 variant?

Wow you're good... I'm using the Hobby Board HVAC monitor, however I modified Input 1 it to be able to read the lower DC voltages based on a modification they did for someone else. The only thing that seems funny is the Calibration may be off; is that in V on pH?

Thank you again,

-Mike

[mloebl]

Wow you're good... I'm using the Hobby Board HVAC monitor, however I modified Input 1 it to be able to read the lower DC voltages based on a modification they did for someone else. The only thing that seems funny is the Calibration may be off; is that in V on pH?

Thank you again,

-Mike

Never mind, if that's a calibration offset in pH that accepts +/- values it works.

-Mike

[fdemange]

LCD 4*20 bug and hub problem

Hello,
2 problems :
the first one :
I have a LCD display (4*20) which come from hobby-boards, i'm using the MCS1wire v2.0.46. When i send a message to the LCD display, like 111111111111111111112222222222222222222233333333333333333333 44444444444444444444, the line 1 is good(111...), the line 2 is overwriten by the data of the line 3 (2222...at the beginning and in a second time, replace by 3333...) , the line 3 is less blank and the line 4 is good (4444....)
the problem is the same with the v1.1.35

the second :
the hobby boards 6 channel hub doesn't work very well. the red leds are never switch on (with or without cable connected) and the devices presents on the lines are not detected
the hub is ok with the v1.1.35

thank's
Fabrice

[Michael McSharry]

I'll contact Eric at hobby-boards.com to get the address map for the first position of each of the 4 rows of his 4x LCD. The data I have from another source apparently is not correct or different than his. If you provide some debug output it may provide a clue as to why V2 is not working for you.

[Michael McSharry]

Fabrice & Mike,

V2.0.48 contains the requested changes for LCD and pH. Neither has been tested beyond the proper opeation of the setup screens so give me feedback if there are problems.

Mike, you will need to provide your own ph.gif icon.

[mloebl]

Fabrice & Mike,

V2.0.48 contains the requested changes for LCD and pH. Neither has been tested beyond the proper opeation of the setup screens so give me feedback if there are problems.

Mike, you will need to provide your own ph.gif icon.

Hi Michael,

Thank you for the fast work on this. I see the new device type with ph.gif (just swapped in blank3.gif for now.) It's reading the sensor correctly for the voltage, but doesn't seem to be applying the formula; ie still spitting out the voltage value of 1.05556298161288.

Thank you,

-Mike

[Michael McSharry]

The voltages will continue to report, but there will also be a type .ph messages that reports on any change of 0.01 or more in the pH reading.

[mloebl]

The voltages will continue to report, but there will also be a type .ph messages that reports on any change of 0.01 or more in the pH reading.

Hi Michael,

This is the source I'm grabbing:
mcs.onewire.mikehome:xapmcs1wire_ph sensor.3a0000000628c720.ph.0

However it seems to be sending the voltage unless this is the wrong one?

Thank you,

-Mike

[fdemange]

hi Michael,
the LCD 4*20 is ok, the v2.0.48 has solved the problem of the third line. Thanks for your work.
my hub problem is solved too (a polling interval very long...)
the last problem is the same than Bdickhaus, HS2 v2.1.143, HS is not able to send an other text than "unknown".

[Michael McSharry]

I changed my wind direction sensor to be pH and put a high calibration of 8 just to assure the calculations are correct. I received what I expected in the following message for a first channel voltage reading near 0. The other thing of note is that my message does not have a ".0" at the end of the address field. I think this means you are reading the voltage channel 0 rather than the computed pH. You probalbly have a WindDirection type of the same serial number. It may be rejected previously so uncheck the "R" for this line and change its type to pH. Restore the other one from pH to Voltage. You may want to start over with this device by "R" rejecting all variants of it. Do a couple saves and then search for devices. Change the WindDirection to pH.

xap-header
{
    v=12
    hop=1
    uid=FF000518
    class=xAPBSC.event
    source=mcs.OneWire.MCS6:xapmcs1Wire_Wind_Direction.6100000001095420.pH
}
input.state.1
{
    state=OFF
    displaytext=<table><td><img alt='pH' src='/images/sensors/ph.gif' height='16' width='16'><img alt=' ' src='/images/sensors/blank3.gif'></td><td valign='middle' align='left'>21.83</td></table>
    text=21.83
}

[mloebl]

I changed my wind direction sensor to be pH and put a high calibration of 8 just to assure the calculations are correct. I received what I expected in the following message for a first channel voltage reading near 0. The other thing of note is that my message does not have a ".0" at the end of the address field. I think this means you are reading the voltage channel 0 rather than the computed pH. You probalbly have a WindDirection type of the same serial number. It may be rejected previously so uncheck the "R" for this line and change its type to pH. Restore the other one from pH to Voltage. You may want to start over with this device by "R" rejecting all variants of it. Do a couple saves and then search for devices. Change the WindDirection to pH.

Michael,

Thanks again, I think that was it! You were right, I never noticed before but there was a wind direction type on that same serial number. As soon as I changed it, it showed up. I'll play with it some more and see how it goes. Thanks again for adding it, I really appreciate it.


-Mike

[Kbevo]

One Wire Error...

Michael, for sometime now I have been getting this error several dozen times a day:

11/1/2006 7:32:11 AM ~!~mcs.onewire.slvrs22g>xapmcs1wire~!~selecthubbranch 3f00000002800d1f for 3f00000002800d1f 0 - line 590 com.dalsemi.onewire.adapter.onewireioexception: onewirecontainer1f verify on command incorrect

I saw this post and understand that it probably is a sensor having problems on that branch. The only thing on that branch is my Wind Instrument and the readings seem to be ok for that device. One difference that I can think of is that I am polling the wind instrument every 30 seconds where as all my other devices are on a 5 minute interval. Can you think of anything that can/should be done?

Thanks
Gary

[Michael McSharry]

I get them infrequently as well. I looked into trying to figure out why, but I could not determine anything. When I look back at my log over the past 2 days I see yesterday with 4 instances and then today with 2 so far. It is always the same hub branch. In my case this branch has a single DS18B20 on it that is part of my telco wiring harness. Failures are usually in the early morning hours so it is not a telco signal interfering.

I'm running 10 active hub branches and this one is in the middle of the access sequence. It does seem to be related to what is on the backside of the branch, but I have no idea as to what it is other than knowing that if I put a bad sensor on a branch it will exhibit the same behavior consistently.

[p51diaz]

MCS
This q will probably show my ignorance, but here goes, any chance your plug-in can be modified to work with the HA7Net unit?
thx