IntelliJect EFI Release Notes
Power4Flight 2621 Wasco Street Hood River, OR 97031 +1-541-436-4299

Version 2.5

2.5.1802 (1 August 2026) (2.5 Update 7)

Bug fixes for IntelliJect Firmware

• Added gating logic to maintenance tracking that depends on cylinder head temperature. At least one sensor must be healthy, and the input voltage must be more than 9.5 volts, and no maintenance tracking will be done for the first second after bootup. This handles the case where the input power was not stable and the analog readings (particularly CHT) may be erroneous, leading to false maintenance triggers.

• Changed maintenance logic for “Preheat CHT”. The new logic arms the preheat CHT check with a threshold in which the CHT must be below the trigger level by a configurable threshold while the rpm is zero. This protects against cases where the trigger level is cooler than the intended operating temperature of the engine and after shutdown the maintenance item could falsely trigger as the engine is cooling off. The arming threshold is configurable between 6C and 36C.

• Changed sensor logic so that it is not possible to disable the input voltage sensor.

• Changed input voltage default sensor error limits from 8V to 36V to 10V and 32V.

• Added second try at EEPROM initialization if the first attempt failed to discover the type of EEPROM.

• Improved speed of SD card setup by using maximum size files in the file system.

Bug fixes for IntelliJect Display

• Fixed issue with command “Reset log files”. The new log file should have configuration and version information written into it automatically, but this was not being done since build 1789.

• Improved the logic for not displaying nack messages. Nacks are expected whenever the display software asks for data that is hidden, therefore the software filters those messages to only show important nacks. The old filtering logic could be fooled, resulting in the occasional nack popup that was not interesting.

2.5.1798 (8 May 2026) (2.5 Update 6)

Bug fixes for IntelliJect Firmware

• Fixed bug when using injector outputs as user command-able signals. If the user command to the injector output was 0% or 100% the injector output may not always follow the command, this has been fixed.

• Added feature to save a special flag to the end of factory flash when a save to factory operation is performed. This flag records the desired initial state of the ignition outputs during reboot (non quick-restart); and will be applied by the (newest) bootloader immediately upon startup, before the firmware CRC check is done.

• Improved initial ignition output when the engine is not running such that if the ignitions are configured to have a max dwell the initial output is active (sparking). This prevents inductive ignitions from charging up and then being later sparked by the max dwell logic before the engine starts.

• If the IntelliJect is configured to control an engine heater, and if the engine heater is on, the engine heater will be commanded off if the IntelliJect heater control is disabled in configuration.

New features for IntelliJect Bootloader Firmware

• Added processing of initial ignition output flag stored at the end of factory flash storage. This flag is used to specify the desired initial state of the ignition outputs while the bootloader is processing before launching the main application firmware.

Bug fixes for IntelliJect Display

• When adding a new chart, the chart was initially hidden, requiring the user to select it from the window menu to make it visible. This has been fixed so the new chart will be immediately visible.

• Improved chart axis selection when using the mouse to drag a chart axis.

• Added variable tooltip descriptions to the chart signal selection list.

• Improved crank wheel graphical display to make better use of screen space.

• Fixed error in crank wheel configuration: when changing the position of the sensor or magnet the other dependent variables were computed incorrectly for once-per-rev sensors. This error only existed in the user interface; it does not affect crank wheel operation in the firmware.

New features for IntelliJect Display

• Improved handling of serial port enumeration to speed up application loading. Previously each window which interfaced with serial ports did its own enumeration, but this could be a lengthy process depending on the operating system configuration. Enumeration is now done once up front when the application starts - reducing the amount of time the splash screen is visible before the main application starts.

• Added support for the AMB II exhaust gas analyzer. The exhaust gas window now supports selecting between Horiba and AMB II devices.

• Added charge temperature, average and cylinder specific, to the list of variables that can be charted or displayed on the gauges.

2.5.1794 (12 February 2026) (2.5 Update 5)

Bug fixes for IntelliJect Firmware

• For series hybrid control logic: when controlling commutators that accept an rpm command, the minimum commanded rpm is now equal to the configured crank speed, bypassing the rpm rate limiter when the series hybrid logic is used to start an engine.

New features for IntelliJect Firmware

• Added logic to detect when a series hybrid commutator has spontaneously shut down and shut down the engine in response.

• Added series hybrid configuration parameter: restarts, which indicates the number of times the software is allowed to autonomously restart the series hybrid engine following a spontaneous shutdown.

• Added logic to command the throttle to the configured start value if a crank command is received, and if the IntelliJect is configured to control the throttle, and the throttle is currently higher than the maximum start value.

Bug fixes for IntelliJect Display

• Fixed bug in dyno control for Taurus based dynos - the command to the taurus was not being refreshed once the taurus telemetry matched the desired commands. Now the taurus command is refreshed at 10Hz anytime the taurus dyno is connected.

• Fixed bug in dyno control for Taurus based dynos - anytime the commanded rpm is less than 3000 the rpm rate limiter on the command is bypassed to facilitate starting the engine from the dyno.

• Fixed bug in dyno control for Taurus based dynos - when the dyno stop command is issued the IntelliJect is disabled before the Taurus is disabled to prevent engine run-away.

• Improved the deployment process for macOS builds – releases are now code signed.

• Added profile telemetry to the list of telemetry packets that are masked by the hide telemetry selection in the packet log display.

New features for IntelliJect Display

• Added support for reading the IVT current sensor on the CAN bus as part of the dataset for Taurus based dynos.

• Added option to hide repeat commands in the packet log display.

2.5.1791 (20 January 2026) (2.5 Update 4)

No changes for IntelliJect Firmware

• This release does not include a new firmware version; there are no changes to the firmware. The included firmware is version 2.5.1789.

Bug fixes for IntelliJect Display

• Fixed UI problem that prevented test mode from being commanded. This bug was introduced in build 1789.

• Fixed display problem with list of table enables. Changes were needed to work with the latest Qt layout engine.

• Fixed bug in spin box implementation that did not correctly enforce the minimum value of the spin box.

• Fixed reverse time handling in strip chart. Reverse time occurs when IntelliJect is reset without restarting the display software. Data that were previously in the strip chart buffers is time shifted to negative times to preserve the information while showing accurate time stamps for new data. Previously this process did not work correctly if the strip chart buffer was full and had wrapped around.

• Fixed display layout issue of the unified maintenance configuration and status window.

2.5.1789 (3 December 2025) (2.5 Update 3)

Bug fixes for IntelliJect

• Fixed bug in the request packet (this bug was introduced in version 2.5.1766) that prevented correctly requesting all the sensor configurations including the AEMK type sensor assignments.

• Fixed initialization bug for ignition 3 output. When the ignition 3 output is enabled, if the ignition was configured active low, the ignition 3 signal would operate active high following reboot. This bug was only in effect if the ignition 3 signal was configured to control an ignition system (as opposed to a heartbeat output).

• Fixed lock protection bug on injector configuration. The injector configuration could be changed even when the configuration was locked and a change should be rejected.

• Added 1/4 second delay after bootup before reading SPI EEPROM. This is intended to provide more time for power supplies to stabilize and improve reliability of initial EEPROM read. This delay is skipped during quick restart (a reboot that happens when the engine is running).

• Added a second SPI EEPROM read at startup if an error was detected during the first read.

New features for IntelliJect

• Updated cooling output pwm endpoints so they can be negative. This makes it possible to force the output signal to clip at zero duty cycle before the cooling control logic reaches 0%. This may be useful in cases where a cooling output is used to control a fan and you do not want that fan to start running until the cooling demand is more than 0%.

• Made it possible to set telemetry data rates to zero. When both fast and slow data rates are set to zero the system will bootup in shy mode with no native telemetry outputs. Shy mode can be exited (temporarily forcing the telemetry rates to 1Hz) by sending a request packet.

• Added support for the Taurus from Allocortech as a CAN-connected series hybrid commutator.

• Made it possible to combine the generic commutator interface with other series hybrid interfaces: when a generic commutator packet is received, and generic commutator is not the configured series hybrid interface, the battery current measurement and command data (if present) from the packet are used. This makes it possible to use either an IVT sensor, or a generic commutator, as the source of battery current for series hybrid feedback control.

• Augmented the unlock ICD to include packet bits to specify packets which should not be automatically downloaded when the configuration is unlocked. Older unlock commands will continue to function as before – in which all packets unhidden by the unlock are automatically downloaded.

Bug fixes for IntelliJect Display

• Improved loading configuration files when not connected to an IntelliJect. Previously this could be very slow if loading many tables; now it should be nearly instantaneous.

• Improved tracking of what configuration has been modified when not connected to an IntelliJect.

• Updated the initial request all that occurs on first connection to IntelliJect: any configuration packets which were locally modified prior to the connection are now not requested, so the IntelliJect does not download those packets and wipe out the local modifications.

• Updated the unlock command packet to specify packet bits for any locally modified configuration data, so IntelliJect does not download those packets and wipe out the local modifications following unlock.

• When switching IntelliJect long CAN identifiers off the resulting CAN addresses could be problematic. Added UI logic to catch this case and set the CAN ids to better initial values.

• For the macos build changed the Qt version to 6.10.1 (from 6.8.3) to fix a problem with audio output.

2.5.1779 (6 October 2025) (2.5 Update 2)

New features for IntelliJect

• Added support for the generic series hybrid commutator. The ICD to the generic series hybrid commutator is part of the IntelliJect ICD and SDK. Anyone that can satisfy this ICD can use their commutator to affect a series hybrid system with the IntelliJect.

• Added support for a passive series hybrid commutator using the IVT sensor as the voltage and current measurement.

• Added sensor configuration option: “Fault Latch”. If enabled, a sensor that faults will have the fault “latched” such that if it reads correctly again it will still be considered bad. A latched sensor fault can only be cleared by disabling and reenabling the sensor, clearing the fault latch configuration option, or by rebooting the IntelliJect.

New features for IntelliJect Display

• Exposed support for the series hybrid control system integrated into the IntelliJect. Previously this support was limited to specific customers. Now anyone with the series hybrid feature bit in their IntelliJect can use the series hybrid control laws in the IntelliJect.

• Improved strip charts: added more right click options, including the ability to move or hide the chart legend. Also added a button to stop or start a chart from automatically scrolling in real time.

Bug fixes for IntelliJect Display

• Fixed simulator bug introduced in version 2.5: the simulated IntelliJect serial number was set to 0 which would prevent the simulator for working correctly. If the software detects a simulated IntelliJect of serial number 0 it will rewrite the emulated OTP file to set the serial number to 1.

2.5.1771 (6 August 2025) (2.5 Update 1)

New features for IntelliJect

• Added initial support for the Currawong Engineering CE2129 “IntelliJect Solo”.

• Improved throughput of SD card record transfers. Improvements were made at the SD card driver interface level, but more importantly compression was added as an option for transferred data. Data compression can reduce the transfer time by 2 to 5 times, depending on the amount and content of the data.

New features for IntelliJect Display

• Improved packet log display descriptions: configuration change packets will now describe what fields were changed.

• Fixed minor errors in documentation of the communications ICD.

2.5.1766 (3 July 2025) (2.5 First Release)

New features for IntelliJect

• Removed the scope feature; it was complex and rarely used.

• Added governor rpm limiter logic to specify a low and high limit window. The limiter will only override throttle if the rpm is within the specified window of the limit.

• Removed sensor configuration option to set sensor to defaults. Setting a sensor to defaults should instead be done via the defaults command button.

• Removed communications configuration option to set communications to defaults. Setting to defaults should instead be done via the defaults command button.

• Added logic to prevent engine start (no spark, no fuel, no self-crank) if a major error is asserted when the engine cranks or is commanded to crank. This logic is enabled in the engine configuration.

• Added a new option to any maintenance item: “No Start”. If this option is enabled, and the maintenance item has triggered, the engine will not start (no spark, no fuel, no self-crank) until the maintenance item has been serviced.

• Added a new maintenance trigger item: “Preheat CHT”. This item is trigger-able by the CHT before the engine starts. It is intended to catch cases of preheat system failures which may damage preheat electronics.

• Added support for external temperature input from AEM K-type CAN Module. Support requires the expansion feature code bit. Each of the 8 temperature channels of the AEM module can be assigned a specific temperature role in the IntelliJect or can be simply reported for data-logging.

• Updated millswood PMU protocol to support version 2.0. Older millswood PMUs will continue to work.

• Added communications options to enable dronecan actuator inputs to be used as external sensors 1, 2, 3. This makes it possible to use dronecan to affect table outputs.

• Removed CAN communications option Generator CAN, this feature is now always enabled.

• Added logic to parse IntelliGen CAN auto-discovery frames. This makes it possible for IntelliJect to discover and interoperate with IntelliGen, even if the IntelliGen CAN addressing is non-standard. This is particularly interesting in DroneCAN environments which will conflict with the standard IntelliGen CAN settings.

• Removed SD Card recording option CAN, this feature is now always enabled.

• Changed interpretation of broadcast base ID in the CAN settings. This is now simply treated as a second input base identifier, which can be used for broadcast purposes if desired. The receive processing of the first and second input identifiers has been improved such that each maintains their own packet-in-progress; this makes it possible for two devices on the bus to send multi-frame CAN packets to IntelliJect without coordination and risk of interleaving the frames.

• Added feature to password protect the ability to update firmware. This uses the same access lock protection feature that configuration categories use.

• Added feature to disable injector skipping. If an injector is configured with a non-zero minimum open time, and skipping is disabled, the injector will open for at least the configured minimum time on every output cycle. This configuration option is intended for direct injection situations in which skipping is not a viable injector control strategy.

• Update digital signals configuration to allow the PWM input signal (typically used for throttle input command) to be configured as an output. Also allowed all digital output signals to be configured as heater control discrete. Previously only the injectors and fuel pump output could be configured as a heater control discrete.

• Added logic to run the CAN interface in packet-over-CAN mode when an SD card transfer is taking place over the CAN bus. This eliminates the possibility of a telemetry CAN frame interleaving between large SD transfer packets, corrupting the packet.

New features for IntelliJect Display

• Moved logic used by IntelliJect Display to assign temperature values to temperatures roles from the user interface to the SDK. This makes it possible for users of the SDK to utilize the same logic, which matches the logic inside the IntelliJect firmware.

• Added fuel pressure critical alarm which can shutdown the engine if the fuel pressure falls below a critical threshold.

• Unified the maintenance configuration and maintenance display windows. The maintenance display window has been removed, and all maintenance related user interfaces are now in the maintenance configuration window.

• Unified the table visualization and table configuration windows. The visualization window has been removed, and the table configuration window has a new tab (alongside cells, rows, and cols) to display the 3D surface of the table.

• Added display of the operating point and operating point history (i.e. the trail) on the 3D table surface and the 2D rows and columns table plots. This uses the same logic as the operating point trail on the cells view.

• Added graphical manipulation to the 3D table surface: you can left-drag points up or down to change the cell value. You can also left-drag whole rows or columns to change all the cell values of the row or column.

• Added the ability to left-click to select points or rows or columns on the 3D table surface. Once selected it is possible to invoke the right-click context menu (the same menu that is available from the cells view) to manipulate the selected points.

• Removed the dual table limitation: previously when showing two tables side by side you were not allowed to show the same table. Now you can, which makes it easy to simultaneously see multiple views of the same table.

• The display now remembers the active view of a table; previously the display always started with the cells view.

• Added menu driven interface for customizing the theme, background color, and text color of the display. The customization is stored by project allowing projects with different appearances.

• Changed automatic resend logic: if the user attempts to send a configuration change packet, and it was not acknowledged by IntelliJect, the display software would re-request the packet from IntelliJect to make sure the display was up to date. Now, if the packet was a configuration change, the display software will re-send the packet. The re-send process leverages the existing implementation used for configuration file upload. This makes configuration changes with imperfect communications more tractable.

• Added resend logic to the firmware flash programmer. This makes it possible (though not necessarily recommended) to do a firmware update over an imperfect connection that might drop packets.

• Added new log variables: Fast ΔT and Slow ΔT which measure the time between fast and slow telemetry cycles respectively.

• Added new testmode command to inject an SD card error.

• Added SD card parsing logic to parse IntelliGen CAN auto-discovery frames, which makes it possible to extract IntelliGen telemetry from an SD log, even if the IntelliGen CAN addressing is non-standard.

• Updated Qt to version 6.8. This resolves a bug in the windows 11 theme; and the workaround has been removed.

• Changed the compiler for Windows from mingw to llvm-mingw (17.0.6).

Version 2.4

2.4.1623 (8 October 2025) (2.4 Update 8)

Bug fixes for IntelliJect Firmware

• Fixed initialization bug for ignition 3 output. When the ignition 3 output is enabled, if the ignition was configured active low, the ignition 3 signal would operate active high following reboot. This bug was only in effect if the ignition 3 signal was configured to control an ignition system (as opposed to a heartbeat output).

2.4.1622 (7 August 2025) (2.4 Update 7)

Bug fixes for IntelliJect Firmware

• Fixed bug in the “CAN All” SD card recording option that prevented short CAN identifier (11-bit) frames from being recorded.

• Added logic to run the CAN interface in packet-over-CAN mode when an SD card transfer is taking place over the CAN bus. This eliminates the possibility of a telemetry CAN frame interleaving between large SD transfer packets, corrupting the packet.

New features for IntelliJect Display

• Added support for IntelliGen CAN auto-discovery frames recorded in an SD card record. This makes it possible for the display to discover the IntelliGen identifiers from the SD record and generate a .gentel file, even if the IntelliGen had non-standard identifiers configured.

2.4.1620 (23 May 2025) (2.4 Update 6)

Bug fixes for IntelliJect Firmware

• Fixed a compatibility issue between newer firmware (since 2.4.1617) that was built with an updated compiler and older bootloader firmware (2.3 and earlier). The compatibility problem would cause newer code to fail to boot following a power cycle after programming the new code. The bug is in the old bootloader firmware; this change adjusts the stack location of the new code to prevent the bug from being excited; allowing new code to be booted correctly by an older bootloader. If this bug is excited the unit cannot be recovered to operational status except by a complex procedure that requires return to P4F.

2.4.1619 (26 March 2025) (2.4 Update 5)

Bug fixes for IntelliJect Firmware

• If IntelliJect was connected to IntelliGen and configured to control the engine heater, and if the heater feedback logic used proportional and/or integral gain, and if the heater command output reached 100% IntelliJect would fail to refresh the switched output command to IntelliGen, causing the switched output timer to elapse and the heating to stop.

Bug fixes for IntelliJect Display

• The 3D surface table visualization had small visual errors due to an interpolation mistake. In addition, the number of triangles used to represent a table with only a few cells was insufficient.

2.4.1618 (8 March 2025) (2.4 Update 4)

No changes for IntelliJect Firmware

• This release does not include a new firmware version; there are no changes to the firmware. The included firmware is version 2.4.1617.

Bug fixes for IntelliJect Display

• Fixed bug in displaying and charting NIDAQ (National Instruments Data Acquisition) variables.

• Changed version comparison logic to look at the version information embedded in the resource firmware file rather than assuming the firmware version will match the application version.

• Improved automatic text highlight for spin boxes when they receive focus.

• Fixed bug on table input automatic text highlight on macos.

• Added the following actions to the serial number changed event: the undo and redo packet buffers are cleared, any send all operation is terminated, and the version comparison performed flag is reset. This makes it possible to keep the IntelliJect Display open while changing IntelliJect hardware without concern of stale data being used.

Bug fixes for IntelliJect Sim

• Fixed bug that prevented the IP connection feature in IntelliJect Sim from working correctly (IntelliJect Sim is the standalone IntelliJect simulator which can use physical CAN and serial buses on the PC).

• Fixed bug that prevented simulated CAN devices (such as the IntelliGen) from interacting correctly with the IntelliJect Sim. This makes it possible to use IntelliJect Sim to test software intended to command features that rely on simulated CAN devices.

2.4.1617 (15 February 2025) (2.4 Update 3)

Bug fixes for IntelliJect

• Changed logic for restore-to-factory command, and for disable-mismatch-check command. Previously these commands required IntelliJect be completely password unlocked, now it can be done in partial unlock mode. This change corrects a logical inconsistency in which it was possible to make limited configuration changes in partial unlock mode, but not possible to restore to the factory settings. Note: partial unlock mode can only happen if a password was set on the IntelliJect configuration, but the password was not used to unlock the configuration.

• Fixed handling of DroneCAN service invocations to prevent problems caused by incorrect service response. This applies to the nodeinfo() and transportstats() services.

• If the DroneCAN actuator identifier (communications configuration) is zero IntelliJect will not pretend to be a DroneCAN acutator: it will not accept the throttle command over DroneCAN and it will not generate the DroneCAN actuator status message. This makes it possible for the IntelliJect to just send ICE telemetry to DroneCAN without also being an actuator.

• Improved handling of communications configuration packet so shy mode can be turned on for the CAN protocols when the communications configuration packet is received over UART and vice versa.

Bug fixes for IntelliJect Display

• Updated SDK to include the files eficompareutil.cpp/hpp and efiprintutil.cpp/hpp. These provide functions for generating and reading human readable text descriptions of IntelliJect packets.

• Fixed display of progress bars when using the Windows 11 theme.

• Added non-modal popup to indicate the end of a “send all” operation, which happens when configuration data are loaded from a file.

2.4.1613 (27 November 2024) (2.4 Update 2)

Bug fixes for IntelliJect

• Fixed bug in cooling control logic which could cause firmware reset. The reset would occur if all cylinder head temperature sources were failed, and if the “failure forward” cooling gain were large enough, and if either of the cooling pwm calibration values were inverted (100% output pulse width smaller than 0% output pulse width). In that case it would be possible to get an underflow in the pwm interpolation triggering a processor reset. This has been fixed by correctly limiting the cooling output.

2.4.1612 (8 November 2024) (2.4 Update 1)

Bug fixes for IntelliJect Display

• Updated average button tooltip to indicate when averaging is not available because no variables have been selected to log.

• Fixed bug with display of “load” table variable.

• Fixed problem with Windows 11 theme and allowed Windows 11 theme to be used.

• Updated to support Dark mode on both Windows 11 and macOS. Dark mode is not supported on Windows 10.

2.4.1609 (3 October 2024) (2.4 First Release)

New features for IntelliJect

• Changed temperature scaling by 2X in telemetry for those temperatures that are configured to be EGT. This allows the EGT readings to go up to 824C. The communications SDK code has been updated to undo the scale change when the telemetry is received.

• Increased the range of the cht warning limits and cooling setpoint. The previous maximum value was 255C, the warning limits can now be set as high as 510C.

• Added three new flags to the enable packet: fuel disable 1,2, and 3. If set this turns off the respective fuel injector output. This can be used for clear flood situations where you want to spin the engine and run the ignitions, but not add fuel. Note that oil injection will be performed normally when fuel disable is set.

• Added support for an “expansion data” packet. This packet is sent as an input to IntelliJect to report expanded sensor information that IntelliJect can use to augment its own sensors. The expansion packet is variable in size and can report 4 additional temperatures and 3 knock sensor values.

• Added a new table variable: “knock”, as a percentage from 0 to 100. The knock value is intended to be used in a spark adder table to reduce spark advance when knocking is detected. If ignitions are being run independently then each cylinder can have its own knock value, otherwise the highest knock value is the one that is used.

• Added more options to heater feedback control: heater control now supports full trajectory feedback options like the normal cooling control.

• Added cylinder deactivation feature. This feature shuts down injectors on a periodic basis to disable a cylinder for a fraction of time, deactivating a cylinder on a configurable period.

• Added new flag to the enable packet: “Cylinder Deactivation Disable”. If set this turns off the cylinder deactivation feature.

• Added new table variable: “Cylinder Deactivation Percentage”. This variable can be used in other tables to adjust fueling, spark, throttle limits, etc., to account for changes caused by cylinder deactivation.

• Added a new table to control the fuel pressure command setpoint. If the table is disabled, the command comes from the pump configuration (as before). Enabling the table makes it possible to adjust the fuel pressure command as a function of the engine operating condition, for example increasing the pressure at high load.

New features for IntelliJect Display

• Improved macos version.

• Improved display variable selection.

• Added display of part number to IntelliJect hardware description.

• Changed csv logging such that if no variables are selected the log file is not written.

• Removed “Start” button from the generator configuration page. Commanding the generator to start can only be done from the main toolbar.

• Added improved command line processing. Use command line –help to see the options.

Version 2.3

2.3.1556 (17 September 2024) (2.3 Update 3)

Bug fixes for IntelliJect

• Fixed bug with enforcement of minimum injector opening time: The injector 1 minimum opening time was used for all three injectors instead of the injector specific minimum opening time.

Bug fixes for IntelliJect Display

• Fixed issue with negative timestamps on the stripchart.

2.3.1555 (7 June 2024) (2.3 Update 2)

Bug fixes for IntelliJect Display

• Fixed problem with parsing SD card data which prevented the writing of the sd_x.efitel record files. This bug was introduced in version 2.2.1539.

2.3.1554 (5 June 2024) (2.3 Update 1)

Bug fixes for IntelliJect

• Added logic to trigger SD card writes if an oil prime, fuel prime, or engine start command is received. This is in addition to the logic that starts writing when the engine starts spinning.

• Reverted logic that removed backward compatibility support for very old throttle configuration. This fixes issues that could occur when upgrading from version 1.9 configurations to 2.3.

• Added check on “max ignition dwell” from the engine configuration. Firmware will now force this value to be at least 50% greater than the maximum dwell specified in the ignition dwell table, if that table is enabled.

Bug fixes for IntelliJect Display

• Corrected default chart configuration: the throttle variable was “throttle out” instead of “throttle pos”.

• When building a throttle curve the user is always asked if they want to open the curve builder even if the input data are not sufficient.

2.3.1553 (31 May 2024) (2.3 First Release)

New features for IntelliJect

• Added support for using dronecan servos for throttle and/or cooling control. The servos can be controlled using the “pwm”, “unitless”, or “position” command types. Conversion from the throttle or cooling percentage to the unitless or position command values is done with new dronecan specific calibration values for each servo.

• Added support for using dronecan actuator status message as a throttle TPS sensor, if “Enable CAN TPS” is set in the throttle configuration. Calibration of the TPS value is done using the same calibration values that are used for the command output.

• Changed the reporting of the dronecan actuator status message from the slow telemetry rate to the fast telemetry rate.

• Increased throttle processing frequency from 50Hz to 100Hz to reduce latency.

• Changed computation of throttle derivative - previously the input throttle to the least squares derivative computation was done using the filtered TPS value. Now it is done using the raw TPS value; this reduces the latency of the throttle derivative.

• Changed the interpretation of CAN setting “No Config”. Previously only command inputs and telemetry outputs were allowed. Now you can request settings using the EFI_PKT_REQUEST packet (if they are not hidden); this makes it possible to discover why it is not possible to alter configuration over the CAN bus once this setting is on.

• Extended the Nack packet to report a new nack cause: “nackCANConfigDisabled” which indicates that the configuration packet was rejected due to the “No Config” option being set in CAN settings.

• Added new temperature warning limit. Previously the temperature warning limits applied equally to coolant temperature and head temperature. Now a new hot limit has been added which is specific to the head temperature. This makes it possible to have a higher limit for cylinder head temperature than for coolant temperature.

• Added support for CE422 fuel pump controller. The fuel pump controller is connected over CAN to IntelliJect. IntelliJect will command the pump on/off and pressure setpoint and can consume the reported pressure from the pump if its own internal pressure sensor is disabled or in error.

• Added more options for controlling oil injection pump: a new table to optionally specify injection pump on time instead of duty cycle. Added oil injector pump frequency as a new table variable.

New features for IntelliJect Display

• Updated default display layout to make the errors windows more visible.

• Improved the process for adding variables to the gauges or variable toolbar.

• Added new default chart: “RPM Control”.

• Added the ability to select which variables are written to the csv log files.

• Removed support for Triplex pump-meter.

Version 2.2

2.2.1540 (7 June 2024) (2.2 Update 5)

Bug fixes for IntelliJect Display

• Fixed problem with parsing SD card data which prevented the writing of the sd_x.efitel record files. This bug was introduced in version 2.2.1539.

• Corrected default chart configuration: the throttle variable was “throttle out” instead of “throttle pos”.

2.2.1539 (28 May 2024) (2.2 Update 4)

Bug fixes for IntelliJect

• Fixed issue when decoding multi-frame dronecan packets. This prevented dronecan throttle actuator commands from being processed correctly if the command was sent as part of a packet that commanded multiple actuators.

Bug fixes for IntelliJect Display

• Fixed issue when generating a csv log file during a SD card record transfer: the temperatures written to the log file were always zero. This was a new bug introduced in 2.2 (as a result of the new temperature type assignment) and only affected log files created during an SD card transfer.

• Fixed issue when saving EFI configuration: if the file already existed the display software was not confirming the user wanted to update the data in the existing file.

2.2.1538 (15 May 2024) (2.2 Update 3)

Bug fixes for IntelliJect

• Fixed issue with dronecan ice status message reported by IntelliJect: previously the exhaust gas temperature was always reported as zero; now, if temperature sensor(s) are configured for EGT, the exhaust gas temperatures(s) are reported accordingly.

• Fixed issue that prevented processing the dronecan actuator command message. The actuator command message can now be received and processed, including “pwm”, “unitless”, and “position” command types. The “pwm” command type uses the existing PWM input calibration values to determine the commanded throttle. The unitless command type maps [-1,1] to [0%,100%], and the position command type maps [-π/4, π/4] to [0%, 100%].

• Fixed issue with dronecan actuator status message reported by IntelliJect. IntelliJect was sending the throttle position as a percentage, however this is not correct according to the dronecan standard. The standard requires the actuator position to be sent as an angle in radians. However, it appears most actuators send a unitless value [-1.0,1.0], which IntelliJect now does by mapping 0% to -1.0 and 100% to 1.0.

• Fixed issue with dronecan actuator status message reported by IntelliJect. Previously IntelliJect was sending zero for the speed of the actuator, now the actuator speed is reported using the computed throttle rate. The throttle rate is converted from %/s to unit/s by using 2 units for 100%.

• Added logic to prevent dronecan messages being sent with source ID of zero. Now, if the alternative protocol address is set to zero, the dronecan source ID will be 127.

• Changed the method of sending dronecan frames. Previously the frames could be spaced in time if the CAN communications setting “smooth” was selected. Now the frames are always sent immediately, the “smooth” setting is not applied to dronecan outputs.

• When changing SD card settings to enable “CAN Log All” the update to the CAN receive filters would not be done until the IntelliJect rebooted (if no other CAN settings were changed). This has been fixed so the filters are updated immediately.

• Fixed bug that prevented GPIO commands from being processed when received on the CAN bus and the “No Config” option was enabled in CAN settings.

Bug fixes for IntelliJect Display

• When generating CAN DBC files only the native IntelliJect protocol was generated. Now, if the alternative CAN protocols (Piccolo, Currawong, PE3) are enabled the corresponding DBC files are also generated for those protocols.

• Improved the automatic change to native protocol CAN identifiers when dronecan is enabled.

• Fixed issue that would flag a configuration as modified when the configuration was only requested - which is not a modification. This would cause unnecessary requests to save configuration to a file when closing the display.

• Fixed error display for the error “cht3high”, which was not previously displayed.

2.2.1535 (2 April 2024) (2.2 Update 2)

Bug fixes for IntelliJect

• Fixed issue with canceling crank command when talking to IntelliGen: the crank disable command was not always forwarded on to IntelliGen.

• Fixed issue when disabling IntelliJect while IntelliGen is cranking the engine: the crank disable command is now sent to IntelliGen in this case.

• Fixed bug when “performing” maintenance items - the resulting logbook entry could have a corrupted description.

New features for IntelliJect

• If fuel prime (a new feature in version 2.2) is non-zero IntelliJect will automatically perform the fuel prime operation when a start command is received, or when start is detected. Automatic fuel priming will not be performed again until the engine has done 1000 revolutions.

• Added injector configuration option to automatically run fuel priming when the system is enabled, instead of when the system starts.

• Added injector configuration option to only run fuel priming when manually commanded.

• Added injector configuration option to automatically run oil priming when the system is enabled, instead of when the system starts.

• Changed throttle behavior when loss of throttle PWM input occurs. Previously, if PWM input was lost, and there was no other throttle input, and failsafe was not enabled, the throttle would go to the start position. Now the throttle will remain at the previous valid command. If this behavior is undesired the throttle failsafe should be enabled.

New features for IntelliJect Display

• Added a new document to the help menu “Getting the most from IntelliJect”.

2.2.1534 (27 March 2024) (2.2 Update 1)

Bug fixes for IntelliJect

• Fixed issue with new fuel prime feature when multiple injectors were configured.

• Fixed problem with spark3 enable signal being ignored, and instead spark3 being controlled by spark2 enable. This issue was new in version 2.2.

New features for IntelliJect Display

• Added the ability to export a CAN database file (*.dbc). This file can be used by third party tools to interpret CAN messages. The DBC file documents the telemetry and commands for IntelliJect, using the active CAN communications settings at the time the file is generated.

2.2.1533 (19 March 2024) (2.2 First Release)

New features for IntelliJect

• Added support for the EcoEFI UART communications protocol (version 1.4 and 1.5). This protocol is output only, sending a single packet of telemetry on the UART at the fast telemetry rate.

• Added new configuration for “assignable IO”. Assignable IO allows the IntelliJect to configure input and output signals to perform non-default functions. Some IO were previously assignable on an ad-hoc basis. The new feature is more comprehensive and cohesive and includes inputs as well as outputs.

• Added the ability for a user to command an assignable IO. A new command packet was created that works with the assignable IO configuration. For any IO that has been configured to be “user commandable” the user can send a packet to command the signal to output a periodic pulse. The pulse high time and period are part of the command. The same command packet can be used to simply set the signal high or low.

• Added the ability for an assignable IO to operate an engine heater, engine starter, or oil pump.

• Added the ability to assign specific temperature functions to any of the temperature inputs. Previously it was possible to assign specific temperature functions to specific temperature inputs, now any temperature input can be used for any temperature function. Temperature functions are one of “Coolant”, “CHT”, “Coolant Out”, “MAT”, “Crankcase (CCT)”, “Fuel”, “EGT”, and “Oil”.

• Added the ability to assign TPS and Fuel pressure analog inputs to one of “External Sense 1, 2, or 3”.

• Added the ability to assign any of the digital inputs (IO Enable, PWM in, Crank sense 1, Crank sense 2) to one of “External Sense 1, 2, or 3”.

• Added table variables to include the new temperature options and the external sense 1, 2, 3.

• Changed management of missing configuration data in storage. Previously, if some piece of configuration data was not present in user or factory storage, the default configuration data would be automatically written to user storage upon bootup. This has been changed so the default configuration data is not written. This change will make it easier to recognize hardware failures of the user storage and facilitate changing firmware versions which might have different lists of configuration data.

• Added verification readback to all user storage writes. Previously knowledge of a user storage failure would not be available until a reboot (and subsequent read of storage). Now data written to user storage will be verified by reading back from EEPROM. The user storage error bit will be set if the readback does not match the write.

• Added logic to not write a user storage packet if the exact packet was already present in the user storage backing buffer; this reduces unnecessary writes to user storage. In the case where a packet is not written a read back verification is performed instead.

• Changed the logic associated with “Save to Factory…”. Previously, saving settings to factory storage would clear out the user storage. Now the save to factory operation writes all configuration and status data to factory storage, and then writes all configuration and status data to user storage. This provides for a redundant copy of the configuration data if either source of storage becomes corrupted.

• Removed the storage command “set configuration valid”. This command can no longer be issued; instead, the only way to mark a configuration as valid is to “Save to Factory…” which will compute the configuration hash and store it to both factory and user storage alongside the other data. The configuration hash check can still be disabled if needed following the store to factory operation.

• Added a new error bit: “factory storage error”. This bit will be set anytime a packet read from factory storage has an incorrect CRC, or anytime a factory storage write fails the readback verification. This new error bit is not available in the older 1_x communications protocol. When the 1_x protocol is in use the “user storage error” bit will be set if either a user or factory storage error occurs.

• Added a new data to the configuration hash packet: The “User Changed” flag will be set if a valid configuration change packet is received which causes the configuration hash mismatch error. The user changed flag is recorded in storage along with the configuration hash. The “Stored Data Size” reports the number of bytes in packets in storage.

• Changed the computation method for configuration hash: previously the communications configuration packet was specially formatted for this computation to remove address information. This was done to make different ECUs, whose configurations only differed by the addresses, have the same configuration hash. This logic has been removed, so the entire communications packet is used, just like the other configuration packets. The expectation of similar configurations having similar hashes is removed. This will result in an ECU which upgrades from earlier firmware with a valid hash to now have an invalid hash; however, that was going to happen anyway due to the new parameters added to the communications configuration packet. Upon upgrading to 2.2 the configuration hash should be reset using the “save to factory” command.

• Changed the ICD for the unlock packet. The new packet has the same structure, but the minimum size has been increased. This forces the packet, when traveling over CAN bus, to use the packet-over-CAN schema, which includes sending the entire packet header and CRC. This change prevents a random unlucky CAN frame from unlocking the configuration. Older versions of the display software will not be able to unlock this version of the IntelliJect firmware.

• Added optional proportional gain for engine heater feedback control. If this gain is non-zero, the engine heater will be duty-cycled on and off at a 1 second period according to the gain and the temperature error. The proportional gain can be used stand-alone or combined with the heater hysteresis term. The engine heater on flag in telemetry has been replaced with a duty cycle value.

• Changed the implementation of shy mode; previously any native packet would turn shy mode off, now only the request packet can turn off shy mode. This makes it easier for customers to integrate native protocol commands with alternative protocols.

• Added “Fuel Prime” command and injector configuration variable that specifies the fuel to prime when the command is received. The fuel prime command is part of the enable packet (like the oil prime command). The command will only be obeyed if the IntelliJect is enabled but the engine is not running. When the fuel prime command is active the fuel pump is allowed to run, even if it is configured to not run when there is no rpm.

• Changed currawong ECU protocol implementation - previously Currawong error bits were cleared after every slow telemetry output, but this was incorrect with respect to the CE367 ICD. Now the Currawong error bits are only cleared following a request for error reporting. In addition the global error bit in Currawong fast telemetry is only set once for each fast telemetry output for which a new error is latched.

New features for IntelliJect Display

• Improved strip chart time control for long data files, increasing the time resolution.

• Added preliminary support for the Currawong TouCAN CAN interface on the mac.

• Added logging of the stored and actual configuration hash.

• Fixed issue with the acceptance test report pdf output: the pdf was erroneously including the “save” button in the output.

• Added options to table visualization window to select heat map separately from the 3D surface, and row plot separately from the column plot.

• Added feature to set a single configuration category to defaults.

• Added automatic baud rate detection for auto-discovery in CAN bus. If no CAN frame is received for 5 seconds, and auto discovery is turned on, the CAN device will switch baud rate; cycling through 1M, 500K, 250K, and 125K bits per second.

• Updated Qt to version 6.6.2.

Version 2.1

2.1.1499 (7 March 2024) (2.1 Update 3)

Bug fixes for IntelliJect firmware

• Improved efficiency of user storage when changing configuration; previously updating a configuration packet without changing its size could cause the new packet to be appended in storage, rather than an in-place update. The packet append operation is slightly more expensive than the in-place update.

• Fixed bug in handling of negative injector opening times. These could occur (rarely) in fast transient fueling conditions.

• Fixed bug in handling of error reporting in the Currawong protocol: it was possible that the errors reported were not up to date when the error request packet was processed.

• Fixed bug in handling of crank command in the Currawong protocol, the crank command was not obeyed.

Bug fixes for IntelliJect display

• Fixed logging of second gas analyzer “OK” status.

• Improved auto-pause feature for replay: previously the pause signal was only obeyed when the replay had caught up to the desired time stamp. Now the pause signal will exit the replay loop as soon as a packet is decoded which caused the pause. This improves the time accuracy of the automatic pause.

• Fixed issue with the acceptance test report pdf output: the pdf was erroneously including the “save” button in the output.

2.1.1498 (6 February 2024) (2.1 Update 2)

Bug fixes for IntelliJect firmware

• Fixed computation of specific telemetry variables in the alternative protocols Currawong (serial or CAN) and Piccolo (CAN only). Errors could be introduced in the fuel pressure, volts, and injector duty cycle telemetry data (only in the alternative protocols) if the fast telemetry rate was not a multiple of the slow telemetry rate.

• Fixed recording of errors in SD telemetry for cases where the slow SD telemetry rate was faster than the engine speed (for example, when the engine was stopped). Previously SD errors were cleared following the SD write operation - but would not be reset until the next engine revolution; leading to a case where a persistent error would be recorded intermittently in SD.

New features for IntelliJect firmware

• Added “Device Enumeration” field to the IntelliJect firmware image to work with latest bootloader. Also added reporting of device enumeration to the software information packet. Older firmware will report “Legacy Device” and new firmware will report “IntelliJect Device”.

Bug fixes for IntelliJect display

• Fixed display of charge temperature on the Injectors tab if injectors were configured to operate redundantly or independently. The charge temp displayed did not properly reflect the injector specific charge temperature.

New features for IntelliJect display

• Added support for the “Device Enumeration” concept introduced with the latest bootloader. Device enumeration prevents users from loading firmware that does not match the type of device (for example, installing IntelliGen firmware on IntelliJect).

2.1.1496 (15 December 2023) (2.1 Update 1)

Bug fixes for IntelliJect firmware

• Fixed computation of fuel pump duty cycle in SD card telemetry records. Previously the value stored in the SD card was always 0. This bug only affected SD card telemetry, not live telemetry.

• Improved error reporting in the “Piccolo CAN” interface. Previously the “fuelperror” would only be set if the fuel pressure sensor was faulty. Now it will also be set if the fuel pressure is low or high.

• Improved logic to suppress sticky crank sense errors: nuisance crank sense errors commonly occur when stopping the engine since the crankshaft may bounce off compression causing multiple crank sense detections. The new logic prevents these errors from becoming sticky unless the engine has been running above 800 rpm for more than 5 seconds.

Bug fixes for IntelliJect Display

• The automatic pause during replay feature did not work correctly when the reported error was a crank sense error. This has been fixed such that a crank sense error will only pause the replay when it first shows up in telemetry.

• Increased throughput for the TouCAN USB-CAN module if the module reports its firmware as 1.0 or greater. Older TouCAN firmware contained a bug that prevented the device from reaching its full speed potential.

2.1.1495 (7 November 2023) (2.1 First Release)

New features for IntelliJect

• Added support for four stroke operation. Previously four-strokes could only be operated using batch-injection and wasted spark. When the four-stroke feature is enabled the second crank sensor is assumed to be a camshaft sensor and the spark and injection will be timed per camshaft revolution rather than per crankshaft revolution. The fuel table still specifies fuel per crankshaft revolution. The injector phase and spark delay tables can now specify angles up to 720 degrees if four stroke rules are enabled.

• Added the ability to compute ignition advances using independent temperatures, such that ignition 1 advance is computed using CHT1 and MAT1, and ignition 2 advance is computed using CHT2 and MAT2. This makes it possible to modify the ignition advance in response to temperature on a per-cylinder basis.

• Added a new option to the idle ignition skip feature: you can now specify the number of cycles to skip, from 1 to 8. If the alternate skip option is selected the 2nd and 3rd spark output will be spaced in time to minimize torque fluctuations.

• Added optional feature to stop the engine if a zero-throttle command is received.

• Added new cooling control gain: “Failed sensor gain”. This replaces the feedforward gain for cases where the temperature sensor has failed. The default value of this gain is 2 - so that 50% load will cause 100% cooling output if the temperature sensor has failed. This feature makes it possible to use a lower feedforward gain value for normal feedback without sacrificing cooling in the failed sensor case.

• Renamed the “OAT” sensor to the “Digital Temperature” sensor, to better reflect that this sensor measures temperature in the ECU box, rather than outside air.

• Expanded the alternative protocols “Currawong” and “Piccolo” to include the ability to receive enable commands so that users of those protocols can affect the user enables, crank commands, and oil injection prime commands.

• Used four bits in the FAST2 telemetry message to indicate when the throttle output is at the minimum or maximum value, or when the throttle output is limited high or low due to rpm control or limiting. These telemetry bits are intended to be consumed by flight control systems that may be commanding IntelliJect and need to know when the command is at the limit. These bits are only available in the 2.x telemetry format.

• Increased the resolution of the timers used to generate cooling control PWM signals. Resolution is now 1/3 microsecond (previously it was 1 microsecond). The maximum period for the PWM output is now 21844 microseconds, and the minimum is 20 microseconds (previously 50000 and 100 respectively). This change improves operation with cooling devices that need higher frequency PWM control.

New features for IntelliJect Display

• Split the user’s guide into two documents: a User’s Guide and a Datasheet. The Datasheet contains the mechanical and electrical ICD. Both documents are included in the IntelliJect Display software.

• Changed UI toolkit from Qt 5.12 to Qt 6.5. This improves operation on high resolution displays. IntelliJect Display will no longer run on Windows 7 or 8, Windows 10 is the minimum operating system version.

• Added preliminary support for the Peak CAN interface on the mac. This requires use of a third-party driver from https://www.mac-can.com/.

Version 2.0

2.0.1458 (15 December 2023) (2.0 Update 8)

Bug fixes for IntelliJect firmware

• Fixed computation of fuel pump duty cycle in SD card telemetry records. Previously the value stored in the SD card was always 0. This bug only affected SD card telemetry, not live telemetry.

• Improved error reporting in the “Piccolo CAN” interface. Previously the “fuelperror” would only be set if the fuel pressure sensor was faulty. Now it will also be set if the fuel pressure is low or high.

• Improved logic to suppress sticky crank sense errors: nuisance crank sense errors commonly occur when stopping the engine since the crankshaft may bounce off compression causing multiple crank sense detections. The new logic prevents these errors from becoming sticky unless the engine has been running above 800 rpm for more than 5 seconds.

Bug fixes for IntelliJect Display

• The automatic pause during replay feature did not work correctly when the reported error was a crank sense error. This has been fixed such that a crank sense error will only pause the replay when it first shows up in telemetry.

• Increased throughput for the TouCAN USB-CAN module if the module reports its firmware as 1.0 or greater. Older TouCAN firmware contained a bug that prevented the device from reaching its full speed potential.

2.0.1456 (1 September 2023) (2.0 Update 7)

Bug fixes for IntelliJect firmware

• Changed dronecan namespace to be rooted in “/uavcan” rather than the individual messages used by IntelliJect.

• Fixed bug in dronecan implementation that corrupted the first CAN frame of multi-frame outputs, causing failed CRC for those outputs.

• Fixed bug in dronecan internal combustion engine status message: temperatures were being sent in Celsius, when they should have been in Kelvin.

• Telemetry values which were moved from slow telemetry to fast telemetry in version 2 were using the wrong averaging time interval when the 1.x telemetry protocol was active. These are the fuel pressure, fuel pump duty, 12V voltage and the input volts. This has been fixed so that the correct averaging interval is used when the 1.x telemetry protocol is active.

New features for IntelliJect firmware

• When using the 1.x telemetry protocol there was no support for the “injectorover” flags (used to indicate that an injector output is saturated at 100%), because this feature did not exist in 1.x versions of firmware. These flags have been added to the 1.x telemetry protocol using bits that were previously reserved. This makes it possible to use this feature while still retaining the old 1.x telemetry protocol.

Bug fixes for IntelliJect display

• The translation layer (in the communications SDK) that converts 1.x telemetry to the 2.x format understood by IntelliJect display did not work the same for telemetry arriving in individual packets versus the summary packet. This could lead to subtle differences in the telemetry for a CAN versus Serial connection. The translation layer has been improved such that both methods of data reception use a common translation layer.

• The translation layer has been simplified by removing support for the very oldest APIs. The oldest fully-supported API is now API5, which was first released with firmware 1.5.

2.0.1454 (22 August 2023) (2.0 Update 6)

New features for IntelliJect firmware

• When using the 1.x telemetry protocol there was no support for the “cht2IsCoolantOut” flag, because this feature did not exist in 1.x versions of firmware. This flag has been added to the 1.x telemetry protocol using bits that were previously reserved. This makes it possible to use this feature while still retaining the old 1.x telemetry protocol.

Bug fixes for IntelliJect display

• Fixed bug with the cooling fan control user interface: entering any value in the trajectory gain would cause the gain to be read as zero - leading to loss of automatic fan control. This bug was previously fixed in 1.10, but the fix did not get ported to 2.x until now.

2.0.1453 (9 August 2023) (2.0 Update 5)

Bug fixes for IntelliJect firmware

• Added support for the latest IntelliGen protocol, API3 (upgraded from API1).

• Fixed bug in the conversion of KTY83 temperature sensors, in the case where the sensor gain was not 1.0 (the gain is normally 1.0).

Bug fixes for IntelliJect display

• When version 2 firmware was configured to output the version 1 protocol the display software did not correctly follow the temperature assignment information for the spare temperature signal - causing the display of CHT3 to be incorrect. This change also applies to the communications SDK.

• Improved the macos build of IntelliJect display to correctly include the CAN bus plugins, and to use universal binary format. The version of Qt for the macos build has been updated to 6.5.2 (windows build remains 5.12.12).

2.0.1452 (21 May 2023) (2.0 Update 4)

Bug fixes for IntelliJect display

• When version 2 firmware was configured to output the version 1 protocol the display software did not correctly chart the variables that were part of the fast 2 telemetry packet, including fuel pressure and input voltage. This has been fixed so these variables are correctly displayed and charted if the firmware is configured for the version 1 or version 2 protocol format.

• When version 2 firmware was configured to output the version 1 protocol the throttle curve builder in the display software did not work correctly because of errors in the charting timestamp. This has been fixed.

New features for IntelliJect firmware

• Augmented the Currawong ECU protocol outputs to include a third slow telemetry packet that outputs the second CHT and spare temperature.

2.0.1449 (20 April 2023) (2.0 Update 3)

Bug fixes for IntelliJect firmware

• Added logic to set user storage error bit if a bad packet is found in EEPROM at bootup.

• Fixed bug related to Millswood ID collision mitigation that was preventing the change of table enable configuration over CAN when “Generator CAN” was enabled in the communications configuration. The bug was new in 2.0 and caused by changes to the table packets to support the new design tables.

Bug fixes for IntelliJect simulator

• Changed simulator to use injector opening times to debit the fuel pressure accumulator model instead of calculated fuel flow. This makes it possible to use the simulator to exercise fuel pressure test modes.

New features for IntelliJect

• Added a new table to control the cooling setpoint. If the table is disabled, the setpoint comes from the cooling configuration (as before). Enabling the table makes it possible to adjust the cooling setpoint as a function of the engine operating condition, for example making the engine warmer at light load.

2.0.1447 (2 April 2023) (2.0 Update 2)

Bug fixes for IntelliJect firmware

• Fixed bug in CAN log recording that could cause CAN frames to be recorded to the SD card before the engine was running.

• Fixed a bug in the proportional fuel pump feedback control: when the “rpm enables pump” feature is enabled, and the rpm is zero, the integral term of the feedback control law was not properly initialized, which could lead to fuel pressure overshoot when the engine starts.

New features for IntelliJect firmware

• Increased the maximum amount of time that a test mode test can run: from 511 seconds to 131072 seconds (₃₆.5 hours).

• Added a new test mode option: “Stop on fuel pressure error”. If enabled this option will cause the crank sense, injector, or fuel pump tests to terminate if a fuel pressure error is asserted (pressure too low, too high, or sensor failure).

Bug fixes for IntelliJect display

• When changing cell value for multiple cells at once the table input dialog did not always send the value unless the user explcitily entered it.

2.0.1441 (16 February 2023) (2.0 Update 1)

Bug fixes for IntelliJect firmware

• Removed the telemetry data that was dedicated to USB communications status. This data were never used since USB is not supported for real time communications.

• Improved robustness of thermistor temperature computation when the measured resistance is very low.

New features for IntelliJect firmware

• Added the ability specify the period of the cooling pwm outputs. This feature supersedes the “motor mode”. The period can be set in the range from 0.1 ms to 50 ms; and the default value is 20 ms.

• Added the ability to skip ignition outputs for purposes of improved two-stroke idle stability. Ignition skipping is subject to a throttle and rpm threshold, and can be done in alternating fashion (skip1, skip2), or all at once (skip all, skip none).

• Added a new analog sensor signal, called “Spare Analog”. This signal is the same physical line as the PWM input. When enabled the PWM input is disabled, and instead the spare analog can be used to measure a voltage from 0 to 3.3V. The spare analog signal was added the list of table variables and added to TelemetrySensors2 output packet.

Bug fixes for IntelliJect display

• Corrected timestamp handling of chart comments, for cases where time goes backwards (i.e. when IntelliJect is power-cycled).

• Fixed decoding of sound meter and weather station data.

New features for IntelliJect display

• Added the ability to capture any window to pdf, or to capture the entire IntelliJect display, including all docked and floating windows.

• Updated acceptance test report feature to include new communications options as well as PWM throttle command enable.

• Added preliminary support for the Currawong Engineering TouCAN USB to CAN interface module.

2.0.1436 (12 January 2023) (2.0 first release)

New features for IntelliJect firmware

• Added option to use the spare and CHT2 temperature sensors as coolant sensors. This adjusts the logic for cooling control, heater control, and charge temperature computation.

• Added a motor mode option to the cooling outputs. When motor mode is turned on the PWM period is 1ms rather than 20ms.

• Added new table design and configuration. Tables now have configurable row and column index variables; configurable multiplier and divider variables; and configurable names. The new table design is dramatically more flexible than 1.x tables. See the user manual for more details, including details for upgrading from 1.x.

• Added new user tables whose output can be used as inputs to other tables.

• Changed how table enable/disable is handled. Previously disabled tables always had an output of zero; which meant that multiplier tables must always have 1.0 added to their output. This has been changed so that the output of a disabled table is set programmatically to be the appropriate value (1.0 or 0.0), and multiplier tables do not have 1.0 added to their output.

• Added a new native protocol with significant changes to telemetry output: a second fast telemetry frame which reports fuel pressure, pump duty, input and 12 volts, and throttle output command. Removed the sensors4 slow telemetry frame and re-organized remaining slow telemetry frames. See the communications SDK for example source code for decoding and converting older telemetry outputs. The communications API for this version is 10. Using older (1.x) display software to interpret the new protocol is not recommended. The new protocol is activated by the communications configuration.

• Added preliminary support for the dronecan protocol. If enabled in the communications configuration IntelliJect will output internal combustion engine telemetry according to the dronecan format and will accept dronecan actuator commands for throttle command.

• Added a new table to specify the injector 1 ratio. Previously only the injector 2 and 3 ratios could be set, and the injector 1 ratio was computed by assuming the total must sum to 100%. This logic is still in effect if the injector 1 ratio table is disabled (as it is by default). However, if the injector 1 ratio table is enabled all three injector ratios are specified by their respective tables, without forcing the total to be 100%. This feature makes it easier to add or subtract fuel to a single injector without affecting the others.

New features for IntelliJect display

• Reorganized the communications SDK. Previously only a ‘C’ language version of the SDK was provided, now a ‘C++’ version is also included.

Version 1.11

1.11.1145 (21 March 2023) (1.11 Update 3)

Bug fixes for IntelliJect firmware

• Fixed a bug in the proportional fuel pump feedback control: when the “rpm enables pump” feature is enabled, and the rpm is zero, the integral term of the feedback control law was not properly initialized, which could lead to fuel pressure overshoot when the engine starts.

1.11.1144 (27 February 2023) (1.11 Update 2)

Bug fixes for IntelliJect firmware

• Fixed bug in CAN log recording that could cause CAN frames to be recorded to the SD card before the engine was running.

New features for IntelliJect display

• Added preliminary support for the TouCAN USB to CAN adapter from Currawong Engineering.

• Changed build toolchain from msvc2017 to mingw7.3. This reduces the installer size.

1.11.1143 (20 February 2023) (1.11 Update 1)

Bug fixes for IntelliJect firmware

• Removed the telemetry data that was dedicated to USB communications status. This data were never used since USB is not supported for real time communications.

• Improved robustness of thermistor temperature computation when the measured resistance is very low.

Bug fixes for IntelliJect display

• When locking the display layout the strip charts could still be moved and resized. This has been fixed so stripcharts are locked just like the other windows of the display.

• Fixed handling of backwards time for comments on the strip charts. Backwards time can occur when the ECU is power cycled, which resets the telemetry clock. Regular strip chart data are correctly adjusted for this, but comments were not - which could lead to spurious chart comments.

New features for IntelliJect

• Added the ability to skip ignition outputs for purposes of improved two-stroke idle stability. Ignition skipping is subject to a throttle and rpm threshold, and can be done in alternating fashion (skip1, skip2), or all at once (skip all, skip none).

1.11.1141 (12 January 2023) (1.11 first release)

New features for IntelliJect firmware

• Added the ability to record CAN frames to the SD card. The recording can be done just for frames that IntelliJect is configured to process, or it can be done for all CAN frames. The recording does not include CAN frames that are part of the IntelliJect native protocol (those were already recorded in the SD card). The recording starts and stops along with the normal SD card recording.

• Added a new crank sense configuration parameter to specify the angular position of the sensor (for sense 1 and sense 2). This number is not used for crank sense processing, but it is stored by IntelliJect and used by IntelliJect Display to make it more intuitive to configure the crank sense setup.

• Added table-specific locking configuration. The global table lock is still available; locking for a specific table is the greater of the global table lock and the table specific lock. This feature makes it possible to have some tables hidden from the end user while other tables are editable.

New features for IntelliJect display

• Added the ability to reconstruct a CAN log when parsing an SD card, or when transferring an SD record. This results in a comma delimited text file with one line for each CAN frame.

• Added the ability to reconstruct an IntelliGen replay file from a CAN log. The resulting “.gentel” file can be replayed by the IntelliGen display software.

• Added configuration of the crank sensor position. Also added the display of the magnet (or sync tooth) angle. The latter value is not part of the crank sense configuration - it is locally computed in the display software using the sensor angle and the synchronization angle.

• Added visualization tool for crank sense configuration. This makes it much easier to configure complex crank sensor arrangement correctly. The “Crank Sense Timing” tool has been renamed to “Crank Sense Analysis” and the new visualization tool added as a tab in that window.

• Improved the 3D table visualization tool - it is now much faster, works on all architectures, and includes contours and text labels.

• Added support for a third exhaust gas analyzer.

• Added the ability to see and change all the sensor enable/disable status at the same time in the sensor configuration window.

• Added feature to the replay toolbar: “Auto-pause”. When enabled the auto-pause feature automatically pauses a replay when significant events happen: an alarm is triggered, a new sticky error is processed, a user comment is processed, a crank sense timing packet is processed, or an oscilloscope dataset is processed.

• Added the ability to specify a symbol for a signal on the strip chart and oscilloscope.

• Added two new options to the profile runner: the ability to crank the engine for start, and the ability to automatically take an average data point. These options are specified per-point of the profile, so the user can both shutdown and restart the engine (for thermal cycling) and average data from just the desired parts of the profile. Also changed the profile runner so that it will run even when the engine is stopped.

• Added the option to save the results of a configuration comparison to a text file.

• Added logic to update the communications settings when opening a project.

Version 1.10

1.10.1131 (21 March 2023) (1.10 Update 9)

Bug fixes for IntelliJect firmware

• Fixed a bug in the proportional fuel pump feedback control: when the “rpm enables pump” feature is enabled, and the rpm is zero, the integral term of the feedback control law was not properly initialized, which could lead to fuel pressure overshoot when the engine starts.

Bug fixes for IntelliJect display

• When locking the display layout the strip charts could still be moved and resized. This has been fixed so stripcharts are locked just like the other windows of the display.

• Fixed handling of backwards time for comments on the strip charts. Backwards time can occur when the ECU is power cycled, which resets the telemetry clock. Regular strip chart data are correctly adjusted for this, but comments were not - which could lead to spurious chart comments.

1.10.1130 (9 August 2022) (1.10 Update 8)

Bug fixes for IntelliJect display

• Fixed bug when opening a project. If the open operation was canceled by the user the operation was not correctly canceled: resulting in a new project in an unexpected location.

• Fixed bug with the cooling fan control user interface: entering any value in the trajectory gain would cause the gain to be read as zero - leading to loss of automatic fan control.

1.10.1127 (22 June 2022) (1.10 Update 7)

New features for IntelliJect firmware

• Added support for automatic detection of a new EEPROM chip, the BR25G1M-3. This feature is needed to deal with supply chain issues. Hardware built with the new chip will require this version of firmware (or newer) to work correctly.

• Added an engine configuration option to disable a running engine by only cutting the fuel (as opposed to cutting fuel and spark). This feature allows an engine to stop more gradually.

Bug fixes for IntelliJect display

• Fixed bug in changing the engine wear data. The revs counter and Hobbs timer were incorrectly limited.

1.10.1126 (29 March 2022) (1.10 Update 6)

Bug fixes for IntelliJect firmware

• IntelliJect would erroneously send the lock password when requested via the Request packet. This has been fixed so IntelliJect should never send the lock password.

• A reserved bit in the lock configuration packet has been allocated to indicate that the password should not be changed. This makes it possible to update the lock configuration settings without changing the password.

Bug fixes for IntelliJect display

• When sending a configuration file the lock configuration password will be cleared and the bit set to not change the password. This makes it possible to send a configuration file without changing the lock password, and without causing the IntelliJect to re-lock in the middle of the file send process.

1.10.1125 (16 March 2022) (1.10 Update 5)

Bug fixes for IntelliJect firmware

• When restoring settings from factory storage the logbook information would be lost until the IntelliJect was rebooted. This has been fixed.

• Improved robustness of the driver for the digital barometer.

• Added support for reporting and changing the throttle input PWM limits via the Currawong protocol (CAN or Serial).

Bug fixes for IntelliJect display

• The fuel density setting for the max-meter fuel flow meter was not correctly saved and restored in application settings. This has been fixed.

• Previously it was possible to erroneously change the fields of a logbook entry by double-clicking on the logbook display. This method of editing did not actually change the logbook in the IntelliJect - only on the display; so, it has been disabled. You must use the buttons or right-click context menu to perform a logbook entry edit.

1.10.1124 (3 February 2022) (1.10 Update 4)

Bug fixes for IntelliJect display

• When loading configuration data from a text file (extension “.efitext”) fixed a problem when loading files saved by older versions that used different table names than 1.10.

• When loading configuration data from a text file (extension “.efitext”) fixed a problem when loading files caused by use of a non-standard character in some table names.

• Changed configuration file save to emphasize use of the binary file format (extension “.efi”) instead of the text file format. The binary file format is more stable and consistent across operating systems. The text file format is still available, but will require users to explicitly type the file name with the extension “.efitext”.

• Fixed bug in changing the engine wear data. The hot-time and high-load time values were incorrectly limited to 291 hours in the user interface, rather than the correct limit of 2912 hours.

1.10.1123 (15 January 2022) (1.10 Update 3)

Bug fixes for IntelliJect firmware

• Fixed error in transmission of large packets over CAN when the CAN output buffer does not have enough free space.

New features for IntelliJect firmware

• Added support for automatic detection of main oscillator frequency. This feature is needed to deal with supply chain issues that forced a different choice of frequency. Hardware built with new frequencies will require this version of firmware to work correctly.

• Added the ability to set the delay time and threshold rpm that are used in the rpm controller to determine when the controller can be engaged. Previously these values were fixed at 5 seconds and 1800 RPM respectively.

• Updated IntelliGen protocol support to the latest revision.

Bug fixes for IntelliJect display

• When using the simulator the digital barometer and OAT sensor now work correctly.

New features for IntelliJect display

• Removed the “Check for Updates” menu option and changed the software to check for updates every time it starts.

• Updated the “About” dialog to show both the latest version available as well as any bug fix updates to the current version.

• Added display of the main oscillator frequency in the system window along with the other hardware information.

• Changed installer code signing from a standard to an extended validation certificate.

• Added logic to automatically re-write known configuration data to the telemetry file if the file is reset.

1.10.1120 (11 November 2021) (1.10 Update 2)

Bug fixes for IntelliJect firmware

• Fixed error in CAN auto-discovery outputs for the case where communications settings have packet-over-CAN forced on (this is not the default configuration).

• Fixed receive processing error that could cause a CAN frame to be stranded in the receive buffer until a subsequent frame was received.

Bug fixes for IntelliJect display

• Improved processing of CAN auto-discovery.

1.10.1119 (20 October 2021) (1.10 Update 1)

Bug fixes for IntelliJect firmware

• Fixed error reporting for barometric pressure sensor in the piccolo and currawong alternative protocols: if both sensors are enabled (analog and digital) the barometric sensor error will only be asserted if both sensors have an error.

• Increased amount of time (from 3 to 5 seconds) the digital barometer must be non-functional before an error is asserted - to reduce the chance of spurious error reporting.

Bug fixes for IntelliJect display

• Fixed bug that prevented internal settings of display windows from loading when a project was opened. Previously they would only load when the software started.

• Fixed logging and charting so that the analog and digital barometric pressure sensors can be logged and charted independently. Previously only the active barometric pressure reading could be charted.

• Fixed logging of the volatile and sticky error bit fields. Previously these 64-bit fields were logged to the csv file without regard to the correct ordering of the error bits, now they are logged in the order that matches the communications ICD.

• Previously there was no way to set the file information in configuration except by opening a configuration file. Now the file configuration information can be set explicitly in IntelliJect Display.

• When saving a configuration to a file, if the name of the file does not match the file information in configuration, IntelliJect Display now prompts to update the configuration file information to match the save file name.

• Fixed problem in IntelliJect configuration comparison tool that prevented the comparison data from being displayed.

• Improved usability of configuration comparison tool.

1.10.1118 (3 September 2021) (1.10 first release)

New features for IntelliJect firmware

• Added throttle failsafe option. If enabled, and if throttle input commands are lost, the throttle will go to a programmable failsafe position. If the failsafe position is 0% the IntelliJect will also be disabled.

• Added fuel puddling table. This is an alternative/complementary method of transient fueling.

• Added fuel puddling low pass filter option. The time constant of this filter is specified in the injector configuration in units of crank period.

• Added feature to specify the injector back pressure in a table. Previously the injector back pressure was assumed to be the manifold pressure - but this was only correct for manifold injection designs.

• Added optional injector deficit tracking. If the injector time is greater than the crank period or is negative (which can happen in transient cases), the deficit is accumulated and made up for on subsequent crank events.

• Injector duty cycle is now computed with the trim time included (previously it was not). The injector time value in slow telemetry does not include the trim time (as before).

• Added configurable throttle derivative time constant. Previously the throttle derivative was computed over 0.25 seconds, now the time interval can be controlled.

• Added optional feature for automatic spark advance with altitude. When enabled this feature uses the fuel table to determine a sea level equivalent throttle (or manifold pressure) which is used in the spark table to determine the advance.

• Added cooling control feature: if the CHT sensor has failed the feedforward gain is limited to at least 1.0, such that 100% throttle will yield at least 100% cooling.

• Added support for CAN connection to the IntelliGen starter generator controller from Power4Flight. This interface can support engine starting and preheat.

• Added option to automatically offset the throttle output to account for generator load. This option uses the generator power reported on the CAN bus and the power estimate table to determine how much to offset the throttle. Using this feature will make the engine more tolerant of sudden generator loads appearing at low speeds.

• Improved sensor error handling: if a sensor reading is erroneous the reading must subsequently be good for 1 second before the sensor is trusted. Also changed the application of the low pass filter, so the filter is only applied to the sensor reading, not to the failed sensor value that is used when the sensor is out of range.

New features for IntelliJect display

• Organized the windows menu to make it shorter by moving charts, tools, and devices to their own submenus.

• Improved the user interface for configuring chart signals and made it possible to name charts.

• Added more default charts, there are now five default charts representing power, fuel, injectors, generator, and exhaust gas data. Also added the option to reset a chart to its default design.

• Added menu option to print all visible charts.

• Added Project concept that keeps all recordings within a user selectable project directory. Added tools for creating, opening, copying, and renaming projects.

• Added a list of all the table enables to the table display. This list is normally hidden to save screen space but can be turned on with a button. When visible the list shows the enable checkbox for all the tables and makes it possible to change the enable status without changing the displayed table.

• Adjusted table cell drawing to make it more obvious when a table is not enabled.

• Added the ability to change the visible table from the table visualization window.

New features for IntelliJect simulator (IntelliJect Display and Intelliject Sim)

• Added standard atmosphere model with user control over the altitude. The atmosphere data are used in the engine model, propeller model, cooling model, and sensor models.

Version 1.9

1.9.1097 (21 March 2023) (1.9 update 15)

Bug fixes for IntelliJect firmware

• Fixed a bug in the proportional fuel pump feedback control: when the “rpm enables pump” feature is enabled, and the rpm is zero, the integral term of the feedback control law was not properly initialized, which could lead to fuel pressure overshoot when the engine starts.

1.9.1096 (22 June 2022) (1.9 update 14)

Bug fixes for IntelliJect firmware

• Added support for automatic detection of a new EEPROM chip, the BR25G1M-3. This feature is needed to deal with supply chain issues. Hardware built with the new chip will require this version of firmware (or newer) to work correctly.

• Improved robustness of the driver for the digital barometer.

Bug fixes for IntelliJect display

• Fixed bug in changing the engine wear data. The revs counter and Hobbs timer were incorrectly limited.

1.9.1095 (29 March 2022) (1.9 update 13)

Bug fixes for IntelliJect firmware

• IntelliJect would erroneously send the lock password when requested via the Request packet. This has been fixed so IntelliJect should never send the lock password.

• A reserved bit in the lock configuration packet has been allocated to indicate that the password should not be changed. This makes it possible to update the lock configuration settings without changing the password.

• When restoring settings from factory storage the logbook information would be lost until the IntelliJect was rebooted. This has been fixed.

• Added support for reporting and changing the throttle input PWM limits via the Currawong protocol (CAN or Serial).

Bug fixes for IntelliJect display

• Previously it was possible to erroneously change the fields of a logbook entry by double-clicking on the logbook display. This method of editing did not actually change the logbook in the IntelliJect - only on the display; so, it has been disabled. You must use the buttons or right-click context menu to perform a logbook entry edit.

• When sending a configuration file the lock configuration password will be cleared and the bit set to not change the password. This makes it possible to send a configuration file without changing the lock password, and without causing the IntelliJect to re-lock in the middle of the file send process.

1.9.1094 (21 February 2022) (1.9 update 12)

Bug fixes for IntelliJect firmware

• Fixed configuration load error that could be caused by upgrading to newer firmware and then downgrading to version 1.9. The expanded table list used by the newer firmware could corrupt some tables (namely fuel and spark) when the configuration was read out by older firmware following the downgrade.

Bug fixes for IntelliJect display

• Fixed bug in changing the engine wear data. The hot-time and high-load time values were incorrectly limited to 291 hours in the user interface, rather than the correct limit of 2912 hours.

1.9.1093 (14 January 2022) (1.9 update 11)

Bug fixes for IntelliJect firmware

• Fixed error reporting for barometric pressure sensor in the piccolo and currawong alternative protocols: if both sensors are enabled (analog and digital) the barometric sensor error will only be asserted if both sensors have an error.

• Fixed error in CAN auto-discovery outputs for the case where communications settings have packet-over-CAN forced on (this is not the default configuration).

• Fixed receive processing error that could cause a CAN frame to be stranded in the receive buffer until a subsequent frame was received.

• Increased amount of time (from 3 to 5 seconds) the digital barometer must be non-functional before an error is asserted - to reduce the chance of spurious error reporting.

• Fixed error in transmission of large packets over CAN when the CAN output buffer does not have enough free space.

• When enabling an alternative communications protocol the native protocol outputs are suppressed until a native protocol packet is received. This is called “shy mode”. Previously shy mode was enabled as soon as the communications configuration was changed, which could cause problems when updating the configuration. Now shy mode is only enabled at bootup.

New features for IntelliJect firmware

• Added support for automatic detection of main oscillator frequency. This feature is needed to deal with supply chain issues that forced a different choice of frequency. Hardware built with new frequencies will require this version of firmware (or newer) to work correctly.

Bug fixes for IntelliJect display

• Improved usability of configuration comparison tool.

• Fixed logging of the volatile and sticky error bit fields. Previously these 64-bit fields were logged to the csv file without regard to the correct ordering of the error bits, now they are logged in the order that matches the communications ICD.

• When saving a configuration to a file, if the name of the file does not match the file information in configuration, IntelliJect Display now prompts to update the configuration file information to match the save file name.

• When using the simulator the digital barometer and OAT sensor now work correctly.

New features for IntelliJect display

• Added display of the main oscillator frequency in the system window along with the other hardware information.

• Changed installer code signing from a standard to an extended validation certificate.

• Added logic to automatically re-write known configuration data to the telemetry file if the file is reset.

1.9.1091 (30 August 2021) (1.9 update 10)

Bug fixes for IntelliJect firmware

• Fixed slow SD card data transfer over CAN when the “Smooth CAN” option was enabled. Now when performing the SD card data transfer over CAN the “Smooth CAN” option is ignored until the transfer is complete.

• Improved crank wheel decode logic. Previously an expected tooth gap would require the intra-tooth time be at least 150% of the average tooth time. This has been adjusted to 125% of the average tooth time to accommodate low tooth count wheels in combination with high crankshaft acceleration.

1.9.1090 (28 May 2021) (1.9 update 9)

Bug fixes for IntelliJect firmware

• Fixed problem with dual crank sensors: high frequency crank sense input (i.e. from a crank wheel) to crank sense 1 could cause the second crank sense input to occasionally miss inputs.

• Fixed problem with dual crank sense test mode: previously testmode could only simulate an input to crank sense 1; now test mode can simulate an input to both crank sensors - even if the sensors have dissimilar configuration.

• Fixed telemetry data for crank sense 2 synchronization angle when the crank was running in the reverse direction. This bug only affected telemetry output.

1.9.1088 (23 May 2021) (1.9 update 8)

Bug fixes for IntelliJect firmware

• Fixed injector output error when using multi-tooth crank wheel sensors. The injector trim time and injector minimum opening time were not accounted for when using multi-tooth crank sensors.

• Miss-fire test was not run correctly when using multi-tooth crank wheel sensors.

• Fixed glitch with cowl2 output that could occur when using split cooling and the cowl1 pwm output value was 1 microsecond less than the cowl2 output.

• Updated PWM outputs for cooling 1 and cooling 2 so the first pulse output is at 0% duty cycle. This prevents initial glitches that could occur as the system is booting up.

Bug fixes for IntelliJect display

• Added copyright notice to the firmware file export option.

• Updated wording on profile repeat function to make it clearer how it works.

• Fixed bug that prevented the profile runner from disabling ignition 1.

• Added button(s) to the maintenance view window to clear maintenance records. Without these the only way to clear an erroneous maintenance record was to clear all the data in IntelliJect.

• Improved management of the main window to reduce the chance of it appearing off-screen.

1.9.1086 (2 April 2021) (1.9 update 7)

Bug fixes for IntelliJect display

• Fixed a bug in the feature that converts tables from alpha-n to speed-density and vice versa.

New features for IntelliJect firmware

• If the alternative protocol “Piccolo CAN” is selected, and if the spare temperature sensor is enabled and healthy, and if the spare temperature sensor is not being used as an MAT, CHT, or Oil temperature sensor; IntelliJect will output the 0x0440xxxx CAN message to send the spare temperature as an OAT to the Piccolo at 2Hz.

New features for IntelliJect display

• Added a help menu option to export the firmware file that is embedded within the display software. There is no requirement to export this file, this feature is a convenient means of saving the file for purposes of configuration management.

1.9.1084 (23 March 2021) (1.9 update 6)

Bug fixes for IntelliJect firmware

• When using the thermistor sensor configuration, if the thermistor was shorted or the thermistor constants were zero, a software exception would occur in the processing of the signal, causing the system to reset. This has been fixed.

• Adjusted default setting for 12V sensor low voltage from 11.5 to 11.0 volts, to prevent nuisance low voltage warnings.

Bug fixes for IntelliJect display

• The ctrl-Z and ctrl-Y (undo/redo) shortcuts did not work when a spin-box had the focus. This has been fixed.

1.9.1083 (4 March 2021) (1.9 update 5)

Bug fixes for IntelliJect firmware

• When using the test mode packet to calibrate the cooling servo outputs the initial PWM would be incorrect. This has been corrected so that calibration of the cooling servo outputs initializes at the current cooling servo position.

• When using the test mode packet to simulate running the engine in reverse the test was not obeyed.

New features for IntelliJect firmware

• Added an option to the cooling configuration to always run the cooling control law, even if the engine is not running. Previously when the engine was not running the cooling outputs followed the throttle output, to facilitate testing of the cooling outputs prior to engine start. Now this behavior can be overridden such that the cooling control laws always run.

Bug fixes for IntelliJect display

• The flash programming user interface was simplified. In addition, if the programmer detects that you are downgrading the firmware, or attempting to install test firmware, it will ask for confirmation.

• Fixed bug in the test mode display that did not correctly implement the misfire test for spark outputs 2 and 3.

• Corrected display of tabs at the top of the configuration window so even when the window is compressed the active tab’s title is not elided.

1.9.1082 (2 February 2021) (1.9 update 4)

Bootloader 10

• The bootloader packet has been extended to include both software version data (when going to the bootloader) and hardware revision data (when coming from the bootloader). Added logic to the bootloader to prevent older (pre 1.9) code from being loaded on rev5 (or later) hardware. Attempting to erase or program with older software will cause the bootloader to ignore the command and issue an erase or program nack. All rev5 hardware will ship with bootloader 10.

Bug fixes for IntelliJect firmware

• Updated default fuel pump control settings to better work with the CE370 fuel pump. Also enabled the ‘RPM enables pump’ feature in the default settings.

• Fixed minor glitch that can occur on fuel pump output when ramping up from 0%.

Bug fixes for IntelliJect display

• Added logic to the flash programming UI that works with bootloader 10 to prevent loading older (pre 1.9) code on newer (rev5 or later) hardware. Attempting to do this will cause a warning to be generated and the program operation will not be enabled.

• Added logic to the CAN interface driver and flash programming UI to recognize and handle a stranded bootloader on CAN. A stranded bootloader can occur when older display software attempts to program a rev5 (or later) IntelliJect, which will cause the new bootloader to reject the erase and program commands. The same logic is also useful for handling cases where power is lost during the program operation. Previously such a situation could only be recovered by using the serial interface to talk to the stranded bootloader.

• Fixed scrolling stutter in strip charts when plotting realtime data.

• If the engine stops while the profile runner is controlling it the profile is stopped; making it easier to resume the profile when the engine is restarted.

• Fixed some toolbars to display better when oriented vertically.

New features for IntelliJect display

• Added the option to set the minimum time between entries in the csv log file. Normally the file contains one entry for each fast telemetry packet, but this can be overwhelming for long running tests. Data that are not logged can be recovered by replaying the efitel telemetry file with the minimum logging period set to auto.

• Added the option to display the time information on the strip chart and profile runner chart as simple seconds versus hours:minutes:seconds.

• Added the option to specify the number of times a profile should be repeated. Previously profiles could only be repeated indefinitely. Now the repeat count can be specified as infinite (the default) or a fixed number of cycles. If repeating is on but the repeat count is not infinite the engine will be stopped when the profile cycles are complete.

• Added the option to reset the log files when the profile is started and stopped. If the profile is in repeat mode the log file will be reset for each cycle.

1.9.1077 (24 December 2020) (1.9 update 3)

Bug fixes for IntelliJect firmware

• Updated revision 5 hardware support: crank sense hardware on revision 5 does not have hardware inversion like revision 4 and earlier.

Bug fixes for IntelliJect display

• Added logic to shut down the profile runner if a network client sends an enable, throttle, or rpm command. This mirrors the same logic used when a local user sends a command. Note that a network client cannot interact with (i.e. cannot resume) a profile on the local machine (although the network client can run their own profile).

• Improvements to the distribution of the macOS build of IntelliJect Display. The macOS build is fully functional except: CAN interfaces are not supported, 3D table surface visualization is not supported. The macOS build is now available on www.power4flight.com.

• Added logic to request all settings from the IntelliJect anytime the connection method was changed. Previously the request was only done when the status went from offline to online; but that may be insufficient when (for example) switching from the simulator to a real IntelliJect, or switching between different IntelliJects connected on different interfaces (i.e. CAN and Serial).

• Fixed problem with network client connections. Previously only dotted decimal (like “127.0.0.1”) addresses were allowed, now resolvable names are allowed as well (like “localhost”).

• Fixed right-click mouse bug on charts: previously right click operations could inadvertently leave the chart in drag mode.

1.9.1070 (7 December 2020) (1.9 update 2)

Bug fixes for IntelliJect firmware

• Fixed a bug in the implementation of maximum ignition dwell time for the spark3 output.

• Fixed incorrect packet configuration in SD card recordings. Telemetry packets should be recorded using the special SD card packet format but were instead recorded in the normal format.

• Fixed SD card recording when the engine stops. Previously as soon as the RPM went to zero the recording stopped (unless always record was set). Now recording continues for 20 seconds after the engine stops - preserving key data which may be needed to determine why the engine stopped.

• Fixed SD card configuration recording. The IntelliJect configuration is written to the sd card when a record is first created (typically when the RPM first becomes non-zero). Previously if the engine was stopped, and configuration changes subsequently made, those changes would not be recorded to the card, which could make analysis of the data confusing. Now, if a record has been created, and if a configuration or command change is made, the data will be recorded to the card even if the engine is stopped.

• Fixed SD card dangling data write. SD card data can only be written in blocks of 512 bytes, and the firmware waits until 512 bytes of data are waiting to be written before performing the transfer to the card. However, after the engine is stopped it is possible that some data could be waiting which will never be transferred to the card. Now, if data have been waiting in the transfer buffer for more than 5 seconds the data are flushed to the card (and the remaining bytes of the sector are set to 0xFF).

• Fixed incorrect resistor value in revision 5 temperature sensor support.

Bug fixes for IntelliJect display

• Fixed compile failure in the IntelliJect Comms SDK.

• Ported new CAN automatic discovery feature to the IntelliJect Comms SDK.

• Fixed bug in window menu that would indicate a window was visible even though it was tabbed under other windows.

• Fixed bug in SD card parsing that did not correctly convert the SD card packet to a normal packet before writing to the output file.

• Made replay packet processing more flexible so it can correctly detect both normal and SD card packets during replay. This is needed to make the display software correctly replay SD telemetry files that were parsed with older software.

• Reverted Qt from version 5.15 to 5.12 to fix crash bug in table surface visualization. This reversion also removes the feature to display the CAN bus status.

• Fixed names of table plots, the plot labeled rows was plotting columns and vice versa.

• Improved the feature that allows you to drag a table plot point or line on the converted table graphic (i.e. the conversion of the table from alpha-n to speed-density or vice versa). Now, when dragging the table converted to speed density, the resulting table will use indices that match the original alpha-n table, rather than the indices of the map estimate table.

• Fix for hiding the surface plot (via checkbox on table visualization).

1.9.1064 (18 November 2020) (1.9 update 1)

New features for IntelliJect firmware

• Added CAN auto-discovery output frames. These are designed to make it easier for other users of the CAN bus to determine the correct address information used to talk to IntelliJect. See the communications ICD for more details.

New features for IntelliJect display

• Added logic to take advantage of the new auto-discovery CAN frames. In addition, improved the CAN auto-discovery logic for older firmware which does not output the new frames.

• Changed communications selection dialog to present the option to automatically discover the IntelliJect CAN configuration. The communications dialog also shows a list of all IntelliJects that were discovered on the CAN bus.

Bug fixes for IntelliJect display

• The feature that automatically adjusts communications settings when the IntelliJect communications configuration was changed was not working. This has been fixed so that CAN or serial settings can be changed, and the display software will adjust accordingly to maintain communications.

• Added logic to reset the log file, strip charts, and re-request all settings if the IntelliJect serial number changes. This could occur if, for example, an IntelliJect is disconnected and new one connected without restarting the display software.

1.9.1061 (3 November 2020) (First release of 1.9)

New features for IntelliJect firmware

• Added option to smooth CAN outputs. When enabled the CAN telemetry output frames are spread in time to reduce the buffering requirement for receiving equipment. This option is turned on in the default configuration.

• Added new sensor configuration options for temperature sensors. In addition to supporting thermistors the firmware now lets you specify temperature reference, resistance reference, temperature coefficient of resistance for RTDs, and shape constant for thermistors. The added options make it easier to configure the calibration and increase the choice of sensors that can be used.

• Added support for revision 5 IntelliJect hardware. Revision 5 uses factory configurable pull-up + parallel resistors for the temperature sense circuitry. This makes it possible to use thermistors, expanding the options for temperature sensing. Previous sensor types are still supported by the new hardware. Older IntelliJect revisions with current drivers are still fully supported. Version 1.9 is the oldest firmware that will support revision 5 hardware.

• Added option for redundant injector operation. When enabled this will divert fuel flow from a faulted injector to the next injector that is enabled and not faulted. Injector redundancy only makes sense if the injectors are feeding a common intake manifold.

• Added option to use injector 2 or injector 3 output to operate an oil injection pump. Three new tables were added as well as new injector configuration options to control the amount of oil injection. In addition, the spare temperature sensor can be used to measure oil temperature.

• Added integration of the Millswood PMU (power management unit) connected via CAN bus. The communications configuration option previously called “Enable NWGCU” is now “Enable GCU”; reflecting support for both the Northwest and Millswood units. The GCU telemetry packet now reports the source of GCU data, and if the Millswood is detected, includes key metadata such as PMU temperature, and generating, charging, and cranking status.

• Added start bit to the Enable packet. If the Millswood PMU+starter is detected, and if the IntelliJect is enabled, setting the crankEnable bit in the Enable packet will cause IntelliJect to command the Millswood to crank the engine. The cranking operation can be terminated by clearing the crankEnable bit; note that the cranking operation will automatically stop if the engine starts or the crank timer on the PMU times out.

• Added fuel pump configuration option: the fuel pump rate limit can now be set differently for increasing versus decreasing output. This makes it possible to soft start the pump with a non-zero positive rate limit and have no rate limit for turning the pump off. This configuration is appropriate for positive displacement pumps that are used in bang-bang control mode. The range of the available rate limit has also been increased by a factor of 10 to a maximum of 12750 %/s to allow faster rates.

New features for IntelliJect display

• Improved ability to download latest version from the website. Previously the download operation was delegated to the operating system, now it is handled locally by the application and an option provided to automatically run the installer.

• Added table plots to the table configuration window (as sub-tabs). These plots are the same as the plots in the table visualization window. However, the plots in the table configuration window can be used to modify table values by clicking and dragging on individual points (or right-clicking and dragging to change entire lines).

• Added the ability to interpolate table color information along with table values.

• Changed the order of the row axis variables in the tables and windows that display table data. Previously this data were shown with the smallest value on top; this has been reversed so now the highest value row indices are on top. In addition, the throttle and RPM command bars have also been reordered to show the highest values on top (when oriented vertically).

• Improved crank timing display: added the ability of the display to detect and show missed teeth in the crank timing data; and added option to save the crank timing intervals to a .csv file for analysis.

• Added the ability to clear sticky errors during replay. This is done by reconstructing sticky errors locally in the display during replay.

• Added logic to support backwards time in the strip charts. Backwards time will occur if the IntelliJect resets; in which case the old strip chart data will have its time shifted so the data remain time continuous (this will result in the old data have a negative timestamp).

• Added a vertical bar indicator to the gauges window to display the cooling percentage. If the cooling fan is doing closed loop control this gauge indicates the percentage of cooling fan output; otherwise this gauge indicates the cooling output from IntelliJect.

• Added a light to the status bar of the main window to indicate the CAN bus status from the device that connects the PC to the CAN bus.

• Added a splash screen to the IntelliJect display application.

• Changed icons for the IntelliJect display application and installer. The new icon replaces the P4F logo with the IntelliJect logo (which is the P4F logo with a stylized fuel gauge).

• Changed NIDAQ (National Instruments Data Acquisition) implementation. Previously only one task could be loaded at a time, now all tasks that are defined on the system are loaded and run simultaneously. Any task whose name includes “null” or “donotuse” is skipped.

• Added GCU user interface. This interface reports the source of generator control unit data, as well as key telemetry. The interface also provides a start button that can be used to command the Millswood GCU to crank the engine.

• Added new button to the main toolbar to crank the engine for starting. This button is only visible if a Millswood PMU+starter is detected.

• Added new variables to the log including: new GCU data and oil injection data.

• Changed acceptance test report to show the average WOT (wide open throttle) RPM rather than the peak.

• Added new toolbar which can be used to show data variables. The variables are selectable in the same way that variables on the gauges dashboard are selectable. All such selectable variables will show red labels if IntelliJect indicates there is a problem with that signal.

• Added automatic resumption of profiles following application restart. This is an optional setting that will resume a profile if a profile was running when the application shutdown and if the engine is running when the application restarts. This feature is useful for long tests in which operating system restarts may occur.

• Added feature to periodically reset the log files. From the logging toolbar you can select the size limit for the log file which can be: no limit (the default), 2K lines, 16K lines, 64K lines, 256K lines, 1M lines, 10 minutes, 1 hour, 8 hours, or 24 hours. If the selected limit is exceeded the log files are reset (the same as if you chose “Reset log files” from the file menu). This feature is useful for keeping the log files tractable when doing long running tests.

• Improved logging toolbar; you can now open the log or average file directly from the toolbar by clicking on the “Log” or “Avg” link respectively. IntelliJect Display will tell the operating system to open the file using whatever system application is set for .csv files. The files are already open by IntelliJect Display, so whatever application opens the file can only do so in read-only mode.

• Added notification feature: IntelliJect Display can now send e-mail notifications for selectable events, errors, and alarms.

• Added option to the cooling fan Modbus connection to automatically reconnect the interface. Also limited the rate at which the fan control commands are output to be 1Hz, even if the slow telemetry rate is faster.

• Added ability to show three head temperatures (instead of just two) in the temperature strip on the gauges display. The third head temperature is enabled if the spare temperature is configured as CHT.

• Improved dual cooling fan control to better handle the case for a failed CHT sensor.

• Increased the cooling control setpoint range. It was 60C to 220C, now it is 20C to 260C.

Added IntelliJect Sim

• A new application that embodies the same software as the IntelliJect firmware; compiled for the PC. This is extremely similar to the simulator built into IntelliJect Display, except this software runs as a standalone application. IntelliJect Sim can use IP, CAN, or Serial hardware on the PC for communications; making it easy to test and develop client software for IntelliJect against the simulator. In most cases it will be more convenient to use the simulator built into IntelliJect Display; this simulator is intended as a tool primarily for software developers.

Version 1.8

1.8.947 (13 November 2020)

Bug fixes for IntelliJect firmware

• Fixed IntelliJect reset that could be caused by using the servo test feature.

Bug fixes for IntelliJect display

• The feature that automatically adjusts communications settings when the IntelliJect communications configuration was changed was not working. This has been fixed so that CAN or serial settings can be changed, and the display software will adjust accordingly to maintain communications.

• Fix for table visualization bug that would not show the table surface when the window was first visible.

1.8.946 (2 August 2020)

Bug fixes for IntelliJect firmware

• Added logic to resend the SD card journal packet when the SD card is erased - so the display software correctly shows the erased status.

• Fixed watchdog reset that could occur on system start if the user storage EEPROM was blank (this would only happen when the IJ was booted for the very first time).

• Fixed indexing error that would cause crank sense timing data to be out of order when using the “On Sync Lost” feature. This only affected the diagnostic data, not the actual crank sense.

Bug fixes for IntelliJect display

• Improved handling of serial ports used for cooling fan and gas analyzer devices. Previously the ports were not always selectable when they should be, and not always remembered correctly on application restart.

• Improved handling of dual cooling fans if a CHT sensor was disabled or failed. Previously this would leave one cylinder without active fan control, now both fans will be driven according to the remaining good sensor.

• Increased precision of table values for transient fueling, from 3 decimal places to 4.

• Fixed problem with timestamp handling when elapsed times were greater than 24 hours. This affected the strip charts and profile running.

• Added adjustment to correct indexing error for crank sense timing data coming from old firmware. This only applies when communicating to older (build 943 or earlier) firmware; or replaying data from older firmware.

1.8.943 (15 April 2020)

Bug fixes for IntelliJect firmware

• Fixed the voltage variable used for injector trim table lookups. The correct variable is the voltage of the injector (12V) rail, but the main input voltage was used instead.

Bug fixes for IntelliJect display

• The row, column, and table interpolate buttons were enabled anytime a cell was selected in the table. This has been changed so the buttons are only enabled if enough cells are selected to allow interpolation.

• Fixed error caused when inserting the maximum possible rows or columns in a table.

New features for IntelliJect firmware and display

• The 2D table packet was updated to specify the value of a reserved bit. The packet decode will not succeed unless this bit is clear (as it was previously - the ICD remains compatible). This is in anticipation of version 2.x software which will set this bit to indicate a new (2.x) style table. Checking the bit reduces the chance of miscommunication between 1.x and 2.x versions of the protocol.

1.8.941 (31 March 2020)

Bug fixes for IntelliJect firmware

• Fixed throttle command rate limiter: When changing from RPM control to direct throttle control the throttle rate limiter was not applied correctly on the first throttle command.

• Fixed application of fuel used corrector to the fuel flow telemetry. This corrector was not applied if the output rate of the slow telemetry was faster than the rate at which the fuel flow was computed (practically this could only happen if the engine was not running).

Bug fixes for IntelliJect display

• Fixed replaying a telemetry file that did not have any IntelliJect data but did have data from other devices.

New features for IntelliJect display

• Added telemetry packet forwarding for local devices (like the cooling fan or exhaust gas data) to any display clients connected over network.

1.8.939 (6 December 2019)

New features for IntelliJect firmware

• Added new table: Manifold temperature. This table provides a fuel multiplier which works like the head temperature table but depends on MAT. The charge temperature fuel multiplier now comes from either the manifold temperature table or the charge temperature table, depending on whether the manifold temperature table is enabled or not.

• Added telemetry to specify if spark 1,2,3 and injector 1,2,3 are triggering from crank sense1 or 2 (or none at all).

• Changed logic used to choose between crank sense 1 and 2. Previously each output (spark 1,2,3 and injector 1,2,3) would trigger off the nearest sensor, unless a sensor was in an error state. Now the determination of a sensor error looks at the age of the error and the sensor with the oldest error is used (unless the error is more than one minute in the past). This protects the system from using a sensor that is intermittently healthy.

• Made crank sense 1 equal to crank sense 2: Previously crank sense 1 was always enabled and crank 2 was optionally enabled. Now both sensors have explicit disable configuration options. In addition, you can now specify which crank sensor is preferred if both sensors are healthy. If neither sensor is preferred, and both are healthy, then the old logic of using the nearest sensor is used.

• Change dynamic errors reporting: previously an error would be cleared immediately upon resolution of the erroneous condition. Now the error is not cleared until after the slow telemetry output cycle. This guarantees that any error will appear at least once in the dynamic errors telemetry packet; even if the error sets and clears faster than the telemetry update rate.

• Removed support for the old engine configuration packet. This packet was superseded by the new engine configuration packet in version 1.7. If you are upgrading from version 1.6 to 1.8, then load 1.7 first to correctly convert the engine configuration to the new format.

• Removed center sense option from crank sense configuration.

• Added feature to measure and report in slow telemetry the crank shaft angle where crank sense 2 synchronizes. This feature can be used to determine if the crank sensor synchronization angles are set correctly with respect to each other.

• Added fuel multiplier table. This table provides a simple fuel multiplier and is intended to make engine fleet calibration easier by allowing engine specific fueling changes to reside in this table rather than the main fuel table.

• Added new test: user storage. The user storage test will exercise every bit in the user storage EEPROM. If the test passes the contents of the EEPROM will not be changed.

• Added new error source: user storage. Problems reading or writing user storage will set this error bit; and may generate a debug message.

• Added TPS source information to the slow telemetry, this complements the throttle command source in the fast telemetry.

• Added a new TPS source: the manifold pressure (via reverse lookup through the MAP estimate table). This TPS source was previously referred to as “Backup” and was only available if there was no TPS source and if IntelliJect was not driving the throttle. Now this source can be explicitly enabled in the configuration, even if the IntelliJect is driving the throttle. The MAP TPS source is the lowest priority TPS.

• Added a new TPS source: the CAN throttle reported position. The CAN throttle servo is now an option if IntelliJect is not driving the throttle: IntelliJect will not command the position or servo enable status if it is not driving the throttle. The CAN TPS source is lower priority than analog or PWM TPS.

• Added TPS error to the slow telemetry. The TPS error is computed when IntelliJect is driving the throttle and a TPS signal is available, otherwise the TPS error will be zero.

• Added option to run TPS feedback which modifies the throttle output so the measured TPS matches the command. This option is only available if IntelliJect is driving the throttle and a TPS is enabled.

• Added a second maximum throttle table, indexed by the hottest CHT and the density ratio. The actual maximum throttle used is the smaller of this table and the first maximum throttle table.

• Added a second minimum throttle table, indexed by the coldest CHT and the density ratio. The actual minimum throttle used is the larger of this table and the first minimum throttle table.

• Changed throttle rate limiter. Previously the rate limiter was applied to the output throttle; now it is applied to the throttle command input, and separately to the output of the RPM governor in direct control mode. This improves the performance of the RPM limiter.

• Added governor feature to enable a minimum and/or maximum RPM limiter. This feature is only available when the trajectory controller is enabled (i.e. trajectory gain is greater than zero). The limiter works when the governor is not running (i.e. throttle is commanded directly) to prevent the user from commanding a throttle that will cause the RPM to go below the minimum or above the maximum RPM configured in the governor.

• Expanded test mode to support tests for the third injector, spark, and cooling outputs.

• Added new telemetry message to report the third injector and spark operational details.

• Added software support for a third spark output. The third spark is enabled in the engine configuration and takes over the heartbeat output. Software support also includes a new spark3 delay table and a third spark on/off command.

• Added software support for a third injector (hardware support is available in IntelliJect rev3). This includes three new tables (ratio, phase, trim) for the third injector, and a third set of injector configuration options.

• Added injector option to specify how the spare temperature is used, either as a second MAT sensor, or as a third CHT sensor. This option is only used if independent injector operation is enabled. Since the spare temperature can now be a CHT sensor the spare temperature encoding in the sensors telemetry packet was changed to allow a higher range signal (same as the other CHT sensors).

New features for IntelliJect display

• Added automatic table text color; selecting between white or black text based on the background color of the table cell.

• Split the sdkexample.c module into two modules: sdkexample.c and sdkexamplesend.c. This facilitates using more of the SDK code in IntelliJect display.

• Added second configuration window. This is just a clone of the first window and provides a convenient way to view two different configuration categories at the same time (if you have enough display space).

• Added undo/redo capability. This works on a packet basis: any configuration change packet which is sent automatically records a reciprocal undo packet which can be invoked with keyboard short cut or menu option.

• Enabled in-cell editing of values in the tables and throttle curve. In-cell editing is done by typing numbers when a cell is selected and IntelliJect is unlocked. The previous editing mode (double-click or enter to invoke the input dialog) is still available.

• Filtered the text display of RPM on the gauges display using a one second finite impulse filter. This affects only the text display, not the logged or charted data.

• Changed tick marks on the gauge display; major tick marks are now spaced every 1000 rpm and minor ticks are spaced every 250 rpm.

• Added open button to the configuration display (next to send and request) which can be used to open and send just that pages configuration data.

• Added logic to opening configuration files to prompt for confirmation if only the address information is being changed in the communications settings. Users typically want to change other communications settings without changing the addresses.

• Added 3D surface plot and heatmap for table visualization. These replace the previous contour plot visualization.

• Added sticky reset count and serial number to the text log csv file.

• Added the ability to convert a table from alpha-n to speed-density and vice versa. The conversion is only an option for tables that use throttle/load on the row axis and RPM on the column axis; and only if a MAP estimate table is populated.

• Consolidated the About and Docs menu into a single Help menu.

• Added support for dual cooling fans. If both fans are enabled the first cooling fan regulates CHT1 and the second fan regulates CHT2. If only one fan is enabled it regulates the hottest CHT.

• Added support for Optidrive cooling fan controlled over Modbus RTU.

• Added support for National Instruments data acquisition. The NI window can be used to load any task that was configured in the NI “Measurement and Automation Explorer” and acquire any channels specified by that task. NI channels are recorded to the replay file, logged, chartable, and can appear in the gauges dashboard.

• Changed throttle curve builder to add the option to define the desired relationship between input throttle command and RPM.

• Changed profile runner window to make better use of screen space by separating the chart and table with a tabbed layout. Also added right-click “goto” menu option to the chart and table.

• Added option to profile builder to use throttle and RPMs from the fuel table; or to split the throttle and RPMs from the table.

• Changed throttle and RPM command toolbars to use throttle and RPMs from the fuel table. Also added an option to apply the throttle curve in reverse, so the throttle commands yield output throttles rather than input throttles.

• Added table display “trails”. The trail shows the history of the operating point on the table display.

• Added right click feature to strip charts to insert a comment or take average data, using a time which is older than the most recent telemetry. This makes it easy to mark interesting events after they have happened.

• Changed gas analyzer window to make better use of screen space by optionally hiding the left or right analyzer display.

• Updated gas analyzer window to compute AFR if possible. This uses the methodology presented in SAE paper 901599 “AFR and Emissions Calculations for Two-Stroke Cycle Engines”.

Version 1.7

1.7.806 (3 December 2019)

Bug fixes for IntelliJect firmware

• Adjusted temperature computation for MAT, CHT1, CHT2, and Spare temperature. The adjustment accounts for reverse voltage leakage current on the ESD diodes of the temperature inputs. The adjustment is only active if the board major revision number is 3 or less and if the minor revision number is 4 or less (i.e. 2.5 and 3.5 boards are fixed in hardware).

• Adjusted temperature computation for MAT, CHT1, CHT2, and Spare temperature. The adjustment uses the CPU temperature to account for temperature induced variation in the current drive to the sensors.

• Fixed bug that could generate an erroneous crank wheel synchronization error if the engine was stopped and started.

• Changed initial state of the ignition outputs. Previously these were initially set active in anticipation of coil ignitions that need to be in the active state to prevent charging the coil. However, this does not make sense with the hardware inhibit of the ignition output that was added in rev2 hardware. Accordingly, the initial output state of the ignitions is now inactive.

• Improved default main and 12V current sensor calibration.

Bug fixes for IntelliJect display

• Improved crank sense timing chart x-axis resolution.

1.7.805 (7 November 2019)

Bug fixes for IntelliJect firmware

• Fixed bug that could cause a floating point reset if a crank period was measured which was faster than the injector trim time.

• Fixed incorrect quick-restart crank sense configuration.

• Fixed incorrect CHT telemetry in the Piccolo ECU alternative protocol.

• Updated spare temperature telemetry: if spare temperature is being used as an MAT, and the spare temperature sensor has failed, the reported telemetry for the spare temperature will be the other MAT sensor (or the default MAT value if the primary has failed). This change does not affect injector operation, just telemetry.

Bug fixes for IntelliJect display

• Fixed bug that could prevent correctly saving or loading cooling configuration to a file if that file also contained “old engine” configuration data.

1.7.803 (31 October 2019)

Bug fixes for IntelliJect firmware

• Fixed timing error that could produce occasional incorrect analog sensor readings. This would occur when receiving configuration change packets that would trigger an EEEPROM write.

• Improved crank sense decoding: using high tooth count wheels at high speeds in combination with high processor loading could cause problems in wheel decoding. The crank sense interrupt architecture has been changed to eliminate this possibility.

• Fixed bug that would always generate a crank “too late” error the first time the crank wheel synchronized.

• Fixed telemetry of MAT in the case where the spare temperature was configured as a second MAT. Previously this would result in MAT telemetry being reported as the average of the MAT and spare temp sensors. Now the MAT telemetry is just the value of the MAT sensor. This change only affects telemetry, not injector operation.

Bug fixes for IntelliJect display

• Fix for oscilloscope display, which was not correctly setting the time extents on the plot.

• Fix to correctly display the modified status for tables. This bug was introduced in 1.7.800 when dual tables were added.

• Fix to various display issues with the crank wheel timing window.

• Fix to automatically highlighting input text: sometimes the boxes could remain highlighted when they should not be.

• Fix to set the CAN addresses to default when running the software for the first time on a new machine.

• Fix to suppress display of new windows when upgrading from older versions of software.

• Fix to correctly display the crank center sensing option in the engine configuration window.

• Deprecated crank center sensing and added warning message that the feature will be removed in the next version.

• Added warning to close the application after downloading a new version before installing the new version.

New features for IntelliJect display

• Added quick color feature to the table display: the six most recently used colors can be applied to the current table selection with a button.

1.7.800 (13 October 2019)

Bug fixes for IntelliJect display

• Fix to correctly set the revcount when changing engine wear status.

• Fix to prevent changing table cell selection due to keystrokes when the table display has the focus.

New features for IntelliJect display

• Added the option to show two tables at once on the table configuration window.

1.7.799 (18 September 2019)

Bug fixes for IntelliJect firmware

• Fix to prevent test mode from triggering spark or injectors when the system is not enabled.

• Support for Currawong ECU protocol version 7.05 (firmware 6.40) which adds fuel pump rate control.

Bug fixes for IntelliJect display

• Fix to throttle and rpm command bars to automatically highlight the command text when the control receives focus.

• Fix for opening configuration file: if both new engine and cooling configuration are in the file do not initially select old engine configuration.

1.7.798 (13 August 2019)

Bug fixes for IntelliJect firmware

• Fix for test mode: Increased the timing precision of a test to 1 millisecond.

Bug fixes for IntelliJect display

• Fix to saving IntelliJect configuration so old engine configuration (for version 1.6 and earlier) can be saved alongside the new engine configuration.

• Updated the CAN database spreadsheet to be consistent with API 7 (firmware 1.7).

• Fix for test mode: previously using the spark skip test would prevent other tests from working.

1.7.797 (1 August 2019)

Bug fixes for IntelliJect firmware

• Fix for receiving fuel pump configuration from the Currawong alternative protocol. The fuel pump bang-bang limit was not set correctly.

Bug fixes for IntelliJect display

• Fix for sending engine wear data by loading a configuration file.

• Fix to include spare temperature sensor data in the oscilloscope display.

• Fixed storing automatic CAN IDs: when sending communication configuration changes the display software updates its connection settings to follow, and could forget the connection settings were using automatic IDs.

New features for IntelliJect display

• Added the ability to check for newer versions of software from the Power4Flight website.

1.7.796 (19 July 2019)

Bug fixes for IntelliJect firmware

• Fix to prevent user from simultaneously configuring throttle position sense and throttle command on the same input.

Bug fixes for IntelliJect display

• Fix for sending old engine configuration data (from .efi files saved from earlier versions).

1.7.795 (9 July 2019)

New features for IntelliJect firmware

• Added heartbeat signal, which is a 1 ms output that is triggered on every crank synchronization. The IO signal is only available on rev 3 hardware.

• Changed how the parameter mismatch detection is applied. Previously the mismatch check was only performed when IntelliJect booted up. Now the mismatch check is also performed anytime the configuration is changed.

• Added new transient fuel table which only applies when the throttle rate is positive. The old transient fuel table functionality is changed so it only applies when the throttle rate is negative.

• Added factory trim option for the temperature sensor current drivers. As part of this the default temperature current setting was changed from 1.144 mA to 1.16 mA to better match production hardware. This will slightly decrease the temperature reported from KTY8x and RTD sensors.

• Added platinum RTD option to the sensor configuration for the temperature sensors. This is similar to the KTY8x options, and specifies that IntelliJect should use built-in conversion functions to translate the analog voltage to temperature.

• Added misfire option to test mode. This can be used to force IntelliJect to skip 1, 2, or 3 consecutive spark outputs; allowing you to test how the system handles a misfire.

• Added option for independent injector operation. This option changes the computation of the charge temp and head temp fuel multipliers. Normally these multipliers are the same for both injectors, but if the injectors are operating independently injector 1 will use CHT1 and MAT to determine its multipliers and injector 2 will use CHT2 and spare temperature. The second set of fuel multipliers are now reported in previously unused space inside the sensors4 telemetry packet.

• Updated default RPM controller gains. The new defaults are less aggressive.

• Removed coil ignition fault option. This feature was not used by anyone, and the fault detection will be unavailable in rev 3 hardware.

• Added options for SD card recording: Previously an SD card record would be started each time the system booted up. Now a record will only be started if the engine runs, unless the “always record” option is enabled. Also added the option to disable SD recording.

• Added the ability to specify SD card recording rates separately from telemetry rates.

• Removed the option to generate telemetry crank synchronously. This feature was rarely used and not worth the complication.

• Added option to receive telemetry from a generator control unit (GCU) on the CAN bus, in the format specified by the Northwest UAV GCU. This is the fourth alternative protocol, which can be combined with the other protocols. Reception of GCU telemetry triggers transmission (and sd recording) of a new native slow telemetry packet that sends the GCU data to the user.

• Added option to output CAN telemetry in the format specified by the Performance Electronics PE3 ECU. This is the third alternative protocol (in addition to the Currawong and Piccolo alternative protocols). The PE3 protocol is output only, and it can be combined with the Piccolo ECU protocol (but not the Currawong ECU protocol).

• Deprecated the load variable in the fast telemetry packet. This variable is still present in version 1.7, but it should not be used by client software, preferring instead to compute load from manifold and barometric pressure in the sensors packet. Later versions of firmware will use this field in the packet for new data.

• Added feature to retrieve a record of information from the SD card over a communications interface (CAN, UART, USB), rather than removing the card from IntelliJect.

• Improved the estimate of the rate of change of throttle used for transient fueling.

• Improved the estimate of the rate of change of RPM used for RPM control.

• Added expanded feedback control options for the cooling output. Previously cooling output was controlled with simple proportional-integral feedback. Now you can enable a trajectory controller, which can do a better job of intercepting a target temperature without overshoot.

• Added support for a second cowl flap output. The current IntelliJect hardware (rev 2 and earlier) only has one cowl flap PWM output, in which case the second output is only available for cowl flaps driven by CAN servo. Rev 3 IntelliJect hardware adds a second cowl flap output on PWM.

• Added option to split the cooling output logic. When this option is enabled, and both CHT sensors are healthy, CHT1 is used to control the first cooling output; and CHT2 is used to control the second cooling output.

• Added software support for spare temperature sensor. This sensor replaces the never used humidity sensor. The spare temperature sensor hardware is part of the original IntelliJect design but has not been enabled in software until now.

• Added fuel pump control option to set the pump output to maximum if the fuel pressure sensor is failed. If this option is not selected the pump output is driven by the feedforward gain if the sensor is failed.

• Added fuel pump control option to only enable the pump if the engine speed is non-zero. A configurable priming time is also added to allow the pump limited run time when the engine is not running for priming.

New features for IntelliJect display

• Added intake serial number to the acceptance test report.

• Added example code to the communications standard developers kit.

• Added new variables to stripcharts, csv log files, and the gauges window. The new variables are the GCU telemetry, injector 2 fuel multipliers, engine rotation direction, hobbs time, and error bitfields.

• Added the ability to specify the horizontal and vertical display compactness in the .ini file (“~\Power4Flight\IntelliJect Display.ini”). To override the automatic compactness add “CompactHorizontal=x” and/or “CompactVertical=x” where x specifies the pixel spacing between horizontal or vetical elements. These settings in the .ini file are overridden if you provide the command line options “-compacthorizontal” and “-compactvertical”.

• Changed installer to be version aware. This makes it much easier to have multiple versions installed simultaneously. By default the installer will place the application in \ProgramFiles\Power4Flight\IntelliJectX.Y, where X and Y are the major and minor version numbers. The uninstaller, start menu shortcuts, and desktop shortcuts are all now version aware.

• Adjusted error display to aggregate the TPS errors to a single error display, and add the spare temperature sensor error light.

• Added table visualization display feature. This is a new window that provides line and contour plots of any table, as well as table smoothing. The feature is useful for seeing outlier points in the tables.

Version 1.6

1.6.741 (1 August 2019)

Bug fixes for IntelliJect firmware

• Fix for receiving fuel pump configuration from the Currawong alternative protocol. The fuel pump bang-bang limit was not set correctly.

• Fix to prevent user from simultaneously configuring throttle position sense and throttle command on the same input.

Bug fixes for IntelliJect display

• Fix for sending engine wear data by loading a configuration file.

• Increased number of decimal places displayed in the transient and injector ratio tables.

• Fixed storing automatic CAN IDs: when sending communication configuration changes the display software updates its connection settings to follow, and could forget the connection settings were using automatic IDs.

1.6.738 (9 July 2019)

Bug fixes for IntelliJect firmware and display

• Fixed rounding error in packet encoding. Fields that were encoded as 16-bit floating point types (for example table data) were rounding towards zero rather than towards nearest.

1.6.737 (19 June 2019)

Bug fixes for IntelliJect firmware

• Fixed injector trim adjustment to phase: If the injector trim is positive the injector phase should be advanced by the trim time to account for the injector start delay; however, the phase was retarded rather than advanced.

1.6.736 (11 June 2019)

Bug fixes for IntelliJect firmware

• Fixed injector phase tables bug: if the table values crossed 0 degrees the interpolation could produce the wrong result. Values in the phase tables represent crank angles, and any math involving crank angles must be correctly wrapped, including the interpolation function. Before the fix interpolation between 350 and 10 degrees would produce a result near 180 degrees. After the fix the interpolation results in a (correct) value near 0 degrees.

1.6.735 (21 May 2019)

Bug fixes for IntelliJect Display

• Fixed bug with table display of load operating point.

• Fixed bug that in acceptance test report that did not show all important RPM controller settings.

• Fixed bug that would allow you to send settings without first unlocking the configuration.

• Fixed bug that could cause multiple modal dialogs to be open, making the application appear to be locked up, when in fact there was a modal dialog waiting for input that was covered by another dialog.

1.6.733 (25 April 2019)

Bug fixes for IntelliJect firmware

• Injector 2 was using the minimum pulse setting from injector 1.

Bug fixes for IntelliJect Display

• Fixed table display bug that would use the wrong CHT (if more than one CHT was enabled) to draw the operating point of the min throttle, max throttle, and spark retard tables.

• Adjusted the result from the button “Set for 1000 Ohm Platinum RTD”. The drive current used for the gain and offset calculation was changed to 1.16 mA to more closely match the real hardware.

1.6.732 (3 April 2019)

Bug fixes for IntelliJect firmware

• Fixed bug with determining rotation direction using two crank sensors. This would only affect engine operation if the “prevent reverse rotation” or “prevent normal rotation” option was selected.

• Slight improvement to RPM derivative computation.

Bug fixes for IntelliJect Display

• Adjusted max machinery fuel meter counter-timer interface to reject bounce signals. This fixes a flow meter calibration problem.

1.6.729 (7 March 2019)

Bug fixes for IntelliJect firmware

• Fixed bug on derivative computation for the RPM controller. This affects the trajectory controller more than the classical controller.

New features for IntelliJect display

• Changed installer to be version aware. This makes it much easier to have multiple versions installed simultaneously. By default the installer will place the application in \ProgramFiles\Power4Flight\IntelliJectX.Y, where X and Y are the major and minor version numbers. The uninstaller, start menu shortcuts, and desktop shortcuts are all now version aware.

1.6.725 (26 February 2019)

Bug fixes for IntelliJect firmware

• Fixed bug that would prevent automatic sensor offsets from updating if the sensor reading was out of range, even if the out of range reading was due to an incorrect sensor offset.

• Fixed bug that could cause automatic sensor offsets to be read incorrectly from saved parameters. This would result in subtle sensor offset changes which were typically not large enough to notice.

• Fixed bug that could cause delay in reading of CAN servo data or alternative ID CAN data

• Fixed bug that prevented PWM throttle command or PWM TPS from working correctly.

Bug fixes for IntelliJect display

• Fix to remember and recall local communications settings changes that are made automatically when changing the communcations configuration of the IntelliJect. For example if you change the IntelliJect baud rate the display software automatically changes its local interface baud rate. However before this bug fix that change would not be remembered when the display software was restarted.

• Fix to remember and recall averaging period for logging averaging function. The average period can also be changed while average is running.

New features for IntelliJect firmware

• Increased the maximum fuel pump PWM period from 4115 to 16403 microseconds. This allows slower pump PWM frequencies which may be helpful for pumps with larger inductance motors.

• Added new formulation for charge temperature correction. A new parameter has been added to the engine configuration which sets the “reference CHT”; which represents the head temperature when the fuel table is determined. When the engine operates at a CHT equal to the reference value the charge temperature multiplier will be 1.0, no matter what value is in the table. In all other respects the new formulation behaves the same as the old. If the reference CHT is set to 0 (as it will be if you upgrade from older software or read an old configuration file) the old formulation is explicitly used (for backwards compatibility).

• Added support for onboard data logging via SD card. The data logging is based on writing the normal communications traffic (including all telemetry) to the SD card. The SD card is journaled such that each time the EFI resets a new record of data is written to the card. The SD card must be formatted as FAT32 and then setup by the IntelliJect firmware. Once this is done the card can record continuously, overwriting the oldest data as needed. Data is retrieved by removing the SD card and plugging it into a PC, so that IntelliJect display can parse the files.

• Removed support for alternative fuel flow measurement based on external meter or pressure accumulator decay rate.

• Added cowl flap servo calibration to the test mode. This is the same as the current-based hard stop detection used for the throttle servo calibration.

• Augmented the servo calibration feature of test mode to specify the actual position of the servo hard stop, rather than assuming it is 0% or 100%.

• Added the ability to specify the PWM throttle input calibration separately from the output calibration. The PWM throttle input calibration applies to the PWM TPS and PWM throttle command. If the PWM input calibration is 0 the output calibration is used for the input.

• Added non-volatile reset count information to the reset report packet. This is in addition to the previous volatile reset count data. The nonvolatile reset count is incremented and placed in user storage each time IntelliJect boots up.

New features for IntelliJect display

• Added sensor configuration option to specify gain and offset appropriate for 1000Ohm platinum RTD temperature sensor. This is purely a UI feature that populates the gain and offset values appropriately.

• Added more baud rate options for serial port interfaces. Previously the fastest baud rate selection allowed was 230400, now you can also select 460800 or 921600.

• Added parsing tool for SD card data logging which converts the recording into one or more replay files that can be replayed in the display software.

• Added the ability to change the grid of text items in the gauges display. Right clicking on the label allows you to select a variable (from the save variable list as stripcharts). The resulting layout is automatically saved and can be explicitly saved and loaded as a display layout.

• Added the ability to specify user enable, ignition 1 enable, and ignition 2 enable in the profile runner. This makes it possible to implement a “mag check” in the checkout profile.

• Added the ability to highlight a range of cells in a table and interpolate across columns, or interpolate across rows, to change the values of the cells in the center of the selection.

Version 1.5 (12 December 2018)

Bug fixes for IntelliJect firmware

• Disabled the USB interface. The USB stack is not as robust as it needs to be. It will be re-enabled in future firmware versions.

• Fixed mistake in test mode packet that did not correctly handle tests with timeouts longer than 255 seconds.

• Adjusted timing of digital barometer sensor to address occasional failed readings. The digital barometer is a backup sensor to the analog barometer.

• Updated handling of table and sensor configuration packets to properly nack an index that is beyond the acceptable range. Previously if you tried to change or request a table or sensor configuration packet with an invalid index there would be no response. Now such a packet will generate a “Packet not recognized” nack response.

Bug fixes for IntelliJect display

• Fixed infinite loop that could occur when attempting to open a replay file that did not use “efitel-” in the name.

• Fixed a crash that could occur when attempting to build a throttle curve without any data.

• Improved replay functionality, previously replaying files could give inconsistent replay rates if the display had been talking to a live IntelliJect.

• Added request for all settings following firmware programming. Without this the version and settings display could be out of sync following firmware update.

• Fixed table selection behavior. Previously selecting one or more cells in a table and then changing those values would clear the selection when the updated table was returned from IntelliJect. Now the table selection does not change, making it easier to quickly change multiple table values.

• Fixed sending settings when mixing new versions of the display with old versions of the firmware. Now the display will not send packets that it knows older IntelliJect firmware versions will not understand.

New features for IntelliJect (firmware and display):

• Added support for toothed wheel crank angle sensors, which use one or more missing teeth to synchronize the position of the wheel. The crank wheel sensor provides improved timing for events spaced around the engine cycle, since the amount of delay time needed to schedule the event can be significantly reduced. This feature includes support for wheels with a single gap, or wheels with two gaps of different sizes. Wheels with two gaps allow detection of engine rotation. As with the previous once-per-rev sensors there are two available sensors allowing redundant sensing. The dual crank sensors can each have their own wheel design, or one sensor can use a crank wheel sensor while the other uses a once-per-rev sensor. As part of this feature the crank errors that can be reported have changed, and the errors telemetry packet has been modified to accommodate the new crank sensor errors.

• Added crank sense timing report and display. The timing report is generated on request and reports the time interval between successive crank sense events. This is useful for debugging crank wheels, and examining engine speed variation through one or more cycles. The timing report can be triggered manually, continuously, or when a crank synchronization error occurs.

New features for IntelliJect firmware

• Changed cooling output to match throttle if the engine is not running. This makes it much easier to test and calibrate the cooling output.

• Added improved watchdogging. The hardware watchdog is now backed up with a software watchdog which makes it possible to determine where the code has faulted before performing the reset.

• Added maximum throttle for starting. If the engine is not yet running, and the throttle is greater than the maximum starting throttle, an error is reported and crank sense events will not generate spark or injector outputs. The error will become sticky if a crank sense is detected in this state. The maximum throttle for starting is useful both as an operator/engine safety check, but also as a feature to clear a flooded engine by cranking it without fuel injected.

• Added safe mode to deal with bad settings data that could cause system resets. Safe mode is invoked if the system has reset due to errors more than 20 times (between power cycles). If that happens safe mode will be asserted, which prevents the system from loading any settings data, thereby preventing whatever bad setting is causing the error. Once in safe mode the system settings data can be cleared if needed. The only recovery from safe mode is to reset to go back to normal operation mode.

• Added setting to center the active crank sense timing. This option tracks the time when the crank sense becomes active and inactive, using the center time to trigger the crank sense event.

• Added new test mode feature to inject crank sense errors on a running engine, either a skip or an extra tooth. The skip error causes the system to skip the processing of a single active crank event. The skip error injection applies equally well to once-per-rev or crank wheel sensors. For crank wheel sensors you can also insert a tooth, as though an extra tooth were erroneously detected. The errors injections can be performed on either crank sense 1 or crank sense 2.

• Added the ability to specify the synchronizing crank angle for reverse as well normal engine rotation.

• Added engine rotation direction sensing based on timing of dual crank sensors. This feature works even if neither crank sensor is a directional crank wheel. The only requirement is that both sensors are healthy and do not synchronize at the same (or 180 deg apart) crank position.

• Added the ability to prevent spark and injector outputs if the engine is rotating the wrong way.

• Added injector configuration option to specify the edge used for injector phasing. Previously the injector phase always gave the end of the injection event. Now it can be configured to specify the end (default), middle, or start of the injection event. The injector angle in telemetry gives the angle of the specified edge.

• Added new test mode feature for calibrating servo closed and open positions. This only applies to configurations where IntelliJect is driving the throttle servo. The test can only be started when the system is unlocked and disabled. The test drives the servo, monitoring the input current until it exceeds a threshold, then drives the servo back the other way until the current is reduced to 25 mA above the starting current. The resulting PWM is recorded as the closed or open throttle PWM (depending on which test was run).

• Added auto-offset feature for the main and 12V current measurements. This feature estimates the offset of the current measurement when the throttle is between 10% and 90% (i.e. off the stop) and IntelliJect is disabled (so the fuel pump, injectors, and ignition are not consuming current). In this case the expected current is very close to zero, so the auto-offset feature adjusts the sensor offset until the measured current is zero. As with the MAP sensor auto-offset, this feature must be enabled in the sensor configuration.

• Changed 2nd order barometric fuel multiplier table to use density ratio rather than barometric pressure ratio.

• Added a new table for density adjustment to the spark advance. The table value is multiplied against (1.225-density)/1.225 to compute a value that is added to the spark advance. Typically as the air density decreases the spark advance should increase, and this table provides the means to do that.

• Added injector term for fuel volume compensation based on the manifold temperature. The assumption is that the injector is at the same temperature as the manifold, and the fuel will reach the same temperature as it flows through the injector. The volume correction adjusts the injector opening time to compensate for changing fuel density. There is a new injector parameter that defines the fuel volume percentage change for degree C of the manifold temperature. The correction factor is 1.0 when the MAT is 15C.

New features for IntelliJect display

• Added logic to automatically make the display spacing more compact on low resolution screens. Also added two command line options “-compacthorizontal” and “-compactvertical”, which sets the display to compact mode independent of the screen resolution. This is useful for low resolution displays where the windows do not easily fit.

Version 1.4

1.4.607 Update 1 (25 October 2018)

Bug fixes for IntelliJect firmware

• Fixed occasional erroneous RPM reading on the first crank revolution.

• Fixed problem with the digital barometer and OAT that could cause a watchdog reset if the sensor was enabled (by default it is not enabled).

Bug fixes for IntelliJect display

• Fixed drawing problem with the rpm gauge that happened if the gauges window was hidden when the application was started.

• Fixed problem with chart signal selection when opening a display layout file which specified chart signals that were different than currently loaded.

1.4.606 (18 October 2018)

Bug fixes for IntelliJect firmware

• Changed the reporting of injector faults. Injector faults will not assert unless the engine is running, but they will remain asserted as long as the fault is present even if the engine stops. This is because an injector fault cannot be cleared except by performing an injection, and spurious faults could occur during engine setup.

• Fixed bug in computation of temperature from the MS5637 sensor. This is a backup sensor and is not enabled by default.

• Fixed incorrect trigger time in scope data if the scope was triggered after 4294967295 microseconds.

• Fixed error reported if the fuel pressure was low while IntelliJect was disabled. Fuel pressure is expected to be low if IntelliJect is disabled.

• Fixed temporary CAN communications bug that could occur when clearing all settings. This would happen when the settings would change to defaults, but the CAN masking hardware was not updated until the system reset. Now clearing all settings will trigger a re-initialization of the communications hardware.

• Fixed bug that could cause a missed output (injection or spark) if multiple outputs were due at exactly the same time.

• Fixed bug that caused an incorrect packet bit number in the nack response to a request packet which was requesting a packet not recognized by the firmware. This bug would lead to an infinite packet request cycle when a new configuration packet was added to the request list.

• Fixed crank sense bug that could cause the system to think the engine was running when it was not. This would only occur if a single crank sense event had occurred in isolation, and the only consequence was that certain commands (such as test mode) would be locked out in this state.

• Fixed fuel pump duty cycle reporting. Previously logic was used to handle the case where the communications output frequency was faster than the pump on/off frequency; the logic attempted to produce an average pump duty cycle. However this logic could make the output confusing in low duty cycle cases and has been removed. Now the pump duty cycle is simply the average duty cycle for the reporting period.

• Fixed computation of settings hash in the event that not all possible packets were part of the configuration. This would happen if the default settings for a particular category did not need to be changed. In that case the configuration hash would be different if the packet had been sent verus if it had not, even though the actual configuration was identical. Now any configuration packet which is not present in the configuration (factory or user) is automatically written to user storage at startup with default values, thereby guaranteeing that the packet will contribute to the configuration hash.

• Fixed computation of settings hash in the event that autocorrect was enabled for the MAP sensor. In that case the sensor offset would vary as needed in the settings, which would cause a spurious settings mismatch error. Now the autocorrect offset is stored separately from the normal sensor configuration data, so changes made by the auto-correct algorithm are not included in the configuration hash.

• Improved automatic MAP sensor offset correction. With the previous continuous algorithm it was possible to produce a small error when the engine was started, by changing the manifold pressure before IntelliJect knew the engine was running. The new algorithm is not continuous, and will only update the offset 2 seconds after computing the new offset, if the engine is still not running.

Bug fixes for IntelliJect display:

• Improved setting the display layout to default. The previous method did a poor job of sizing the tabified windows.

• Fixed bug in charting of oscilloscope data. Scope data are now double-buffered and the display is only painted on the complete reception of the time window of scope data.

• Fixed bug that caused the last row of the throttle curve to be corrupted when deleting rows from the throttle curve.

• Fixed replay pause/play button which could get out of sync with the actual paused/playing status if you opened a second replay file.

New features for IntelliJect (firmware and display):

• Replaced the fuel pump output scope channel with an output edge error channel. This channel can be used to trigger the scope output to catch spark or injector outputs that have diabolical timing which cannot be satisfied.

• Increased the amount of engine wear data. In addition to hobbs time and engine revolutions IntelliJect now tracks the amount of time the engine was at high load, the amount of time the engine was running too hot, the peak engine temperature, and the number of times the engine was started. Hot time is subject to a time multiplier, such that increasing temperature causes hot time to accrue faster. Since engine wear is a regular telemetry packet, and adding the new data caused the packet to exceed the 8 byte data limit that is preferred for telemetry packets on the CAN bus, the engine wear packet now has a short form (with 8 data bytes) and a long form with all the data bytes. When the short form engine wear packet is used it is followed with a new packet that provides the extended engine wear data.

• Added logbook feature. The logbook consists of a series of packets that include name, date, and log entry description text. The logbook is stored on board flash of the IntelliJect processor (not the user storage eeprom). New log entries can be added when IntelliJect is locked, but editing or erasing the log requires IntelliJect to be unlocked.

• Added maintenance feature. This consists of a new configuration packet which defines a maintenance schedule and a packet which defines the maintenance status; including an indicator if a maintenance item is due to be serviced, the serial number of the engine that the maintenance status applies to, and a command to indicate when the maintenance has been performed. Maintenance items in the schedule can be triggered by engine time, rev count, hot time, load time, peak CHT, or number of starts. The maintenance feature has two windows: a configuration window (and packet) that is controlled by the lock/unlock access; and a maintenance view window that displays the schedule and allows the user to indicate that maintenance service has been performed. Performing a maintenance item automatically adds an entry to the logbook.

New features for IntelliJect firmware

• Removed the comment and file packets from the configuration hash computation. Also changed how the communications packet contributes to the configuration hash, to remove the effect of the CAN identifiers (which typically change from unit to unit). The content of these packets do not affect how the engine runs, so leaving them out of the hash makes it easier to determine if something important has been changed in the configuration.

• Changed the behavior of the clear all storage command. Previously this command would preserve the engine wear information, now it clears everything, returning IntelliJect to a completely default condition.

• Changed default settings to include non-zero settings for the fuel table, spark table, starting fuel table, head temp table; and injector1 trim table. These defaults only apply if these tables are not present in the configuration, and are meant only to provide a useful starting point for a new configuration.

• Changed how IntelliJect saves volatile quick-restart data and user commands to reset proof storage. Previously this data were stored in SRAM, however the contents of SRAM are lost with a few hundreds of milliseconds after power is removed. Now IntelliJect stores this data in backup RAM on the processor. The backup RAM will remain valid for several seconds after power is removed, extending the interval of time that power can be interrupted while still performing a quick restart.

• Improved fuel pump control logic. You can now specify the PWM period used to control the pump motor, as well as specify a duty cycle rate limit to minimize current transients in the motor control.

New features for IntelliJect display

• Added menu option to toggle fullscreen mode for the display. Fullscreen mode hides the application title bar and covers the operating system taskbar.

• Added options to the acceptance test report to choose the files that were used to record the checkout data, the configuration file, and the checkout profile. These values are automatically populated, but changing them is useful for cases where the acceptance test report is generated from a replay.

• On the CAN settings of the communication selection dialog, if you select an ID that is currently visible on the bus, the resulting value is transferred to the CAN input ID. Now it also transfers the value to the output ID by assuming that the output ID has the least significant set bit of the input ID cleared (above the type shift). This is not guaranteed to be the case, but is likely to be so unless the CAN settings of the IntelliJect have been changed from their defaults.

• Added a button to the communication selection dialog to set the CAN configuration to default values. Also added support for auto-detecting the actual CAN IDs on the bus for cases where the CAN settings are at their default values, and then using those detected values.

• Improved the layout of individual windows - utilizing more consistent spacing and margins, and in some cases re-organizing the fields to better fit the dialogs.

• Added the ability to insert or delete throttle curve rows using a right click on the table.

• Changed the default display layout so that it centers the main window, if the window is not maximized or full-screened

• Added support for dual Horiba gas analyzers (“Left” and “Right”). This is useful for twin engine development, in particular for doing cylinder balance. This features changes both the Horiba display and the toolbar, and also changes the layout of the log files.

Bootloader version 5:

• Version 5 of the bootloader adds the ability to jump from the bootloader back to main code after programming.

• Version 4 of the bootloader adds support for reset commands in backup RAM, in addition to data in SRAM. This increases the amount of time power can be interrupted while still supporting quick restart. Reset commands in SRAM are still supported, so bootloader 4 can work with firmware versions older than 1.4.

Version 1.3 (11 August 2018):

Bug fixes for IntelliJect firmware

• Fixed mistakes in emulation of Currawong ECU: the reported throttle curve was zeroes unless it was enabled, the RPM controller gains were scaled wrong by two orders of magnitude, and the charge temperature telemetry was computed wrong.

• Fixed native packet UART protocol handling that was broken when Currawong ECU emulation was enabled for the UART.

• Fixed reversed sense on EFI enable signal.

• Fixed sensor sampling logic that would lose crank sync above 6000 RPM. This would lead to sensor value computation out of phase with the crank.

• Removed recursive packet search algorithm. This algorithm was not a bug, but it could cause substantial CPU blocking in the presence of communications noise (such as an unconnected UART cable).

• Fixed bug in measurement of CPU time, watchdog interval, and max interrupt blocking time. These values could previously be incorrect at high packet rates.

• Improved the logic used to fire the outputs (spark and injectors) for short periods of time, or for time events that are in the past. Previously these (rare) cases could cause the outputs to stall for 0.26 seconds, now they are handled gracefully.

• Fixed throttle logic for case where IntelliJect is driving the throttle output, and is also measuring the throttle position through a TPS.

• Fixed reported injector duty cycle when engine was not running. If the engine is not running the injector duty cycle is reported as 0%.

• Fixed default gain on 12V current monitor.

Bug fixes for IntelliJect display:

• Changed the color of the CHT readout in the head temperature gauge from red to black. The red text would become unreadable when the CHT became too hot and the gauge turned red.

• Fixed display of analog versus digital barometer reading on the sensors page, they were reversed.

• Improved the ability to work with configuration files when not connected to an IntelliJect.

New features for IntelliJect (firmware and display):

• Added support for alternate fuel flow rate measurement based on the pressure decay rate when the fuel pump is not running. This flow rate measurement can only be used with bellows-style fuel accumulators and dead-headed pumps with bang-bang control (i.e. Currawong single piston pumps). In that case the fuel pump will turn off for short periods and the pressure decay rate can be observed. This decay rate is directly related to the rate of fuel consumption, particularly when used with bellows-style fuel accumulators. The estimated flow rate is then integrated to provide an alterate fuel consumption estimate. The alternate fuel consumption is reported in its own packet, and can optionally be reported in the regular fuel telemetry packet.

• Added support for alternate fuel consumption measured by external counter (for example, the Max Machinery 210m). When enabled the throttle PWM digital input is used to count rising edges from the external meter (throttle PWM TPS and command must also be disabled). The alternate fuel consumption is reported in its own packet (the same packet as the pressure decay rate), and can optionally be reported in the regular fuel telemetry packet.

• Added the ability to set (or reset) the fuel used indicator. This is useful for cases where the fuel was topped up without the EFI being reset. It is also useful when doing flow rate calibrations.

• Changed alternative protocol handling to remove the option to specify shy mode over CAN. Instead all alternative protocols (UART or CAN) are implicitly in shy mode. Shy mode means that the native protocol outputs are suspended in favor of the alternative protocol outputs; although the native protocol outputs will resume on the first receipt of a native protocol input. In addition the display software now issues a request for data over the native protocol whenever a communications interface is opened, even before any telemetry is received from the EFI. In this way the display software can successfully connect to an EFI that is configured for an alternative protocol.

• Removed option to change the active sense of the EFI enable signal. The active sense is fixed by the hardware (active high).

• Added option to specify a crank sense delay. The crank sense delay defines the amount of time that elapses between the assertion of the crank sense signal, and the propagation of that signal through the crank sense hardware filter.

• Added option for automatic manifold pressure offset correction. The manifold pressure sensor output has the potential to change over time as the sensor is exposed to fuel. When enabled this feature automatically adjusts the calibration of the MAP sensor so that, when the engine is not running, the MAP pressure reading matches the Baro pressure reading.

• Added option to specify manifold pressure error threshold in the engine configuration. If the manifold pressure from the MAP estimate table is different from the measured manifold pressure by more than the threshold the manifold pressure measurement is replaced with the estimate, and the associated error bit is set.

• Added TPS missing and TPS error bits to indicate if there is no valid TPS sensor when one is expected, or if the TPS sensor has a discrepancy with the throttle output.

• Added option to specify TPS error threshold in the throttle configuration. If IntelliJect is driving the throttle, and if a TPS sensor is enabled, but the difference between the throttle output and the TPS measurement is more than the threshold the TPS error bit will be set.

• Added new slow telemetry packet, TelemetrySensors4. This packet repeats the CHT and fuel pressure data from existing packets; but changes the encoded format to provide more information: the CHT signals can now go from -100C to +461.5C, and the fuel pressure is represented using floating point to accommodate negative values and more dynamic range. The equivalent signals from the previous telemetry packets are still available but should be considered deprecated. They will be removed from later versions of software.

New features for IntelliJect firmware

• Changed fuel pressure sensing for fuel pump control. Previously the fuel pressure used for fuel pump control was not subject to the low pass filter, now it is. Also updated the default fuel pressure senor configuration to use a 5Hz low pass filter rather than 0.1 Hz.

• Added quick restart support. This feature saves key injector, spark, and throttle data to reset proof RAM, which allows IntelliJect to fire the spark and injector on the first crank sense after reboot (before the RPM can be measured or sensor data computed). In addition, the quick restart stores a flag to reset proof RAM that instruct the bootloader to skip the normal code verification step when the system reboots (only if the engine is running). Also re-ordered the bootup sequencing to minimize the amount of time required before the CPU can handle a crank sense event. The combination of these features makes it possible for IntelliJect to go through a reset with only a 100ms delay before resuming spark and injection outputs.

• Changed USB support: The USB peripheral is not configured or enabled until the VBus sensing signal is asserted, and only if the engine is not running at that point. This isolates key firmware functionality from any bugs in the USB software stack. It is not recommended to use the USB interface while an engine is running.

• Changed how the fuel pump duty cycle is reported in the slow telemetry. Previously bang-bang control of the fuel pump would produce pump duty cycle telemetry which was not very meaningful. Now the reported pump duty cycle correctly represents the average pump duty cycle, even if the slow telemetry rate is faster than the rate at which the pump controller is cycling the pump on and off. This change only affects the reporting of the duty cycle, not the control applied to the pump.

• Changed how the min and max throttle tables are interpreted. Previously these provided the min and max input throttle. This has been changed so these tables provide the min and max output throttle.

• Changed how the RPM controller is run. Previously the controller was run once for each crank revolution; however, at higher engine speeds better performance can be achieved by running the controller slower to reduce noise. A configurable update rate (from 10 to 85 Hz, defaulting at 50hz) has been added. The rpm controller now counts the time of successive revolutions until the elapsed time is longer than the desired update rate and then computes the RPM using the entire elapsed time to get a less noisy reading for the control law.

• Changed how the feedforward term of the RPM controller is implemented. The feedforward term was previously a straight line interpolation from the command RPM divided by the max RPM, multiplied by the feedforward gain. Now the feedforward term is the feedforward gain multiplied by the output of the throttle to RPM model of the RPM governor.

• Added feature to compute the manifold temperature from the US standard atmosphere (based on the baro pressure) if the MAT sensor is failed or disabled. The default value of the manifold temperature specifies the failed sensor reading at standard day pressure (101.325 kPa).

• Added feature to compute a backup TPS using the manifold pressure, barometric pressure, and MAP estimate table if the engine is running. The backup TPS is used if there is no other valid source of throttle position (efiDrivesThrottle is off, and analog or PWM TPS is invalid).

• Changed logic regarding low pass filter on the analog TPS. Previously this filter was disabled, and the throttle input filter was used instead. Now the filter is enabled, and the analog TPS value in telemetry will reflect the effect of this filter. The throttle input filter is still used, and its effect is visible in the throttle data.

New features for IntelliJect display:

• Increased the resolution of the fuel used display. The display now gives fuel consumption to tenth of a gram. This much resolution is useful when doing injector flow testing over short time intervals.

• Added the ability to control the line width in strip charting.

• Added the fuel used multiplier to the acceptance test report.

• Added a feature for scoring an engine checkout. The scores are based on the rpm, smoothness, overshoot, lag, and transition whenever the throttle is moved during the checkout (assuming a fixed pitch propeller load).

• Added more information to the reset report dialog, for resets caused by exception.

• Added telemetry file recording of packets sent by the display to IntelliJect (packets from IntelliJect have always been recorded). These packets are written to the same file as the packets that are received from the EFI. To determine the direction of the packet (to or from the EFI) the new packets are written to the file in a modified form that uses a different synchronization 1 byte. Such a packet is invalid in any context other than the telemetry file. When the display replays a telemetry file the special packets are used to populate the packet log window, indicating packets that went to the EFI when the file was recorded.

Bootloader version 3:

• Version 3 of the bootloader adds support for quick restart. Quick restart is enabled when the firmware writes a special flag to reset proof RAM. When version 3 of the bootloader detects this flag it will skip the normal code verification check, so that the firmware can start as quickly as possible and keep the engine running.

Version 1.2 (4 April 2018):

Bug fixes for IntelliJect firmware

• Changed the fuel pump switch frequency to 500Hz from 1kHz to better match the turn on and off times of the switch hardware.
• Fixed problem with ignition maximum dwell time - which would occasionally cause erroneous spark timing.
• Fixed application of injector trim time. Previously the trim was applied to the end of the injection pulse. Now the trim is applied to beginning of the injection pulse if it is positive, and to the end of the injection pulse if it is negative. This should better line up the actual fuel injection with the desired injector phase.
• Fixed ignition output sense to be the correct polarity. Now if you select the engine configuration option “Ignition Active High” the ignition output will be active high.

Bug fixes for IntelliJect display:

• Changed replay processing so that a bad or unrecognized packet does not pause replay.
• Added missing documentation to the packet log display for fictitious packets (from non IntelliJect devices).
• Improved handling of floating displays when the display layout is locked.

New features for IntelliJect (firmware and display):

• Added high speed oscilloscope feature. The oscilloscope records the analog signals at their base sample rate (1kHz) and digital signals asynchronously to generate a triggerable high speed display of data with microsecond resolution. This display can be used to debug key timing events, and to study the analog signals intra-cycle. The scope setup is volatile and not considered part of the EFI configuration, although the setup can be requested along with the normal configuration information.
• Added debug message. This message is used by firmware developers to insert human readable debug strings where needed. The debug information is displayed in the packet log.
• Added support for the Currawong Engineering CAN servo. IntelliJect can be configured to command a CAN servo for throttle and cowl flap (cooling) control. IntelliJect will report an error bit if a CAN servo is expected but not discovered, or if the servo is reporting an error code.
• Added test mode feature. Test mode is used for hardware debugging and test. Test mode can simulate a crank signal, run injectors, ignitions, and fuel pump options. Test mode is only available if the engine is not running; and is automatically canceled if the engine starts running.
• Added the ability to perform calibration of sensor offset or gain by providing the true sensor reading and computing the gain or offset that makes the raw data match the provided sensor output.

New features for IntelliJect firmware

• Changed interpretation of injector phase table. The injector phase table now gives the crank angle when the injection ends, rather than the middle of the injection.
• Augmented the interrupt time value in the CPU telemetry packet. Previously this time was the worst case amount of time spent in any one interrupt. Now it is that OR the maximum amount of time that interrupts were blocked, whichever is greater.
• Added MMFAR and BFAR registers to the exception reset report packet. These registers report the address of an invalid memory access (if any).
• Added new crank sense error “Missed crank sense edge” for crank sense 1 and 2. A missed edge is asserted when the crank sense interrupts for two consecutive edges of the same type (active or non-active). A missed edge error is distinct from a crank late or crank bounce error.
• Added feature to track the time between active and non-active crank sense edges. This time is used to reconstruct the active edge time if the active crank sense edge is missed.
• Changed CPU temperature sensor so that it uses the on-chip calibration. Also changed sensor handling so that the sensor limits do not indicated “out range reading” but instead indicate that the system is too cold or hot.

New features for IntelliJect display:

• Changed the name of the temperature difference table. It is now called the “charge temperature” table. The functionality of the table has not changed.
• Added acceptance test report feature to automatically generates a report of the IntelliJect configuration and the charted performance.
• Added the ability to un-synchronize a chart, so that its time axis does not follow other charts. This makes it possible to have a chart scrolling live data while having another chart reviewing old data.
• Changed handling of nack messages to suppress the nack warning message while in replay.
• Added display of replay file progress (as a percentage) in the replay toolbar
• Separated the error display into two windows, one for dynamic errors (errors asserted now) and one for sticky errors (errors asserted in the past).

Version 1.1 (5 February 2018):

Bug fixes for IntelliJect firmware

• Improved interrupt time tracking. Not all interrupts were contributing to the total interrupt time counter.
• Improved processing of CAN transactions by enabling CAN masking.
• Fixed handling of interrupts that could cause missed crank sense events.
• Changed the logic for the crank sense active high option; to account for the crank sense inversion on the hardware. “Active high” now refers to the signal at the IntelliJect harness, not the CPU.
• UART baud rate configuration is now being correctly applied at bootup.
• Fixed analog sensor sampling to prevent sensor overruns, which degraded the sensor accuracy.
• Changed the process of storing configuration data in the user storage space so that IntelliJect remains responsive while the storage operation is proceeding.

Bug fixes for IntelliJect display:

• Fixed bug that was preventing the strip chart auto scale setting from saving and restoring correctly.

New features for IntelliJect (firmware and display):

• Added feature to select load -or- throttle on a table by table basis rather than globally in the engine configuration data.
• Added option to force a sensor to default configuration.
• Added support for KTY83 temperature sensor.
• Added option to force communications configuration to default.
• Added new communications options, including the option to support the Currawong ECU protocol and the Piccolo ECU protocol.
• Added telemetry for communications system performance, which provides error indicators for USB, UART, and CAN systems.

New features for IntelliJect display:

• General improvements to layout and usability.
• Improvements to windows installer.
• Switched software to 64-bit on Windows (macOs and Linux were already 64-bit).
• Added display of table output. This makes it easier to see the exact value that a table is computing, rather than trying to eyeball it based on the operational condition.
• Added comment feature. The comment feature allows you to enter a comment when something interesting happens. The comment is saved in the replay .tel file, and is written to the log file, and is displayed on the strip charts.
• Rebranding from generic “Power4Flight EFI” to “IntelliJect”.
• Added ability to save and open configuration data in human readable text format.
• Added configuration comparison feature; you can compare IntelliJect configurations given by two files, or by a single file and a live IntelliJect.
• Added save and open configuration selection option. This makes it easy to pick and choose what pieces of the configuration should be updated from a file.
• Added alarm for CHT sensor failure.
• Added support for firmware update over CAN.
• Added feature to show what CAN IDs are active on the bus. This is helpful to the user when they are trying to discover the ID of the IntelliJect.
• Added preliminary support for CAN bus devices other than the Systec USB-CAN module.

Version 1.0 (13 November 2017)

This is the first release, no notes.