RealDash version 2.7.0

2.7.0 released 7.9.2026

New:

  • Race track: Kaanaa, Finland.

Fixes:

  • Fixed keyboard control issues on global popups.
  • Fixed a crash on non-animated GIF loading.
  • Fixed crash on networking.
1 Like

Hi Yani,

Moe from Muxwiring , we have major issue with rev 2.69 and 2.7.0, in RealDashcan mode as we use with the module, all the button do not work, buttons that are for HOLD mode, they send go down find but release goes on forever and locks all the other buttons, aslo keys with SET on release, they act like the button is pressed and release so many times, may be 12 times, it will all great till updates, and can not go back, my cars is all locked up, the windows 11 also stopped it just got update this morning to 2.6.9, this has worked for ever not sure what happened, hope you can help to fix this and release newer version. thanks so much

Yes, 2.6.9 introduced an feature that when an input is changed via CAN messaging, the message is duplicated into the can BUS. This was done to make system reliable with very busy CAN bus that may lose packages on the way.

Same idea applies to the Hold action. After hold button is released, the release value is send multiple times to prevent hold value “sticking on” due possible lost message.

You know that I’m using Muxwiring modules in our DEATHFISH 2 demo car and I have not experienced any negative issues with this change. Please explain why your modules would hang if message is sent multiple times. Send an email if you do not wish to discuss publicly.

This may be ok for some but not all, may be this should have been option to enable it.
Now why it does not work.

  1. In Hold mode in rev 2.6.8 it send Down and then up for about 700 mssec, not great idea but did not have negative effect, the 2.6.9 send for ever once it is released, so it locks all all the other functions.
    2.We have a keypad that we use for entering passwords and other set able items, we have a register that gets set by value of the key, like 1,2,3, and so on, when you press a 4 RD send and set the reg. to 4 we read it and clear it, and when it is pressed again RD take value and set it to 4, and so on, so for each key press we get 4 then value becomes 44 if 4 was pressed twice, and this has been great for over 5 years now, with 2.6.9m just touching 4 once we get 55068 ( 10 time 4 enter on calculator and use 16 bits only), like the button was pressed 10 times, because of your new REV.
  2. Toggles, sort of work, but again no need to send 10 time, when you touch a button , the button lights up and there should be feedback, this is how we know the massage got there we do not need to be send so many time, if the button did not light you press again just like anything else.

All this will be less of an issue if we have way to go back, my laptop which I use for development is totally useless right now. Please let me know if you need more info.

BTW, Module do not hang, just key do not function, specially after any hold buttons, to stop we have to close and reopen or make data source to none and reenable

I can disable this feature from Muxwiring connection and provide Android version for testing. Drop me an email if its possible for you to test it. contact@realdash.net.

sent you email.
thanks much.