Jump to content

Adamw

Moderators
  • Posts

    11,284
  • Joined

  • Last visited

  • Days Won

    622

Adamw last won the day on July 22

Adamw had the most liked content!

About Adamw

Profile Information

  • Gender
    Female

Recent Profile Visitors

11,765 profile views

Adamw's Achievements

  1. You are on old firmware, User CAN was only added in 4.8.0. I suggest you update to the latest 4.10.2
  2. Have you got the blue/pink lock thing slide over to one side as per my pic below?
  3. Bit number zero is usually the least significant bit (right hand end of the byte, bit number 7 is the left hand end. From wikipedia:
  4. Connect the signal wire to any DI, set the DI to one of the wheel speeds, set pull-up to on. Calibration number can be calucluated using the formula in the help file or just drive it at a known speed (GPS on your phone or similar) and tweak the calibration number until speed in the software matches you phone. In Chassis & Body menu assign your new wheel speed as both driven and non-driven wheel. In the Engine protection menu set up the speed limiter. Set the ON/off control to the DI you pit limiter switch is connected to, set the target speed. Usually you will need to set the speed limit to advanced mode and tweak the limiter setting to get a smooth limit at the correct speed.
  5. Front 02 is AN Volt 4 (pin 76), the rear 02 is not connected to any input in our ECU. You will have to move the wideband wire to the front 02 pin or you can use one of the spare AN Volt pins such as Air flow meter on pin 90 (ANV2) or the MAP on pin 73 (ANV8), or one on the expansion port.
  6. Your PID is poorly tuned, the throttle control gets an oscilation in it so TP bounces back and forwards, not settling on target, Throttle shuts down once the TP/Target error accumulator reaches 100. If you attach your tune I can possibly suggest some changes, otherwise it should go back to the tuner.
  7. It looks like it is not happy about something trigger related, the RPM drops to zero during cranking every couple of seconds. Can you do a triggerscope while cranking and I will take a look. Make sure yoiu only click the capture button when the engine is turning and keep it cranking for a couple of seconds after that. Secondly, the fuel table is not suitable for modelled mode, usually VE numbers will need to be around 60 at idle and 100 at WOT. Import the fuel table below as a closer starting point. (right click on your existing fuel table, then >import/export>import from file. VE Fuel Table .lte
  8. It should work. You will likely have to do a custom calibration for the temp sensor.
  9. Trigger 1 & 2 are swapped. You have the 24T signal on trig 2 and the single tooth on trig 1. Swap the trig 1/2 wires at the CAS plug and it should be happier.
  10. Change the parameter in the user stream to whichevr DI you want to receive it as. Frame ID is added on to the base ID. The dash2pro stream sends out 4 sequential frames and we have it set up on ID1000. So Dash2pro stream uses ID's 1000, 1001, 1002 & 1003. You will see at the top of the xml file the base ID is set to 1000 and the frame ID 0,1,2,3 cover the dash2pro stream. i.e. Base ID1000 + frame ID3 = 1003. The frame ID 4 covers the "transmit user stream *" that you have sent on ID1004. The frame ID5 covers the "receive user stream *" on ID1005. The bit positions are explained in red in a pic in the original realdash example. So your start bits to match your xml would be 7,6 & 5
  11. Ok, you need to click capture while it is cranking. That would explain why there is no signal in those scopes. Can you do another
  12. With ECU connected, if you go to >help>ecu information, what is the maincode firmware verison? And if you go to >help>about, what is the PC Link version?
  13. Was the engine cranking when you clicked the capture button? (not clicked before cranking).
  14. You dont nesecarily need a B loom, but knock is on the B plug. So you would need the B plug and a shielded cable to run from that to the knock sensor. "Flywheel supply" is an internal circuit that the flyback diodes on the aux outputs dump any large voltage spikes to.
  15. Another option is this: https://www.micropdm.com/products/p/micropdm This connects to the Blink keypad and handles all the logic such as toggle/flash/count and the LED's etc. All the button "outputs" can be sent to the ECU via CAN as well as some of the pins on the relay can be controlled by the buttons too.
×
×
  • Create New...