forum

Hi,

I have a zstick (with z-way-server) and I usually connect to it via a network/usb server (i.e. virtual com port) in ubuntu.

For some reason, with this particular unit, the device will not connect properly, failing to create a virtual com port...

i.e. /dev/serial/by-id/xxxxxxxxxxxxxxxxxxxxxxxxxx

Could this be a known issue with the stick itself, not completing some sort of handshake etc?

Never seen this before.

Is the USB stick upgradeable? Could this be a firmware issue?

Thanks

Neil

Think I found the issue.

Did a 'lsusb' in ubuntu and for some reason, the zstick is declaring itself as a 7 port USB Hub?

update...

I've found that this zstick is missreporting its hardware ID... is should be a 0403/6001, but instead its a 0403/0000

I managed to update the f/w of this device but it has not altered anything.

Is this stick a dud?

It was from vesternet, but they aren't showing them for sale anymore.

Thanks

Neil

Ok, I found what the issue was....

It seems, that for this zstick (with z-way-server), when the stick is plugged into windows (7?), some home, the hardware ID is being changed from 0403/6001 to 0403/0000.

When this happens, linux no longer correctly identifies the device and thus does not connect it.

This was the information I stumbled upon...

http://superuser.com/questions/822249/f ... se-windows

using the FT programmer software, I cloned a parameter config from a known working unit and flashed it to the FTDI part of the stick. After this, linux see's the 0403/6001 and connects.

As I test, I put back into windows and once again, the HID was returned to 0403/0000.

Once I'd restored the correct HID once again, linux could see it and it attached the port as it should /dev/ttyUSB0

However, on starting the z-way-server I'm now getting the -9 error, did not return correct packet.

So it would appear this stick could be a paper weight after all.

How is it windows can mess with the FTDI hardware ID's and cause this grief in the first place?

Neil