freezing when logging analog inputs

Snyphor · Post by **Snyphor** » Sat May 21, 2011 5:37 am

Any updates? I have a similar issue.

nemiro · Post by **nemiro** » Mon Jul 11, 2011 10:25 pm

Also looking for updates. I try to record with a Trinity on a SRT-4, and I get random freezes (says HALT MONITORING at bottom of screen), that requires a hard reset of the Trinity, and a key on/off cycle to apparently clear the PCM bus. In addition, I am having a problem with recording from Analog 1. I see it plainly on the Trinity's screen while monitoring and logging, but I cannot get it to show up in my logs on the PC. I sent a log file to duster360, and he confirms that the analog channel is not there, yet when I run a log, it is indeed reading on Trinity's screen. Any ideas?

gizmodo · Post by **gizmodo** » Tue Jul 12, 2011 9:22 am

How many PIDs are you logging? If you're using Duster's list it is too many to use as a stored dashboard. If you create the dash and log immediately you'll be fine, but that is a huge pain to do every time. Another thing to check is the connection on the bottom of the Trinity. When I still had mine in the case I had to take a razor knife to the Trinity's case and remove some plastic to get the connector to fit without feeling as if I was going to break it.

What version of DataViewer are you using? Make sure it is the latest version. Can you see the external PIDs while looking at live data?

I've attached a log from my car with Duster's list, removing as few PIDs as necessary to get the Trinity to reliably log. It also has AFR on analog 2. If you can't see the analog PID you need to update your version of DataViewer. I have 3.3.0.8, at least that's what the Help -> About says. Ignore that knock.

nemiro · Post by **nemiro** » Tue Jul 12, 2011 9:41 am

I am recording 8 pids, including AFR. As I said, I can see it display on the Trinity, but it is simply not recording it. Not sure why. It is Analog 1, BTW. Not sure that would make any difference, but I am pointing it out. I am using 3.3.0.8. I will take a look at you log later on today. Thanks for looking at this!

gizmodo · Post by **gizmodo** » Tue Jul 12, 2011 10:31 am

Are you saying the Trinity isn't recording it, as in you can't see AFR if you playback the log on the Trinity or it doesn't show when viewing in DV?

nemiro · Post by **nemiro** » Wed Jul 13, 2011 10:20 am

I'm saying I see it live on the Trinity, but if I record the log (which should have the analog), and transfer it to my PC, all of the other PIDs are there, but the analog is not.

jimb · Post by **jimb** » Wed Jul 13, 2011 10:30 am

This is typically indicative of DV out of sync with Trinity's analog input configuration. (Trinity xmits analog config to DV whenever it connects or exports a logfile).

Do the following:
- options Analog config->reset to defaults.
- add your AFR setting lower and upper bound using the analog input channel you have wired in.
- DON'T DELETE any of the default analog input channels.
- reselect the analog input of choice IF using a pre-defined dash and save
- Record a new log

Make sure your using the current version of DV 3.3.0.8; NOT 3.2.0.7 when real-time live stream logging or downloading Trinity logs.

Note:older log files may still not play back when downloaded.

nemiro · Post by **nemiro** » Mon Jul 18, 2011 2:02 am

OK, I'll give that a shot. I will be able to test this next weekend. Thanks!

duster360 · Post by **duster360** » Mon Jul 18, 2011 2:06 pm

See Neil, I told you Jim would have some wiz bang idea of how to fix it.

Post by **mikel** » Mon Jul 18, 2011 2:27 pm

and....thanks Jim!!

nemiro · Post by **nemiro** » Thu Aug 25, 2011 9:48 pm

jimb wrote:This is typically indicative of DV out of sync with Trinity's analog input configuration. (Trinity xmits analog config to DV whenever it connects or exports a logfile).

Do the following:
- options Analog config->reset to defaults.
- add your AFR setting lower and upper bound using the analog input channel you have wired in.
- DON'T DELETE any of the default analog input channels.
- reselect the analog input of choice IF using a pre-defined dash and save
- Record a new log

Make sure your using the current version of DV 3.3.0.8; NOT 3.2.0.7 when real-time live stream logging or downloading Trinity logs.

Note:older log files may still not play back when downloaded.

I know this is a bit old, but I just got around to testing, and got the same results. Maybe I am not understanding correctly. I deleted my AFR definition, built it again, per these instructions, and re-added the AFR parameter to my logging setup. Again, same results.

So this got me to thinking. Do I need to add my AFR definition, AND the Analog 1 input, as a separate voltage only display, in order to get it to show up in the logs? Won't it just show up as a voltage, without my AFR scaling applied?

I attached my .TDS file, which I think should have what data parameters I should be recording, correct?

jimb · Post by **jimb** » Thu Aug 25, 2011 10:00 pm

NO. You need to reset Trinity analog configuration back to factory default. THEN add your AFR as a new input definition. Leave the default Analog 1 definition alone. Don't delete anything.

Trinity should then live stream using DV 3308.

nemiro · Post by **nemiro** » Fri Aug 26, 2011 2:05 am

OK, that is what I thought, but for whatever reason, I am not getting it to work. I have reset, per the above instructions.

I can monitor the AFR all day long. It seems to read accurately enough, but when I go to log using that same setup, it will record all of the OBD data, but the analog is left off, despite seeing it on the Trinity's screen while logging.

jimb · Post by **jimb** » Fri Aug 26, 2011 7:34 pm

Do you mean you cannot select the AFR input in External Inputs section of DataViewer? (Your using 3.3.0.7 ?) Capture a short log on Trinity (with AFR on the Dashboard) and export using DataViewer. Post it here.

Keep in mind, any logs recorded with the previous analog configuration probably will not play back on DV when exported.

nemiro · Post by **nemiro** » Sat Aug 27, 2011 12:29 pm

I'm using 3.3.0.8. I attached a log here (which I recorded after following the procedure above). While recording this log (not hooked up to the laptop), I could plainly see AFR on the logging screen, and it seemed to correlate with the XD-1 gauge in the car. It pulled off the Trinity, into DV, without issue - except that there was no analog data with it.