Forced Induction and SSSICK/BUOY: Difference between pages

From WWWIKI
(Difference between pages)
 
 
Line 1: Line 1:
=Introduction=
Buoy is an all-in-one data-logging and tuning tool for the SSSMCK (SSSQUID MAF CONVERSION KIT). It is in beta stages and as such may have bugs. Please [https://sssquid.com/v3/contact contact us] with any bugs you may encounter.
This tool was developed in and for Linux first. The Windows port is in very early stages and will naturally have more bugs than the Linux flavor. There is no version for Mac OSX and we do not have any plans to ever release a version for that OS.
Expect new software to be released regularly. We have not implemented any auto-update functions yet. Please bookmark this page to get quick access to the latest software.
=Download=
Latest Version: 0.18.07
*Windows
**32-bit (JRE required) - [https://sssquid.com/strg/sssmck/buoy/buoy-001807-win32.zip Download]
**64-bit (recommended for most users! Pre-compiled JRE included) - [https://sssquid.com/strg/sssmck/buoy/buoy-001807-win64.zip Download]
*Linux
**32-bit - [https://sssquid.com/strg/sssmck/buoy/buoy-001807-lin32.tar Download]
**64-bit - [https://sssquid.com/strg/sssmck/buoy/buoy-001807-lin64.tar Download]
**arm32 - coming soon, please contact for early access
**arm64 - coming soon, please contact for early access
Previous versions available by request, though you should most likely be using the latest version!
[[SSSMCK/BUOY/Version_History|Version History]]
==Installation==
This program is designed to be portable -- there is no installation necessary. Simply extract the compressed folder contents to its own directory and run "Buoy.sh" (Linux) or "Buoy.exe" (Windows).
For the 32-bit Windows version of Buoy, the necessary JRE (Java Runtime Environment) is not pre-packaged. You may need to install the JRE if you haven't already: [https://docs.oracle.com/goldengate/1212/gg-winux/GDRAD/java.htm Java JRE]. The JRE is pre-packaged on the 64-bit version (what most everyone will be using). Unless you are running an older 32-bit version of Windows (like 32-bit XP), it is recommended to use the 64-bit version.
For Linux users, Java is required to run but is not prepackaged. Many flavors of Linux will come with the necessary runtime environments pre-installed, but if you're not sure you can check with your package manager.
==Drivers==
Most flavors of Linux will come pre-installed with the necessary drivers.
For Windows, you may need to install the standard FTDI D2XX drivers available at the following link: [https://ftdichip.com/drivers/d2xx-drivers/ FTDI D2XX Download Page]
=Interface=
*Main
**Setup port, flash firmware, and view diagnostic information.
*Live Dash
**View and log live airflow data.
*Log Replay
**View previously recorded logs with many ways to manipulate and filter the data.
=Usage=
==Connecting==


=Introduction=
With the top cover removed, you will need to find a 6-pin header. This is where the logging/flashing module will be plugged.
Converting from N/A (Naturally Aspirated) to F/I (Forced Induction) is a popular choice of gaining a fair amount of power for a fair price. There are many important factors to take into consideration when going this route that may or may not work out for your goals.
 
[[File:Loggingmoduleport.jpg|center|thumbnail]]
 
Plug in your logging/flashing module. It can only be inserted in one direction.
 
[[File:Loggingmoduleconnected.jpg|center|thumbnail]]
 
Connect the USB cable to your computer. If you are logging, please skip the next step.
 
ONLY if you are flashing the module!: it is recommended to use the USB power. You can do this by moving the "REG-USB" jumper from the "REG" side to the "USB" side as pictured below:
 
[[File:Usbpowerselected.jpg|center|thumbnail]]
 
Once you finish flashing, please make sure to move this jumper back to the "REG" side before continuing use on your vehicle.
 
On the "Main" tab you will find the connection and flashing options.
 
[[File:Buoy001804_main.png|center|thumbnail|600px]]
 
First you will need to select the correct port. Click on "Select Port" and you will be presented with a list of available ports.
 
If you are unsure of which port the SSSMCK is connected through, you can simply disconnect the device and reconnect it to see which port is added and removed. The list automatically updates.
 
[[File:Buoy001804_portselected.png|center|thumbnail|600px]]
 
Once the port is selected, click "Connect". It will take 2 seconds to connect, do not repeatedly click the "Connect" button during this time period. The SSSMCK should connect and automatically start sending airflow data. If data is not graphed on the "Live Dash" page, you can try disconnecting and reconnecting.
 
==Data-logging==
Once connected the SSSMCK should automatically begin transmitting airflow data to the program. This is displayed in kilograms per hour (Kg/Hr).
 
[[File:BUOY001804_LIVEGRAPH.png|thumbnail|center|600px]]


Going F/I does not mean you will automatically gain 300+ Hp, and many people are upset when their $800 eBay turbocharger can only produce 80-120 extra Hp on their completely stock vehicle. Therefore it's important to temper your nerves and do research on how to best achieve your power goals. Keep reading for more information on this fun modification!
On this page you can set an output file. Use the file extension ".csv" for logs (this file extension should automatically be added, but there is a bug in Windows where if your file path has one or more periods it may not be automatically added).


=Fueling=
Once you have set the output file, you may begin logging by selecting "Start Recording". Once you are finished recording, select "Stop Recording" or simply close the program.
==Injectors==
It is recommended to use injectors that will flow enough for your power level, but are not excessive as to decrease low-load efficiency.


If you are looking for a tool to estimate injector flow required, please check [https://sssquid.com/v3/choosing-fuel-injectors/ HERE].
There are many ways to display the data, as a line (recommended and default), as dots, or as bars. The rest of the options are primarily for further diagnostics when necessary, but should not be needed or used by most users.


==Fuel Pressure Regulators==
===Log Replay===
If you are unable to size injectors correctly for one reason or another, or you are limited on your intake metering options, you may want to consider using an RRFPR (Raising Rate Fuel Pressure Regulator). These devices are placed in-line after your stock FPR and have a dynamic diaphragm that is linked to your intake manifold pressure. This diaphragm will adjust fuel pressure depending on your intake manifold's pressure, adding a certain pound of pressure (X) for every pound of positive pressure above atmosphere (Y) in your intake manifold. These devices are rated as "X:Y", generally ranging from 4:1 to 14:1, although there are other options.
If you would like to view previously recorded logs, you can open them a number of ways. They are output as simple CSV files (Comma Separated Values). These can be read by programs such as OpenOffice/LibreOffice Calc, Microsoft Excel, or within Buoy.


This is considered a lesser option than using correct injectors, as the increased fuel pressure puts additional strain on injectors and fuel pumps leading to premature failure.
To open a previously recorded log, select "Open CSV File" and browse to the folder where the log was recorded. Select and open the log to populate the graph.


=Power=
[[File:BUOY001804_LOGREPLAY.png|thumbnail|center|600px]]
In general, you can expect a gain of 3-5 lb/ft of torque per pound of positive pressure added for every 1.0 litre of engine displacement. E.G. on a 2.5 litre engine, 10 PSI will generally add between 75 and 125 ft/lb of torque ---- 3 Hp * (2.5 L / 1.0 L) * 10 PSI = 75 Hp; 5 Hp * (2.5 L / 1.0L) * 10 PSI = 125 Hp.


=Intake Airflow Sensors=
You can manipulate the data, apply filters, change how it is displayed, and more by using the "Graph Options" and "Data Manipulation" sections.
Any intake metering device ''should'' be within the intake track of the turbo (know as "draw thru" or "pull thru"). It is not recommended to place your intake metering device (VAM, MAF, HFM, etc) in the charge-pipe (known as "blow thru") unless it is a specifically designed piece of hardware that can properly read a pressurized system. This is because these systems are designed to meter airflow at atmospheric levels (corrected for air temperature in the ECU). Therefore, when pressures are different than atmospheric, reported airflow becomes drastically different than actual airflow. A graph (fig. 1) illustrates this effect in terms of positive pressure.


[[File:MAF_compare_forced_induction_blow-thru_3.png|thumb|fig. 1 - A comparison of reported airflow by a MAF under different positive pressures.]]
==Flashing==


While it is possible to use a MAF as a blow-thru style, it will give you incorrect readings.  
On the "Main" page, make sure you have the proper port selected and are connected to the SSSMCK. Under "Firmware Control" click on "Select Firmware" to be presented with a file explorer. Navigate to the firmware (file extension ".mckf") you wish to flash to the device and select it.


* Why is this important?
[[File:R001804_flashing.png|center|thumbnail|600px]]
** Because every aspect of your engine's operation is determined by intake flow rate, most notably: ignition timing, fueling, knock correction, and idle control.


* Why does it matter if it reads differently at +8 PSI than at +0 PSI? Can't you just tune for that?
Once you have chosen the firmware, the button underneath it will change to "Flash Firmware". Click this button to flash the firmware. A success or failure message will be displayed in the console log.
** +8 PSI can have the same actual airflow as +0 PSI depending on a number of factors such as throttle position and RPM.
** As a generic example, 250 kg/hr airflow at atmos (+0 PSI) reports 250 kg/hr to the ECU. However, 250 kg/hr at +8 PSI reports about 500 kg/hr to the ECU.
*** This means any tune would be created for one circumstance and not the other.


It is worth noting that no retail "blow-thru" MAF we've tested have worked as advertised, and all have been standard MAFs, sometimes with a resistor added. Yes, this includes the HPX "turbo" MAFs that were supposedly designed to be used as a blow-thru MAF.
==Configuration==
You can configure most of the program's settings, such as the theme and interface scaling, by clicking on the settings icon in the upper-right side of the application.


=Manifold Air Pressure Sensors=
=Firmware=
Almost every factory-equipped F/I vehicle is equipped with a MAP (Manifold Air Pressure) sensor. This sensor, in conjunction with an intake-tract airflow sensor, provide an exact intake rate and cylinder pressure to an ECU. Manifold pressure is indicative of cylinder pressure (engine efficiency), which drastically affects tuning choices.


When converting from N/A to F/I, it is highly recommended to use an ECU that can read manifold pressures (such as MegaSquirt). However, it is possible to add a MAP sensor to most any Motronic ECU through a piggyback converter board (available [https://sssquid.com/ here]).
".MCKF" files contain the calibrations for the MAF and VAM selected. Since we are constantly releasing new versions, please [https://sssquid.com/v3/contact contact us] with your required MAF and VAM combination and your hardware version, we will reply with a download of the latest available software.


=Alpha-N=
All units ship with the proper and latest available firmware for your selected MAF and VAM, so there is no need to flash a new unit unless you are changing vehicles/tunes/MAFs, there are fixes, or the latest software requires it.
[[Alpha-N]] is a tuning solution utilizing the TPS (throttle position sensor) and vehicle RPM. This is not a good tuning solution for turbocharged vehicles, and is also a poor solution, but to a lesser degree, for supercharged vehicles.

Revision as of 18:38, 18 October 2021

Introduction

Buoy is an all-in-one data-logging and tuning tool for the SSSMCK (SSSQUID MAF CONVERSION KIT). It is in beta stages and as such may have bugs. Please contact us with any bugs you may encounter.

This tool was developed in and for Linux first. The Windows port is in very early stages and will naturally have more bugs than the Linux flavor. There is no version for Mac OSX and we do not have any plans to ever release a version for that OS.

Expect new software to be released regularly. We have not implemented any auto-update functions yet. Please bookmark this page to get quick access to the latest software.

Download

Latest Version: 0.18.07

  • Windows
    • 32-bit (JRE required) - Download
    • 64-bit (recommended for most users! Pre-compiled JRE included) - Download
  • Linux
    • 32-bit - Download
    • 64-bit - Download
    • arm32 - coming soon, please contact for early access
    • arm64 - coming soon, please contact for early access

Previous versions available by request, though you should most likely be using the latest version!

Version History

Installation

This program is designed to be portable -- there is no installation necessary. Simply extract the compressed folder contents to its own directory and run "Buoy.sh" (Linux) or "Buoy.exe" (Windows).

For the 32-bit Windows version of Buoy, the necessary JRE (Java Runtime Environment) is not pre-packaged. You may need to install the JRE if you haven't already: Java JRE. The JRE is pre-packaged on the 64-bit version (what most everyone will be using). Unless you are running an older 32-bit version of Windows (like 32-bit XP), it is recommended to use the 64-bit version.

For Linux users, Java is required to run but is not prepackaged. Many flavors of Linux will come with the necessary runtime environments pre-installed, but if you're not sure you can check with your package manager.

Drivers

Most flavors of Linux will come pre-installed with the necessary drivers.

For Windows, you may need to install the standard FTDI D2XX drivers available at the following link: FTDI D2XX Download Page

Interface

  • Main
    • Setup port, flash firmware, and view diagnostic information.
  • Live Dash
    • View and log live airflow data.
  • Log Replay
    • View previously recorded logs with many ways to manipulate and filter the data.

Usage

Connecting

With the top cover removed, you will need to find a 6-pin header. This is where the logging/flashing module will be plugged.

Loggingmoduleport.jpg

Plug in your logging/flashing module. It can only be inserted in one direction.

Loggingmoduleconnected.jpg

Connect the USB cable to your computer. If you are logging, please skip the next step.

ONLY if you are flashing the module!: it is recommended to use the USB power. You can do this by moving the "REG-USB" jumper from the "REG" side to the "USB" side as pictured below:

Usbpowerselected.jpg

Once you finish flashing, please make sure to move this jumper back to the "REG" side before continuing use on your vehicle.

On the "Main" tab you will find the connection and flashing options.

Buoy001804 main.png

First you will need to select the correct port. Click on "Select Port" and you will be presented with a list of available ports.

If you are unsure of which port the SSSMCK is connected through, you can simply disconnect the device and reconnect it to see which port is added and removed. The list automatically updates.

Buoy001804 portselected.png

Once the port is selected, click "Connect". It will take 2 seconds to connect, do not repeatedly click the "Connect" button during this time period. The SSSMCK should connect and automatically start sending airflow data. If data is not graphed on the "Live Dash" page, you can try disconnecting and reconnecting.

Data-logging

Once connected the SSSMCK should automatically begin transmitting airflow data to the program. This is displayed in kilograms per hour (Kg/Hr).

BUOY001804 LIVEGRAPH.png

On this page you can set an output file. Use the file extension ".csv" for logs (this file extension should automatically be added, but there is a bug in Windows where if your file path has one or more periods it may not be automatically added).

Once you have set the output file, you may begin logging by selecting "Start Recording". Once you are finished recording, select "Stop Recording" or simply close the program.

There are many ways to display the data, as a line (recommended and default), as dots, or as bars. The rest of the options are primarily for further diagnostics when necessary, but should not be needed or used by most users.

Log Replay

If you would like to view previously recorded logs, you can open them a number of ways. They are output as simple CSV files (Comma Separated Values). These can be read by programs such as OpenOffice/LibreOffice Calc, Microsoft Excel, or within Buoy.

To open a previously recorded log, select "Open CSV File" and browse to the folder where the log was recorded. Select and open the log to populate the graph.

BUOY001804 LOGREPLAY.png

You can manipulate the data, apply filters, change how it is displayed, and more by using the "Graph Options" and "Data Manipulation" sections.

Flashing

On the "Main" page, make sure you have the proper port selected and are connected to the SSSMCK. Under "Firmware Control" click on "Select Firmware" to be presented with a file explorer. Navigate to the firmware (file extension ".mckf") you wish to flash to the device and select it.

R001804 flashing.png

Once you have chosen the firmware, the button underneath it will change to "Flash Firmware". Click this button to flash the firmware. A success or failure message will be displayed in the console log.

Configuration

You can configure most of the program's settings, such as the theme and interface scaling, by clicking on the settings icon in the upper-right side of the application.

Firmware

".MCKF" files contain the calibrations for the MAF and VAM selected. Since we are constantly releasing new versions, please contact us with your required MAF and VAM combination and your hardware version, we will reply with a download of the latest available software.

All units ship with the proper and latest available firmware for your selected MAF and VAM, so there is no need to flash a new unit unless you are changing vehicles/tunes/MAFs, there are fixes, or the latest software requires it.