| One of the biggest problems in maintaining a good connection is the way in which the USB port operates. Here is a link to troubleshooting and fixing things related to the USB port that can cause disconnect problems. Two of them are the port going to sleep and not waking up, and the port not having enough power for the device. This is what I saw with the BLAZT interface. It uses to much amperage compared to the Consult USB interface. I'm going to add this info to my website under interface help too. [ http://www.guidenet.net/resources/usb.html ] Also. The Ostrich 2 has built in abilities to perform it's own data output stream for use with your own tracing routines (if creating software) for tracing. You can have it stream a data location for you to monitor. I just read the documentation again and noticed it said that if you place the Ostrich into this streaming mode to do tracing of "whatever" data and while it's doing this you send data to it, it will cause a hard interrupt to occure and place it back into a ready state. This tells me that if your software is doing some sort of monitoring and this was to happen without you applying the proper error routines it could cause you to have a disconnect. You might want to let Matt at NISTune know what you are experiencing in case it may have some bearing on his software functioning.
 www.mytwinturbo.com Nissan Data Voice - The first Nissan diagnostic software with a voice!
 Download my Nissan 300ZX Vin/Model Lookup. Watch an ECZA meet caravan! |
