S300 not being detected via USB
Posted: Sun Feb 23, 2014 1:29 am
Hi there, my S300 is no longer being detected on my laptop, not either being detected as a new USB device.
It is in a standalone race car which has no factory wiring remaining how ever I put a wiring loom in and have had it connected, powered up, registered and datalogging.
I had tried to connect a rear wheel speed sensor and had the signal wire connected to VSS B10 (YEL/BLK)
I wired it up how via this http://www.xenocron.com/downloads/RaceS ... Sensor.pdf and when using a volt meter on a spare battery I could not get the output wire (BLK) to output ANY voltage - so I'm not sure what has gone wrong.
Could this have damaged the ECU?
I also at one point lost my balance and ended up falling onto the ECU itself, I can't imagine it would have flexed enough to damage anything but thought I would make note of it.
Are there any tests I can do to show if the ECU has been damaged? All voltage inputs on the wiring loom side are working as per normal
I had updated to 2.2.8 and thought that may have caused an issue with USB drivers so went back to 2.2.7 and still no dice
Thanks
It is in a standalone race car which has no factory wiring remaining how ever I put a wiring loom in and have had it connected, powered up, registered and datalogging.
I had tried to connect a rear wheel speed sensor and had the signal wire connected to VSS B10 (YEL/BLK)
I wired it up how via this http://www.xenocron.com/downloads/RaceS ... Sensor.pdf and when using a volt meter on a spare battery I could not get the output wire (BLK) to output ANY voltage - so I'm not sure what has gone wrong.
Could this have damaged the ECU?
I also at one point lost my balance and ended up falling onto the ECU itself, I can't imagine it would have flexed enough to damage anything but thought I would make note of it.
Are there any tests I can do to show if the ECU has been damaged? All voltage inputs on the wiring loom side are working as per normal
I had updated to 2.2.8 and thought that may have caused an issue with USB drivers so went back to 2.2.7 and still no dice
Thanks