[Logicaluk]

I've been asking myself that question a lot.

I'm a normal ish guy, working 40hr weeks and I love building/modifying cars it's my hobby, I don't earn a big wage, so my money has, when I have some spare be spent very carefully, I first came across Speeduino, in 2017 it looked like a great but not well-supported or documented, so I went with the next best option which was a Micro Squirt, that looked much better documented and supported.
Long story short I blew the MS controller when I was working on the car and need a new ECU, and looked at Speeduino again, and it's come on leaps and bounds, one of the first things I did was download the manual, (go do it, pretend it's the first encounter you have had with Speeduino, what do you think?)

Please don't take what I'm about to say badly, I just want to improve the experience for new users.

I found the manual to be confusing, it's not laid out logically, the wiki version is better, but it's not great, if you know what you're looking for there is a lot there, but if you don't, and you're just starting out with Speeduino it's a really steep learning curve and there are not many signposts on the way, so the people who get that far have to ask a lot of questions, luckily there is a core community that really supports new users.

The beginners guide by oldgray is very useful but needs updating, so I started building my own manual, using the data from the Wiki, bits from forum posts. The jump from something just for me to a manual for the whole project is bigger than I thought it would be, but I thought I could make it my contribution to the Speeduino project, because I can't write code or design circuits. More people using Speeduino is more better, more places would be willing to work on it and tune it, and that can only be good for all of us.
Dan

[pazi88]

Why wouldn't you just modify the Wiki to be better, rather than making another manual?

[Logicaluk]

Why not modify the manual.
1 Because what I had in mind was such a massive reorganization, it wouldn't have been honest of me to have said I just wanted to add to it, then effectively ripped the whole lot to bits and redone it.
2 If I had done that, it would have been pretty much useless to anyone whilst I was doing it.
3 I can see it probably would have upset some people.
4 It was much easier to do it all offline, prove what I had planned would work (in fact it took 3 rewrites of the basic layout before I was really happy with it, before trying to get some support for the idea.
5 It could be trialled it separately so it could fettled up in to the easy to use, really useful tool it should be, before going live.

But after spending all my free time on the project for weeks, I got the feeling it wasn't wanted and I couldn't find a free way of publishing it so people could make their own minds up about it, so I stopped working on it.

Dan

[JHolland]

You can publish almost anything for free on Github, put a copy on their and share a link so others can take a look at it. I haven't read the Speeduino manual for a long time but I just looked and it has been updated recently so its not a 'dead' document.

[Logicaluk]

I tried git hub but iirc security issues between git hub and the wiki stopped it working, I am not particularly good with the way it works.

I'm not saying it's a dead document just not as easy to use as it could be.

If it's wanted and I can have access I think it can be uploaded next to the existing manual.

Dan

[pazi88]

The manual is automatically updated from the wiki, so if you update the wiki, it also affects the manual.

[Logicaluk]

Yes, I used the trm manual because I'm an old fart, how do I go about getting access to upload to it?
Dan

[purplelightning]

Yes, I used the trm manual because I'm an old fart, how do I go about getting access to upload to it?
Dan

Are you looking to upload it to Github? In the near term you can add it as an attachment to this topic.

[Rednaxs60]

Perusing the Speeduino forum for the umpteenth time, and this topic/thread is interesting. I have been reviewing Tuner Studio, will get to MegaLogViewer in time, and need to look at the Speeduino Manual/Wiki in conjunction with this review. There are gaps, missing information that would be nice to have, but a person needs to use what is available.

I review these apps, documents to get a better understanding of the engine tuning process and what is needed to be successful.

Understand the frustration of those that need to use it. It is possible to cobble together an exact picture if you want to peruse the manual/Wiki, the Speeduino forum, on-line and other threads.

This issue is much like the engine tuning process. There are a lot of on-line companies, YouTube and other information that needs to be assimilated, organized into a cohesive - concise order.

It's not that there is not a need to have an on-going review/change, it's having someone to coordinate the effort. Doesn't have to be a complete rewrite than publish, can be done in small bites.

I am doing my own review, doing a personal rewrite based on my understanding and research. There's a lot of idiosyncrasies with the Speeduino ECU, but not insurmountable.

Not much in this post to support a new version of the manual/Wiki. I submit that there are probably a few members doing their own annotations for their own edification.

Cheers

[Rednaxs60]

I just finished my review of the Tuner Studio (TS) software, and will be looking into MegaLogViewer (MLV). It was well worth the effort. There are a lot of nuances and interrelationships that may not be as obvious as one may think, but once researched, are not as much "rocket science" as one may think. I'm expecting a review of MLV to be just as interesting and rewarding.

The Reader's Digest version of my review is that the family of Speeduino ECUs provides the user with a very complex and capable ECU regardless if it is a Speeduino ECU, or Speeduino clone ECU. These ECUs may not have all the exotic features/functions found in high end proprietary ECUs, but has most, if not all, features/functions that the DIY EFI enthusiast will require.

This review took me approximately 4 months in between everything else life throws at you.

Thought I'd follow-up on my previous post. Cheers