Development / Support Schedule
Moderator: Matt
Development / Support Schedule
Below is a list of my current development and support schedule. These changes include but are not limited to items in my email TODO box as well as other items listed on Mantis and in my older development spreadsheet. I have enough work to keep me busy for a long time so I'll list here the current priorities
Type 1 + 2 FP updates
- Add AIV control routine for nitrous control for Z32 ECU
- Investigate: Z32 FP firmware performs fueling differently to standard with same tune
Type 3 + 4 FP updates
- Test updates for Type 3 + 4 Feature pack updates for invert flex maps and flex crank enrich
- Add ethanol vs boost control ER34/WC34/S14A/S15
- Investigate removing 8000rpm limiter for certain models
Future ECUs
- Investigate TB48 and 350Z ECUs (hardware and cables aquired, but working on this after the above completed)
Mantis page is here:
http://www.nistune.com/mantis/view_all_bug_page.php
Type 1 + 2 FP updates
- Add AIV control routine for nitrous control for Z32 ECU
- Investigate: Z32 FP firmware performs fueling differently to standard with same tune
Type 3 + 4 FP updates
- Test updates for Type 3 + 4 Feature pack updates for invert flex maps and flex crank enrich
- Add ethanol vs boost control ER34/WC34/S14A/S15
- Investigate removing 8000rpm limiter for certain models
Future ECUs
- Investigate TB48 and 350Z ECUs (hardware and cables aquired, but working on this after the above completed)
Mantis page is here:
http://www.nistune.com/mantis/view_all_bug_page.php
Re: Development / Support Schedule
I dont know if its mistype, or its the same issue, but I emailed you about this issue on s14 sr20det 74F ECUMatt wrote: Type 3 + 4 FP updates
- Investigate B13 SR20DE soft rev limit affecting injection when set certain values
Re: Development / Support Schedule
Yeah it was a mistype from the email. I've not looked into it yet
Re: Development / Support Schedule
Fixed:
Update Type 1 design to support XC9536XL Xilinx chips (3.3V) as 5V versions are out of production
- Critical: No more current design Type 1 boards available. Stocks low. New design not running in ECU
Updates for XC9356XL are completed
Xilinx Memory mapped addresses F700 (default)
Z31_VG30
CR31_RB30
EFK10_MA09ET
F31_VG30ET
HR31_RB20
N12_E15ET
N13_CA16
N13_CA18
R30_FJ20
S12_CA18
S13_CA18
S13_KA24E
Y30_VG30
Z31_RB20
Alternate Xilinx memory mapped addresses E000:
A31_RB20 late (Used with all new 74L00 RB20DET/RB25DET firmware)
D21_KA24
D21_VG30
J30_VG30
Update Type 1 design to support XC9536XL Xilinx chips (3.3V) as 5V versions are out of production
- Critical: No more current design Type 1 boards available. Stocks low. New design not running in ECU
Updates for XC9356XL are completed
Xilinx Memory mapped addresses F700 (default)
Z31_VG30
CR31_RB30
EFK10_MA09ET
F31_VG30ET
HR31_RB20
N12_E15ET
N13_CA16
N13_CA18
R30_FJ20
S12_CA18
S13_CA18
S13_KA24E
Y30_VG30
Z31_RB20
Alternate Xilinx memory mapped addresses E000:
A31_RB20 late (Used with all new 74L00 RB20DET/RB25DET firmware)
D21_KA24
D21_VG30
J30_VG30
- Attachments
-
- Xilinx_Programming_Guide.txt
- (1.64 KiB) Downloaded 451 times
Re: Development / Support Schedule
-Update HCR32 11U1F to include knock sensing
when will this update?
this is the most important update)))
when will this update?
this is the most important update)))
Re: Development / Support Schedule
The whole 6303 code (Type 1+ Type 2) is in mid development for updates
What that means is I can either roll back to the older files to generate this one file. Or proceed forward with finishing and testing the code changes and release it all together.
I prefer to test everything together once the main files have been modified. It is more time effective. As a note this is next on my list anyway
What that means is I can either roll back to the older files to generate this one file. Or proceed forward with finishing and testing the code changes and release it all together.
I prefer to test everything together once the main files have been modified. It is more time effective. As a note this is next on my list anyway
Re: Development / Support Schedule
Added support for Y33_VQ30DET_6P50F_MT_FP. Y33 ECU arrived last week. Has very similar code to ER34 Skyline so has been integrated with latest code base
Found a few issues with latest test code whilst developing this one so will re-run through pre-release Type 3/4 firmware patching
Found a few issues with latest test code whilst developing this one so will re-run through pre-release Type 3/4 firmware patching
Re: Development / Support Schedule
Not many interruptions today so got some firmware updates finally completed and tested
Type 1 + 2 FP updates
- Update HCR32 11U1F to include knock sensing
- Relies on completing updates to existing firmware for Type 1 + 2 for invert flex maps and flex crank enrich
Updates for Type 2 boards are in this thread for now
viewtopic.php?f=12&t=2874&p=23254#p23254
Full feature pack release will be done once all the others are done and tested
Type 1 + 2 FP updates
- Update HCR32 11U1F to include knock sensing
- Relies on completing updates to existing firmware for Type 1 + 2 for invert flex maps and flex crank enrich
Updates for Type 2 boards are in this thread for now
viewtopic.php?f=12&t=2874&p=23254#p23254
Full feature pack release will be done once all the others are done and tested
Re: Development / Support Schedule
Updating the Type 1 S13 CA18DET to add in crank enrich and invert tables. Completed. Found a bug with flex fuel disabled in the patch code (used for Type 2 also). Fixed. Removed ZIP file from forums. Do not use these until an update is posted (or enable Flex fuel tickbox to avoid the problem)
Re: Development / Support Schedule
Finished code development for VL/R31 RB30E/ET today. Moved code across to Z31 VG30.
I've used the diagnostic screw input as normal for flex input. For the launch control since we have no power steering input switch I'm reusing the input port #06 of the HD46510 chip in this ECU
- MAF calibration screw (RB30)
- Fuel temp (VG30)
Fuel temp will need to be hard coded to a set temperature (like 25 degC) so we can use the spare input for the launch control switch. Doing the new coding at the moment for this
I've used the diagnostic screw input as normal for flex input. For the launch control since we have no power steering input switch I'm reusing the input port #06 of the HD46510 chip in this ECU
- MAF calibration screw (RB30)
- Fuel temp (VG30)
Fuel temp will need to be hard coded to a set temperature (like 25 degC) so we can use the spare input for the launch control switch. Doing the new coding at the moment for this
Re: Development / Support Schedule
Hitting technical issues with the Z31 ECU. These are a pain... there is no central loop where subroutines are called from.
Adding code into this is causing the ECU to occasionally fall over (both where the MAF is accessed - which occurs if engine running/not) as well as the LED access routine
More debugging required...
Adding code into this is causing the ECU to occasionally fall over (both where the MAF is accessed - which occurs if engine running/not) as well as the LED access routine
More debugging required...
Re: Development / Support Schedule
Crap its been two weeks since my last update.... still working on the VLT/Z31 ECUs
There has been some MAJOR delays due to technical problems with these ECUs. An peripheral chip is performing a watchdog reset to the processor when new code has been added in. Basically because the hardware is so old and slow that adding new code is taking precious clock cycles away from other processing and causing resets to trip
I'm reworking the current LC + Flex code with Type 1 USB consult code together to optimise clock cycles. Its gradually getting there and I'm hoping I can finish it up this week
There has been some MAJOR delays due to technical problems with these ECUs. An peripheral chip is performing a watchdog reset to the processor when new code has been added in. Basically because the hardware is so old and slow that adding new code is taking precious clock cycles away from other processing and causing resets to trip
I'm reworking the current LC + Flex code with Type 1 USB consult code together to optimise clock cycles. Its gradually getting there and I'm hoping I can finish it up this week
Re: Development / Support Schedule
Good news after a lot of hard work coding and fixing problems... the firmware is finished and bench tested. I will be releasing next week on the forum for beta testing (I have no car to run one of these ECUs from with single coil distributor type)
I ended up doing some changes to the flex code for the 6802 (Z31/VLT/R31)
- Move call for USB code from MAF routine to start of injection calculation routine (only called when engine running)
- Added secondary call to USB code when engine not running in separate loop
- Alternate and store between the main fuel/timing/enrich and flex fuel/timing/enrich between program loop reads to mimimise any increase to total program time
- Check every 20 loops for launch control condition changes
- Alternate LED green/red when launch control active
- Use MAF calibration input for VLT/R31 launch trigger
- Use fuel temp input for Z31 launch trigger
- Also offer speed as input trigger/disable
Just finishing up changes to the Nistune windows software to support these vehicles. I've also improved the detection of when someone loads a standard Nissan file (non-FP) into an ECU which has feature pack loaded
Just need to clean up a few things (being able to force Nistune to load a FP address file for Type 1) before releasing the next update
I ended up doing some changes to the flex code for the 6802 (Z31/VLT/R31)
- Move call for USB code from MAF routine to start of injection calculation routine (only called when engine running)
- Added secondary call to USB code when engine not running in separate loop
- Alternate and store between the main fuel/timing/enrich and flex fuel/timing/enrich between program loop reads to mimimise any increase to total program time
- Check every 20 loops for launch control condition changes
- Alternate LED green/red when launch control active
- Use MAF calibration input for VLT/R31 launch trigger
- Use fuel temp input for Z31 launch trigger
- Also offer speed as input trigger/disable
Just finishing up changes to the Nistune windows software to support these vehicles. I've also improved the detection of when someone loads a standard Nissan file (non-FP) into an ECU which has feature pack loaded
Just need to clean up a few things (being able to force Nistune to load a FP address file for Type 1) before releasing the next update
- Attachments
-
- z31_flex_test.png
- (173.86 KiB) Downloaded 5173 times
Re: Development / Support Schedule
Very exciting updates Matt! I will happily test on my Z31 once available.
Re: Development / Support Schedule
ZIP file. Extract to your Documents\Nistune\Type 1 folder
Test release for
VL_RB30ET_B490F_MT_FP.ENT
Z31_VG30ET_1988_26P0F_MT_SS_FP.ent (can be used in 1986-1989 Z31 ECUs)
Also updated the maps for S13 CA18DET (ENT files are unchanged)
[Attachment removed]
Test release for
VL_RB30ET_B490F_MT_FP.ENT
Z31_VG30ET_1988_26P0F_MT_SS_FP.ent (can be used in 1986-1989 Z31 ECUs)
Also updated the maps for S13 CA18DET (ENT files are unchanged)
[Attachment removed]