[wish-info] echo off > /dev/x10/??? not working anymore

[Daniel P. Stasinski]

I just built a new system based on Centos 4.

Everything loads fine. It seems to be communicating fine with the cm11a
because if I send RF to say /dev/x10/e1 it will read the correct status.
The bad part is that no outgoing commands work (echo off > /dev/x10/e1).
I can read it again and it sees the change, but the light never goes off
or on.

When I pull put the new drive and pop the old one back in, all works
fine so I know the cm11a is working correctly.

I am out of ideas. Anyone else have any?

Daniel

[wsh]

The reason that you are seeing the status is that the cm11a doesn't hear
what it sends and so the driver simulates hearing what it is sending.
Therefore, regardless of what is put on the powerline, you will see the
status showing up as if it sent it.

What version of the driver did you compile for the old system and for the
new system? I haven't changed the drivers for the cm11a in some time so it
is unlikely to be version related, but it possibly could be.

What I am wondering about is whether the new system disk sees the serial
ports the same way as the previous one. On one of my systems I had an odd
port configuration so that com port B was at 2e8 interrupt 3 and under 2.4
this still showed up as ttyS1 but under kernel 2.6 it showed up as ttyS3.

Look in your /var/log/messages or run "dmesg" to see if your port names
changed between systems. When you start the cm11a, you have to pass it the
name of the serial port that you are using for the device and if you get it
wrong you could end up with the behavior you are describing. Eventually the
cm11ad daemon should give up on trying to talk to the device in which case
it will no longer be in your process table. Make sure that cm11ad continues
to run all the time.

If you find that indeed your ttyS# is correct and that the cm11ad daemon is
running properly then restart the cm11ad daemon with the "-debug" option and
send the results from your /var/log/messages so that we can have a look at
what kind of error is coming back when you try to transmit.

Scott

----- Original Message -----
From: "Daniel P. Stasinski" <***@avenues.org>
To: <wish-***@lists.sourceforge.net>
Sent: Monday, May 02, 2005 12:58 AM
Subject: [wish-info] echo off > /dev/x10/??? not working anymore

Post by Daniel P. Stasinski
I just built a new system based on Centos 4.
Everything loads fine. It seems to be communicating fine with the cm11a
because if I send RF to say /dev/x10/e1 it will read the correct status.
The bad part is that no outgoing commands work (echo off > /dev/x10/e1).
I can read it again and it sees the change, but the light never goes off
or on.
When I pull put the new drive and pop the old one back in, all works
fine so I know the cm11a is working correctly.
I am out of ideas. Anyone else have any?
Daniel
--
| ---------------------------------------------------------------
| Daniel P. Stasinski | http://www.saidsimple.com
| --------------------------- | http://www.scriptkitties.com
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
wish-info mailing list
https://lists.sourceforge.net/lists/listinfo/wish-info