Any updates on this issue?

mikel wrote:Theres a big update coming soon that will address this and any other pid display issues ideally. Hoping to see it in the next week.

Mike is this update you talking about going to include fixes for the EAS data logging issues we have been waiting on for over a year now?

rkuzniewski wrote:A permanent fix is coming when??? When hell freezes over? I have been waiting since the end of April for a fix!

It will never be fixed I've been waiting since June of 2019 for a fix on the EAS data logging and still nothing they are all talk and no action.

Hey mike it's been a year now any updates

mikel wrote:ok, let me see the tcm backup as well please.

I didn't think an 06 ram had a tcm I thought it was built into the pcm ?

Same issue here ECT, AAT are in Celsius and IAT is Fahrenheit . I called tech support about it in Sept and never heard anything back.

I keep having this p0300 code pop up...I have changed coil packs, plugs and camshaft sensor...need help. Does my t2 have fuel pressure gauge? is there any other settings i can use to diagnose problem?
I would check for broken valve springs or worn cam and lifters. I don't think the T2 will read ...

orange345 wrote:Updated t2 will not read pcm

You need to post more info like year make and model to many variables.

Mike does a fantastic job, I think we all can agree.....It’s not his fault !!!! for the EAS data logging wows, he works for the company, but some of us here with major mods that want to see their AFR / boost fuel /pressure etc through a recording and not starting at a dash board at 140 mph that’s ...

Mike does a fantastic job, I think we all can agree.....It’s not his fault !!!! for the EAS data logging wows, he works for the company, but some of us here with major mods that want to see their AFR / boost fuel /pressure etc through a recording and not starting at a dash board at 140 mph that’s ...

sbenja2008 wrote:

mikel wrote:There is development happening to get this working, yes.

Any updates yet?

Any updates yet? Its been 8 months and still no news on datalogging with the EAS system.

Put an 87 tune on my 2017 Ram 1500- cel came on-- cleared it using the Trinity 2 EX- upon next start it appears again. Rolled back to stock tune- still appearing upon every restart of the truck.

Help?

Dave Weig
[email protected]
2017 Ram Rebel
Hemifever ECU (unlocked)
T2 EX

Possible Causes
Error ...

mikel wrote:There is development happening to get this working, yes.

Any updates yet?

I have a 2010 challenger 5.7, What is the difference between the 91 tune and the diablo tune. I started with the 91 ran fine switched to the diable tune and on WOT it started to backfire and reported 14 on knock so I shut it down went back to 91 wondering why it runs so awful on the diablo tune ...

Dragon23 wrote:Maybe I'll write to Santa Ho Ho Ho

Lol maybe he and his elves can fix it seeing how Diablosport can't seem to.