1wire support

[hari]

when you add the interface to the core, it of course needs a quick reload to start the OneWire DCE device. When this is started, it iterates over all temperature devices found by owfs and tells the general info plugin to create the child device if it does not yet exist. These won't be active till the next quick reload. Maybe that adds to confusion?

[DragonK]

when you add the interface to the core, it of course needs a quick reload to start the OneWire DCE device. When this is started, it iterates over all temperature devices found by owfs and tells the general info plugin to create the child device if it does not yet exist. These won't be active till the next quick reload. Maybe that adds to confusion?

So the steps are?

• Connect 1wire interface to core
• Add the 1wire interface in webadmin using template 2161
• Select the port the 1wire interface is connected to
• When prompted do a quick reload
• Once the sensors are detected, another quick reload is needed
• Now you should have Multilevel Sensors as childs, for every sensor connected to the 1wire bus, in the webadmin
• Choose the rooms that the sensors are in and add to the floorplan.
• Another Quick reload should do the job

Karel

[Gangsingen]

So the steps are?

• Connect 1wire interface to core
• Add the 1wire interface in webadmin using template 2161
• Select the port the 1wire interface is connected to
• When prompted do a quick reload
• Once the sensors are detected, another quick reload is needed
• Now you should have Multilevel Sensors as childs, for every sensor connected to the 1wire bus, in the webadmin
• Choose the rooms that the sensors are in and add to the floorplan.
• Another Quick reload should do the job

Karel

Spot on, that exactly how I got mine working!

[twodogs]

When do you see the interface show "registered" in LMCE admin?
Where in the sequence do you plug the sensor/s into the interface adapter?

[Techstyle]

Do you have to regen the orbiters?

[Techstyle]

Does anybody know how to display the Temp in Deg F instead of C?

[huh]

If you go into the web admin pages -> show devices tree -> 1wire and then click on "view whole log", I have a couple errors:

Code Select Expand


01 02/11/12 1:33:42.167 TranslateSerialUSB pci0000:00/0000:00:13.0+1 result /dev/ttyUSB2 <0xb78686d0>
01 02/11/12 1:33:42.167 Opening port: /dev/ttyUSB2 <0xb78686d0>>


lsusb gives me this:

Code Select Expand


Bus 005 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC


dmesg gives me this:

Code Select Expand


[  785.564300] ftdi_sio 5-1:1.0: FTDI USB Serial Device converter detected
[  785.564371] usb 5-1: Detected FT232RL
[  785.564376] usb 5-1: Number of endpoints 2
[  785.564381] usb 5-1: Endpoint 1 MaxPacketSize 64
[  785.564386] usb 5-1: Endpoint 2 MaxPacketSize 64
[  785.564390] usb 5-1: Setting MaxPacketSize 64
[  785.566328] usb 5-1: FTDI USB Serial Device converter now attached to ttyUSB2


Any idea why my temperature probes aren't discovered?

[hari]

if you can't even read them out with owfs, you probably have a short circuit on the bus.. this happened to another user. So as a first debug step I'd recommend to see if owfs gives you values. If that works fine, continue to debug on the lmce side

[Gangsingen]

Where in the sequence do you plug the sensor/s into the interface adapter?

I had mine plugged in all the time!

[huh]

if you can't even read them out with owfs, you probably have a short circuit on the bus..

How else do I check for this?  I have (2) of the LinkUSBi's, (5) temperature sensors and a pile of cat5 cables...  tried both LinkUSBi's and 3 of the temperature sensors.  The usb device appears in the log file as posted above, but cannot get my temperature sensors to load.

Thanks

Edit:
I tried adding a MD to see if I had the same experiences as others- that the sensors would start populating.  Unfortunately, it's been 6+ hours and while my device is spawned, no such luck with the sensors:

Code Select Expand


1 02/12/12 20:14:23 124 (spawning-device) Starting... 1
1 02/12/12 20:14:23 124 (spawning-device) Found /usr/pluto/bin/OneWire
01 02/12/12 20:14:24.280 TranslateSerialUSB pci0000:00/0000:00:12.0+2 result /dev/ttyUSB2 <0xb76e96d0>
01 02/12/12 20:14:24.280 Opening port: /dev/ttyUSB2 <0xb76e96d0>


[huh]

OK- tried something new-

Added:  deb http://mirrors.rit.edu/ubuntu/ precise main universe to my sources by added it to here:

Code Select Expand


nano /etc/apt/sources.list


Then, started the owserver using this:

Code Select Expand


owserver --device=/dev/ttyUSB2 -p 4304


Then, started the owhttpd web client using this which creates a webpage on port 3000:

Code Select Expand


owhttpd -s localhost:4304 -p 3000


Most of the instructions are from here:
http://www.openremote.org/display/docs/OpenRemote+2.0+How+To+-+1-Wire+Sensors

The webpage shows (1) sensor with a temperature, so I got greedy and added another (2) to make sure it was working... unfortunately it still only says I have (1) thermocouple attached after restarting my core.

Edit:  Leaving breadcrumbs...  much quicker than core reboot...

You can kill a process using the follow:

Code Select Expand


/usr/pluto/bin/ForciblyKillProcess.sh OneWire


And restart using

Code Select Expand


/usr/pluto/bin/Spawn_Device.sh 124

Where 124 is MY device id- yours is likely different...

[hari]

you can't run them in parallel, you need to stop the owserver first

[huh]

OK- I blew away my system and tried again.  I followed exactly per the wiki and was surprised when one after another sensors were added to my 1-wire device... until number 5.  At number 5 the device died (per the log) and I could not get it to restart- either manually or by restarting the computer.

So, I deleted that device and created a new 1-wire device again following the wiki.  Whereas before the temperature sensor was found after a few minutes- now been 30 minutes or so and no luck...  Per the log it looks like everything started correctly and per dmesg I'm set to the correct USB port...

Going to let it run overnight.

Edit:  As a side now- although I have run Diskless_CreateTBZ.sh, I have not yet installed a MD.  I have (2) qorbiters and a web orbiter configured along with the core.  Also have a USBUIRT and a gyration remote installed.

[huh]

Going to let it run overnight.

No luck...  devices did not appear.  I'm going to reinstall from scratch and this time leave out everything except the bare minimum (removing the USBUIRT, gyration remote, zwave and hauppauge cards)...

Any other suggestions for debugging?  The device worked initially and I didn't really move the wires around, so pretty confident there isn't a short.

[hari]

i'd be quite interested in the core dump from the event when it died after recognizing the 5th event, can you upload it somewhere?