DataViewer - stuck on "Acquiring Tool Information"

[cobraz]

I have been using the Predator with the Dataviewer for two months now without a problem. It has been two weeks since I pulled a log off the Predator and now the DataViewer won't get past the "Acquiring Tool Information". I have tried on two separate computers that worked previously and I have tried upgrading the DataViewer to 3.3.0.7, but no matter what I try it never gets past that message (no matter how long I wait). I have tried connecting the Predator directly to the Jeep but same message on the DataViewer.

Anybody seen this before and have any ideas. The DSDownloader works fine so it can't be a USB driver issue (though I uninstalled and reinstalled).
__________________
2010 Jeep Grand Cherokee SRT8
- Vortech V-3 Si-Trim Supercharger Kit, Corsa Exhaust, BT Catch Can

[jimb]

What tool/version Predator?
Get the runtime.txt file found in "My Documents\DataViewer" on your PC/Laptop and post it.

[cobraz]

It is U7135 - Predator v.9r23

Here's the runtime.txt file data:

22887795 Info: .\DataViewer.cpp, line 169, CDataViewerApp::InitInstance, DataViewer Version 3.3.0.7
22887795 Info: .\DataViewer.cpp, line 173, CDataViewerApp::InitInstance, The DataViewer is initializing.
22887998 Info: .\ParamTreeView.cpp, line 313, CParamTreeView::UpdateParamsFromLogData, Loading parameter tree from log file data.
22888341 Info: .\comm\httpconnect.cpp, line 208, CHTTPConnectThread::ExtractServerVersion, Server Version: 3306
22888341 Info: .\comm\httpconnect.cpp, line 194, CHTTPConnectThread::ExtractRunningVersion, Running Version: 3307
22888341 Info: .\comm\httpconnect.cpp, line 171, CHTTPConnectThread::Run, Exit HTTP Update Thread
22893333 Error: .\comm\SlipCommunicator.cpp, line 341, CSlipComm::ReceiveXml, PSLIP Receive Failed [Binary Package Size=0]
22893333 Error: .\comm\ToolCommand.cpp, line 338, CToolCommand::Execute, Transaction Retry: General error ocurred during data reception.
23095901 Error: .\comm\SlipCommunicator.cpp, line 341, CSlipComm::ReceiveXml, PSLIP Receive Failed [Binary Package Size=0]
23095901 Error: .\comm\ToolCommand.cpp, line 338, CToolCommand::Execute, Transaction Retry: General error ocurred during data reception.
23370057 Error: .\comm\SlipCommunicator.cpp, line 341, CSlipComm::ReceiveXml, PSLIP Receive Failed [Binary Package Size=0]
23370057 Error: .\comm\CommThread.cpp, line 989, CCommThread::GetToolInfo, Failure retrieving tool info!<BR/>Please reboot, and consider upgrading your tool firmware.
23370057 Error: .\comm\CommThread.cpp, line 996, CCommThread::GetToolInfo, GetToolInfo ERROR
23370057 Warning: .\comm\CommThread.cpp, line 359, CCommThread::ShutDown, Shutting down communications...
23702199 Error: .\comm\SlipCommunicator.cpp, line 341, CSlipComm::ReceiveXml, PSLIP Receive Failed [Binary Package Size=0]
23702199 Error: .\comm\CommThread.cpp, line 574, CCommThread::ExitXmlRpcMode, ExitXmlRpcMode FAILED
23937011 Error: .\comm\SlipCommunicator.cpp, line 341, CSlipComm::ReceiveXml, PSLIP Receive Failed [Binary Package Size=0]
23937011 Error: .\comm\ToolCommand.cpp, line 338, CToolCommand::Execute, Transaction Retry: General error ocurred during data reception.
24107942 Error: .\comm\SlipCommunicator.cpp, line 341, CSlipComm::ReceiveXml, PSLIP Receive Failed [Binary Package Size=0]
24107942 Error: .\comm\ToolCommand.cpp, line 338, CToolCommand::Execute, Transaction Retry: General error ocurred during data reception.
24439584 Error: .\comm\SlipCommunicator.cpp, line 341, CSlipComm::ReceiveXml, PSLIP Receive Failed [Binary Package Size=0]
24439584 Error: .\comm\CommThread.cpp, line 989, CCommThread::GetToolInfo, Failure retrieving tool info!<BR/>Please reboot, and consider upgrading your tool firmware.
24439584 Error: .\comm\CommThread.cpp, line 996, CCommThread::GetToolInfo, GetToolInfo ERROR
24439584 Warning: .\comm\CommThread.cpp, line 359, CCommThread::ShutDown, Shutting down communications...
24771679 Error: .\comm\SlipCommunicator.cpp, line 341, CSlipComm::ReceiveXml, PSLIP Receive Failed [Binary Package Size=0]
24771679 Error: .\comm\CommThread.cpp, line 574, CCommThread::ExitXmlRpcMode, ExitXmlRpcMode FAILED
25030344 Error: .\comm\SlipCommunicator.cpp, line 341, CSlipComm::ReceiveXml, PSLIP Receive Failed [Binary Package Size=0]
25030344 Error: .\comm\ToolCommand.cpp, line 338, CToolCommand::Execute, Transaction Retry: General error ocurred during data reception.
25268573 Error: .\comm\SlipCommunicator.cpp, line 341, CSlipComm::ReceiveXml, PSLIP Receive Failed [Binary Package Size=0]
25268573 Error: .\comm\ToolCommand.cpp, line 338, CToolCommand::Execute, Transaction Retry: General error ocurred during data reception.
26446225 Info: .\comm\CommThread.cpp, line 176, CCommThread::ExitThread, CommThread::ExitThread complete.
26446225 Info: .\DataViewer.cpp, line 299, CDataViewerApp::ExitInstance, CDataViewerApp::ExitInstance complete.

[jimb]

I tried this on the bench with SRT8 PCM, WinXP, u7135-9r23 using Prolific USB-Serial adapter and Predator holding a backup. Could not recreate your issue. Your runtime log is showing communication errors between PC and Predator.

Check the following:

Predator is set for 115200 baud (Options->Serial Baud)
Have DSDownloader closed when using DV.
Use My Computer->Manage->Device Manager->Ports and verify USB-Serial port settings are also 115200. Also, check which COM port is used.
Have Bluetooth turned off.
Try another USB-Serial adapter cable.

See: http://www.diablosport.com/index.php?na ... pic&t=2396 and the topic how to change COM port.

Lastly, IF DSDownloader is working. Please use Help->Tool Info and paste contents here.

[cobraz]

I just got back last night from my 2500 mile Thanksgiving journey between Iowa and North Carolina. I found some time last Wednesday after reaching North Carolina and after a series of random driver and program uninstalls and reinstalls I still had no luck. I then tried
my work laptop which had never been connected to the Predator before and
installed the drivers and programs and was able to download the original tune on
the first try and after that the Predator was working again as normal from all
computers.

I still have no idea what was wrong and don't have a real solution to what fixed it other than I think I got lucky. Everything works fine for the last week, but the odd part is still that the DSDowloader had no issues on any computer and that the DataViewer would not work on any computer. Once it was working again then it worked on all computers again (without any further software changes)

[cobraz]

The problem came back a few weeks ago and I have tried everything to read data off the Predator. Now the Predator won't even let me write new data to it. I have tired all the same things as last time with multiple computers and versions of the DatatViewer and DSDownloader. My tuner has tried too using his own cables, computers and multiple versions. I think the hardware has gone bad for the serial port communications. The computer recognizes the device and the Predator shows it is under remote control but nothing ever happens after that. The Predator is not a year old yet as the Dealer who installed my Vortech received it arournd March of 2010.

What other support or warranty options do I have. I hate not being able to pull logs or load custom tunes.

[mikel]

Tools are under warranty for 2 years, feel free to fill out an rma request and get it in to us for testing.

[cobraz]

Tools are under warranty for 2 years, feel free to fill out an rma request and get it in to us for testing.

Since the Predator was working fine on multiple computers before and nothing had changed with my software the only conclusion is a a problem with the hardware.

I guess I'm out of luck on the receipt for an RMA as my Predator was included as part the Vortech installation by my Jeep dealer. I'm not sure if the Predator I received came directly from Vortech or from RDP Motorsport who did the Vortech tune for the Cleveland Jeep Dealer. I purchased the 2010 Jeep new with the Vortech already installed so i have no receipt other than my new vehicle purchase order.

$99 bucks to look at this doesn't seem like a good deal for me especially since I was planning to upgrade to a Trinity soon. I guess I need to research how the transfer process works switching from a Predator to a Trinity. Do I still have to load the original tune back first, which would be tough since I have Vortech and can't drive the Jeep until if I have to send the Predator in for credit and wait to get the Trinity to load back the custom tune.

[mikel]

If you want to updrade to a trinity, we will give you $99 for the predator, so you cvan get the trinity for $500.

Export the last tune written from your Predator, post it here, and I'll make you a new custom tune to load to your Trinity.