serial to usb driver (aem wideband)
I am trying to log my AEM wideband. It used to work in the past but after i got my laptop formatted there seems to be a conflict somewhere..
i have already made the usb to serial and it used to work .. but now i just cant log it. in the device manager it shows there is a conflict. And it does not show the location of the com port (displays as 0).
In mitsulogger i can only choose 3 or 4 com port but none seems to work..
can someone provide me with the correct driver or how to sort out my problem?
Thanks,
Bader
i have already made the usb to serial and it used to work .. but now i just cant log it. in the device manager it shows there is a conflict. And it does not show the location of the com port (displays as 0).
In mitsulogger i can only choose 3 or 4 com port but none seems to work..
can someone provide me with the correct driver or how to sort out my problem?
Thanks,
Bader
A friend made it for me. Prior to formating, I had the same issue, but I was missing the driver and when I found the correct one it worked. Now I can't seem to source the driver or fix the conflict.
See if this driver works:
http://www.dynexproducts.com/skins/S...B9_Drivers.zip
Try logging with Hyper Terminal and see if you can figure the problem out there.
http://www.dynexproducts.com/skins/S...B9_Drivers.zip
Try logging with Hyper Terminal and see if you can figure the problem out there.
Trending Topics
still doesnt work :/
on the computer, in settings - hardware - devices, it shows as an exclaimation mark (conflict)...
the only thing changed was me formatting the laptop ... it shows as driver malfunction .....
any other suggestions ..
on the computer, in settings - hardware - devices, it shows as an exclaimation mark (conflict)...
the only thing changed was me formatting the laptop ... it shows as driver malfunction .....
any other suggestions ..
Damn, that driver was a shot in the dark. Try going in device manager, click on the "Ports" and try updating the driver. If that doesn't work, try removing the driver and installing it agian.
it should definately be the driver. I had the same issue with mine till I had to source an install CD. Granted I bought mine from the store but I got the same error messages as the OP till I located the drivers for it.
It was made by someone else. But like I mentioned before, it used to log my wideband prior to formating. It shows as a conflict in device manager now though.
Someone must have the driver...
Someone must have the driver...


