I checked the Realdash Target identifiers, I couldn’t find it.
And I find a improvable feature of multicast, I’m having an issue when I multicast trip data from my dashboard to RealDash on the head unit. If the two values aren’t identical, the display keeps jumping back and forth between them. I’d like to avoid this, but the data inevitably gets out of sync sometimes.
My current workaround is to manually reset the trip on both devices to zero to keep them consistent, but it doesn’t always work well. I’m now considering assigning the trip data to some unused dummy (like dummy30 to dummy39), multicasting those to the head unit, and then re-mapping them to the internal trip variable.
This feels quite tedious and I’m concerned it might put an unnecessary load on the hardware. Is there a cleaner way to handle this? Perhaps there is a way to force the device to prioritize the incoming multicast data for both the display and the internal calculations?