Want to head to Monterey, but can't start Megasquirt because missing drivers?! Please Help.

T

tomcolitt

(deceased)
Messages
289
Reaction score
4
Location
Los Angeles, CA
I was going to leave for Monterey tomorrow morning and as I feared, I am having trouble using the MS ECU. I plug everything in, but my laptop doesn’t even communicate with the ECU and says that it needs a driver for the controller. I can’t find that driver on my DYIautotune installation CD, nor on their website. Does anybody know where I can get those within the next few hours?

Thanks, Tom
 
They don't have them online? Oh, nevermind. Does it say what the driver name is? Part numbers, serial numbers... anything to help with a search.
 
Are you using a USB to serial port adapter? When I was doing it a few years back, not all adapters would work. You had to have a certain one, and I believe there is a driver for the adapter itself.
 
afeustel said:
I think Layne is referring to these drivers...I think I had to install the same thing.

http://www.ftdichip.com/Drivers/VCP.htm
Click to expand...

Probably need that too, but I believe there is a driver for the adapter itself. This is the one everyone used back then because it was known to work, other brands were a crap-shoot. Getting computers to do what you want seems to never be exactly the same process twice, and I always forget what it actually took to make it work.

dynex-usb-to-serial-gray-xl.jpg
 
Here's an update to the troubles with my Megasquirt ECU. It turns out that the serial to USB cable I got with the purchase was not compatible. I bought the correct cable and my laptop now communicates with my ECU.
 
I have tried to load an initial start-up tune to set up my ECU for it's first start,but it looks like I am having trouble with that as well, even though the msq file that I tried to load is from another forum member who is using the same version of MSPNP2 ECU as I am. Here is what is happening:


When I first started my new project and clicked the “detect” button,

  • Found: MS2/Extra release 3.3.1 20131206 18:45GMT(c)KC/JSM/JB PNP - On RS232: Port:COM3, Baud:115200
After that, I got the following warning message when I tried to load my start-up file (it’s attached above):

Signatures do not match.!


Tune File Signature: MS2Extra Serial 310

Configuration signature: MS2Extra comms330NP


Do you want to load it anyway? Yes/ No

I clicked yes and got the following error warning log:


47 Warnings:

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:IdleCtl equal to the proposed PWM Warmup

Warning: Value in .msq '"Port Injection"' for parameter: injType is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Disabled"' for parameter: AMCOption is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Spark Retard"' for parameter: RevLimOption is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Disable"' for parameter: enable_pollADC is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:can_poll equal to the proposed Disabled

Warning: Value in .msq '"1"' for parameter: can_poll_id is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Master"' for parameter: can_poll_slave is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Local"' for parameter: flexFuelRemote is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Local"' for parameter: knk_remote is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Remote Port3 Bit 0"' for parameter: knkport_remote is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Off"' for parameter: spk_conf2_ngc is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:spk_config_spka equal to the proposed D14

Warning: Value in .msq '"Advanced"' for parameter: userlevelbits is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:rtbaroport equal to the proposed MS2 AD6/JS5

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:ego2port equal to the proposed MS2 AD6/JS5

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:flexport equal to the proposed JS11

Warning: Value in .msq '"PWM0"' for parameter: flexportRemote is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Off"' for parameter: feature4_0maxdwl is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Off"' for parameter: feature4_0mindwl is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Off"' for parameter: feature4_0vanos is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Normal"' for parameter: boost_ctl_settings_invert is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: baroCorrVals array size does not match the currently loaded configuration, rescaled .msq values to match configuration.

Warning: baroCorrDelta array size does not match the currently loaded configuration, rescaled .msq values to match configuration.

Warning: Value in .msq '"Local"' for parameter: tsf_remote is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Remote Port3 Bit 0"' for parameter: tsf_remote_port is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Local"' for parameter: tss_remote is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Remote Port3 Bit 0"' for parameter: tss_remote_port is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"78Hz"' for parameter: pwmidleset_hz is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:tacho_opt3f equal to the proposed IGN (JS10)

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:launch_opt_pins equal to the proposed PE0/JS7

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:N2Oopt_pins equal to the proposed PE0/JS7

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:N2Oopt_pins2 equal to the proposed IAC1+2

Warning: Value in .msq '"Local"' for parameter: N20remote_input is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Local"' for parameter: N20remote_output is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Remote Port3 Bit 0"' for parameter: N20remote_inport is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Remote Port1 Bits 0+1"' for parameter: N20remote_outport is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Disabled"' for parameter: RotarySplitModeRX8 is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Rotary off"' for parameter: RotarySplitModeOn is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:testop_coil equal to the proposed CoilA

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:testop_inj equal to the proposed Neither

Warning: Value in .msq '"Off"' for parameter: testmode is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Neither"' for parameter: test_addinj is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"run"' for parameter: iactest is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: Value in .msq '"Off"' for parameter: iactestlock is of a type that is not compatible with the current firmware.This will be ignored, please correct manually.

Warning: idleadvance_curve array size does not match the currently loaded configuration, rescaled .msq values to match configuration.

Warning: idleadvance_loads array size does not match the currently loaded configuration, rescaled .msq values to match configuration.



What do I have to do to make my start-up file compatible with the config. signature?
 
Hi Tom. I have not looked at my MSPNP config for a bit but I think what those messages mean is 1) either the .msq tune file you borrowed is NOT from an MSPNP2 box that is the same version as yours or 2) your initial config parameters are not correct for your own MSPNP2 box.

That said, I think Turner Studio tries to auto detect your ECU model and MSExtra version so it may be that the .msq tune file is in fact not from the same version of box and guts (case 1 above).

However, the Turner Studio messages in your note appear to indicate that the software took appropriate steps to modify the input parameters so that you can open the file. The main thing you want are the VE, Ignition, and AFR tables to load into your project. The remainder of settings can easily be modified. There are some critical setup steps regarding the timing/toothed wheel config as well as calibration of the TPS and IAT temp sensor, and O2 sensor that have to be performed before attempting to start the vehicle.

Others with more Megasquirt skills can please chime in for assistance.

Drew
 
Hi Drew

Thanks for the good info. Since I have no MS experience, what you say makes much sense and I went ahead and tried to start the car as is and it did, in fact run, although not quite as well as I expected. The person I got this start-up tune from has an engine quite similar to mine and he has the same ECU and firmware as I do, so we are puzzled at this incompatibility. As you said, Tunerstudio seems to have loaded the file anyway. I didn't check the timing because I read that on the BMW 68 toothed wheel it is not necessary because it is indexed to the crankshaft. As for the IAT sensor, I still had the BMW AFM connected, but I will check it anyway. Also, I was going to see if I could configure the original D-jet IAT sensor to work with MS as I am shooting for the most original look I can get and it's located right in the intake "log". I even built my own injection harness that looks almost like the original.

Thanks again, Tom
 
You must log in or register to reply here.
Back
Top