MS2 new documentation discussion

[jsmcortina]

Good catch.
What value resistors have you used and in what applications?

James

[juansh2385]

Tooth wheel application where there more than 12 tooth. I test different values from 1k to 10k until the sync lost it's solve. Mostly 10k. 60-2 is the most problematic.

[Matt Cramer]

With the MAX9926, we've found a 10K resistor in parallel with the sensor is often the best way to work with a VR sensor and 60-2 wheel.

[jsmcortina]

Another new one MS2/V3.0 hardware guide (draft.)

http://www.msextra.com/doc/pdf/MS2V30_H ... -07-02.pdf

The current versions of the other PDF manuals are:
http://www.msextra.com/doc/pdf/MS2_Sett ... -06-20.pdf
http://www.msextra.com/doc/pdf/Microsqu ... -06-16.pdf
http://www.msextra.com/doc/pdf/Megasqui ... ce-3.3.pdf

These links are subject to change. See http://www.msextra.com/doc/pdf/ for all files.

I'm particularly keen to know if there is anything in the current web manuals that ought to be included in the manuals. If there are no objections, I'll retire the web manual pages to archive status in the very near future.

James

[Manu]

James,

in '*Setting Up' document I think it's here important to tell users what to do if they don't use there sensors :

2.4 :

"In cases where MAF or TPS (Alpha-N) are used exclusively for load measurement, then the MAP sensor connection can be omitted. In this case the connection must be grounded with sensor ground wire" or something similar

I ad this to translated version ;-)

Also I have a thought about the possibility to use some 'skill level require' icons (i.e. stars, tools, etc) attached on each possible hardware mod in V3.0 manual to indicate user how good he have to be to do the job (i.e. MS2 cpu pin mod will require a skilled user while wire the 2 CAN wires will be easy). This concept can be extended to a lot of things.

Hope this can help ;-)
Regards,
Manu

Edit : add thoughts

[dontz125]

P.155, 9.1 "Example Wiring - Nitrous" uses uS or uSM pin names - FLEX, SPAREADC, SPAREADC2.

[jsmcortina]

P.155, 9.1 "Example Wiring - Nitrous" uses uS or uSM pin names - FLEX, SPAREADC, SPAREADC2.

I'll fix that.
Let me know if you spot any remaining Microsquirt-isms that I haven't edited.

James

[Breastfed]

James
http://www.extraefi.co.uk/sequential_fuel.html is very informative maybe these could be added to section 4.1.2 of the setting up guide

BTW this pdf manual is great work..well done

Breastfed

[ErnieJones]

Let me know if you spot any remaining Microsquirt-isms that I haven't edited.

James

Not being smart but are you interested in spelling/grammar call out's ? I printed the manuals and read some of them (to date) and saw a couple minor issues.

[jsmcortina]

Let me know if you spot any remaining Microsquirt-isms that I haven't edited.

James

Not being smart but are you interested in spelling/grammar call out's ? I printed the manuals and read some of them (to date) and saw a couple minor issues.

Go ahead.

My top priority is "the big picture" - whether the suite of manuals sufficiently covers what is required to build, install and tune a Megasquirt. Also, whether the way the topics are split up between "Setting Up" and "Hardware" sections works - that was intended to keep the wiring sections focussed on just one piece of hardware. The existing web manuals had just about no coverage of Microsquirt or V357 and were a mix of "if you've got one of these, then do this, otherwise..." I was trying to make it so the MS2V30 manual, for example, just covers MS2V30. With a goal of "everything you do need and nothing you don't."

Grammatical errors, cut/paste errors, typing mistakes etc. are all useful to know about too and I'll fix them.

Contructive critique of the actual text is welcome too - if the current wording is unclear, please post it up and ask for it to be re-explained.

James

[ErnieJones]

This is truly fantastic!

As a total newbie (read close to incompetent) I'm able to look things up and, quite possibly, learn how to make the majority of my custom PCB without asking a million questions on the forum.

One thing, I bought a nice binder with separators and printed the Microsquirt Hardware Guide, the Microsquirt Module Developer's Guide & the Tuner Studio Reference Guide (ie, lots of printing).

Would it be possible to maintain a changelog so that I don't have to re-print the whole scmear when changes occur? I don't want to add to your work load though as I really appreciate what you've done with these docs. I think they are going to make the 'squirt way, way more accessible to people

[ErnieJones]

I'm in the middle of trying to design a base board for the Microsquirt module to interface with. As such, you could say I'm being a bit of a pin-head (see what I did there?)

But, I seem to be running into....a documentation discrepancy?

On this page => http://www.microsquirtmodule.com/indexright.html

It shows these pins 35, 37, 39, 41, 43, 49 as Power Ground
Question - what about pins 45 & 47 - there seems to be no mention of them anywhere

In the new Microsquirt-Module Developers Guide, which seems to also be called the Microsquirt Hardware Guide (even though that's a different publication altogether) those same pin-out's on page 4 are explained like this;

35,37,49,41,42,43,45,47,49: Power GND. Use all Power Grounds in parallel

This is really weird. 39 has gone missing altogether, 42 has been included which is from the other side (apparently it's INJ2 out), and they are out of order in the list.
Shouldn't it be something like pins 35 through 49 inclusive are Power GND, ie, 35,37,39,41,43,45,47,49 ?

[jsmcortina]

Yes, there were a couple of typos in the Microsquirt-Module Developers Guide. The diagram on the left should match the silkscreen on the module itself.

I'd like to include some more content in there in the future. Especially around tach inputs which are quite different to the cased Microsquirt (V3)

James

[ErnieJones]

Doh! Looking at the module itself to determine the proper pin-out's would be definitive Unfortunately, I don't have mine yet having ordered all the other little bits and pieces. I figured I could save the module for last as it was easiest to source. Perhaps it should have been first on the list

It would be nice to see more information for the module. The Microsquirt docs are very comprehensive and confidence inspiring - the module docs are very limited (so to speak) so I'm bouncing back & forth between the two and trying to extrapolate the differences - not easy for someone if they are not fluent in the product(s).

[AudiA4QT]

Hi NOT new to Megasquirt just the forum
New manual is great in regards to info just used it to reconfigure my Megasquirt for an Audi A4 install.

I'm also a trainer and assessor in Australia so have a little experience with manual writing.
Contents is HUGE and very hard to navigate. My only suggestion is a main contents with main headings and the sub contents when you get to each main heading.

[weeblebiker]

Hi,
looking through 4.7 boost control in the current set up draft linked in the post above and there is no mention of the "closed loop sensitivity" slide bar. from the help icon it sounds like another form of "P" like in the pid maybe for simple closed loop? however the slide bar remains active in either closed loop setting.

what to use the slide bar for and how the slide bar affects the pid settings should be fleshed out.
otherwise, incredible work!!!!!

[jsmcortina]

Contents is HUGE and very hard to navigate.

Do you find the TunerStudio reference any easier? That has a list of chapters and then the detailed contents.

what to use the slide bar for and how the slide bar affects the pid settings should be fleshed out.

Agreed. Thanks for pointing that out. That section of the manual hasn't yet been fully updated for the current firmware.

Also, thanks to everyone that is giving feedback and pointing posters to the new docs.

Do people think it would be of value to provide an online PDF->HTML page by page viewer ? That way you could hyperlink directly to the page in the live manual instead of quoting a section number? I'm undecided on whether this just complicates things or if it makes it easier to provide support.

James

[Matt Cramer]

That way you could hyperlink directly to the page in the live manual instead of quoting a section number? I'm undecided on whether this just complicates things or if it makes it easier to provide support.

James

Yes please. That would make a huge benefit for us.

[jsmcortina]

That way you could hyperlink directly to the page in the live manual instead of quoting a section number? I'm undecided on whether this just complicates things or if it makes it easier to provide support.
James

Yes please. That would make a huge benefit for us.

Ok, I'll do my best.

James

[Matt Cramer]

Much appreciated. Linking directly to the appropriate section of the manual is very useful for us when we're providing support.