rb26dett

I chose it years ago when I was younger as I liked those engines :-)

I've heavily thrashed my rb20de though, heavily heavily thrashed.

All twincam RB motors are stout and thrashable if tuned properly. Like all other engine/car types, the ones that blow up are mostly from hacked oem ecus and increased boost etc.

Consider importing an RB30E from ozzy or NZ to put an rb25de head on. There are pdf guides available to show how to do that fairly easily and cheaply. With the usual rods and pistons, 600crank hp and 7krpm with 15 - 25psi are achievable fairly easily depending on intake and exhaust mods etc.

Hows that? :-)

rb26dett

Minor update :



Human readable serial logging is working as of this morning. I'll tidy it up and add a bunch more variables before doing a release later today.

I also changed the formatting of the forum a bit. The moderators are now Blue, the members that have contributed the most useful stuff to discussions are Green, I am now Fred instead of Admin which feels much more natural, and I added an Admin user for site stuff (who is me for now, but could be others later).

Fred.

rb26dett

There was a bug in the handling of char to ascii so now lostcranksync can be displayed it works :-)

Also visible is rpm increasing and decreasing and pulsewidth decreasing and increasing and 1/3 down a processor reset (induced by me). All things that have been happening for ages, it's just that now I can view the exact numbers involved, the RPM jitter etc etc.

Mint!

Fred.

AbeFM

iTrader: (3)

Very very very cool Mr. Fred. This is like the time I wasn't happy with the paper towel holder in my kitchen and fixed it, But you know.... more. It does have a ring of progress to it, and for one guy doing it you're working at a breakneck pace.

rb26dett

You mean like I'm working while having a broken neck? (ie slow) lol

I'd just like to point out that although no one could see it, my code had a lost sync counter BEFORE ms2extra :-) In fact, it may even have been me that suggested it to them ;-) As a bonus, you can now see mine too! lol.

Fred.

ps, nice avatar Abe

rb26dett

Introducing FreeTherm a new little utility that does a similar thing to easytherm :



C# + mono = "up yours" to M$. (microsoft)

Result :



Real temperatures in the ECU :-)

Too easy.

(in degrees K * 100, so divide by 100 and subtract 273 for deg C, you are on your own for deg F)

Fred.

rb26dett

Screen shot of my little thermistor app running on Vista :

http://i260.photobucket.com/albums/i...ermOnVista.jpg (190kB)

Get it here : http://sourceforge.net/project/showf...ease_id=608485 (166kB)

And the library it needs here : http://forge.novell.com/modules/xfco...-win32-0.0.exe (23.3MB)

I'm *hoping* that Stu intends to use GTK# for the tuning app if/when he does it, so that library install should cover both apps and we can produce other utils in C# in future too to keep the downloads to a minimum.

Of course, it's no use to any of you really, and not 100% finished (see the TODO in the zip) either, but I thought I'd post it up anyway.

Fred.

rb26dett

OK, it has been nearly 3 months since I made a code release, but to be fair, I have a few excuses...

I had to get one of those things... what are they called? A job! Yes, that's it! Which took up a bit of time to obtain, and more to maintain... Plus, on my third day of work, my hard disk died a horrible death and I was silly enough to try Ubuntu instead of my usual Debian. Anyway, to cut a long story short, I'm back on track now! And in fine form even if I do say so myself :-)

Tonight I've released 0.0.16-FlashGordon

It does many things like jumping through hoops, but no engine running just yet ;-)

The zip file is nearly 25% bigger than the last release so as you can imagine quite a bit of work has gone into it...

SeanK has written some code to do flash burning, and I've added RAM paging to allow many tables and things to be tunable. Lots of other little things too.

In the mean time a couple of clever blokes called Jared and Dave have been hard at work designing some hardware for us :



http://i260.photobucket.com/albums/i...10_A18_P01.png

Those are just drafts, but it is coming along pretty nicely. So nicely in fact that they are well ahead of me. By the time I'm ready to run an engine, the hardware will be chrome plated and capable of running a small city ;-)

Expect more regular releases now as winter is coming and there will be nothing else to do except perhaps keep the missus warm ;-)

Thanks for your patience!

Fred.

arga

Great work. I haven't been to DIYEFI in a couple of months. I need to check out this latest release. What do I need to compile it?

BTW, SW is supposed to come after HW and hold up release. It's just our lot in life.

rb26dett

Cheers :-)

You need : make, m68hc11/12 gcc and friends, zip, and maybe a few other little things. Roughly the same stuff you need for an ms2e build. It includes files for an eclipse project. It should open up nicely in there. I'm using the latest version, but older ones should be fine too.

Fred.

rb26dett

Last week I put out 0.0.17-SpudEchoes With two way checksummed packetised headered IDed data and a matching really really simple gui called FreeEMS-Tuner.

It can do basic stuff like send back it's own name and version etc. It could also return blocks of memory, ve tables etc, thermistor lookups etc, and blocks of setting data.

In the unreleased code it can receive data too and thus it is now tunable :-)

It needs more work, but it's getting pretty close to being useful.

I reckon in a few weeks the gui and firmware will talk to each other in more detail and it will be tunable.

Why spud echoes?

spud because the source in that release is half baked... and echoes because it can echo data back and forth on command, and also because I listened to pink floyd echoes about 50 times while developing it.

I'll give you a screen shot of the big red button because that is fairly cool in a childish sort of way :



One guy in Wellington NZ and one in South Carolina are working on that, and I'm working on trying to make the EMS side of the comms deal ROCK solid. Currently it's pretty good, but I'm not done yet!

I hope to finalise more of the comms stuff and do another release in a few weeks or less such that those guys can focus on making a nice GUI for it while I work on the guts that will actually run the engine. Mean while the hardware guys will be working on their share, and hopefully we'll all come to a climax at exactly the same time producing a wonderful system that actually works TM :-)

Fred.

AbeFM

iTrader: (3)

It'd be cool to see if you could get it working with MS Tuner Studio. That has a nice look to it, and the guy who writes it, while not always speedy, seems to be pretty good.

I'm trying to con him into writting a spark map autotuner right now. :-)

rb26dett

You know, I saw the body of your post in my email subscription and was quite looking forward to a witty response.... but it's you... so I'm a bit stunned...

In case you don't know he's about as close to B&G as their underwear and about as likely to add our protocol (do NOT ask me to use theirs... SO many reasons NOT to do that...) as Bruce is to design us a PCB or Al is to join in coding ;-)

I think that about sums it up. Plus, it's too megatune in it's feel if you ask me. Mainly because it works the same way...

Fred.

rb26dett

Now it's comprehensible too :-)

He's like me, working on it daily heaps! Will be useful in no time :-)

rb26dett

Teaser :



More to come soon :-)

Fred.

wayne_curr

iTrader: (8)

I just gave this thread a quick read. Interesting stuff you've got going on here. However, your last screenshot left me wondering...

rb26dett

Ask Aaron, I'm pretty sure that, the version, the reference to me next to that, the icon on the desktop and maybe more were all put there esp for that screenshot to get the likes of you going ;-)

Not my screen shot, not my app, I'm the firmware guy ;-)

Fred.

wayne_curr

iTrader: (8)

I suspected that as well haha. Sorry to crap on your thread like that :P

rb26dett

It's all good :-) The more interest the better!

rb26dett

Latest update hot off the press :

New firmware release : 0.0.18 JackTheRipper

The last two releases added real packet based serial communications with extensive error checking and verification. This isn't quite ready for the world as the tuning interface isn't quite finished just yet. It shouldn't be long before we can adjust the parameters the device is using on the fly, and when I say that, I mean almost all of them.

Enhancements over MS due to the serial architecture include, but are not limited to :

• Datalogging at double the speed over the same speed link.
• Reset the device via the tuning app without cycling the key.
• What you send IS what you get (checksummed and verified).
• Random data can not corrupt memory (no DMA setup, all by logic/lookups)
• If it works, it works right, though bad connections will make it slow, but that is FAR better than corrupt maps running your engine!
• Ability to burn small blocks straight to flash without sending the whole page
• Ability to save part of a block from live tunable ram without saving the rest

Additionally, it now builds on windows 2k and XP, thanks to Daniel for his help making that work. Thanks to Sean for his assistance in getting this far, the flash stuff is great. Finally, the mathematics code is much cleaner with no reduction in functionality.

A demonstration of the serial and flash functionality is available in this video :

YouTube - FreeEMS 0.0.18 JackTheRipper + Tuner



Version Control by Git

The firmware source code is now publicly hosted on github with the following URL :

fredcooke's freeems-vanilla at master — GitHub

This is an exciting move for a large number of reasons. Not least of which being the ability to fork the code easily and allow me to keep track of what you are doing with it. In this way if you don't want to discuss what you are doing with me until it is done, you don't have to. Of course, it is better if you say "I'd like to work on XYZ" so I can advise whether that is a good idea, and if so avoid that area myself. It is also possible to just download a tar ball or zip of the current repository version of the code at any time, however I urge you to fork it using github and publish your work for the world to see so we can easily integrate it back in.



Code Statistics by ohloh

With the public source code repository we now have a source of genuine statistics about the code base. These are generated by ohloh.net automatically and available for the world to see. So far the results look good. It will be interesting to see how they change over time. If you are interested, take a look here :

https://www.ohloh.net/p/freeems



Issue tracking with MantisBT

As the system grows and diversifies we will face many challenges. One of these is keeping track of bugs and feature requests from users and testers. In that direction Aaron was kind enough to set up and host an instance of Mantis Bug Tracker. This is available for use right now. Anyone can view it, but you must sign up to create bugs, at the moment an administrator needs to allow a member to create bugs, but we could change that in the future if it is too restrictive. Please use this for anything non-trivial that you notice that needs fixing or that you would like to see. Please us this service if you are planning on reviewing the code and/or testing it out on the bench and/or just want to ask for a feature. Also have a read around the forum and check for existing bugs and requests before creating your own, but don't be shy about it. The URL is here :

http://freeems.aaronb.info/tracker/



User driven documentation on DocuWiki

Aaron has also setup a user documentation system ah la wiki. The wiki is a DocuWiki which is best suited to source code use. To prevent vandalism by those who are less than enthusiastic about this project you need to have a login. If you feel you have something to contribute (So I can keep coding) you can find it here :

http://freeems.aaronb.info/wiki/



Doxygen code documentation

Jared has been generating automatic documentation from the source code with Doxygen for a few releases now. If you want to get a more visual insight into the source code, you can find them at the following location :

Index of /doxygen



Release versions of the code

If you are interested in getting the latest official version of the code to tinker with, you can always find them on sourceforge. It is far superior to get the latest development copy from github as above, however the release versions are guaranteed to more or less just work as described. If you are conservative or want something to use on an actual car in future (once it works as a system) then get your copy from here :

https://sourceforge.net/project/show...kage_id=258422



What is planned?

Hopefully in about 48 hours Aaron will get a tar ball copy of the fully reworked Tuner code to me. This, among other things, is supposed to have threading and a working decoder for the packets, awesome!. Who knows what else it may have in it :-)

For the firmware, 0.0.19 is due out in early January with goals including :

• A revised serial specification and implementation
• A fully documented serial interface and data map
• Restructuring and tidying up of the overall code base
• Multiple datalog types including super fast scope and logic analyser functions
• Other documentation like serial implementation, freemind mind map, readme etc etc updated
• Documented hardware setup design

Of course, all of that is subject to change and re-evaluation, but this is the current plan of attack!

Thanks for reading and your interest in this project and indeed the whole movement!

Regards,

Fred.