Hey All,
First a quick intro - my name is Sasha Anis and I'm from a motorsport electronics background. I spend most of my days tuning Motec and other engine management systems. Being a firm believer in climate change and appreciating the efficiency of electric power (and let's face it, being inspired by Tesla), I decided it was time to build an electric sports car that is as capable on the racetrack as it is on the road.
So, Why an Evora?
Simple really. The body comes off, so access is great. With a Tesla drive unit, there needs to be enough space to fit the drive unit and batteries, so a mid-engined car is really the optimal layout. The options were a Cayman (uni-body, 4 wheel mac-strut), an Elise (basically a Tesla roadster at that point), a Ferrari 360 or something in that era (too expensive and old). No one will miss the Naturally Aspirated V6, so it's the ideal car that has a great deal of potential once you double the power output. Oh did I mention it has an all aluminum chassis?
Who the hell is this guy? I've raced as a driver and crew chief in Continental Tire Sports Car Championship (Camaro Z/28R and Aston Martin DB9 GT4), as well as World Challenge and have won championships in the Canadian Touring Car Championship with cars we built (Hyundai Genesis Coupes). My personal racecar is a Nissan 350z GT car with a 3.5L V6 (sound familiar?) with a Quaife sequential gearbox, 12" wide wheels all around, big slicks, carbon bodywork etc. I'll attach a few photos, and here's a video of the Z in a regional race at Mont Tremblant with some GT3 machinery:
Mont Tremblant Road Racing with the 350z Recently:
Last week I purchased a 2014 Evora with Serial # 514. If you look through some photos of my stuff, you'll know that 14 is my lucky number, so I'm feeling pretty positive about how this project is going to turn out. We had it out at the local test track for a few laps to configure the dash and do some CAN sniffing, as well as to get a benchmark. With old-ish tires the car did a 1:21.9 - to compare my Z does a 1:12.1 at the same track. So there is a lot of room to grow. The ultimate goal will be a low 1:16 for the car, in full street car trim with all of the creature comforts. Here's a link to a clip of the car going over curbing while on power. Talk about well tuned dampers. The car is SO composed, and ridiculously fun to drive. It hardly feels like it is on street tires!
https://www.instagram.com/p/BMfTbRjgg8f/?taken-by=onpointdyno
We've already installed Motec's largest display - the C1212 (12"!) with display creator, which enables us to design whatever kind of display we want on the logger, while still keeping the Motec quality functionality, logging and robustness I've come to expect and love. We already have a Tesla Model S drive unit and a Chevy volt battery, once we finish doing the CAN decoding for what we need, it will be time to strip the Evora down and start on the mounting.
I'm sure I will need a lot of help from you all here, being so new to this car and to the brand. So I hope that in exchange for some of the information I share, you will all be helpful with this project as well. I'm excited to share it with you all, and I hope you enjoy it and don't get too discouraged by the lack of a screaming gasoline burning four stroke. It will still be awesome, I promise.
Here is a little bit of CAN information that I've found for those of you that might find it useful if you want to connect a data logger to your Evora:
CAN Data we have processed so far:
Evora uses a 500kbps bus speed. Devices on the bus are ECU, Dash, Yaw Sensor, Steering Angle Sensor, ABS Module (and trans module for IPS)
ECU - 0x114:
Engine Speed - 0x114, Byte 0-1, Length 2 Bytes, Little Endian (Intel) format, unsigned, scale 0.25 gets it close to engine RPM but I don't believe that is quite right.
Accel Pedal Position - 0x114, Byte 3, Length 1 Byte, (0-255), unsigned scale 0.4 will get you close to 0-100%
Clutch Position - 0x114, Byte 4, Length 2 bits, offset 4, unsigned,shows clutch position as a 2 bit number 0, 1, 2
Stability / Traction Status (from ECU) - 0x114, Byte 4, Length 1 bit each, offset 2 and 3, one bit set when sport mode active, one bit set when TC is off.
Steering Angle Sensor - 0x85:
Steering Angle: 0x85, Byte 0-1, Length 2 bytes, Little Endian (Intel) format, signed, scale 0.05 gets you very close to steering wheel angle
Steering Rate (speed of steering): 0x85, Byte 2, Length 1 byte, Little Endian (Intel) format, signed, scale 10. Not sure units.
ABS - 0xA2, 0xA4, 0xA8:
Wheel speeds are very strange. They appear to be either 12 or 14 bit numbers although only 12 are set (You would need to exceed 255km/h to see if the 13th bit will be set). If you're staying under 255km/h you can mask half the byte which should allow you to get these values into a Motec logger.
Wheel Speed LF - 0xA2, Byte 0-1, Length 14 bits, Little Endian (Intel) format, unsigned, scale 0.0625 gets km/h
Wheel Speed RF - 0xA2, Byte 1-2-3, Length 14 bits, offset 6 on byte 1, same as LF for the rest of the settings
Ground Speed / Gauge Cluster Speed (10km/h too high at 100km/h) - 0xA2, Byte 3-4-5, Length 14 bits, offset 4 from Byte 3 bit 0. Rest of settings the same as Speed LF
Wheel Speed RR - 0xA4, Byte 0-1, Length 14 bits, Little Endian (Intel) format, unsigned, scale 0.0625 gets km/h
Wheel Speed LR - 0xA4, Byte 1-2-3, Length 14 bits, offset 6 on byte 1, same as RR for the rest of the settings
Yaw Sensor - 0x303
Lateral G - 0x303, Byte 4, Length 1 byte, Little Endian (Intel) format, unsigned, scale TBD, start with 10 for the scale and -1250 for the offset.
ECU To Dash - 0x400, 0x402
Engine Temp - 0x400, Byte 5, Length 1 byte, Little Endian, unsigned, scale TBD 1-1 gets somewhat close in F but it is not correct.
Fuel Level - 0x400, Byte 4, Length 1 byte, Little Endian, unsigned, 0-255, 255 is full, 0 is empty. Scale to 60L if you want to estimate remaining litres.
TMPS - I will have to confirm the corners for these and the scale. I don't have it in front of me right now. They are on 0x402, each 1 byte, bytes 0 through 4. Little endian, unsigned.
More photos and updates will come. We will also have all of the base evora (non supercharged, MY14) engine / gearbox stuff for sale, naturally.
Thanks for reading!
Sasha Anis
OnPoint Dyno
First a quick intro - my name is Sasha Anis and I'm from a motorsport electronics background. I spend most of my days tuning Motec and other engine management systems. Being a firm believer in climate change and appreciating the efficiency of electric power (and let's face it, being inspired by Tesla), I decided it was time to build an electric sports car that is as capable on the racetrack as it is on the road.
So, Why an Evora?
Simple really. The body comes off, so access is great. With a Tesla drive unit, there needs to be enough space to fit the drive unit and batteries, so a mid-engined car is really the optimal layout. The options were a Cayman (uni-body, 4 wheel mac-strut), an Elise (basically a Tesla roadster at that point), a Ferrari 360 or something in that era (too expensive and old). No one will miss the Naturally Aspirated V6, so it's the ideal car that has a great deal of potential once you double the power output. Oh did I mention it has an all aluminum chassis?
Who the hell is this guy? I've raced as a driver and crew chief in Continental Tire Sports Car Championship (Camaro Z/28R and Aston Martin DB9 GT4), as well as World Challenge and have won championships in the Canadian Touring Car Championship with cars we built (Hyundai Genesis Coupes). My personal racecar is a Nissan 350z GT car with a 3.5L V6 (sound familiar?) with a Quaife sequential gearbox, 12" wide wheels all around, big slicks, carbon bodywork etc. I'll attach a few photos, and here's a video of the Z in a regional race at Mont Tremblant with some GT3 machinery:
Mont Tremblant Road Racing with the 350z Recently:
Last week I purchased a 2014 Evora with Serial # 514. If you look through some photos of my stuff, you'll know that 14 is my lucky number, so I'm feeling pretty positive about how this project is going to turn out. We had it out at the local test track for a few laps to configure the dash and do some CAN sniffing, as well as to get a benchmark. With old-ish tires the car did a 1:21.9 - to compare my Z does a 1:12.1 at the same track. So there is a lot of room to grow. The ultimate goal will be a low 1:16 for the car, in full street car trim with all of the creature comforts. Here's a link to a clip of the car going over curbing while on power. Talk about well tuned dampers. The car is SO composed, and ridiculously fun to drive. It hardly feels like it is on street tires!
https://www.instagram.com/p/BMfTbRjgg8f/?taken-by=onpointdyno
We've already installed Motec's largest display - the C1212 (12"!) with display creator, which enables us to design whatever kind of display we want on the logger, while still keeping the Motec quality functionality, logging and robustness I've come to expect and love. We already have a Tesla Model S drive unit and a Chevy volt battery, once we finish doing the CAN decoding for what we need, it will be time to strip the Evora down and start on the mounting.
I'm sure I will need a lot of help from you all here, being so new to this car and to the brand. So I hope that in exchange for some of the information I share, you will all be helpful with this project as well. I'm excited to share it with you all, and I hope you enjoy it and don't get too discouraged by the lack of a screaming gasoline burning four stroke. It will still be awesome, I promise.
Here is a little bit of CAN information that I've found for those of you that might find it useful if you want to connect a data logger to your Evora:
CAN Data we have processed so far:
Evora uses a 500kbps bus speed. Devices on the bus are ECU, Dash, Yaw Sensor, Steering Angle Sensor, ABS Module (and trans module for IPS)
ECU - 0x114:
Engine Speed - 0x114, Byte 0-1, Length 2 Bytes, Little Endian (Intel) format, unsigned, scale 0.25 gets it close to engine RPM but I don't believe that is quite right.
Accel Pedal Position - 0x114, Byte 3, Length 1 Byte, (0-255), unsigned scale 0.4 will get you close to 0-100%
Clutch Position - 0x114, Byte 4, Length 2 bits, offset 4, unsigned,shows clutch position as a 2 bit number 0, 1, 2
Stability / Traction Status (from ECU) - 0x114, Byte 4, Length 1 bit each, offset 2 and 3, one bit set when sport mode active, one bit set when TC is off.
Steering Angle Sensor - 0x85:
Steering Angle: 0x85, Byte 0-1, Length 2 bytes, Little Endian (Intel) format, signed, scale 0.05 gets you very close to steering wheel angle
Steering Rate (speed of steering): 0x85, Byte 2, Length 1 byte, Little Endian (Intel) format, signed, scale 10. Not sure units.
ABS - 0xA2, 0xA4, 0xA8:
Wheel speeds are very strange. They appear to be either 12 or 14 bit numbers although only 12 are set (You would need to exceed 255km/h to see if the 13th bit will be set). If you're staying under 255km/h you can mask half the byte which should allow you to get these values into a Motec logger.
Wheel Speed LF - 0xA2, Byte 0-1, Length 14 bits, Little Endian (Intel) format, unsigned, scale 0.0625 gets km/h
Wheel Speed RF - 0xA2, Byte 1-2-3, Length 14 bits, offset 6 on byte 1, same as LF for the rest of the settings
Ground Speed / Gauge Cluster Speed (10km/h too high at 100km/h) - 0xA2, Byte 3-4-5, Length 14 bits, offset 4 from Byte 3 bit 0. Rest of settings the same as Speed LF
Wheel Speed RR - 0xA4, Byte 0-1, Length 14 bits, Little Endian (Intel) format, unsigned, scale 0.0625 gets km/h
Wheel Speed LR - 0xA4, Byte 1-2-3, Length 14 bits, offset 6 on byte 1, same as RR for the rest of the settings
Yaw Sensor - 0x303
Lateral G - 0x303, Byte 4, Length 1 byte, Little Endian (Intel) format, unsigned, scale TBD, start with 10 for the scale and -1250 for the offset.
ECU To Dash - 0x400, 0x402
Engine Temp - 0x400, Byte 5, Length 1 byte, Little Endian, unsigned, scale TBD 1-1 gets somewhat close in F but it is not correct.
Fuel Level - 0x400, Byte 4, Length 1 byte, Little Endian, unsigned, 0-255, 255 is full, 0 is empty. Scale to 60L if you want to estimate remaining litres.
TMPS - I will have to confirm the corners for these and the scale. I don't have it in front of me right now. They are on 0x402, each 1 byte, bytes 0 through 4. Little endian, unsigned.
More photos and updates will come. We will also have all of the base evora (non supercharged, MY14) engine / gearbox stuff for sale, naturally.
Thanks for reading!
Sasha Anis
OnPoint Dyno
Attachments
-
32.2 KB Views: 4,037
-
121.9 KB Views: 4,201
-
98.7 KB Views: 4,063
-
109.6 KB Views: 4,071
-
68.5 KB Views: 4,069