Syvecs Forums

Hi all, I'm new to Syvecs ownership having just bought a Syvecs equipped MR2 Turbo.

I am considering buying one of these http://www.autosportlabs.com/product/racecapturepro/ and adding the bluetooth module to allow me to do the following:

1. Log large amounts of telemetry and overlay GPS information
2. Capture CANBUS info from the Syvecs
3. Provide a display in the cabin to monitor certain engine based things (intake temp/knock etc)
4. Provide lap timing.....
5. Control devices on the car based on certain engine based things

I 'm hoping that someone intelligent on here can help me with these questions before I commit any cash....

1. Will the Syvecs 'talk' to this device over CANBUS?
2. Can 'things' be changed on the Syvecs over the CANBUS?
2a. What sort of things might I want to change?
3. Do Syvecs offer an alternative solution that has all the bells and whistles of the product above?

Please go easy on me, I'm a noob who doesn't know my sCAL from my elbow, and I haven't even connected a laptop to the ECU yet. I do know IT, but I'm not a developer.

Cheers

Paul

Hiya Paul!

The link you posted isn't working for me right now. In regard to your points etc :

1) Logging large amounts of data and GPS info externally should be fine. The Custom CAN stream allows you to send up to 80 run mode parameters at up to 100Hz each. You'de just need to choose what you want to log.... your external logger would need to be able to receive the stream though.

2) Capturing CAN bus info shouldn't be a problem. In the Custom CAN config you set the frame numbers and contents. Each frame contains up to four parameters which are transmitted as 16 bit big endian. The bus runs at 1MBit/sec when using this config. The formula for getting the raw values into engineering units are displayed in SCal when you select a parameter.

3) Certain dash products already display runmode parameters (eg Race Tech DASH2, AIM Sport Strada / Pista, MoTeC SDL/ADL etc) so it is clearly possible, it's just a case of finding something that will accept data in the format that we send it.

4) Lap timing is normally a function of a race dash more than the ECU, but the ECU does have a lap beacon input available which helps with datalog analysis.

5) If you want to control things beyond the strategies provided by the ECU firmware then you'll need a CAN enabled device that can be configured to receive the telemetry data and act upon it.

In answer to the questions themselves :

1) Yes, it will "talk" to other stuff on the CAN bus, but "listen" less. If you want to do things based on info coming *out* of the ECU then that is easy enough. If you want to feed stuff back *into* the ECU then that too is possible but presently the list of parameters that can be received is limited.

2) Certain things like the Cal position can be changed based on CAN frames received by the ECU. Things like ALS arm etc can also be received. Eventually more "things" will be possible. If you could elaborate on what "things" you might want I can give further info on whether it can be done.

2a) LOL, I thought you were gonna supply that sort of info The "normal" type of stuff is "virtualising" stuff that you would have ordinary switches for under other circumstances, such as CAL select, TC select, ALS Arm etc

3) Since the link isn't working for me I cannot look at the features so I cannot give a meaningful comparison at this time.

Hope this helps,

Pat.

Hi Pat, thanks for the reply.

Not sure what was wrong with the link but it seems to be working ok now.

I have to be honest and say that I don't really know what I might need to capture, or what I could do if I can control the ECU on the fly. I'm doing this from my desk at work, and don't get to spend nearly enough time in the car on the track....

I've been speaking to the AutoLabs distributor, and he reckons that the RaceCapture device won't be able to understand the CAN stream from the Syvecs due to software limitations, so I'd say that certainly means that I won't be able to change any of the settings on the Syvecs from the cabin. Thinking about it, I can't actually think of any settings I'd need to change as I already have the map selector switch in the car with a range of maps.

For now, I think all I really want is the data logging functionality provided by the RaceCapture, and I will need to take a feed from the tacho wire for revs.

I guess I'll have to do some more reading to fully understand what is required to make the two devices 'communicate'. Not sure if it makes any difference, but apparently the RaceCapture device uses the Lua language.

pat wrote:
4) Lap timing is normally a function of a race dash more than the ECU, but the ECU does have a lap beacon input available which helps with datalog analysis.
Hope this helps,

Pat.

Dear Pat,

It is possible to forward this beacon input to an exetrnal device via CAN?
I can't find it at frame content