Race Technology Dash2

[Abbosevolution]

Am looking for help with the installation/config of my Dash2 so that I might yet get to drive my Ultima this summer. Apart from a few minor issues the build has gone very well and I'm 95% finished with just the dash to sort. Have had some great help from Mark (356speedster) who has provided the config files that work on his setup, he's using the same engine/ecu/dash setup as me. Trouble is that despite considerable hours spent on the Dash I still cant get the thing to work properly. I can get the analogue inputs shown in the dash but nothing sensible via the CAN interface. Have contacted Race Technology and they have helped but not to conclusion. So anyone out there down south with a knowledge of the dash2 and its installation available to help someone in need, it would really be appreciated.

Edited by Abbosevolution on Sunday 25th May 12:27

[anonymous-user]

Where abouts are you? I know nothing specific about RTD2s but i know a lot about CAN ! (with the ability to log/decode real time CAN data and configure .dbc files etc)

[Abbosevolution]

Just off the M23 on the outskirts of Crawley

[macgtech]

If I recall we had a lot of problems with this in the early days and resorted to using RS232

[Abbosevolution]

macgtech said:

If I recall we had a lot of problems with this in the early days and resorted to using RS232

Thanks - glad to see i'm not the only one having issues. I've now spent over 25 hours on this, have a call out with the company and hope i can resolve, after all i cant be the only one using a Dash2 with a GM ECU can I ?
Have had lots if input from buddies yet have moved no further on. I've found the Dash2 easy to configure using the analogue inputs but no joy with that via the CAN adapter. Lets hope it's a simple hardware issue and the adapter supplied was incorrect as this is the only probable solution I can come up with (hoping). I'll keep you posted on progress and supplier response.
PS enjoyed the video, great stuff

[anonymous-user]

I hope you get it sorted. Unfortunately i'm a fair way away (Northampton) but if you're really stuck, and don't mind paying my travel expenses i could probably get down to you and at least find out which bits of the CAN system are working (like the basic, "is there actually CAN data coming out the ECU" etc!)

[Abbosevolution]

Max_Torque said:

I hope you get it sorted. Unfortunately i'm a fair way away (Northampton) but if you're really stuck, and don't mind paying my travel expenses i could probably get down to you and at least find out which bits of the CAN system are working (like the basic, "is there actually CAN data coming out the ECU" etc!)

Thanks ever so - going to give the supplier a chance before I start spitting the dummy but will keep your offer in mind thanks, its appreciated.

[356Speedster]

Max-T.... I'm in Redditch and have the same setup at Steve. I've got all the basics out of the ECU and have provided Steve with my config files (although I know he's got some issues re-using them). I'd like to know if there's more data that can be pulled from the ECU, so if you're in the area and don't mind lending your know-how, myself, Steve and a few others with this setup would appreciate it

[Abbosevolution]

+ 1 Mark - Happy to travel to sort out - anything, well almost anything to get on the road this summer

[anonymous-user]

Okies, i'm sure we can sort something out ;-) Let me know how you get on with your current leads, and if that draws a blank we can arrange something!

I'm assuming that the GM ecu does not need to be "prompted" to send out the CAN data? IE it will just broadcast its normal CAN message packets when active, and the DASH is "passive" and just listens for those packets and strips out the info it wants (so you 'just' set up the CAN Msg ID and byte location/scaling in the dash calibration?) Because CAN is a "multidrop" architecture, where all devices listen simultaneously to the data bus, and only act on message IDs that match their input filters, you can get issues with systems designed for lots of devices only having 2 (ECU->DASH). Often these can be fixed with changing the bus termination resistors, but sometimes it is an issue with a "bootup race". In this case, the devices powerup, and start to send out data, but if the other device isn't ready to receive, you get a bus error that may then suspend transmission from the master device etc!

One of those things that is difficult to diagnose without the proper tools....... ;-)

[356Speedster]

Max_Torque said:

Okies, i'm sure we can sort something out ;-) Let me know how you get on with your current leads, and if that draws a blank we can arrange something!

I'm assuming that the GM ecu does not need to be "prompted" to send out the CAN data? IE it will just broadcast its normal CAN message packets when active, and the DASH is "passive" and just listens for those packets and strips out the info it wants (so you 'just' set up the CAN Msg ID and byte location/scaling in the dash calibration?) Because CAN is a "multidrop" architecture, where all devices listen simultaneously to the data bus, and only act on message IDs that match their input filters, you can get issues with systems designed for lots of devices only having 2 (ECU->DASH). Often these can be fixed with changing the bus termination resistors, but sometimes it is an issue with a "bootup race". In this case, the devices powerup, and start to send out data, but if the other device isn't ready to receive, you get a bus error that may then suspend transmission from the master device etc!

One of those things that is difficult to diagnose without the proper tools....... ;-)

Interesting! I can report that the CAN adapater which Race Tech supply (it's a seaprate interface specifically for the GM ECU... and possibly others of the same architecture, I guess) is configured as you describe: Msg ID, byte location, scaling, etc... When I get home I can take a screen shot of my screen and show you better.

On my car, it's working nicely. The RPM, water temp, inlet temp and a few other bits & pieces are coming thru' the CAN adapater and being passed to the Dash2 OK. What I'd like it to find out what other data that's being presented by the ECU is readable and can be configured to show on the Dash2. I'll add a screen shot later

I do have a log file that was captured from my ECU using the Race Tech data logger. This can then be read by the free to download Race Tech software and should show better what's being presented (apparently!!). I can send the file and a link to the s/ware if you think that'll help too?

Thanks for your help, it's great to find someone who understands these things better!

[356Speedster]

As promised, here's a screeshot from the RT CAN config program for the adapter (obviously the Ultima doesn't use all these settings, I never got round to clearing out the unused settings)...


If you drop me a PM, I can send you the actual file, as well as the log files generated on the data logger, plus the software download link

Thanks for your help!

[anonymous-user]

A quick perusal of the RT website for their CAN adaptor suggests it a "dumb" CAN -> RS232 bridge. i.e. it just passively listens to the CAN bus, waiting till it receives a message with an ID that matches it's filters (set with the config tool) then it picks the correct bit stream from that CAN message (again, using the info in its setup config (ie bit length 16, start bit 32, etc). Then that data is re-packed into the RS232 serial format the Dash expects to receive, and that is sent out to the dash.

This suggest the GM ecu just broadcasts it's data without any polling, which means there is quite likely to be a lot more data available on the CAN bus.

[Abbosevolution]

So much to my disappointment i've had to admit defeat with my Dash2 install. Despite the hours spent by myself and friends i have finally come to the conclusion that I need an expert to complete this part of the build. Race Technology have been as helpful as they can but being a significant distance away its not that easy. Being fortunate enough to own a covered trailer i have arranged to take my 95% built car up to the company where they have agreed to look at the issue, the rate being charged quite reasonable in my opinion. In my mind I think the issue is going to be something simple but as with some problems, sometimes you cant see the wood for the trees. I'll update idc on what was the issue, fingers crossed

[Abbosevolution]

So a big thanks to Race Technology for sorting out the problem. It turned out to be two faulty CAN adapters and a fault with the GM element of the loom. Full speed ahead with the build

[356Speedster]

Abbosevolution said:

So a big thanks to Race Technology for sorting out the problem. It turned out to be two faulty CAN adapters and a fault with the GM element of the loom. Full speed ahead with the build

Glad to hear it, Steve! 2 faulty adapters is plain unlucky.... you might never have found the loom fault, so while it's been frustrating, sounds like it could have been worse without their help!