Alright, will check.
Thank you. Also any chance you have those data value IDs I asked earlier?
Do you have the target IDs for distance till next service and hours till next service?
Also any updates on the number of cel codes?
I’m having a new issue related to cel codes.
I used torque originally to check for what specific cell code I had. Stopped using them once RealDash was able to tell me cel codes. I decided to double check yesterday and the cel code Torque gives me is completely different then the cel code that RealDash gives me.
I get p0420 from torque and you guys give me p0104.
Send a debug log while reading error codes:
How to send a debug log - General / Frequently Asked Questions - RealDash Forum
Just sent one right now, 2010 Acura TSX
Alright, thanks. Will check.
Any updates on the triggers using miles and not km if the settings are in miles?
Also do you have the value id for ‘hours till next service’ and ‘distance till next service’?
Triggers with user units is not trivial fix, as it would break existing dashboards. Also, if you make a dashboard with Triggers on Miles and someone else uses it with Kilometres, it would not work right. While we think of a good solution, we just must agree that Triggers use metric values.
The Speak Text action is capable of speaking input values, and it will respect user units on next release. This will help a little bit.
I have still not found time for updating the input ID list. But ID for Hours until service is 775.
The support for USB cameras has postponed 2.4.3 release for two weeks already. And it seems that release will have to wait for another week at least.
This is interesting, your vehicle responds to error code request with:
18DAF1110443010420
18DAF11D024300
As far as I’m aware of, This should result to error code ‘0104’, which is a P code P0104.
So are you 100% sure that P0420 is the actual ‘real’ DTC that your car has active? Can you confirm that on a proper scanner? Any vehicle that I know places the error codes right after ‘43’ indication that its a response to DTC request 03.
Could it be sending the character as well after the 43; so 43010420 is actuall 01 = P and then 0420 for the code;
Maybe 01 - P, 02 - C, 03 - B and 04 - U
So 43041000 would be U1000
Just a thought?
That’s where I got confused. I was told the same thing in email by a Dev but with temperature I’ve never had that issue. My triggers for temperature work fine in °F even though it’s initial value is in °C.
The only issue is as you said is speak text where it’ll say the value as °C instead.
Edit: Maybe you guys should look into the coding on ‘Coolant Temperature’ and see how that was done. I use °F and it properly notifies me when the engine is below 180°F, when it hits 180°F and when it’s above 214°F. I’ve compared it to my stock dash which matches as the gauge starts to rise once I’m above 217°F.
So I’m assuming something in the coding there should be slightly different then the coding for miles.
I sent an email again recently but there is a dashcam that supports wifi. I got it 2-3 years ago for work. I can stream the video chanel to VLC and it works, I only think no audio. It uses RTSP:// I believe but it won’t work on RealDash. Maybe you can add it to the list. Only issue I’ve found is my hotspot changes the IP address on the camera if I don’t drive my car for a few days.
I can pass by an AutoZone or O’Reilly’s to double check but torque pro has usually been accurate with my car. I know I need a new catalytic as it’s been like that for a year. The other code is only 2 months new.
Also what was weird to me is that I’ve had another code that would show up with the p0420 code and those showed correctly on both apps.
This is the first time p0420 doesn’t show up on your app and gives me the other code instead.
Problem for me is that any other vehicle that we have tested lists error codes right after the ‘43’ reply code. In your case we would need to jump over the ‘01’ on the reply but there is no way to identify if 01 should be skipped or not.
Let me unplug a sensor to see if I can trip another code and send you new data.
Also would you have the data value of “Distance till Next Service”?
Also regarding RTSP should I be entering the URL a specific way? I’ve been using the way the manufacturer told me and it’s worked for me on VLC just not on RealDash.
364
Your RTSP stream may be in format that is not supported by Android ExoPlayer.
Just sent a new debit log to you.
This is me with the original code but now unplugging the MAF sensor while engine was running.
I can take a look, but if issue is the same that there is an extra byte at the beginning of error codes, I’m not going to fix it as it would break error code reading for all other vehicles we have tested on.
Edit; I did some investigation. The C1555 error is not there, so that must be some kind of an erroneous read. Good news is that I did found a way to parse your error codes without breaking the support for other vehicles.