Jump to content

ThatDamnRanga

Members
  • Content Count

    6
  • Joined

  • Last visited

About ThatDamnRanga

  • Rank
    Newbie

Recent Profile Visitors

22 profile views
  1. I know I'm a notorious moaner when it comes to CANBus, but given my frustrations I've begun development of what would effectively be a configurable translator module to allow Link ECUs to operate in vehicles that are heavily dependant on CANBUS (my GT86, the above RX8 etc)... Unfortunately that comes with a feature request, as currently both the ECU and the translator module find themselves having to waste considerable numbers of I/O pins on functions which would ordinarily be transmitted over CAN. Note that I'm not asking for improvements in the CAN environment to enable direct OEM integration. As I appreciate that's a lot more work, and simply not on the roadmap. What I'd like to see is a number of 'Virtual I/O' pins which can be assigned to any function as if they were physical pins. So a pin like 'CAN DI #1' would have a page like 'DI 4' does. Giving me the ability to assign a Start Switch, Traction Control Switch or GP Input for Map Switching. Virtual analogue in might be more difficult, but it would be helpful in situations where the CAN bus presents an input with a linear value (torque reduction request, etc) And the same kinda thing for the outputs. This would save Link engineers from having to create specific code to make things like Cruise Control indicators work over CAN. You could simply assign them to a virtual output.
  2. The vehicle in question is a Toyota GT86 aka Subaru BRZ. I believe I have all the CAN data (6 messages) necessary for the operation of a key-start vehicle, thanks to a bunch of people including Tiz in this thread. It's the push-button start vehicles that use a couple of extra messages I have yet to decode. There's probably one or two more 'nice to have' messages that contain things like CEL, Traction Control lights and Cruise Control indicators that I also need to track down.
  3. Unfortunately this drastically limits the number of frames we can work with, as there are only six streams available, at one frame each. Basically meaning you have two options for vehicles which utilise more than six frames: a third party CAN-to-IO/CAN-to-CAN adapter, or go with someone else's product?
  4. Not the Vehicle OEM in this case. Aftermarket ECU vendors, first one that springs to mind is Emtron, do this. After all, what other possible purpose could there be for allowing multiple frames to be defined on a single stream? Two different messages with the same message ID would be... Bad.
  5. Huge thanks to Tiz for the headstart. I've taken the data and made some corrections based on the known format of the Can messages used in these cars. Also reduced the number of needed channels to four, leaving two spare. (This is based on an untested assumption that each frame added to a stream increments the transmitted or received ID by one (so on a stream with ID 354, Frame 1 would be 354, Frame 2 would be 355, etc.) as this is how other vendors do things. I'm left with one limitation. At present the G4+ cannot take a starter request via CAN. Am I missing something? As I can assign an attribute to a CAN DI#, but I can't then do anything with that input. I'd be super keen if I could configure CAN DI#s the same way as normal DI#s (though it would probably require an additional value to set momentary/toggle)
×
×
  • Create New...