PDA

View Full Version : CM12U COMmunication Issue


tassist
08-25-2003, 11:39 AM
There have been two of us working on this problem for a week now, on 4 different PCs all with Windows XP on them and all with varying levels of install status. One of which is a fresh install.

We have tried 2 different modules - The CM12U and the one purchased just a few days ago the MX10 (which is the new ver of the CM12)- and 4 different pieces of software and still no joy.

We are getting to our level of patience now and it is looking very much like we shall be returning all items for a refund.

We just cannot get a communication link between the Interface Modules and the PC.
COM1 seems to be the only free port yet no link can be made.

What are we missing!??
Please someone Help!!!

We are trying a last ditch attempt at posting to bulletin boards and web sites.

JimMcGowanInlet
08-25-2003, 01:47 PM
Have you verified COM1 is working? Did you do a loopback test or put some other known device on COM1 to test it? Just because Windows says the device is working doesn't mean it is.

Test COM1 with a loopback adapter or with something you know works. Are you using HAL or some other package? Are you using the correct cable(s) and adapter. Have you tried a Null Modem Adapter? Have you tried HyperTerminal to communicate with the device?

tassist
08-25-2003, 01:54 PM
[quote:445ce42912=\"JimMcGowanInlet\"]Have you verified COM1 is working? Did you do a loopback test or put some other known device on COM1 to test it? Just because Windows says the device is working doesn't mean it is.

Test COM1 with a loopback adapter or with something you know works. Are you using HAL or some other package? Are you using the correct cable(s) and adapter. Have you tried a Null Modem Adapter? Have you tried HyperTerminal to communicate with the device?[/quote:445ce42912]


Faulty COM ports on \"Four\" PCs....I think not.

JimMcGowanInlet
08-25-2003, 02:16 PM
[quote:2e4b475319=\"tassist\"]Faulty COM ports on \"Four\" PCs....I think not.[/quote:2e4b475319]

Yes if all 4 PC's are the same chipset then XP can fail the same way on all of them.

I never said the hardware was bad. The common product is XP. I've seen MANY cases where Windows says the driver is working properly when its not. Its usually caused by windows mis identifying the chipset. By chance are all the PC's using the same chipset for the Com port?

According to your original post you tried 4 PC's, 4 different peices of software and two differnet devices. I suggest you test the COM1 Port with something that is known to function.

Greg from HAL Support
08-25-2003, 02:57 PM
When using the HAL software you are using the interface choice of HAL11a/CM11a/etc?

If so then with HAL closed open the System Setting screen (Start to Programs to HAL to System Settings). Go to the X10 icon and have it Autosense. What does it report when it scans com port 1 for the different ones you have?

If it was that the com port could not be opened, then this is probably due to something else using the com port that needs to be closed. This can typically be a different automation software, PDA software, digital camera software (even if the PDA and camera do not use com port 1). Please make sure these are all closed, many will be running in the System Tray by the PC clock.

If it is com port opened but the device was not found. then do you have batteries in the device? If so HAL does not require them, please remove. Some US equivilants of the CM12u lock up for different reasons, sending an X10 signal for a different X10 source will typically unlock them.

HAL Tech Support
Greg

tassist
08-25-2003, 03:13 PM
[quote:9ec3bbc6d2=\"Greg from HAL Support\"]When using the HAL software you are using the interface choice of HAL11a/CM11a/etc?

If so then with HAL closed open the System Setting screen (Start to Programs to HAL to System Settings). Go to the X10 icon and have it Autosense. What does it report when it scans com port 1 for the different ones you have?

If it was that the com port could not be opened, then this is probably due to something else using the com port that needs to be closed. This can typically be a different automation software, PDA software, digital camera software (even if the PDA and camera do not use com port 1). Please make sure these are all closed, many will be running in the System Tray by the PC clock.

If it is com port opened but the device was not found. then do you have batteries in the device? If so HAL does not require them, please remove. Some US equivilants of the CM12u lock up for different reasons, sending an X10 signal for a different X10 source will typically unlock them.

HAL Tech Support
Greg[/quote:9ec3bbc6d2]


As I keep saying...We have tried it on 4 PCs. One of which was a fresh install - Nothing running, nothing connected and only one instance of any software installed at any one time. With and without batteries in the device.

JimMcGowanInlet
08-25-2003, 03:38 PM
I'm not sure if I'm just mis-reading your posts or not, but the're comming off a bit annoying. You comment

[quote:a0186fe57f=\"tassist\"] As I keep saying...[/quote:a0186fe57f]

I only see one post where you give any information and that post is lacking details. In case I missed it show me where you mentioned the battery issue greg brought up? Where did you mention what brand PC's you tried? Where did you mention that you tried the HAL com port scan? Where did you mention that the driver set is working? Here is your original post for your review.

[quote:a0186fe57f=\"tassist\"]
There have been two of us working on this problem for a week now, on 4 different PCs all with Windows XP on them and all with varying levels of install status. One of which is a fresh install.

We have tried 2 different modules - The CM12U and the one purchased just a few days ago the MX10 (which is the new ver of the CM12)- and 4 different pieces of software and still no joy.

We are getting to our level of patience now and it is looking very much like we shall be returning all items for a refund.

We just cannot get a communication link between the Interface Modules and the PC. COM1 seems to be the only free port yet no link can be made.

What are we missing!??
Please someone Help!!!

We are trying a last ditch attempt at posting to bulletin boards and web sites.[/quote:a0186fe57f]

What I do see is \"Please someone help!!!\". So lets look at it this way. The 2 of you have tried for a week and can't get it working, but your sure that both Greg's and my opinions are wrong.

[quote:a0186fe57f=\"tassist\"]
What are we missing!??
[/quote:a0186fe57f]

Common courtesy.
.
.

tassist
08-25-2003, 04:18 PM
[quote:6ec9cea5ad=\"JimMcGowanInlet\"]I'm not sure if I'm just mis-reading your posts or not, but the're comming off a bit annoying. You comment

[quote:6ec9cea5ad=\"tassist\"] As I keep saying...[/quote:6ec9cea5ad]

I only see one post where you give any information and that post is lacking any details. In case I missed it show me where you mentioned the battery issue greg brought up? Where did you mention what brand PC's you tried? Where did you mention that you tried the HAL com port scan? Here is your original post for your review.

[quote:6ec9cea5ad=\"tassist\"]
There have been two of us working on this problem for a week now, on 4 different PCs all with Windows XP on them and all with varying levels of install status. One of which is a fresh install.

We have tried 2 different modules - The CM12U and the one purchased just a few days ago the MX10 (which is the new ver of the CM12)- and 4 different pieces of software and still no joy.

We are getting to our level of patience now and it is looking very much like we shall be returning all items for a refund.

We just cannot get a communication link between the Interface Modules and the PC. COM1 seems to be the only free port yet no link can be made.

What are we missing!??
Please someone Help!!!

We are trying a last ditch attempt at posting to bulletin boards and web sites.[/quote:6ec9cea5ad]

What I do see is \"Please someone help!!!\". So lets look at it this way. The 2 of you have tried for a week and can't get it working, but your sure that both Greg's and my opinions are wrong.

[quote:6ec9cea5ad=\"tassist\"]
What are we missing!??
[/quote:6ec9cea5ad]

Common courtesy.[/quote:6ec9cea5ad]


Well as you brought it up....

Your comment re. a faulty port on 4 different PCs is just a waste of time. One maybe but Four....Please!
So yes your comment is \"Wrong\"

Nothing wrong in making comments and suggestions and them being wrong but when you try to pass off Blatantly ridiculous notions, even to a lay person which incidentally I am not, and then trying to justify them in a follow up post, that is what gets up my nose.

Please don't tell me what I am not supplying as I could be hear for a very long time writing. If I am lacking in any detail then a simple question/post re that info is all you have to request thus resulting in a yes or no reply and where the answer is \"no we havn't tried that\" we could then pursue that thread further.

With ref to other peoples posts - IF they have an issue I am sure they are big enough to take it up with me and do not require you to speak for them. I have no intention of commenting on them.

JimMcGowanInlet
08-25-2003, 07:47 PM
Ahhh, Ok I see I wasn't misreading your posts.

[quote:9f8944bbbd=\"tassist\"]
even to a lay person which incidentally I am not,
[/quote:9f8944bbbd]

Sorry I wasted your time. Obviously a brillant person such as yourself should have no problem getting it to work. Another week or two and I'm sure you'll figure it out.

TomGoerz
08-25-2003, 09:10 PM
Okay.. Since we are trying to determine what you have without actually being there a bit of information would help the people that are trying to help you.

You have tried 4 Pc's and nothing. For the moment I will presume that the Com ports on all the PC work although you have not really indicated that you have tested any of them besides hooking them up to the two modules.

You have tried two modules and nothing happens. I will presume the two modules are new and work.

Are you by chance using the same defective cable between the PC's and the two different modules ? That would seem to be a common single item that could easily give you problems which would seem to effect all devices involved...

Just a suggestion........

tassist
08-26-2003, 02:27 AM
[quote:21c993176c=\"TomGoerz\"]Okay.. Since we are trying to determine what you have without actually being there a bit of information would help the people that are trying to help you.

You have tried 4 Pc's and nothing. For the moment I will presume that the Com ports on all the PC work although you have not really indicated that you have tested any of them besides hooking them up to the two modules.

You have tried two modules and nothing happens. I will presume the two modules are new and work.

Are you by chance using the same defective cable between the PC's and the two different modules ? That would seem to be a common single item that could easily give you problems which would seem to effect all devices involved...

Just a suggestion........[/quote:21c993176c]

Thanks for your suggestion...

At the time of writing this - one of the four ports have been tested (working)and we are currently testing the others.
At least one of the modules can be confirmed as working as it works on a Win 95 PC. Which also means the cable is working.

Anything else I could try? Cheers.

TomGoerz
08-26-2003, 10:30 AM
It is still possible that the connecting cable is bad when placed in certain positions. I have had 5 different times with different cables where the cable would work in one position and not in another. In each case one of the pins on the connector would contact the wire when certain pressure was exerted on the cable. One event just happened last week with a new USB cable. The scanner I was installing would work in one location but when I moved it to another location it would not work. It was very very frustrating. New USB cable fixed this.
Just for confirmation you may want to move the cable around while it is hooked to the Win95 and communicating with the module. Maybe trying a different connecting cable if possible.

ToddG
08-26-2003, 10:35 AM
Yes I hate dealing with COM ports too. I purchased a Powerlinc USB powerline interface (around $20) several months ago and have been extremely pleased. In addition to not having to dedicate one of my system's precious COM ports, the USB controller is quicker and more stable in processing X-10 commands. As far as cost goes, I would think the value of the time and frustration you have spent spinning your wheels many times exceeds the cost of this interface upgrade from smarthome.com. I have no relationship with that company other than as a customer.

tassist
08-26-2003, 10:54 AM
[quote:25e32f5048=\"ToddG\"]Yes I hate dealing with COM ports too. I purchased a Powerlinc USB powerline interface (around $20) several months ago and have been extremely pleased. In addition to not having to dedicate one of my system's precious COM ports, the USB controller is quicker and more stable in processing X-10 commands. As far as cost goes, I would think the value of the time and frustration you have spent spinning your wheels many times exceeds the cost of this interface upgrade from smarthome.com. I have no relationship with that company other than as a customer.[/quote:25e32f5048]

I couldn't agree with you more and have desperately been searching for such a device in the UK.
Yes sadly I am in the UK and HA is not as prolific or well established over here and as such not all devices available in the US are available over here either - Unless anyone can tell me otherwise?

Regards

ToddG
08-26-2003, 12:26 PM
You say COM1 is available.
1) Can I then assume you have checked the hardware profile and verified that this COM port is not suffering from an IRQ conflict?

2) How many other COM ports are currently in use on your PC and what kind of divices are using each of them?

3) Have you tried setting up a different COM device (modem, camera, printer, scanner, etc.) on COM1 (without first physically or logically removing any devices you already have installed.) I have a gut feeling that your system simply doesn't want you to install any additional COM devices. To test this you could try temporarily removing (logically as well as physically) one of your other COM devices. Boot your system, see if HAL can now find your interface.

God, I hate debugging serial ports!

TomGoerz
08-26-2003, 03:39 PM
Another thought.. Get one of those USB to Serial Port converters. Those should be an off the shelf item in the UK.. I am not sure if HAL will see a USB serial port ?? Any comments from HAL support..

tassist
08-26-2003, 03:42 PM
[quote:5ba6133c3d=\"TomGoerz\"]Another thought.. Get one of those USB to Serial Port converters. Those should be an off the shelf item in the UK..[/quote:5ba6133c3d]


:D
Ordered one about 30 mins ago - Thanks.

Greg from HAL Support
08-27-2003, 01:42 PM
HAL will see USB added serial ports.

HAL Tech Support
Greg