Trinity Unstable

[Speedy!]

I have recently updated my Trinity to CROM 1r13g in order for it to see the data from my 2016 Dodge Challenger Hellcat A8.

I'm experiencing a couple of problems, the biggest of which is frequent lockups by the device. The screen just freezes and you have to unplug and replug in the device for it to come back to life. Is this a known issue?

The tool is almost unusable. I can barely get a single gauge page created without locking up and it frequently locks up while trying to data log.

Also, I've added PIDs that don't seem to read correctly:

WB01 Bank 1 (Ratio) - this changes to "Engine Run Time" after I save the dashboard. Tried changing it back several times with no success.

WB02 Bank 2 (Ratio) - this PID only reads 7.9x all the time on the Trinity and is the value I see in Data Viewer as well.

Desired FA CYL1 - doesn't read correctly on the Trinity, but does show correct values in Dataviewer.

I would assume the WB sensors should read and display something close to the car's built in AFR gauge and have some association with desired FA CYL 1.

[mikel]

My understanding is the WB PIDs do not work, i didnt realize they were mapped out. I might suggest removing them from the layout to see if that resolves the freezing issues.

[Speedy!]

Removed the WB pids and still had the same issue.

Borrowed a friends brand new Trinity, exported my gauge layout to SD card, and imported on his Trinity (unmarried of course). Hooked it up to my car and lock ups galore.

Deleted the gauge layout and rebuilt it from scratch on this second Trinity. Things seem fine until the 4th gauge page, then things become unstable from there on out.

This was not the case with previous CROMs I've used on my 2009 R/T Challenger.

It seems this latest CROM has an issue with more than 3 pages of PIDs??

I'm logging the following PIDs:

Ambient Temp
ECT
IN MAN AIR TEMP
Actual Spark Cyl1
Air Charge
Injector PW Cyl1
IAT
MAP
BARO OBDII
Desired FA CYL1
MF Counts Current
MPHX64
Time from start run
KNK FUEL RETARD
KNK LT RETARD
KNK ST RETARD
Knock Sensor 1 Volts
Knock Sensor 2 Volts
RPM
TPS %

No external analog inputs.

[mikel]

Removed the WB pids and still had the same issue.

Borrowed a friends brand new Trinity, exported my gauge layout to SD card, and imported on his Trinity (unmarried of course). Hooked it up to my car and lock ups galore.

Deleted the gauge layout and rebuilt it from scratch on this second Trinity. Things seem fine until the 4th gauge page, then things become unstable from there on out.

This was not the case with previous CROMs I've used on my 2009 R/T Challenger.

It seems this latest CROM has an issue with more than 3 pages of PIDs??

I'm logging the following PIDs:

Ambient Temp
ECT
IN MAN AIR TEMP
Actual Spark Cyl1
Air Charge
Injector PW Cyl1
IAT
MAP
BARO OBDII
Desired FA CYL1
MF Counts Current
MPHX64
Time from start run
KNK FUEL RETARD
KNK LT RETARD
KNK ST RETARD
Knock Sensor 1 Volts
Knock Sensor 2 Volts
RPM
TPS %

No external analog inputs.

it sounds like the issue is specific to your custom layout.
Id suggest making a new one from the current crom and see how that does.

[Speedy!]

Removed the WB pids and still had the same issue.

Borrowed a friends brand new Trinity, exported my gauge layout to SD card, and imported on his Trinity (unmarried of course). Hooked it up to my car and lock ups galore.

Deleted the gauge layout and rebuilt it from scratch on this second Trinity. Things seem fine until the 4th gauge page, then things become unstable from there on out.

This was not the case with previous CROMs I've used on my 2009 R/T Challenger.

It seems this latest CROM has an issue with more than 3 pages of PIDs??

I'm logging the following PIDs:

Ambient Temp
ECT
IN MAN AIR TEMP
Actual Spark Cyl1
Air Charge
Injector PW Cyl1
IAT
MAP
BARO OBDII
Desired FA CYL1
MF Counts Current
MPHX64
Time from start run
KNK FUEL RETARD
KNK LT RETARD
KNK ST RETARD
Knock Sensor 1 Volts
Knock Sensor 2 Volts
RPM
TPS %

No external analog inputs.

it sounds like the issue is specific to your custom layout.
Id suggest making a new one from the current crom and see how that does.

Built the layout from scratch and skipped the WB02 pids which you said don't work. Same issue.

Is there a better way to get support for this $600 device than this forum? I'm getting a bit frustrated if I'm honest.

[mikel]

i dont think this is related ot the number of PIDs, but more likely a specific pid in that list thats causing the issue.

You can feel free to email me if you prefer, mlitsch @ powerteq.com

Thanks

[passmg2]

I have the exact same problem with my Trinity being unstable since the 13g crom update for my Jeep. What a pita! I've been on the phone with Diablo support 4 times. We tried a lot of things. It's been hard reset as well. It's not my layout. This all started with the crom update. Can I go back to the previous crom and if so can you give me instructions on how to do that please? I've spent hours on this over the last couple of weeks and nothing has worked so far. What next?

[mikel]

I have the exact same problem with my Trinity being unstable since the 13g crom update for my Jeep. What a pita! I've been on the phone with Diablo support 4 times. We tried a lot of things. It's been hard reset as well. It's not my layout. This all started with the crom update. Can I go back to the previous crom and if so can you give me instructions on how to do that please? I've spent hours on this over the last couple of weeks and nothing has worked so far. What next?

we resolved the issues here by removing the odd misfire PID in the layout, and it seems to be working as expected thus far.

Thanks