Speeduino

stum wrote: ↑Fri Jan 10, 2020 7:11 pm Ok, I stand corrected. It was running good, and I had not looked at it for a while. But recently there must have been a update to realdash, it is has changed how it loads the .ini file. And it will no longer pharse the speeduino.ini file, or allow you to pick one.

So my dash has stopped working too. STINK......

I will log back into the RealDash fourm and see if I can find/get an answer...

Cheers

There should be no changes in RealDash Megasquirt connection code in last 6 months.

Yes, we wish to add 'native' Speeduino support into future release of RealDash. As I have not used Speeduino myself, I would appreciate some pointers on how to get started. Is there a specific way you would like to configure the connection in RealDash? Does Speeduino have its own custom serial protocol, and where to find info?

realdashdev wrote: ↑Mon Jan 13, 2020 9:41 am
There should be no changes in RealDash Megasquirt connection code in last 6 months.

Yes, we wish to add 'native' Speeduino support into future release of RealDash. As I have not used Speeduino myself, I would appreciate some pointers on how to get started. Is there a specific way you would like to configure the connection in RealDash? Does Speeduino have its own custom serial protocol, and where to find info?

For connection to the secondary serial see info here
https://speeduino.com/wiki/index.php/Se ... _interface

For primary serial the TS ini is your best source

Although we have a so called "legacy" mode on serial0 if we have native support it would be by far a better option.

realdashdev wrote: ↑Mon Jan 13, 2020 9:38 am

pazi88 wrote: ↑Fri Jan 10, 2020 5:34 pm Tried also the realdash but got really annoyed it. Lot of unnecessary useless stuff. Couldn't understand the logic of how to customize gauges. And worst of all. No real option to change away from imperial units...

To change units, go to Settings->Units & Values. Entire app is developed on metric, so that should not be a problem.

I agree that RealDash has (too)many 'stuff' in it, but could you elaborate a little bit how they are useless? RealDash will never achieve a typical mobile app simplicity, but we are still trying to improve.

I tried to run the realdash in my android car stereo, and did found that the labels for the units did not change from miles/farenheit, when I changed the settings. The speed reading actually changed correctly, but it always said mph.

And I especially find the 3D model of the car useless and annoying to use. To enter the dash, I need to rotate the car, open door and then thouch the dash to enter there. Every tine I open the app.

pazi88 wrote: ↑Mon Jan 13, 2020 11:10 am I tried to run the realdash in my android car stereo, and did found that the labels for the units did not change from miles/farenheit, when I changed the settings. The speed reading actually changed correctly, but it always said mph.

And I especially find the 3D model of the car useless and annoying to use. To enter the dash, I need to rotate the car, open door and then thouch the dash to enter there. Every tine I open the app.

I agree, some people dislike the Garage with 3D car. Its there because its more fun to develop than boring list of settings. But I do not understand why need to go there every time you open the app? Garage is needed only once to setup the vehicle parameters and connections and then you usually do not have to go there.

Could it be that you did not allow RealDash to write external storage and for that reason it did not save any settings, like the metric units?

Hi Guys,

Just letting you know I've forked the Speeduino Repo an spent the morning adding a "Y" function to "Comms.ino" and prototype functions to "Comms.h" which writes the full Speeduino data array out of Serial 2(3) in RealDashCAN format.

I will do a Pull Request as soon as I've tested the code on hardware, but will try to get it done before the weekend.

Only catch is that I've spoken to RealDash admin on their forum and RealDashCAN can't support the "Y" character send... so what I would suggest is that I add a bit condition on one of Speeduino's GPI/Os so that you can just pull it low in hardware... that way you get the data steam for RealDash on power-up...

I just need concensus on which pin number you would prefer I use...?

I know there are two routes to interface to RealDash... 1.(Select Megasquirt and us Speeduino,ini) 2.(Select RealDashCAN and use a custom XML)...

the first option works, but only on Serial "0"... so you can't have your laptop plugged in and gauges working at the same time... tat's the reason for me writing the XML file and modifying Comms.ino in order to get all the data out over Serial3.

So, if all of this makes sense then please recommend which pin to use to trigger the RealDashCAN data stream and I'll get this Fork and Pull request wrapped up.

GhjEng wrote: ↑Mon Jan 13, 2020 2:12 pm Hi Guys,

Just letting you know I've forked the Speeduino Repo an spent the morning adding a "Y" function to "Comms.ino" and prototype functions to "Comms.h" which writes the full Speeduino data array out of Serial 2(3) in RealDashCAN format.

I will do a Pull Request as soon as I've tested the code on hardware, but will try to get it done before the weekend.

Only catch is that I've spoken to RealDash admin on their forum and RealDashCAN can't support the "Y" character send... so what I would suggest is that I add a bit condition on one of Speeduino's GPI/Os so that you can just pull it low in hardware... that way you get the data steam for RealDash on power-up...

I just need concensus on which pin number you would prefer I use...?

I know there are two routes to interface to RealDash... 1.(Select Megasquirt and us Speeduino,ini) 2.(Select RealDashCAN and use a custom XML)...

the first option works, but only on Serial "0"... so you can't have your laptop plugged in and gauges working at the same time... tat's the reason for me writing the XML file and modifying Comms.ino in order to get all the data out over Serial3.

So, if all of this makes sense then please recommend which pin to use to trigger the RealDashCAN data stream and I'll get this Fork and Pull request wrapped up.

The point here is that realdash dev are looking to make a native connection to speedy.
There is already protocol in place to stream the real-time from serial3 using the original A command or the upcoming n command( which is being tweaked along with the completion of can interfacing and broadcasting, so hence not formally released)
The later of which will have more real-time available than even serial0 does at present .
This is all part of the universal device expansion that was discussed recently for future external hardware such as dbw,abs,traction control as well as dashes.

By the way use of ms protocol is somewhat questionable especially knowing hoe protective they are of their IP.

Hahaha,

Ok, I’ll stop coding then Looking forward to the releases.

dazq wrote: ↑Mon Jan 13, 2020 3:01 pm The point here is that realdash dev are looking to make a native connection to speedy.

Exactly, and we are willing to write a Speeduino specific protocol parser into RealDash; what ever is the way that best suites the Speeduino users.

Great news guys,

Shout if any help is needed. Happy to pitch in.

Any idea on when this will be complete by? Just weighing up whether to wait, or if I should do my own code changes for the project I'm busy with now...?

Thanks for all the efforts on both sides

I agree this is brilliant news.

We have realdash working well with speedy via bluetooth.

For us it would be good to integrate the aux io better as i had to modify some of the unused standard outputs which were available in realdash e.g. afr2.

Also the ability to easily log data would make it almost perfect!