Jump to content

cwhite951

Members
  • Content Count

    10
  • Joined

  • Last visited

  1. cwhite951

    CAN to Stack Dash

    thanks. to get this all up and functioning I can live with the one frame per ID - that gets me 6 channels with 4 data items (at 16 bit). i'll play with converting to 8 bit and/or multiplexing when I need to (later) So if I am correct I should only have 1 stream with 1 frame per channel with each stream associated with a specific address
  2. cwhite951

    CAN to Stack Dash

    OK, so the last detail to get the Stack and Link configured is matching up the data transfer 'channels' Stack is looking for channels and each channel has a separate CAN id and each channel is limited to 8 bytes @ 8 bits each. its a little confusing that the stack has a very limited amount of data per channel but it looks little the Link is happy to fit in huge amounts of data per 'channel'. here is what I have set up so far: Link (under generic dash/user defined) has 6 channels each with what seems to be unlimited streams and each stream with unlimited frames. Link so far: to make it a little easier I am using the Link data with out modification to get it up and running (16 bit stays 16 bit). I can always play with that later. again - many thinks for guiding me thought this! the end result will be worth it. BTW - the Stack 9918 is a very cool dash/data system. I have to admit that the AIM (I have worked with their dataloggers quite a bit) is fine technically but i just don't like the aesthetics of the dash and the graphics. Some cool screens for the Stack: Yes - thats a dashboard screen that you can configure with any 4 scrolling data graphs! Race Dash. great predictive lap timing features Many more possibilities and they are all very editable to fit your needs. You can even set up a lat/long G force circle for driver coaching. and it very large....size is important (!)
  3. cwhite951

    CAN to Stack Dash

    that pretty handy to know about - thanks!
  4. cwhite951

    CAN to Stack Dash

    OK, I'm learning stuff one 'bit' at a time! I see that there is a 6 channel/stream limit but it seems to allow unlimited frames per stream - is there a limit of frames per stream? perhaps I need to fully understand the channel/stream/frame structure limitations - the G4+ CAN set up is allowing me to have unlimited streams and frames! My experience with other ECUs is that the native sensor range (say 0-5v) is divided by the resolution allowed by the bit count- so it would be .0196v per bit. if you had a 150psi sensor you would get .588v psi per bit (acceptable resolution). Same example for MAP sensor says that a 3 bar MAP sensor should give me .17 psi per bit - I level of detail that I am also comfortable with. I would think almost all data should be OK at 8 bit resolution - even RPM (8k limit) gives you 31rpm per bit vs 1.77 RPM per bit at 16 bit (OK- maybe 16 bit woudl be better for RPM!) here is a more detailed example of the Stack input editor (input from a Porsche GT3 ECU as an example): I would assume that the output from the ECU is 0 to 16 bar and at 8bit you get the .0627 resolution. The 'output' becomes the info for the stack display. I really appreciate the help. I will be doing installs for others so I want to get all the details right on this one!
  5. cwhite951

    CAN to Stack Dash

    thanks Adam....a couple more Q's (because I get fixated on figuring stuff out!) When to use 8 b it vs 16 bit - I see in your example you used 16 bit for oil pressure. I woudl have guessed that 256 points would have been sufficient for a 0-100 scale. Does upping the detail in all the channels to 16 bit eventually choke the speed of the can bus? If its fast enough not to be an issue then we could 'default' to 16 bit for all data, if not I can 'dumb down' the resolutions to 8 bit for many items (pretty much all temps / pressures). I also saw that you used the bit bandwidth for the min/max values. In other example I notice that the min/max listed was the actual psi/temp/whatever that was being transmitted (I hope I don't zing the engine to 65,535 rpm!) - what is the correct approach? Does the 'file' name on the Stack editor make any difference? : BTW - I hard wired the can bus to the D connector on the Thunder ECU using Can 1 - seemed like the best way to do that - right? one last Q - every time I try to sign in I get an incorrect password notice. I reset the password to the same password and I good for that session. Odd. thanks
  6. cwhite951

    CAN to Stack Dash

    So here is where I am at so far - a screen shot showing the Link can set up and the Stack can editor with the first couple of lines configured. I think I am going in the right direction - any comments? Also - any thoughts on number of bits per channel? It I get too much info (like all 16 bit) will it slow down communication if i have 30 channels? I am new to Can Bus to any thoughts/ help woudl be appreciated.
  7. cwhite951

    CAN to Stack Dash

    Vipec is not listed in the pull down menu for ECU Protocols - here is the protocol editor, it seems to be pretty flexible BTW - better to use the CAN connection in the D harness or one of the com ports?: example for Electromotive TecS I have quite a bit of info going into Thunder that I would like to datalog on the Stack dash as well. usual engine data as well as wheel speed (ABS) and shock pots. thanks
  8. cwhite951

    CAN to Stack Dash

    Has anybody configured the CAN BUS to work with the Stack ST9918? I just picked up one of these dashes for the track car and now need to get it up and running - any help woudl be appreciated!
  9. cwhite951

    Trigger scope

    I do have a 'real' scope...but I was trying to set up the trigger and I wanted to use the vi-pec scope to get a basic delta between the cam synch and the crank 60-2 trigger. That would be an easy way to set it up since I use a cam lobe as the cam trigger. it would be a wild guess to get it to run to fine tune the ignition timing, The TDC mark on a Porsche 944 is very small and only shows up in a +/- 5 degree window in the bellhousing - so the chances of seeing it by the guess method are pretty small! That makes it hard to do by yourself. The other odd thing is that the scope function is not showing anything more than a tenth of a volt variation when cranking but the engine speed display is showing a steady cranking RPM. Background info - this car was running with a Haltech ECU so all sensors were functioning and the engine is sound.
  10. cwhite951

    Trigger scope

    I am setting up a new i88 install and I am trying to use the built in scope function - how do you clear the scope? It's a pain to look through all the past junk to get to a brief sample. Also - you can only set the v/division but not any offset. No real Instructions to work with!
×