FAQs Performance, Economy and Tuning Simplified. EFI Analytics bringing the superior Automotive Tuning Software to simplify EFI http://tunerstudio.com/index.php/faqs Fri, 23 Feb 2018 00:30:16 +0000 Joomla! 1.5 - Open Source Content Management en-gb Illegal and Unlicensed MegaSquirt clones http://tunerstudio.com/index.php/faqs/85-illegal-unlicensed-megasquirt-clones http://tunerstudio.com/index.php/faqs/85-illegal-unlicensed-megasquirt-clones MegaSquirt has offered a high level of openess for people from the community to get involved and sometimes contribute back improving the EFI experience for all MegaSquirt users. This model has brought forward several key contributors that have become critical to the ongoing development and support of MegaSquirt products.

However it should always be understood that the licensing of all MegaSquirt Firmwares requires that firmware to be run on B&G manufactured or licensed MegaSquirt boards. This licensing cost is what supports the infrastructure of the MegaSquirt community such as forums and servers, but even more so, the key contributors such as developers and documentors. B&G Licensing is quite modest in cost as is the amount that makes it back to the key contributors, but these people are critical to supporting the community in an ongoing fashion and the development of new features and products.

 

Unfortunately there are always opportunist without regard for legalities or support for the community and will produce MegaSquirt clones without licensing in order to steal the development done by the MegaSquirt firmware developers, and expect to leverage the support channels provided by MegaSquirt at MegaSquirt's expense. This is sometimes to simply redirect a few dollars into their own pocket and sometimes because their product is of such low quality that MegaSquirt does not wish to associate their branding with the product.

 

So make sure you know who you are buying your MegaSquirt from. Some of the greatest offenders of MegaSquirt licencing have been:

KDFI  - these are unlicensed MegaSquirt 2 knock offs that run on typically a very dated and stolen version of MS2 Extra firmware. 

 

 

Beware of these units, you will likely find yourself without proper support when you need it. Please seek a reputable MegaSquirt dealer for your own protection and to benefit from the highly regarded MegaSquirt support network.

 

]]>
p_tobin@yahoo.com (Phil Tobin) FAQs Mon, 31 Dec 2012 16:14:58 +0000
Windows BSOD http://tunerstudio.com/index.php/faqs/82-windows-bsod http://tunerstudio.com/index.php/faqs/82-windows-bsod Question: I am getting a BSOD on windows, why and how do I fix it?

 

Answer: This is a a known problem with the Prolific usb to serial driver impacting all cables that are based on the prolific chipset including the IOGear cable.
I have seen computers work fine with this chipset and driver, but then at some point BSOD and from there on it will cause problems. It seems as though the driver does not handle a potential resource conflict and Prolific has been slow to fix it.

 

The best and easiest solution is to buy an FTDI based cable

Update:
Prolific has released a fairly new (May25, 2011) driver that appears to finally fix this: New Driver
This driver will not auto-update in Windows (on my machines, anyhow), You must remove the old driver first using the device manager, or the following utility if the device manager doesn't work: Driver Removal Utility
The software and driver update page is here: http://www.prolific.com.tw/eng/downloads.asp?ID=31

 

]]>
p_tobin@yahoo.com (Phil Tobin) FAQs Mon, 25 Jun 2012 13:10:07 +0000
Why is connection dropping when driving? http://tunerstudio.com/index.php/faqs/76-usb-connectivity http://tunerstudio.com/index.php/faqs/76-usb-connectivity Question: Why is my connection to the ECU dropping when I am running the engine or when I rev up the engine?

Answer: This is caused by data loss communicating with your ECU. The most common cause for this data loss is a poorly shielded USB to Serial Cable. Also on more rare occasions there are problems with real serial cables such as pinch or break in the line.

 


 

Question: Why will a poor USB to Serial Cable cause this?

Answer: Real Serial Ports on Laptops have all but gone, there are few laptops left that have a true DB9 serial port. However for many devices this is still the most commonly used means of transport. After market ECU's are in this group and RS232 Serial communication is still the dominate way of connecting to your ECU. So how? There are several devices to fill this gap, but by far the most common is a USB to serial cable, this can fill the need and no one will miss the old Real DB9 on their laptop.

However if connecting to a running vehicle for data logging and live tuning, it is critical to understand a few things before selecting your USB to serial adapter.

A car is full of EM noise! EM noise is the Electro-Magnetic noise created by current flowing in electrical devices. the higher the current, the more EM noise. Think about your typical car electrical system; low voltage with high current to make up for it. You have injectors turning on and off, alternators running and coils firing, ohh the coils... There are terribly high levels of EM noise generated by an automobile. USB was not designed to be used in the automotive environment.

Why is USB so much more susceptible to EM Noise than standard RS232 serial? It all comes down to 1's and 0's when transporting data, in either USB or traditional RS232, 1's and 0's are represented by voltage differences. However, look the substantial difference in the signal voltage:

USB Specification States - The receiver defines a differential ‘1’ as D+ 200mV greater than D- and a differential ‘0’ as D+ 200mV less than D-.

Standard RS232 Specification: The RS-232 standard defines the voltage levels that correspond to logical one and logical zero levels for the data transmission and the control signal lines. Valid signals are plus or minus 3 to 15 volts

That is 200 mV difference in USB, compared to 3-15V using "Real Serial"! How does that relate to the EM noise in a car, well just think how much less EM noise it takes to cause a 200mV difference for corruption or a disruption to your data over USB compared to the good old serial where it takes a 3-15V difference! The RS-232 standard was originally conceived in a different era, to transport data via modems over primitive voice lines. So it needed a high signal to noise ratio for assured delivery. That era may be gone, but this still serves car enthusiast well in our high EM noise machines.

 


Question: But How do I connect to my car then?

Answer: While USB does present potential problems, it is commonly used to connect to cars without problems and is usually the most practical solution. You just need to follow some simple guidelines when purchasing a USB to serial cable and you will save your self a great deal of trouble and time...

What to look for in a USB cable:

  • You should have either an adapter with no USB cable, or well shielded cable
  • If it does have a cable, the cable is best to be no more than 1m (3ft).
  • An FTDI Chipset is recommended. Prolifics chips are also very common, but many of their windows drivers have a nasty bug that can cause a BSOD.
  • Important! I VERY Highly discourage use of USB adapters built into the MegaSquirt they cause connectivity issues and dropouts (other than those designed in like on the MS3). They should not be offered by any reseller and WILL cause you problems.

Generally you will need more than a 3ft cable, but for that you should use a traditional DB9 cable. These are typically 6ft long, when combined with a 3ft USB cable, you have 9ft of cable. If that isn't enough, you may want to consider using a Bluetooth to RS-232 adapter.

 


For USB to serial cables that meet these requirements or a Bluetooth solution, check out what we offer in:

Cables and Bluetooth

References:
USB In a nut Shell
RS-232

]]>
p_tobin@yahoo.com (Phil Tobin) FAQs Thu, 08 Mar 2012 18:53:24 +0000
Using MSII B&G Code with Bluetooth http://tunerstudio.com/index.php/faqs/74-msiibluetooth http://tunerstudio.com/index.php/faqs/74-msiibluetooth MSII B&G firmware is sensitive to having bytes sent too fast. If you send bytes too fast, the firmware may be executing another task, by the time it finishes that task and checks if a byte has been sent by tuning software, the 1st byte may have already been over written by the next byte and the previous is missed.
 
If this is occurring, you will likely continuously drop connection, reconnect, drop, etc... Or worse, if loading an msq, you could end up with corrupt settings on your controller.
 
To prevent this, there is a configuration setting in the ini file called interWriteDelay.
 
The interWriteDelay throttles the speed that bytes are sent to the controller, it sets the number of milliseconds that TunerStudio will wait between each byte written before writing the next byte. With the MSII B&G Code, this typically needs to be set to 2 to 3 ms to ensure no bytes are missed.
 
The trouble with Bluetooth is that the specification does not allow for such fine grained control of the byte delivery. TunerStudio may send the data with a 3ms wait between each byte, but then it gets queued in a BT buffer down stream and flushed all at once. Thus on the on the firmware side it sees no bytes, then a bunch of bytes too fast for it to read.

So there is a work around... You need to set the interWriteDelay to a very high number, high enough to insure that each byte is flushed before the next is sent. I have found this to be any where from 10-25ms depending on the BT Adapter.

Shadow Logger manages the interWriteDelay on its own, however TunerStudio uses the values in the ini file, so you will need to edit your ini file. The ini file is found at:
[YourTunerStudioProjectFolder]\projectCfg\mainController.ini
 
To edit your ini, search for the line:
 
interWriteDelay =     5
 
In many of the recent MSII firmware ini files there is no interWriteDelay set, therefore it will be using the default value of 3. This works fine for cabled connections, however not always so with bluetooth.
 
Add this line near
pageActivationDelay =  50 ; Milliseconds delay after burn command.
blockReadTimeout    = 200 ; Milliseconds total timeout for reading page.
interWriteDelay =     20
That will set it to 20, and it should be pretty stable. You can play around with it some and see what is the lowest number you can use and stay stable. Making this number high will slow the time to load an msq quite a lot, but making it too low means a byte could get dropped and your settings could get corrupt. So you are best making it higher than it needs to be even if that does slow performance.
Also I should note, if you use MS2 Extra or MS3, this isn't an issue. MS2 Extra firmware doesn't mind when the data is sent at full speed with no wait between.
 
]]>
p_tobin@yahoo.com (Phil Tobin) FAQs Wed, 29 Feb 2012 20:21:47 +0000
Basic FAQs http://tunerstudio.com/index.php/faqs/24-faqs http://tunerstudio.com/index.php/faqs/24-faqs Question: Does TunerStudio support Macs?
Answer: Yes! There is now OS X installer in the download section.

 


Windows Crash

Question: I am getting a BSOD on windows, why and how do I fix it?

 

Answer: This is a a known problem with the Prolific usb to serial driver impacting all cables that are based on the prolific chipset including the IOGear cable.
I have seen computers work fine with this chipset and driver, but then at some point BSOD and from there on it will cause problems. It seems as though the driver does not handle a potential resource conflict and Prolific has been slow to fix it.

Update:
Prolific has released a fairly new (May25, 2011) driver that appears to finally fix this: New Driver
This driver will not auto-update in Windows (on my machines, anyhow), You must remove the old driver first using the device manager, or the following utility if the device manager doesn't work: Driver Removal Utility
The software and driver update page is here: http://www.prolific.com.tw/eng/downloads.asp?ID=31

 


What ECUs are supported?

TunerStudio and MegaLogViewer started with the MegaSquirt community but because of its ease of use and adaptability, it has been getting adopted by users of several other EFI controllers and data acquisition units.

MegaLogViewer now has specialized editions:

MegaLogViewer HD - For motor cycle users of Harley Davidson TTS, Dyno Jet Power Commander, Dyno Jet Power Vision, TCFI, Twin Scan and more. Learn More

MegaLogViewer BigStuff3 - Fully function MegaLogViewer for BigStuff3 users. This even includes VE Analyze and table editing of .big tune files. This is a big move forward for BigStuff3 users with data log capabilities far beyond what they have been using. Learn More

Monster Products has adopted a specialized version of TunerStudio for their Monster ECM line.

Several other TunerStudio support efforts are in the pipeline.

Naturally Shadow Logger Support comes with the TunerStudio Adaptations.

 


How do I get support for my fuel injection controller?

If you would like to have all the great features of our software work with your ECU you should contact your hardware vendor. Let them know that you what it to work with TunerStudio and MegaLogViewer. Have them contact us and we can work with them to make it happen.

 

 

]]>
p_tobin@yahoo.com (Phil Tobin) FAQs Thu, 12 Oct 2006 22:33:10 +0000