Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 06/13/2019 in Posts

  1. 2 points
    Richard Hill

    programmable logic

    I moved away from using generic dash as it employs a compound CAN message, which can be a bit of a mouthful for both the ECU sending and the device receiving. I prefer to use messages which are split over several CAN IDs such as transmit generic dash 2. The only problem with Generic Dash 2 is there's appears to be a bug in the non driven wheel speed (1 byte assigned, but shows as 0-1000kph, guess the text was copied from generic dash). Not a problem though if you aren't planning on going more than 158 MPH...
  2. 1 point
    Ducie54

    Hondata Strain Gauge

    Features say, Analog (voltage) output proportional to gear level force. So you need to use a Analog input not a digital input.
  3. 1 point
    Adamw

    SOI question

    Yeah sorry, I done that spreadsheet about 10 years ago and have obviously made a mistake in one of the formulas for end of injection somewhere. I dont really have time or interest in fixing it right now. You will have to get your calculator out...
  4. 1 point
    redmist

    programmable logic

    I've currently got all 6 seven segments and the 8x8 Matrix to work with Link "generic dash" can bus output. There is some work to do with my neopixel library conflicting another of my libraries, and a weird issue with my can bus adapter only picking up frame 0 or 1 when you start to introduce a delay (like writing to the 7 Segs). However given a correction of my frame issue I'm not seeing any problems with refresh from the Nano. Weird thing is the Nano will do several hundred main loops prior to picking yet another frame 0 from the buffer. Although there is a deep imprint of my keyboard in my forehead I'm enjoying battling with the cheap ahrse and very flashy intelligent 7 Segs, 8x8 and neopixels... the cheap can bus adapter... not so much.
  5. 1 point
    Adamw

    trigger 2 sync problem

    I notice in your screenshot above your camshaft position doesnt go below 15deg. I think this is due to your tooth offset table and maybe the trigger 2 offset are not correct. The first cell of the tooth offset table should always be zero. Subtract 14 deg from all the numbers in your tooth offset table and add 14 deg to your trigger 2 VVT offset.
  6. 1 point
    Simon

    trigger 2 sync problem

    The ECCS sync is only applicable for Nissan 360 opto trigger mode. It will show no for all other trigger setups.
  7. 1 point
    Davidv

    programmable logic

    Yeah the transciever is miniscule though, doesnt increase footprint: https://www.tindie.com/products/Fusion/dual-can-bus-adapter-for-teensy-35-36/ The refresh rate is good especially when optimized to minimize pixel writes. But if youre spamming it with lots of fast moving stuff or your code has a lot of unnecessary writes it can chug a bit. Moving over to realdash on a tablet is a whole bunch less work to be fair. But this is a learning exercise for me as much as anything else. The start up time, for me, is something that needs to be super snappy. Thats where a microcontroller is so good. I want to migrate my project to a twin core stm32 and a custom board at some point. So i wont need nextion it can control an lcd panel directly. But this is a huge amount of work and ive got lots to learn in the meantime.
×
×
  • Create New...