Jump to content

Mario Schneiderbanger

Members
  • Posts

    35
  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Like
    Mario Schneiderbanger got a reaction from Anfurnyy in Introducing RealDash - A Dashboard App for Android & Windows   
    Alright over the next few days i'll put together a how to on getting Real Dash to read data off the G4+ using a Seedstudio Can-Usb adapter. This way you can tap into all the available data including lambda/Ethanol% and whatever else that the serial stream doesn't support. With help of another forum member i've stumbled my way through this and now have a working gauge setup on my android tablet. 3 days ago I had no idea where to start with this and i assume other users probably feel the same so I'll share what I learned. 
    This will include how to:
    -wire the adapter 
    -connect it it to realdash
    -write the xml file
    -try to explain how to use the can calculator to make sure your conversion are properly setup 
    When all this is done you can even display it on a android enabled radio
    First thing to do is wire the can adapter into your Can 2 output on your B plug. I chose this route because i didn't want to buy the connector required to tap into Can 1 under the tuning port. The adapter also needs a single ground wire going to chassis "sensor ground would probably be fine too"
    next you're going to want to open your CAN setup in your PC link file and select Can Module CAN2.
    Mode will be User defined, but rate 1Mbits and OBD set to off.
    Under Data you will see 6 available channels. Each of those channels will be set to 1 can stream on the next page. Each Stream can hold 64 bits of data. Some parameters are 16 bits and others only 8. It tells you when you select them. More on that later.
    Click channel 1 and under Mode select "Transmit User Stream 1". Transmit rate is 200hz. Under CAN ID set ID to 1001 "you can put anything you want but you'll see why I did 1001 soon. Once this is done go to the streams page.
    Click on Stream 1 and then "Add frame" then click on "Frame 1" and then under parameters click "add"
    Look at my example photo. Lambda has a width of 16 bits "2bytes" but ethanol % only has a width of 8 bits. You can either have 4 parameters each 2bytes or 8 parameters each 1byte or a mix of both like me. Once you fill up stream 1 with 8bytes you have to click on stream 2 and add another frame and keep going till you have all the data you want. 
    If you have 2 streams or 3 streams or more you have to go back to the first tab and assigns stream 2 to channel 2 and set the ID to 1002. same with stream 3... "now you know why i named the ID 1001-1002...."
    NOTE: WHEN SELECTING THE PARAMETER YOU WANT BE CAREFUL THAT YOU DONT SELECT THE AN VOLT VERSION OF THAT PARAMETER FOR EXAMPLE AT1 and AT2 FOR ECT/IAT WILL OUTPUT THE SENSOR VOLTAGE AND NOT THE TEMPERATURE. 
    We're done in this window. Apply and Ok out of the window. Store to ecu and save
    tomorrow i'll explain how to get real dash to now read the incoming data that you just sent out in this menu.
    Take a look at the screen shot of my XML file. After <Frames> you will see the beginning of the data stream. frame ID 1001 is Channel 1 aka Stream 1 from the CAN Setup menu. Notice that the parameters under frame ID 1001 in my xml file match the parameters in my can setup under stream 1-frame 1.
    This is where it gets a bit tricky. Target ID means the address in realdash you are sending the data to. in other words when you create a gauge in realdash it's going to ask for a data source. You then pick from a list of channels and in order to figure out which channel is what ID you use the link here: 
    https://realdash.net/manuals/targetid.php
    Target id 254 is Lambda 1 under Engine/ECU Inputs and that's what we're going to use.
    Next is the offset and the length. Look at the can setup. Lambda 1 has a "Start Pos" of 0 and a "width" of 16 "remember 16 is 2bytes"
    Ethanol% then has a "Start Pos" of 16 and a "width" told 8 "1byte"
    this makes sense because if lambda is 16bits then the next parameter has to have a start pos of 16 and if ethanol is 8bits wide then the next parameter  has to have a start pos of 24. So far so good?
    Now in the XML file we don't use bits we use bytes so for Lambda the "offset" <----start pos  will be 0 and the "length" <----width will be 2
    For ethanol% the "offset will be "2" and the "length" will be 1
    Which means the next parameter would have a offset or 3.....
    eventually you will have all the parameters on stream 1 in your xml file and then you need to tell the xml file to start looking in stream 2. you can see that where frameid 1002 starts.
    After "length" you will see some parameters require a conversion in order to display properly. You can go to the help file under CAN examples and look for the conversion method and then under can setup try it out in the can calculator. This was the most confusing part for me and i don't really know how to explain it well. Maybe Adam Walmsley can help. It was trial and error for me.
    Once you have the xml file built you save it to your tablet in the realdash folder and now we go to setup realdash.
    Open realdash and go to your garage. open the door of the car "click on it" and then click on the gauge cluster. This will open a menu where you can add connections. Add a can/lin connection and go through the options. make sure your tablet is connected to your can adapter during this step. At the end it you will see a button for picking a custom can configuration file. navigate to the real dash folder and click on your xml file.
    once that's done leave the garage and either pick a theme or make a custom page and start setting up gauges. Now you have to assign the gauges you want to use a data source. So hit edit and click on the gauge you want to use. Click inputs and navigate the list to get to the input associated with the Target ID you chose in the xml file. Use the target ID page i posted to help you navigate. 
    There's some info on how to do that part in this video. https://drive.google.com/file/d/1_ynfTPGEdv66t1SfTVrf1hsk6QOM3AkX/view?usp=drivesdk
    I'm sure i forgot some things so if you get stuck anywhere let me know and i'll help.

    can't upload any of my screen shots because of the image size so i'll update this when i reformer them 

  2. Like
    Mario Schneiderbanger got a reaction from Invecii in Introducing RealDash - A Dashboard App for Android & Windows   
    Alright over the next few days i'll put together a how to on getting Real Dash to read data off the G4+ using a Seedstudio Can-Usb adapter. This way you can tap into all the available data including lambda/Ethanol% and whatever else that the serial stream doesn't support. With help of another forum member i've stumbled my way through this and now have a working gauge setup on my android tablet. 3 days ago I had no idea where to start with this and i assume other users probably feel the same so I'll share what I learned. 
    This will include how to:
    -wire the adapter 
    -connect it it to realdash
    -write the xml file
    -try to explain how to use the can calculator to make sure your conversion are properly setup 
    When all this is done you can even display it on a android enabled radio
    First thing to do is wire the can adapter into your Can 2 output on your B plug. I chose this route because i didn't want to buy the connector required to tap into Can 1 under the tuning port. The adapter also needs a single ground wire going to chassis "sensor ground would probably be fine too"
    next you're going to want to open your CAN setup in your PC link file and select Can Module CAN2.
    Mode will be User defined, but rate 1Mbits and OBD set to off.
    Under Data you will see 6 available channels. Each of those channels will be set to 1 can stream on the next page. Each Stream can hold 64 bits of data. Some parameters are 16 bits and others only 8. It tells you when you select them. More on that later.
    Click channel 1 and under Mode select "Transmit User Stream 1". Transmit rate is 200hz. Under CAN ID set ID to 1001 "you can put anything you want but you'll see why I did 1001 soon. Once this is done go to the streams page.
    Click on Stream 1 and then "Add frame" then click on "Frame 1" and then under parameters click "add"
    Look at my example photo. Lambda has a width of 16 bits "2bytes" but ethanol % only has a width of 8 bits. You can either have 4 parameters each 2bytes or 8 parameters each 1byte or a mix of both like me. Once you fill up stream 1 with 8bytes you have to click on stream 2 and add another frame and keep going till you have all the data you want. 
    If you have 2 streams or 3 streams or more you have to go back to the first tab and assigns stream 2 to channel 2 and set the ID to 1002. same with stream 3... "now you know why i named the ID 1001-1002...."
    NOTE: WHEN SELECTING THE PARAMETER YOU WANT BE CAREFUL THAT YOU DONT SELECT THE AN VOLT VERSION OF THAT PARAMETER FOR EXAMPLE AT1 and AT2 FOR ECT/IAT WILL OUTPUT THE SENSOR VOLTAGE AND NOT THE TEMPERATURE. 
    We're done in this window. Apply and Ok out of the window. Store to ecu and save
    tomorrow i'll explain how to get real dash to now read the incoming data that you just sent out in this menu.
    Take a look at the screen shot of my XML file. After <Frames> you will see the beginning of the data stream. frame ID 1001 is Channel 1 aka Stream 1 from the CAN Setup menu. Notice that the parameters under frame ID 1001 in my xml file match the parameters in my can setup under stream 1-frame 1.
    This is where it gets a bit tricky. Target ID means the address in realdash you are sending the data to. in other words when you create a gauge in realdash it's going to ask for a data source. You then pick from a list of channels and in order to figure out which channel is what ID you use the link here: 
    https://realdash.net/manuals/targetid.php
    Target id 254 is Lambda 1 under Engine/ECU Inputs and that's what we're going to use.
    Next is the offset and the length. Look at the can setup. Lambda 1 has a "Start Pos" of 0 and a "width" of 16 "remember 16 is 2bytes"
    Ethanol% then has a "Start Pos" of 16 and a "width" told 8 "1byte"
    this makes sense because if lambda is 16bits then the next parameter has to have a start pos of 16 and if ethanol is 8bits wide then the next parameter  has to have a start pos of 24. So far so good?
    Now in the XML file we don't use bits we use bytes so for Lambda the "offset" <----start pos  will be 0 and the "length" <----width will be 2
    For ethanol% the "offset will be "2" and the "length" will be 1
    Which means the next parameter would have a offset or 3.....
    eventually you will have all the parameters on stream 1 in your xml file and then you need to tell the xml file to start looking in stream 2. you can see that where frameid 1002 starts.
    After "length" you will see some parameters require a conversion in order to display properly. You can go to the help file under CAN examples and look for the conversion method and then under can setup try it out in the can calculator. This was the most confusing part for me and i don't really know how to explain it well. Maybe Adam Walmsley can help. It was trial and error for me.
    Once you have the xml file built you save it to your tablet in the realdash folder and now we go to setup realdash.
    Open realdash and go to your garage. open the door of the car "click on it" and then click on the gauge cluster. This will open a menu where you can add connections. Add a can/lin connection and go through the options. make sure your tablet is connected to your can adapter during this step. At the end it you will see a button for picking a custom can configuration file. navigate to the real dash folder and click on your xml file.
    once that's done leave the garage and either pick a theme or make a custom page and start setting up gauges. Now you have to assign the gauges you want to use a data source. So hit edit and click on the gauge you want to use. Click inputs and navigate the list to get to the input associated with the Target ID you chose in the xml file. Use the target ID page i posted to help you navigate. 
    There's some info on how to do that part in this video. https://drive.google.com/file/d/1_ynfTPGEdv66t1SfTVrf1hsk6QOM3AkX/view?usp=drivesdk
    I'm sure i forgot some things so if you get stuck anywhere let me know and i'll help.

    can't upload any of my screen shots because of the image size so i'll update this when i reformer them 

  3. Like
    Mario Schneiderbanger got a reaction from JeremiahJ in Introducing RealDash - A Dashboard App for Android & Windows   
    got mine working via can adapter today. i assume this will work for g4x as well. If anyone wants to set this up order one of these and i'll post a step by step to walk you through it 
    https://www.seeedstudio.com/USB-CAN-Analyzer-p-2888.html

  4. Like
    Mario Schneiderbanger got a reaction from aerace_fab in Requesting: S2000 Factory Coolant Temp Functionality   
    Update: I was able to Use 3 Virtual outputs with ECT based conditions to vary the cluster output. It doesnt make use of all the bars since im out of conditions on the Physical Aux but its enough to know when the engine is warmed up. and overheating.
     
    May be able to add another Virtual aux to expand 2 more variables.
  5. Like
    Mario Schneiderbanger got a reaction from pvainola in Introducing RealDash - A Dashboard App for Android & Windows   
    Alright over the next few days i'll put together a how to on getting Real Dash to read data off the G4+ using a Seedstudio Can-Usb adapter. This way you can tap into all the available data including lambda/Ethanol% and whatever else that the serial stream doesn't support. With help of another forum member i've stumbled my way through this and now have a working gauge setup on my android tablet. 3 days ago I had no idea where to start with this and i assume other users probably feel the same so I'll share what I learned. 
    This will include how to:
    -wire the adapter 
    -connect it it to realdash
    -write the xml file
    -try to explain how to use the can calculator to make sure your conversion are properly setup 
    When all this is done you can even display it on a android enabled radio
    First thing to do is wire the can adapter into your Can 2 output on your B plug. I chose this route because i didn't want to buy the connector required to tap into Can 1 under the tuning port. The adapter also needs a single ground wire going to chassis "sensor ground would probably be fine too"
    next you're going to want to open your CAN setup in your PC link file and select Can Module CAN2.
    Mode will be User defined, but rate 1Mbits and OBD set to off.
    Under Data you will see 6 available channels. Each of those channels will be set to 1 can stream on the next page. Each Stream can hold 64 bits of data. Some parameters are 16 bits and others only 8. It tells you when you select them. More on that later.
    Click channel 1 and under Mode select "Transmit User Stream 1". Transmit rate is 200hz. Under CAN ID set ID to 1001 "you can put anything you want but you'll see why I did 1001 soon. Once this is done go to the streams page.
    Click on Stream 1 and then "Add frame" then click on "Frame 1" and then under parameters click "add"
    Look at my example photo. Lambda has a width of 16 bits "2bytes" but ethanol % only has a width of 8 bits. You can either have 4 parameters each 2bytes or 8 parameters each 1byte or a mix of both like me. Once you fill up stream 1 with 8bytes you have to click on stream 2 and add another frame and keep going till you have all the data you want. 
    If you have 2 streams or 3 streams or more you have to go back to the first tab and assigns stream 2 to channel 2 and set the ID to 1002. same with stream 3... "now you know why i named the ID 1001-1002...."
    NOTE: WHEN SELECTING THE PARAMETER YOU WANT BE CAREFUL THAT YOU DONT SELECT THE AN VOLT VERSION OF THAT PARAMETER FOR EXAMPLE AT1 and AT2 FOR ECT/IAT WILL OUTPUT THE SENSOR VOLTAGE AND NOT THE TEMPERATURE. 
    We're done in this window. Apply and Ok out of the window. Store to ecu and save
    tomorrow i'll explain how to get real dash to now read the incoming data that you just sent out in this menu.
    Take a look at the screen shot of my XML file. After <Frames> you will see the beginning of the data stream. frame ID 1001 is Channel 1 aka Stream 1 from the CAN Setup menu. Notice that the parameters under frame ID 1001 in my xml file match the parameters in my can setup under stream 1-frame 1.
    This is where it gets a bit tricky. Target ID means the address in realdash you are sending the data to. in other words when you create a gauge in realdash it's going to ask for a data source. You then pick from a list of channels and in order to figure out which channel is what ID you use the link here: 
    https://realdash.net/manuals/targetid.php
    Target id 254 is Lambda 1 under Engine/ECU Inputs and that's what we're going to use.
    Next is the offset and the length. Look at the can setup. Lambda 1 has a "Start Pos" of 0 and a "width" of 16 "remember 16 is 2bytes"
    Ethanol% then has a "Start Pos" of 16 and a "width" told 8 "1byte"
    this makes sense because if lambda is 16bits then the next parameter has to have a start pos of 16 and if ethanol is 8bits wide then the next parameter  has to have a start pos of 24. So far so good?
    Now in the XML file we don't use bits we use bytes so for Lambda the "offset" <----start pos  will be 0 and the "length" <----width will be 2
    For ethanol% the "offset will be "2" and the "length" will be 1
    Which means the next parameter would have a offset or 3.....
    eventually you will have all the parameters on stream 1 in your xml file and then you need to tell the xml file to start looking in stream 2. you can see that where frameid 1002 starts.
    After "length" you will see some parameters require a conversion in order to display properly. You can go to the help file under CAN examples and look for the conversion method and then under can setup try it out in the can calculator. This was the most confusing part for me and i don't really know how to explain it well. Maybe Adam Walmsley can help. It was trial and error for me.
    Once you have the xml file built you save it to your tablet in the realdash folder and now we go to setup realdash.
    Open realdash and go to your garage. open the door of the car "click on it" and then click on the gauge cluster. This will open a menu where you can add connections. Add a can/lin connection and go through the options. make sure your tablet is connected to your can adapter during this step. At the end it you will see a button for picking a custom can configuration file. navigate to the real dash folder and click on your xml file.
    once that's done leave the garage and either pick a theme or make a custom page and start setting up gauges. Now you have to assign the gauges you want to use a data source. So hit edit and click on the gauge you want to use. Click inputs and navigate the list to get to the input associated with the Target ID you chose in the xml file. Use the target ID page i posted to help you navigate. 
    There's some info on how to do that part in this video. https://drive.google.com/file/d/1_ynfTPGEdv66t1SfTVrf1hsk6QOM3AkX/view?usp=drivesdk
    I'm sure i forgot some things so if you get stuck anywhere let me know and i'll help.

    can't upload any of my screen shots because of the image size so i'll update this when i reformer them 

  6. Haha
    Mario Schneiderbanger got a reaction from SchuKingR in Introducing RealDash - A Dashboard App for Android & Windows   
    Ach na dann halt auf deutsch   melde dich mal auf whatsapp ‪+1 (727) 485‑6673‬
  7. Thanks
    Mario Schneiderbanger reacted to Scott in Subaru Knock sensor setup   
    Ok, here (quickly) are the steps you would normally take to set up the Knock detection system:
    Make sure the ignition system is completely tuned. Set the knock gain to a value of 1. Select the correct frequency filter (we have covered this) Monitor the individual cylinder knock levels, adjust the gain until the max reading you get in the levels is approx 500. This is normally somewhere around high rpm and high engine load. Monitor the individual cylinder knock levels and adjust each cylinders gain until the cylinders all read evenly. Fill in each cell of the target table. Set the values to be 10% higher than the values you are seeing on the individual cylinder knock levels. Logging could be a helpful way to do this. Now whenever the knock level of a cylinder exceeds the current value from the knock target table, the ECU will try to retard the ignition timing for that cylinder to reduce the noise (knock) level. You can decide at what rate the ECU will retard the timing, and what the maximum level of retard can be. Benefits to having a quick retard and large maximum retard are engine protection. Benefits to having a slower retard and small maximum retard are the engine does not drop so much power.
    Lets assume you have ended up with a setup like this:

    At 50% throttle and 1500 RPM you are normally getting cylinder knock levels of 255, so you set the cell in the Knock Target table to 280. One day you lend the car to someone and they put a lower octane fuel into the tank. This causes the engine to knock lightly and produce cylinder knock levels of 320. The ECU sees this and retards the ignition timing until all affected cylinders (probably all of them) have a noise level less than 280 or until the Ign Retard Limit is reached.
    Regardless of the cause of the higher cylinder knock levels the ECU will retard the timing in an attempt to reduce the levels to be below the level specified in the Knock Target Table.
    One good way to view this is by logging on the Timeplot. Display each cylinders level and then then Knock target (threshold). This will allow you to easily see when a cylinder jumps up over the allowable level.
    Scott
  8. Like
    Mario Schneiderbanger reacted to 1320MINI in S2000 Speed Sensor Erratic   
    Adam,
    It worked for me also, 
  9. Like
    Mario Schneiderbanger reacted to Adamw in S2000 Speed Sensor Erratic   
    Q3 gives you a divide by 8, Q4 is divide by 16.
  10. Thanks
    Mario Schneiderbanger got a reaction from Kimple Fi in Bigger injectors   
    What if you started with stock injectors in traditional mode and have a solid calibration and now you’re switching to ID injectors and want to use Modeled fuel?
    Anything else besides the obvious:
    -flow rate
    -dead times
    -short pulse 
  11. Like
    Mario Schneiderbanger got a reaction from JMP in Requesting: S2000 Factory Coolant Temp Functionality   
    Update: I was able to Use 3 Virtual outputs with ECT based conditions to vary the cluster output. It doesnt make use of all the bars since im out of conditions on the Physical Aux but its enough to know when the engine is warmed up. and overheating.
     
    May be able to add another Virtual aux to expand 2 more variables.
×
×
  • Create New...