FastHatch

Version 0.43 is available, added

- Leading ignition map
- Sequential turbo

http://www.fctune.com/download/FCTune_0_43.exe

Please let me know how you would like to have ignition split displayed. Extra read only map? Or should the values be editable and Trailing is than Leading - Entered split value?

SlvrRexx

i'd vote that you can change the split values... this will help new users starting out to get 15 split in all boxes. also it will help save time while tuning for max power.

FastHatch

If you enter a split value, should i set Trailing = Leading - Split or Leading = Trailing + Split?

P.S.: If someone has already download v0.43 please download it again, it was set up to work with my own box and not the Datalogit. Sorry.

SlvrRexx

IMO i think you should make it Trailing = Leading - Split. because most people will probably do their leading b4 their trailing. just seems like leading should be the main one.

TailHappy

Wow, what can I say, I'm very impressed. Your response eases my mind a lot. Until you know otherwise, you basically have to assume people don't know what they're doing. There's a lot of people just calling themselves programmers... (again, no direct insult to you, just saying in general)

The only reason I trust FC Edit is because it's been tested by so many people. I'm generally leery of beta testing when it comes to my car's engine.

Glad to see you're doing this in C++. Should be a lot more efficient than the VB6 of FC Edit. I assume you'll try to have logging capability at some point? That's one of my gripes with FC Edit is that I imagine the code isn't optimized. I'd be willing to bet you can get more than 10 samples per sec out of the PFC, but I could be wrong.

I also agree that you should be able to edit split directly. And it should be Trailing = Leading - Split. That's also the way FC Edit works.

Also, something I use in Edit all the time that doesn't appear to work in Tune. If you select a range on a map, and then type in a number, it's nice for that to adjust all the numbers in the range. For example, on my fuel correction map, it's common for me to select an entire P-row, and then type in 1.1 to add 10% to that whole line. Hope that makes sense.

Thanks for your response and like I say, that has greatly increased my confidence. Extremely nice software so far. I'll be glad to do whatever I can to help! Like I say, I'll do a download tonight and compare with Edit and post the results tomorrow.....

FastHatch

You can do the testings without the engine running, so there is no risk. Make a copy of your calibration and write it back when you are done.

*hint* You can also connect two com ports with a null modem cable and then start FC Edit and FC Tune, FC Tune emulates the Power FC *hint*

You can change some values in FC Tune and then click "read all" and you'll see your values in FC Edit


Actually only the Win32 stuff is in C++, everything else is written in ANSI C. The reason why i made this is the portability to microcontrollers.

Even the windows are not Win32/MFC code, i've made a generic interface with InitView, QueryValue, QueryString, UpdateValue, ...

InitView describes the columns/cells (value type, number of digits, packet id, lower and upper limit) and than the grid calls QueryValue for each cell or UpdateValue if a cell was changed.

You can't even enter a character that is not valid for a cell. If you enter "a99" in FC Edit it result in a 0.




Logging capatibilies are already built in, but i don't know how to display the values yet. FC Edit has it all on one page. Should i make one window for each block of monitor data? Bar graph? Line graph? Only a textual view?

The logging rate is limited due to the baud rate. Although the baud rate between the box and the PC is 56000, between the box/Commander and the PFC it's only 19200. More than 10 samples a second won't be possible.

But i'll save the logging data binary, that makes it possible to add built in logging on the box.


I'll have a look at it tonight.

EvoErik

How can I help with a Mitsubishi Evo?

Regards,
EvoErik

TailHappy

Wow, with every post, FastHatch, I'm more and more impressed.

That's REALLY slick the way Edit can talk to Tune. NICE! And yes, I had already thought about mitigating the risk by doing another write from Edit to the PFC after using Tune. My only fear was that Tune apparently accesses some data that Edit isn't aware of. But that's minimal, so after hearing more about the inner workings, I'm feeling a lot more comfy about it.

Good job staying away from MFC. Portability is a definite plus. And it never hurts to stay away from MS (which is ironic for me to say since I'm a lowly .NET programmer...) But on the other hand, if you need any fancy Windows GUIs I can definitely help.

Tough call on how to display the windows. I initially wasn't real fond of the way all the settings are in their own windows. But I think that was just from me being used to Edit. As long as you allow the user to save the window positions/sizes (especially if it's into different files) that would probably be better in the long run. However, for a Monitor type screen like Edit's, there's probably no reason not to just put that all on one screen, or break them out into Basic/Advanced. Hard to say, might be good to get other people's input on that one. However, one MUST for me, is that the logged data can be displayed on a map like in Edit. For example, I constantly look at my average AFRs overlayed onto the fuel map grid so that I can quickly tell exactly where I need to go to change fuel. The other function I frequently use is the line graph, such as AFR vs Time and RPM, for example. Those are the two I'm looking at while I'm in the car. The rest I can do at home in a spreadsheet with just raw data files....

Too bad about the logging limitations. I knew the baud rate would be a limitation, but I thought maybe you could get better sample rates if you had a way of only selecting the exact data you wanted to log. Edit forces you to log all of Basic, or all of Advanced, etc, so there's a lot of data saved that I don't even care about. Wasn't sure if that's how the PFC forces you to pull it, or if that was just how Edit was written. However, I also run Edit on a slow laptop, so I don't even get the full download rate, as seen by the commander being able to still update itself while I'm logging. I'm betting your code will run more efficiently on slower machines....

One last thing...hoping you're planning on being able to log from the AN inputs on the datalogit box??? Obviously, logging from my wideband is very important.

Again, I'm EXTREMELY impressed!

cewrx7r1

iTrader: (2)

Andre,

I just finished checking the 43 version against my FC_Edit.
All data matched for the shown maps that are also on the FC_Edit.


Have you come across any code that affects fuel based on TPS setting vs time or just time? https://www.rx7club.com/power-fc-forum-47/anyone-know-about-pfc-entry-434278/

TailHappy

Just finished verifying everything. Things I noticed:
* Injection vs Air Temp (hot) also has a boost associated with it in FC Edit
* Injections vs TPS voltage: TPS voltage is displayed as a percentage instead of voltage (same on others)
* Inj vs Water temp (Cold) was 0.001 off from FC Edit...no biggie, obviously
* Inj vs Water temp should also be tied in with a boost
* Ign vs TPS is all 0's in Tune and all 1's in Edit

And just to be sure, I also did a full read with FC Edit before and after doing a read with FC Tune, and everything was the same.

Hope that helps....

paulr33

Hi FastHatch,

The problem with me downloading my maps is I, probably like many others don't have the cable required to hook up comXYZ to the commander port. If I had of had the cable I would have done some testing with my real map data and compared what I had found but alas I can't cos no cable.

I've had a look as kashima's cable schemantics which covers the cable and parts needed. Do you know if this cable/dongle works with the software you've done. Ive noticed you can choose which cable/dongle box but they are all greyed out on my pc when I launch FC Tune.

Thanks for update, I've been away but I am back now and ready to assit where I can (well with nissan skyline version)

once again awesome work

TailHappy

I also meant to add a couple more things to my post...

1) When you save the dat file in Tune, if you don't type ".dat" it doesn't add the extension
2) Reading the file saved by Tune back into Edit worked perfectly, with no differences displayed using the Compare function from a file saved using Edit. I think that's what you're original question was asking for us to do...

FastHatch

Right, also some other settings have MAP values associated with it were Edit doesn't display them. But i have to admit that i don't understand these values. First, they are not boost, they are absolute pressure. Second, i know they do not limit the max. boost, they correct the target idle RPM for various conditions. I have absolutely no idea what these values are good for. Idle air?

FC Edit is faulty here. The values are TPS voltage from 0V to 4.980V. FC Edit interpretes 0V as 0% and 4.980V as 100%. That's wrong. For Hondas it is 0.5V = 0% and 4.5V = 100%. 0V and 5V is used to detect a bad circuit. I know the Mazda ECU does the same.


FC Tune rounds and does not cut off the values. But i check it again. But honestly, who cares about 0.001?


Again, FC Edit is faulty here. They had no idea how to interpret the values so they used the same as for injection. Honestly, what shoud do a value of 1.245 do to the ignition? You can either retard or advance the ignition.


Thanks for testing.

TailHappy

I don't think anybody else does either. I'm not aware of anyone even messing with these values...

No problem, let me know if there's anything else I can do to help!

FastHatch

I'll release a version that supports monitoring/logging in the next days, would be great if you could test it then. Also if someone wants to paint an icon (16x15 pixel, 16 colors) for ignition split i would appreciate it.

I hope you feel a little bit more confident now to use the software.
I'm also using a linter (PC lint) to check the source code for potential failures. And every structure and function is completly documented.

Nzo

My sad attempt at ign split. 16x15 is a little constraining

TailHappy

Well I personally like the icon. Pretty clever.

I'll be glad to test the logging as soon as you release the next version.

And yes, I DEFINITELY feel more confident using the software. You've definitely proven yourself to be thorough!

FastHatch

After 3 days working almost the whole day and night on FC Tune some features are done now:

- Multiple grids on a view
- Cell merge
- Radio buttons in grid



As you can see above Injectors, Idle Ignition Control and Pressure sensor settings are now done.

http://www.fctune.com/download/FCTune_0_50.exe

The merged cells have some minor drawing "bugs", you can see 1 pixel of the grid lines in the cells and the focus rect is sometimes 1 pixel to small. But that doesn't affect the function of the cells, i get that "fixed" tomorrow.

What i also don't like is if multiple grids are on one view and you click through the grids every grid has a focus rect and you don't see which grid currently has the focus. I'll "fix" that tomorrow.

Please let me know how you like the views and if you can find any bugs or issues.

I can't promise anything but i should get done everything else within 1 week.

fritts

iTrader: (5)

Are the boxes still on schedule for August? Also how much time will it take to get fc tune ready for Windows CE once its complete? Looks great so far. Keep up the good work.

TailHappy

Looks great! One thing I was impressed with was that I noticed in your screenshot that there were commas instead of decimal points. Thought us Americans would just have to deal with that but now I was pleasantly suprised that either you gave us a different version or it pulls from Windows' international settings. Nice.

I like the new windows. Only little bug I noticed in addition to what you mentioned, is that on the pressure sensor window, as you click each radio button, it changes the color of the box. As if it were highlighting that you selected it, but it doesn't set it back to black when you change it again. No biggie, just thought I'd mention it.

Again, nice work. We appreciate it!

FastHatch

Beta testing should start in August.

FastHatch

GetLocaleInfo (LOCALE_USER_DEFAULT, LOCALE_IDIGITS, ...);
GetLocaleInfo (LOCALE_USER_DEFAULT, LOCALE_ILZERO, ...);
GetLocaleInfo (LOCALE_USER_DEFAULT, LOCALE_SGROUPING, ...);
GetLocaleInfo (LOCALE_USER_DEFAULT, LOCALE_SDECIMAL, ...);
GetLocaleInfo (LOCALE_USER_DEFAULT, LOCALE_STHOUSAND, ...);
GetLocaleInfo (LOCALE_USER_DEFAULT, LOCALE_INEGNUMBER, ...);

Each cell (column) has a different NUMBERFMT.

The red cell text means that you have changed the setting. If you click undo the text will go back to black. The behavior you describe is not a bug. Maybe it's a bit unclear with radio buttons.

FastHatch

Still needs some work, but FC Tune runs on Windows CE

I may have to use shorter header captions and a smaller font, but you can see the advantage of one window for each setting instead of a massive page now



And FC Tune runs on little endian processors as well as on big endian.

Who wants FC Tune for his cell phone?

mrlaw

Great work !!!
Are you planning to release a MR2 version too?

Let me know how I can help you test that version

FastHatch

FC Tune will support every available PFC model.
Toyota models (including AP Engineering models):

/* Toyota */
414-T001 MR2 SW20 3S-GTE 10/1993 - 10/1999 SW20 415-A002
414-T003 Chaser / Mark II JZX100 1JZ-GTE 09/1996 - 09/2000 JX100 415-A003
414-T006 Altezza SXE10 3S-GE 01/1998 - 04/2001 SXE10
414-T007 Celica ZZT231 2ZZ-GE 09/1999 - ZT231
414-T008 MR-S ZZW30 1ZZ-FE 10/1999 - ZW30
414-T009 Chaser / Mark II (AT) JZX100 1JZ-GTE 09/1996 - 09/2000 J100A
414-T010 Altezza (Turbo) SXE10 3S-GE 10/1998 - SXE10T
414-T011 Chaser / Mark II JZX100 1JZ-GTE 09/1996 - 09/2000 J100M
414-T012 MR-S (Turbo) ZZW30 1ZZ-FE 10/1999 - ZW30T
414-T013 Altezza SXE10 3S-GE 05/2001 - SX10A
414-T014 Altezza (Turbo) SXE10 3S-GE 05/2001 - SX10TA


/* Toyota */
4E14T02Z Celica ST205 3S-GTE 02/1994 - 09/1999
4E14T04Z MR2 SW20 3S-GTE 12/1991 - 09/1993
4E14T01X Starlet EP91 4E-FTE 12/1995 - 07/1999
4E14T01Y Starlet EP82 4E-FTE 12/1989 - 11/1995
4E14T01Z Corolla AE86 4A-GE 05/1983 - 04/1987
4E14T05Z Soarer JZZ30 1JZ-GTE 05/1991 - 08/1996
4E14T03Z Soarer JZZ30 VVT-i 1JZ-GTE 08/1996 -
4E14T05Z Mark II JZX90 1JZ-GTE 10/1992 - 08/1996
4E14T05Y Supra JZA70 1JZ-GTE 08/1990 - 04/1993
4E14T05X Supra JZA80 2JZ-GTE 05/1993 - 08/1997