Adamw

Can you give us a log and a copy of the tune so we can see voltage and calibration setup etc.

It looks like I had the MAP lockout too low, I have bumped that up a bit and smoothed out the base pos table a bit. LetsLearn V1.2.pclx

Reduce air gap between sensor and wheel.

Bottom of this doc: https://linkecu.com/wp-content/uploads/2021/09/CAN-Cables-Manual-1.pdf FYI, The pin numbers are actually moulded into the seal end of the mating female receptacle.

The arming threshold is 1.5V on the DI's. Some VR ABS sensors will need some speed to reach that voltage.

There is a "joinable track" on the TT plug in to connect Ign 5. Solder the 2 pads together that are next to the expansion connector as shown below and Ign 5 will be available on pin 47. Ensure proper antistatic protection is used.

Attach your map.

Do you have one of the USB/CAN adapters recommended by realdash, such as this one?:

The fan shows on all the time in that log, but Aux 7 status is showing "Fault". Was the fan running or not in this log? What is the voltage on pin A12 with Aux 7 in test mode?

Are you using realdash and a USB-CAN adapter or OBD2? What is your native Language?

Ok, most of the CAN should be in there now. Fan & Fuel pump request, DBW Relay & CC Press sent to PDM. In the PDM config, status variables set up for multiposition boost & DBW target. Toggle variable set up for Pit & Qualify - These are triggered by keypad buttons 1-4 as examples. These are sent to ECU on CAN 1 output. Boost is received into ECU as GP Rotary Sw 1. DBW Target is Rotary Sw 2. Pit is CAN DI1 - set up as speed limit. Qualify mode is CAN DI 2 - GP Input 1. LINK_RyanH Custom_@20220217_074819_001620.xc1 PDM32 GT86R.5 V1.1.zconfig GT86R007PDM CAN.pclx

You can use the >file>compare function to see what I changed.

Try this map, I have changed quite a bit so may not work well yet. Need another log done with this map. After loading this map, do a store, then switch ign off for 10 sec to allow stepper to reset, before starting. LetsLearn V1.1.pclx

The error “ID Not in database” would mean you are using an ecu with older firmware. Update the firmware and you won’t get the message. This won’t cause any issues, so is not related to your start up issue. For the start up issue give us a log and triggerscope of it cranking, preferably when it shows the zero rpm problem.

Yes it looks like this always shows the value that is being pulled from the pre-crank prime table. Im not sure if that is intended to work that way or an oversight, but the actual pulse does only occur when the prime conditions are met (ign switch or start pos).

Your setup looks mostly how I would have done it. The only possible mistake I see is the "Start Node" message that you have set up in the CAN output. Im pretty sure this needs to be sent on ID 0x00, not 0x0A. Ideally we would only send this message once but I dont see a way to do it in RS3, not sure if sending it every second is going to upset things or not.

FYI, the CAN update is a free service, you just need to look after shipping to Link and back.

Can you attach the current map, it looks like it needs idle ign control set up and base position fixed.

Sorry no I forgot about you. Can you go into your CAN builder in RS3 and export the Motec Keypad template that you have set up.

I just looked in your tune and there is not even an idle valve assigned. Does it still have the stock stepper motor at the throttle body? Has it ever worked?

That google drive link is restricted. Go back into your drive and right click on it, >share> down the bottom, change to anyone with link.

For the log file you can share it using onedrive, google drive, dropbox, wetransfer etc. The initial change I would suggest is increase MAP lockout as with bigger cams your idle MAP is probably above the set 50kpa.

Example below. Launch button connected to DI2. GP RPM limit 1 will give a 5000RPM limit when the launch button is pressed, 10000RPM limit when button is not pressed. If you wish you can use instead a 3D table with for example wheel speed if you want to slowly increase RPM limit as car starts to move.

Actually, it looks like they have finally officially released an ARM64 version. I will mention it to the software team to see if it can be added into our software. In the meantime you can find the driver here: https://ftdichip.com/wp-content/uploads/2022/02/CDM-v2.12.36.4-for-ARM64-Signed-Distributable.zip

Sync tooth was fixed at tooth number 1 in G4+. So if sync tooth is set to 1 in G4X the sync strategy is the same as G4+. The sync tooth setting allows you to change the sync point if for example you have a VVT engine where the cam tooth moves across crank tooth #1. Give us a log of a few start attempts and a couple of trigger scopes.