Jump to content

CamB

Members
  • Content count

    87
  • Joined

  • Last visited

  • Days Won

    5

CamB last won the day on January 4

CamB had the most liked content!

1 Follower

About CamB

  • Rank
    Advanced Member

Profile Information

  • Location
    Auckland

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. CamB

    Xtreme + CAN Dash + CAN Lambda

    I believe it is "Second comms port CAN1 / RS232" (RS232 not for PC Link, for a serial stream).
  2. CamB

    Wiring for distributer ignition

    Would also be nice if you had a way to measure load (MAP or TPS, although I am not sure how feasible either is with Webers as I've never looked into it - must be options) for ignition mapping.
  3. CamB

    CAN Lambda / Resistor

    Was just reading this the other day - the manual says it is required (page 12): http://www.linkecu.com/wp-content/uploads/2016/10/CAN-Lambda.pdf
  4. CamB

    Can protocol sample

    @Davidv - thanks, I should have looked more closely at that! It was easy enough to change the code (I ended up using a custom stream rather than the generic one as I had trouble capturing all the incoming CAN messages if there were too many).
  5. CamB

    Can protocol sample

    From my messing around with it, all the raw data in the Generic stream is the second parameter + 256 * the first parameter (in the pair). Interestingly when you set a custom stream the order is reversed... Is there a reason not to just use the standard convention? (I guess efficient coding?)
  6. If stalling I would try: - using "idle ignition", so you've got an increase in timing when idle falls below target (there is an HPA webinar on this) - turning off transient ignition retard unless you are convinced you need it, and at least zero-ing it anywhere near idle There's a bunch of other stuff in the map (assuming the first one you posted is close enough to what you are using) that I am unfamiliar with but wouldn't necessarily expect (like quite significant ECT ignition trims, etc). These may not actually be affecting anything - its not possible to tell as your log doesnt have enough parameters. I can, however, see that your first map's ignition table doesn't match the logs (although, without the data, can't say why).
  7. CamB

    Motec PDM to Fury CAN

    There should be more than that - a relatively recent PCLink upgrade pushed it out to 8x. Try loading the Monsoon example if you don’t have an ECU to update.
  8. CamB

    GP Activation Strategy

    Quite hard to read the picture - any chance you can post a higher quality one?
  9. CamB

    GP Activation Strategy

    This got me intrigued (can see the benefit), so I had a look at mechanical options. This came up: "Push to make" would be the launch activate button (a momentary), energising the coil and closing the contacts, which because of A-B being closed would remain closed until "Push to break" is open, which could be the clutch switch or I guess an auxiliary output from the ECU for gear change. The Launch input to the ECU would be on the second pole (C-D).
  10. Yep, could do. Send me a PM when you are ready
  11. CamB

    DIY vipec display

    I had a look at your code (based on the original poster's?), and if there is a button on pin 3 it is supposed to flip page when pressed. At least I think it is - I am a complete novice. Although it may be that you need to reword the interrupt as per discussion on "digitalPinToInterrupt(pin)", so it won't matter which board you have: https://www.arduino.cc/reference/en/language/functions/external-interrupts/attachinterrupt/ Is that the only issue? Or are you having trouble with the CAN side too? I am using the same code / libraries as Paul - starting with his sketch (thanks!) but with the newest version of the libraries from here: https://github.com/coryjfowler/MCP_CAN_lib
  12. CamB

    DIY vipec display

    Thanks - I've put that part of it far down the list of priorities (although actually may not be too hard using a bit mask after a quick google) as I have decided I am more worried about basic functionality and what I think I've learned so far is: - at higher bit rates, I think the buffer on the can shield might be overflowing. It definitely misses frames - easy solution is sending only what I want to know and using 125kbps bit rate. I don't need all 39 items in the generic dash plus another 5-10 "nice to have", so it will be much easier if I just create a custom stream with the ~15 items I really want. I just had it in my head it would be nice to have code someone else could just grab, compile and go with minimal config in PCLink required
  13. CamB

    DIY vipec display

    I've had a go at this as well using the instructions from Paul (awesome - thanks!). I had a go, but I have questions... So far I have a 4duino (arduino with integrated 4D Systems screen), had a go at the graphics side (promising) before realising I should focus on making sure I can read and understand the CAN messages from my ECU. The shield is this, which is a 16Mhz Seeed style one. I used a 100R terminating resistor because that's what I had, and will get a 120R. Although its taken me a while (I am starting essentially from scratch), using the code from Paul's website I can successfully connect the arduino to the ECU and get serial display of the "Generic Dash" CAN messages. Questions... 1) If I leave the CAN bitrate at 500kbps, the serial monitor does not report every line (5 out of 13). If I drop it to 125kbps, I see almost all of them (12 of 13 - see pics). It's not always the same missing messages, so ... are they actually missing or not being reported somehow? Changing the "Transmit Rate" even down to 1hz doesn't seem to affect whether they are there or not, just the update speed (as you'd expect). 2) I can see that the instructions Paul provided to decode the CAN stream work (the "96" in the message starting "00" is hex for the 150kpa for the MAP sensor, which I set manually). How do I interpret where it spans two data blocks (eg ECU voltage is "95 04", which should somehow translate to about 1200 (12.00v). (edit - I think I figured it out, you take the second number in the pair and put it in front of the first number, then convert from hex. So voltage is 0x0495, which is 1173 (being 11.73v, which is about right as its an old battery on the bench. I wonder how my extremely basic coding skills / google are going to join those pairs together). (edit again - worked it out - can take the second pair and multiply by 0x100 (or decimal x 256) then add the first pair, so in decimal 4*256 + 149 = 1173) (and a final edit - have looked at Paul's code which displays on his 4D screen and see exactly this...) 3) For when I get to it, what will the message look like for the Limit Flags? (edit - have had a think about it and presumably its a number that is converted to (considered in?) binary and then whether there is a 0 or a 1 in each bit is whether the flag is on - eg CAN message "05" would be binary 101, which is RPM Limit and Speed Limit active (being bits 0 and 2). Am feeling this might be low priority for me as code to pull that out would take me a looong time. Thanks for any assistance.
  14. I asked over at another forum where you asked this, but this is probably a better place... does the change in backpressure have any relativity to the change in cam timing?
  15. CamB

    GP RPM LIMIT

    I'm pretty sure you can do this part (without the latching) if you set a Virtual Aux to CE Light and the CE light Aux Output as a GP output that goes on with the Virtual Aux OR an Engine Limit.
×