Home Automation Domotica Forum Europe, Bwired Forum

Ok today I got my new Zwave stick. Plugged it in, installed the drivers from the AEOn-labs website and it worked!

Well until I found out that the driver had kicked out my PMIX35 (Xanura) device.
They use the exact same bridge/driver and it doesn't want to install two bridges.

I have reinstalled the driver sets, unplugged and re-plugged the devices but still one wants to work. If I unplug one, the left over one starts to work.

Did anybody find a solution?
Does anybody has two 2101 comm ports running?

Yesterday I have spent another few hours to try to solve the issue.
When I have one device plugged in it works at lets say COM5
When I plug the second device in, it change the COM port to COM9 and gives an exclamation mark. None of the device work.
WHen I take one out it starts working again. Same behavior if I do it in different order.

I have taken away all drivers, cleaned the whole machine, installed the latest driver but no change.
I tried to install with on COM port open, hoping it would force another instance of the driver but also no luck.

Then tried it on one of my Win7 machines but nor 32bit nor 64bit wanted to install the drivers.

It seems we got new technology with old style drivers. I have mailed AEONlabs but no answer.
Going to try to mail SIlabs, who are the original manufacturer of the driver system.

Still I am surprised I am the only one having trouble...

What is the OS of your HS server? 2003? XP?

WinXp Sp3

Got a reply on the Silabs forum which doesn't sound good....

Message:
<i>But when I plug the stick in, it forces the current driversetup to a new COMM port but gives an exclamation mark.
THere is still only one instance of the bridge and none of the devices work.
When I unplug one of them they work."</i>

This symptom sounds like same as this case,

"2 or more CP2102 in WinXP"
http://www.cygnal.org/ubb/Forum9/HTML/001270.html

In above thread, a customized VCP driver conflicts with the original one, because of an INF file trouble - the service name.

Preston of SiLabs posted as follows in the thread,
[blockquote]posted June 04, 2007 10:13 AM by preston, from SiLabs
This issue has been addressed in the Driver Customization Wizard v3.8, and has been updated on the application notes page as AN220SW.[/blockquote]

The XANURA and AEONLABS drivers may be old ones.

<i>"installed a fresh v5.4 but I can't get the two device working."</i>

XANURA and AEONLABS may apply custom VID/PID.

It's better to ask the manufacturers for new driver,
but if you can't wait for,
- Read out the descriptors from the CP2101s using USBView and get the VID/PID value
- Make custom drivers of the VID/PID

MS USBView on FTDI site
http://www.ftdichip.com/Resources/Utilities/usbview.zip

SiLabs MCU KB: CP210x Troubleshooting Techniques
http://portal.knowledgebase.net/article ... 010&p=4120
On this page, you'll learn how to use UVCView (USBView)

"C8051F32x and CP210x USB Driver Customization"
https://www.silabs.com/Support%20Docume ... /an220.pdf
https://www.silabs.com/Support%20Docume ... N220SW.zip

Do the devices have custom VID/PID ? If this is the case you can create 2 drivers and it should work fine.

Changing the serial number should do the trick. Send me a PM and I mail you the tool to do it.

Ok found the reason. Checking the device manager I found a suspicious device that appeared as normal working, under Universal Serial Bus controllers. It was called a bridge but disappeared when I unpluged my Zwave device.
When I checked the driver it appeared to use also SIlabs. I tried to update and then it showed me a list of CP2101 drivers and it was running an older 4.2 version. When I update the driver to 5.4 it jumped suddenly back to the COM ports sections and created a second device driver on a diferent port. Great, now it all works.

Thanks for all the help and suggestions!