Page 1 of 2
v2.881 release
Posted: Sun Sep 23, 2007 5:59 am
by grippo
This v2.881 release has two changes from v2.88:
1. When you load fresh code, the fuel pump and led will toggle on and off every second in addition to MT rpm bouncing from 0 to 8000. This makes it more obvious to users that soemthing needs to be done (set ECU Type), and after Bruce flashes code to new microsquirts, it lets him know the code is running correctly.
2. I also found and fixed some code problems in dual spark at very low rpms.
No ini changes are required.
no access to VE and AFR tables
Posted: Sat Sep 29, 2007 6:09 am
by tubefan
Hi,
I have loaded the newest firmware into my brandnew MicroSquirt. But I have no access to the basic tables via Megatune 2.25p1.
Communication to MicroSquirt works. ECU type is set, Injection control parameters are also set except of the 'Engine type', which is not accessible too. See attached screenshots.
Posted: Sat Sep 29, 2007 7:00 am
by Bernard Fife
Be sure to get the latest code
and INIs from here:
http://www.megamanual.com/ms2/code.htm
and follow the directions on that page (
Al meant no INI changes are required if you are moving from the 2.88 code).
Lance.
no access to VE and AFR tables
Posted: Sat Sep 29, 2007 10:54 am
by tubefan
Hi,
the megasquirt-II.2.8, the settings.ini are the latest version 2.881 (just fetched them today).
I am moving not from the 2.88 version, but from 2.867 which was delivered with the MicroSquirt.
Would you suggest to start frm 2.88?
Strange is also that the software does not see the cam trigger signals (Hall sensors). The hardware is ok.
Posted: Sat Sep 29, 2007 11:15 am
by Bernard Fife
tubefan,
Make sure the setting.ini is in the project \mtCfg\ sub folder. Have a look in the audit.log file in the prject directory, it will tell you which files are being used. It will be something like:
Code: Select all
r settings.ini
+ C:/Program Files/MegaSquirt/2.88/mtCfg/settings.ini
settings.ini:0018 #group CODE_VARIANT
settings.ini:0019 unset DFI (false)
settings.ini:0020 unset DUAL_TABLE (false)
.....
If the correct file location is being used, then open the settings.ini file and look for two lines:
If they are not there, you might add them.
However, if they are not there, then it is very likely the megasquirt-II.ini isn't the right one (since ECUType isn't being found). So I would redownload it (you may be downloading a cached version), and
either:
- rename it to megasquirt-II.ini and copy it to the project folder,
or
- download it to the C:\Program Files\MegaSquirt\MegaTune2.25\mtCfg folder, and acrtivate it using the configurator.
If you download and rename the file in the project folder,
don't then activate megasquirt-II.ini.2.8 in the configurator, as this will use the old megasquirt-II.ini.2.8 from the \MegaTune2.25\mtCfg\ folder.
Lance.
Posted: Sun Sep 30, 2007 2:27 am
by tubefan
Lance,
that was the perfect hint. In my settings.ini the MAPbaro was set. So it was an easy fix. The tables are accessible now.
But one problem still exists: The MicroSquirt does not see the tach trigger signals, neither via OPTION+/- nor via VRIN.
Via OPTION the Hall signal toggles between 1.8V/0V. That's what I expect for a 4k7 pullup to 5V, controlled by a Hall sensor with open collector. So the hardware seems to be fine.
The wires of the VRIN are ok. But I just can check them up to the AMP connector.
What else I could check?
Tubefan
Posted: Sun Sep 30, 2007 3:38 am
by Bruce Bowling
tubefan wrote:Lance,
that was the perfect hint. In my settings.ini the MAPbaro was set. So it was an easy fix. The tables are accessible now.
But one problem still exists: The MicroSquirt does not see the tach trigger signals, neither via OPTION+/- nor via VRIN.
Via OPTION the Hall signal toggles between 1.8V/0V. That's what I expect for a 4k7 pullup to 5V, controlled by a Hall sensor with open collector. So the hardware seems to be fine.
The wires of the VRIN are ok. But I just can check them up to the AMP connector.
What else I could check?
Tubefan
For a Hall source, you should use the opto circuit (incorrectly named option on the wires).
Here is a quick way to check the opto circuit - tie opt+ to +12V and tap the opto- wire to ground, each tap is a tach pulse and you should see tach activity.
- Bruce
Posted: Sun Sep 30, 2007 4:22 am
by tubefan
Bruce,
That works.
So I have learned, that 1mA (5V / 4k7 Ohms) ist not enough to drive the Optocoupler MOC205. Can you tell me the threshold current?
Can you also tell me the threshold voltages of the VRIN and the VRIN2?
Tubefan
Posted: Sun Sep 30, 2007 6:48 am
by tubefan
Bruce, Lance,
Now I have applied 12V to the OPTO and VRIN2 and everything works fine. For the VRIN I am surprised that such a high trigger voltage is necessary.
Thanks for your endurance.
Tubefan
Posted: Sun Sep 30, 2007 8:16 am
by Bruce Bowling
tubefan wrote:Bruce, Lance,
Now I have applied 12V to the OPTO and VRIN2 and everything works fine. For the VRIN I am surprised that such a high trigger voltage is necessary.
Thanks for your endurance.
Tubefan
The VRIN2 input (the second one) has a threshold voltage of 1.8V, there is a note on this on the top of the schematic page:
http://www.microsquirt.info/schm4.gif
This should be high enough for the hall sensor. However, the saturation voltage drop of the hall's C-E needs to go below this point, it looks like the +12V source with the resulting on-current value produced this.
For the opto, it does need more than 1ma to operate. And, the LED and series diode (on the uS) drops probably 3.5 volts. Again, +12V gave the added headroom.
Also, for the opto setup, you can run the hall transistor as a series switch - since it is an open-collector (emitter grounded) you can hook the opto+ lead to +12V and the opto- lead to the collector of the hall sensor. But it sounds like you have the tach working, which is excellent!
- Bruce
