Problem Connecting to T1000 with Dataviewer
Moderator: mikel
Problem Connecting to T1000 with Dataviewer
I have DV 3.4.1.0 and a Trinity here with r.13 loaded on it and the two just won't talk to each other- see the image below for the Error message in DV
- Attachments
-
- ScreenDVERR.jpg (203.61 KiB) Viewed 2389 times
Seth Patterson
FederalPerformance.ca
FederalPerformance.ca
Re: Problem Connecting to T1000 with Dataviewer
DSDownloader works fine with it and I found an old DV 3.3 on my laptop and I am using that for now, but I would like to get this solved
Seth Patterson
FederalPerformance.ca
FederalPerformance.ca
Re: Problem Connecting to T1000 with Dataviewer
A few questions for you so I can try and help...
What version of Windows are you running?
With the Trinity connected to your PC, go into Device Manager. Under "Ports (COM & LPT)" what COM port is displayed next to "DiabloSport Trinity CDC"? COM1, COM4, COM11...?
Are there any yellow exclamations or red X's next to the "DiabloSport Trinity CDC" in device manager?
Are there any other "COM" devices listed under Ports (COM & LPT)?
Does that error come up while DataViewer says "Scanning Serial Ports" or after is says "Acquiring information" like it found it but then had trouble? Does it ever seem to connect to the Trinity at all?
Jim
What version of Windows are you running?
With the Trinity connected to your PC, go into Device Manager. Under "Ports (COM & LPT)" what COM port is displayed next to "DiabloSport Trinity CDC"? COM1, COM4, COM11...?
Are there any yellow exclamations or red X's next to the "DiabloSport Trinity CDC" in device manager?
Are there any other "COM" devices listed under Ports (COM & LPT)?
Does that error come up while DataViewer says "Scanning Serial Ports" or after is says "Acquiring information" like it found it but then had trouble? Does it ever seem to connect to the Trinity at all?
Jim
Re: Problem Connecting to T1000 with Dataviewer
A few questions for you so I can try and help...
What version of Windows are you running?
Windows 10
With the Trinity connected to your PC, go into Device Manager. Under "Ports (COM & LPT)" what COM port is displayed next to "DiabloSport Trinity CDC"? COM1, COM4, COM11...?
Com4
Are there any yellow exclamations or red X's next to the "DiabloSport Trinity CDC" in device manager?
No
Are there any other "COM" devices listed under Ports (COM & LPT)?
I'll have to double check that
Does that error come up while DataViewer says "Scanning Serial Ports" or after is says "Acquiring information" like it found it but then had trouble? Does it ever seem to connect to the Trinity at all?
It comes up when it is scanning for the serial ports, and it also comes up once after I close the program. As I mentioned, i am using an older (much older 3.3) version and it works well, I also tried a 3.3.03 version and that one comes up with the same error message
What version of Windows are you running?
Windows 10
With the Trinity connected to your PC, go into Device Manager. Under "Ports (COM & LPT)" what COM port is displayed next to "DiabloSport Trinity CDC"? COM1, COM4, COM11...?
Com4
Are there any yellow exclamations or red X's next to the "DiabloSport Trinity CDC" in device manager?
No
Are there any other "COM" devices listed under Ports (COM & LPT)?
I'll have to double check that
Does that error come up while DataViewer says "Scanning Serial Ports" or after is says "Acquiring information" like it found it but then had trouble? Does it ever seem to connect to the Trinity at all?
It comes up when it is scanning for the serial ports, and it also comes up once after I close the program. As I mentioned, i am using an older (much older 3.3) version and it works well, I also tried a 3.3.03 version and that one comes up with the same error message
Seth Patterson
FederalPerformance.ca
FederalPerformance.ca
Re: Problem Connecting to T1000 with Dataviewer
Check the other com ports, especially any you have below com4. DataViewer polls the com ports when looking for a connected device. One of those may be causing that error when DV connects to it. That error usually (not always, thanks MS) has to do with some COM+ service running as a different user. It's possible that some other device on another com port does.
jim
jim