X10 Community Forum

🖥️ActiveHome Pro => ActiveHome Pro General => Topic started by: arf1410 on June 06, 2005, 11:48:40 PM

Title: CM15A Kills COM ports
Post by: arf1410 on June 06, 2005, 11:48:40 PM
I found these posts on another automation
forum.  Can someone explain this a bit
better to me, and also clarify how to fix
this problem (para 2). Also X10 Pro- can
you comment / verify this info?  Does X10
Pro's serial ports work with AHP installed?

"I tried to give the CM15A a spin, but did
not get very far and now have an
undesirable side-effect. It turns out that
once the CM15A usb drivers are installed
they introduce a layer on top of the COM
drivers and the COM ports will not work
unless the CM15A is installed"

"I am new here. I have also experienced the
COM ports not working after installing the
drivers for the CM-15A. Even when you
uninstall them, a system service is left
behind that kills your serial ports. Just
look for the system sevice (X10net or
something like that) and disable it (set it
to "disabled" so after next boot you don't
have to do it again). COM ports will work
again after that."
Title: Re: CM15A Kills COM ports
Post by: carmine pacifico on June 07, 2005, 09:37:10 AM
Arf1410

Are you referring to a physical COM Port or
a USB to serial device?
I do not have much confidence in the CM15a
+ AHP, and yes they do leave that annoying
X10net running even after uninstall, but I
do not think it should affect your other
port settings.
Many USB enable peripherals devices add a
virtual COM driver, win XP can have up to
256 virtual COM ports, what is probably
happening, windows mapped the CM15a on the
same COM port number as your other devices,
you can easily change that: go to System
property, Ports (Com & Parallel) select
port settings _> advanced and make sure
that the CM15a and your other serial device
are set to different COM numbers.
Before you make the changes both devices
need to be plugged in.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 07, 2005, 11:09:33 AM
yes, physical com ports, not USB to serial
adapter.  My physical COM ports haven't been
able to talk to my GPS or CM11A since
installing AHP...I have tried messing with
the hardware / device mgr, but no success.

Do your physical COM ports work when AHP is
installed?
Title: Re: CM15A Kills COM ports
Post by: carmine pacifico on June 07, 2005, 12:54:48 PM
ARF1410

My computers do not have physical serial
port.
You need to check with X10net running, the
resources allocated, it is possible that
Windows has mapped the CM15a COM driver
with the same COM number as your physical
COM port. Make sure you physical COM is
enable in the bios and should be set as
COM1 or COM2.
What version of windows you are running?
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 07, 2005, 01:12:24 PM
I am using XP Pro ...

Why would the CM15A map a com port? it is USB

X10-Pro - I would like a comment on AHP and
COM ports...
Title: Re: CM15A Kills COM ports
Post by: X10 Pro on June 07, 2005, 02:26:58 PM
ARF: Does this problem happen if the CM15A is
plugged in? It shouldn't. There's some legacy
support for the CM17A that will grab a serial
port, but that should happen if there's an
X10 USB device present. In fact, it shouldn't
happen at all, since that code is supposed to
have been disabled. There's a registry entry
that will fix the problem. I promised that to
a couple people, so I'll send it out to all
of you today.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 07, 2005, 02:42:01 PM
Just to be clear, you think the COM ports
might work with the CM15A attached, but not
work with the CM15A not connected?

Have you tested X10 computers COM ports, to
see if they still function normally with AHP
installed?

I've got to conenct my GPS in the next night
or 2, so I will test it...
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 08, 2005, 12:32:31 AM
how do I disable X10net ???
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 08, 2005, 12:35:05 AM
OK - my COM port DOES work with a CM15A
connected???!!!!
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 08, 2005, 12:55:10 AM
tried it again with AHP running, and no
luck...
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 08, 2005, 02:20:52 PM
X10-Pro -

You said yesterday you would send out a reg
fix for this problem...When?
Title: Re: CM15A Kills COM ports
Post by: X10 Pro on June 08, 2005, 03:02:23 PM
arf1410: I just sent you what you need.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 08, 2005, 11:38:56 PM
I ran software you provided, and GPS would
still not connect via serial port.  Tried
it with Cm15A connected and AHP running
(which worked once last night).  Didn't
connect...Rebooted PC, and tried again.  No
luck...I'm frustrated...
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 09, 2005, 12:14:09 AM
OK - the only way I can talk to my CM11A or
GPS (my only 2 serial devices) is if I boot
the PC with the CM15A connected.  Even with
this done, if I disconnect the CM15A after
boot up, I can no longer communicate via
the serial port ... this tells me that it
is the CM15A, in some way, shape, or form,
that has messed up my serial ports!
Title: Re: CM15A Kills COM ports
Post by: carmine pacifico on June 09, 2005, 10:01:16 AM
Arf1410

Considering the mess the web installer
does, I would not be surprised if other
unnecessary drivers are installed that
locks the serial port.
As I suggested before, they are ways to
check if your port is working correctly,
under “Computer System Property – Hardware –
Device manager - Ports”, it’s evident that
you have another device driver that lock
your COM port, unless you provide some
information from the System property, it’s
next to impossible to help you.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 09, 2005, 10:30:33 AM
Carmine -

I checked hardware profiles / device
manager , etc, and the 2 COM ports are
listed with no special notes or exclamation
marks...everythings looks normal...
Title: Re: CM15A Kills COM ports
Post by: X10 Pro on June 09, 2005, 11:53:59 AM
The CM15A isn't the problem, but it could be
that the X10 Device Network Service is using
the serial port when it shouldn't be. The
easy way to tell is to stop the service,
either from the Services panel, or by running
"net stop x10nets" from the command line.
Title: Re: CM15A Kills COM ports
Post by: carmine pacifico on June 09, 2005, 12:09:40 PM
ARF1410

It would not be any exclamation mark; under
ports you should see a name for the device,
and (COMX), if any virtual serial port has
the same  COM number than your physical COM
port , re-map that virtual device to a
different com number.
If everything appears normal than is
probably X10net keeping the port open
(X10net can communicate with some X10
serial devices else). Reboot your computer
without the CM15a, use the Window Task
Manager to end “X10net” process, and you
should regain control o the port.

There a built in windows
utility “msconfig”,this is a very powerful
utility for enable/disable start-up program
+many more features , use it with care.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 09, 2005, 12:13:54 PM
at office now, so can't fiddle with home
PC...However, I am fairly certain x10nets
was not running (at least as shown on the
task manager), and that there were no COM
port conflicts, but I will try and check
tonight...
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 09, 2005, 01:06:42 PM
X10-Pro (or anyone else) - you state that
the CM15A isn't the problem, but could you
explain why / how booting the PC with the
CM15A installed, and keeping the CM15A
installed FIXES the problem?
Title: Re: CM15A Kills COM ports
Post by: roger1818 on June 09, 2005, 02:03:58 PM
ARF:  I think what X10 Pro is trying to say
is that it isn’t a hardware bug with the
CM15a but a software bug with the X10
Device Network Service (X10Net).  Did you
have your CM11A or GPS when installing (or
upgrading) AHP (maybe it is confusing the
GPS for an X10 device for some reason)?
The installation process seems to search
for X10 hardware.  You might try installing
AHP with both of them unplugged.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 09, 2005, 02:13:24 PM
after more "Google-ing", it appears X10nets
likely is the problem, and will kill access
to COM ports.  I do not think I can stop it
using the Task Manager, as I don't think it
is listed, but I will try X10-Pro's
suggestion of using the command line
"net stop x10nets"  - do I add the ".exe"
extension?

Do I have to do this every time I want to
use a serial device?  If so, there must be a
better, permanent fix!  Also, I still want
to be able to use my X-10 Firecracker (which
likely is the original cause of this
issue)!  Will that be possible?  
Title: Re: CM15A Kills COM ports
Post by: roger1818 on June 09, 2005, 04:31:56 PM
Arf:  In the Task Manager you have to
select the “Processes” tab to see
x10nets.exe.  It also helps to sort by name
by clicking on the “Image Name” heading.

Overall it might be easier to call “net
stop x10nets” when you want to use a COM
port and “net start x10nets” when you want
to use AHP or Firecracker (AHP will
automatically start it if it isn’t running
and Firecracker may do likewise).

X10 Pro suggested to me in an e-mail that
if I were to plug a MR26A into the CM17A,
X10 nets would confine its use of COM ports
to just that port.  I think the problem is
that the software can’t determine which
port the CM17A is plugged into (it doesn’t
talk back) so X10Nets grabs all the ports
just to be “safe.”

This is ludicrous, especially since the
CM17A has a through port so that you can
plug something else into it.  The proper
thing to do would be to keep all of the COM
ports closed until they are needed.

One other thing you might want to try is to
open the firecracker software and specify
which port the CM17A is connected to.
Hopefully this would confine the port use
to the CM17A’s port.  You wouldn’t be able
to use anything else on that port though.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 09, 2005, 04:40:10 PM
thanks for the tips Roger.  Suppose I want
to PERMANENTLY stop / remove the x10nets.
Can that be done?
Title: Re: CM15A Kills COM ports
Post by: roger1818 on June 09, 2005, 04:56:02 PM
Arf:  It can be done, but both AHP
(including SDK) and the Firecracker
software require “x10nets,” so unless you
don’t want to use them anymore, you
shouldn’t permanently remove it.

The proper thing is for X10 to fix the
problem.
Title: Re: CM15A Kills COM ports
Post by: roger1818 on June 09, 2005, 05:01:18 PM
Arf: I forgot to mention, X10 Pro e-mailed
me a program that “will make the registry
changes needed to turn off the X10 Device
Service's use of serial ports.”  Maybe he
can send it to you too or put it up on
X10’s ftp site.  This will allow AHP to
work, but Firecracker won't.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 09, 2005, 05:24:05 PM
X10 emailed me that software too, but it
didn't seem to help  - and yes, I rebooted...

Howver am still confused.  You say both AHP
and Firecracker need X10nets...if so, how
will AHP work after x10nets is removed
(either manually, or with special
software)?  I though X10-Pro stated x10Nets
was NOT needed for AHP??

If, hypothetically the problem is AHP, which
for all practical purposes is synonymous to
the CM15A, as they are always used as a
pair, then this is a problem that X10 needs
to fix.  Having AHP making COM ports
unusable is UNACCEPTABLE.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 09, 2005, 05:24:11 PM
X10 emailed me that software too, but it
didn't seem to help  - and yes, I rebooted...

Howver am still confused.  You say both AHP
and Firecracker need X10nets...if so, how
will AHP work after x10nets is removed
(either manually, or with special
software)?  I though X10-Pro stated x10Nets
was NOT needed for AHP??

If, hypothetically the problem is AHP, which
for all practical purposes is synonymous to
the CM15A, as they are always used as a
pair, then this is a problem that X10 needs
to fix.  Having AHP making COM ports
unusable is UNACCEPTABLE.
Title: Re: CM15A Kills COM ports
Post by: X10 Pro on June 09, 2005, 05:31:49 PM
Roger H: I sent ARF the same registry program
I sent you, but since he wants to use the
CM17A, it's not an option.

You make a good point about running
Firecracker and selecting the COM port. I
forgot that you could do that. I'm pretty
sure that if you use the Firecracker settings
to specify the port to use then the X10
service will only grab the one that you have
specified.

On my PC here I run AHP and have the X10
service running all the time. I also have a
CM11A and another serial device connected,
and can use them both without problems, with
and without AHP running.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 09, 2005, 05:35:53 PM
I CAN use COM ports without AHP running, but
the CM15A must be CONNECTED to the PC
Title: Re: CM15A Kills COM ports
Post by: roger1818 on June 09, 2005, 05:36:02 PM
Arf:  I am not sure where you read that
x10nets was not needed for AHP, as far as I
know it is.  If x10nets isn’t in memory, it
will be opened by AHP but if you removed
x10nets from your hard drive, I don’t think
AHP will run.

I agree with you about CM15a and AHP.  I
tend to use CM15a to describe the hardware
and AHP to describe the software.

I also agree that x10nets (and thus AHP)
making COM ports unusable is unacceptable
and should be fixed.
Title: Re: CM15A Kills COM ports
Post by: X10 Pro on June 09, 2005, 06:19:09 PM
ARF: Have you tried running Firecracker and
selecting a specific COM port? Unless you use
the GPS on the same port as the CM17A that
should allow you to use your COM ports even
when the CM15A isn't connected.

The reason that you can use the COM ports
when the CM15A is connected is that the X10
service doesn't look for serial devices when
an X10 USB device (CM19A or CM15A) is present.

You cannot remove X10net/x10nets from your
system if you want to run AHP or any other
X10 software except the original ActiveHome.
The X10 Device Network Service
(X10net/x10nets) is a shared service that is
used to communicate with the CM17A, MR26A,
CM19A, and CM15A. Without it, none of those
programs can run.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 09, 2005, 06:28:04 PM
I hope to have time for a few more test
tonight...
My PC has 2 COM ports.  Should I plug GPS
into the firecracker, or other COM port?
Title: Re: CM15A Kills COM ports
Post by: X10 Pro on June 09, 2005, 07:36:07 PM
Plug the GPS into the COM port that the CM17A
is not plugged into.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 09, 2005, 08:34:37 PM
using Windows Task Mgr, I have found and
STOPPED x10nets...

GPS still CANNOT talk to PC...I will try
rebooting...
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 09, 2005, 11:04:16 PM
OK firecracker re-installed, however it
doesn't seem to work!  Is there a conflict
with AHP?  AHP Activity monitor shows CM15A
recieves firecracker command, but does NOT
execute command???
Title: Re: CM15A Kills COM ports
Post by: X10 Pro on June 10, 2005, 12:44:22 PM
I'm not sure I understand. You're sending a
command using the Firecracker software -- but
through what interface? Where do you see the
CM15A receiving the commands? What are you
trying to do exactly?
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 10, 2005, 01:04:09 PM
Firecracker (CM17A?) is plugged into COM
port.  Unless my memory is wrong, the CM17A
itself sends an RF Command, which can be
recieved by the CM15A, and sent along the
powerline.  According to the AHP Activty
monitor, when I use the fircracker software
to send a command, the AHP recieves the E6
ON (for example), but the light does NOT
actually turn the light on.  When I use the
Palm Pad remote to send an E6 ON, the AHP
recieves the command, and the light actually
turns on...X10-Pro - if you are able to
actaully call me this morning, we might be
able to resolve this in 5 minutes, rather
than this msg board.  Email me if possible...
Title: Re: CM15A Kills COM ports
Post by: roger1818 on June 10, 2005, 03:50:16 PM
Arf:  The Firecracker software will use the
CM15A to send the RF command (even if you
have told it to use a serial port).  The
CM15A won’t transceive its own RF
commands.  As a result you can’t use the
firecracker software to control lights if
the CM15A is connected to your computer.
If you disconnect the CM15A from your
computer, the firecracker software will use
the CM17A (assuming it is configured
properly) and the lights should turn on and
off.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 10, 2005, 04:18:12 PM
Looks like the bottom line is I cannot get
Firecracker software (I really don't care
whether the CM17 or CM15 actually sends
signal), AHP and my GPS to all work at the
same time, or in any combo, without some
type of work-around...
Title: Re: CM15A Kills COM ports
Post by: X10 Pro on June 10, 2005, 04:29:37 PM
Roger H: That's almost exactly what I sent to
ARF in an e-mail. Scary.

ARF: If you have something besides the CM15A
to receive the RF commands you are sending
(TM751, RR501) using Firecracker, then you
can have all three plugged in at once and use
them all.

A better question might be what you are
trying to do by using the Firecracker
software to send RF to control lights. Do you
just want to use the Firecracker software
instead of AHP? I can see wanting a small
interface you can leave open to control light
when you need to, without having to have the
whole AHP program open. If that's what you
want, take a look at the Javascript PalmPad
sample in the SDK. It sends PLC directly
through the CM15A from a PalmPad in the
browser.  You could open that in a small
browser window and use it like you do the
Firecracker.
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 10, 2005, 04:39:26 PM
You got it - I just like that Palmpad
lookoing software - a nice, simple interface
to turn on a light.  I don't normally keep
the CM15A attached to the PC - it is in a
different room, in the middle of the house.
I will look at that s/w in the SDK, but
looks like that will still require me to
plug in the CM15A...
Title: Re: CM15A Kills COM ports
Post by: arf1410 on June 10, 2005, 04:50:40 PM
searched all over - cannot find that SDK /
palmpad sample