Raptor-Dev-Release-Notes

New Eagle > Products Wiki > Raptor Platform > Raptor-Dev > Raptor-Dev Release Notes

Below is a list of all Raptor-Dev versions and their change logs, beginning with the most recent version.

2022b.1.0

• Issue 0004352: [General] Regression Floating point tests failing.
• Issue 0004351: [GCM048] CAN queue not clearing, CAN RX Processing performance has declined
• Issue 0004329: [RCM80] RCM80: Add Wake Source Measurement
• Issue 0004345: [Legacy] CM0711 Always initializes CAN to 250K for base software
• Issue 0004173: [Build] Expose Reset Reason to Application
• Issue 0004298: [VeeCAN] Menu Screen block set does not compile
• Issue 0004005: [Build] Fault Data definition blocks should support a vector input
• Issue 0004338: [RCM112] Update Template Model for RCM112
• Issue 0004284: [Build] Add ability of CAN RX and TX Blocks to use the default value as defined in the DBC.
• Issue 0003844: [RCM80] RCM80: XCP Traffic seems to timeout
• Issue 0004346: [RCM112] SENT block block does not build when placed in a Simulink While iterator block
• Issue 0004337: [GCM048] Use of HW Mailbox Config will cause module to reset with REG_CFG_MON exception
• Issue 0004190: [RCM112] RCM112: Add Support for Multiple VLANs
• Issue 0004307: [RCM80] implicit declaration of function 'CAN_RX_Queue_Get_Status'
• Issue 0004320: [RCM112] Add support for LIN Slave
• Issue 0004306: [RCM112 EOL Tester] EOL Tester AD5674 Driver Integration
• Issue 0004276: [Build] Error opening CANFD tx block when dbc is not on the path
• Issue 0003925: [RCM112] Create quadrature encoder and interface to RCM112 API
• Issue 0004232: [Build] Compile error when there is a vector input to a lookup table
• Issue 0004212: [RCM80] RCM80: Compiler optimizations need to be set to optimize for size.
• Issue 0004251: [UDS] UDS Client Functional Request cannot send Extended IDs
• Issue 0004290: [Build] If no signals are selected on a dbc_pack block you get an uninformative tlc error
• Issue 0004342: [Build] Code Replacement libraries are missing pow(double, double)
• Issue 0004317: [RCM80] RCM80: The millisecond ticks counter can become locked
• Issue 0004196: [RCM80] Remove unnecessary time-related globals from the RCM80 SDK
• Issue 0003820: [RCM112] RCM112: Create Reset Reason Tracking Logic
• Issue 0004277: [RCM112] VR/DG Select logic inverted
• Issue 0004296: [RCM112] Update L9945 Configs for the RCM112
• Issue 0004297: [VeeCAN] Menu Screen Definition block not accessible to other blocks
• Issue 0004304: [General] Update Telematics lib to 2020b
• Issue 0004233: [VeeCAN] Adjustment not being set to default upon flashing different software on a veecan 320
• Issue 0004262: [Build] Add Optimization to DBC Pack block for Non Scaled Signals.
• Issue 0004207: [General] Remove support for S32K EVM/UAS Module
• Issue 0003296: [GCM048] Cryptic build error when Power up block is not included
• Issue 0004254: [Build] Output from raptor_get_buildNum and Config Read block do not match
• Issue 0004226: [Build] Remove Support for Motor Control S32K144 Targets out of installer.
• Issue 0003997: [Build] Add support for MATLAB 2022b
• Issue 0004065: [RCM80] Implicit function for ADC reading leads to compiler warnings
• Issue 0004185: [VeeCAN] Draw Text block cannot render multiple lines - update help
• Issue 0004240: [UDS] Service 0x19 - Read DTC Info block always lists Permission Function on the block mask
• Issue 0004204: [General] Temperature Measurement Block MaskType and help page spelled wrong
• Issue 0004218: [Build] Remove support for Matlab 2022a
• Issue 0004235: [Build] Initialized Enumeration Simulink Data Store designated as a Raptor.Signal results in a compiler error
• Issue 0004199: [RCM112] AN16-AN19 have improper scaling when used as Analog Inputs
• Issue 0004205: [RCM112] RCM112 667k CAN Baud rate timing
• Issue 0004175: [BCM60] BCM60 : Error when no nonvolatile is present
• Issue 0004179: [Build] Use of a function call split and a CAN Rx trigger fails to build in Raptor 2022a_2.0
• Issue 0004181: [Build] Imprecise XPath command can break items with multiple kinds of baud rate
• Issue 0004186: [RCM112] CANFD: Update RCM112 SDK to detect received BRS messages
• Issue 0004189: [VeeCAN] DisplayHideButtonBar returns a compile error
• Issue 0004206: [RCM112] RCM112 TLE Transceiver Baud Rates
• Issue 0004075: [General] Internal Measurement Block MaskType spelled wrong
• Issue 0004202: [RCM112] CAN Compiler warnings

Test reports for 2022b_1.0.14751 are available here.

2022a.3.2

• Issue 0004327: 2022a: RCM80: The millisecond ticks counter can become locked
• Issue 0004328: 2022a: Update L9945 Configs for the RCM112

2022a.3.1

• Issue 0004236: [RCM80] RCM_80_2203 SDK irregular behavior from installed builds.

2022a.3.0

• Issue 0004184: [RCM80] RCM80-2106 Takes a full minute to reboot when the reboot block is executed
• Issue 0004183: [RCM80] CAN3 and CAN4 Resources swapped.
• Issue 0004018: [RCM112] RCM112 - Expand CAN FD support
• Issue 0003746: [RCM112] RCM112: Add Support for SENT
• Issue 0003748: [RCM112] RCM112: Add support for the Accelerometer/IMU
• Issue 0004135: [GCM048] Clock monitoring unit
• Issue 0004176: [RCM112] RCM112-2202 unusable when CAN 1 set to 1 Mbps
• Issue 0004054: [RCM112] Application doesn't build if XCP definition isn't included
• Issue 0004033: [Build] Fixed Point Data Types calculate gains in the A2L incorrectly for gains that are not a multiple of 2
• Issue 0004139: [GCM048] Enable the Software Watchdog Timer Registers Hard Lock
• Issue 0004136: [GCM048] Configuration register check
• Issue 0004134: [GCM048] Application flash integrity
• Issue 0004174: [RCM80] RCM80-2106 Fails to shutdown when key is turned off and power_hold is released
• Issue 0004180: [RCM80] RCM80-2203 Does not expose LSO3 Current Feedback
• Issue 0004011: [RCM112] Saving NonVolatile resets the target
• Issue 0004104: [RCM80] RCM80-2203 Change Input Capture from DG5/6 to DG9/10
• Issue 0004138: [GCM048] stack underflow detection
• Issue 0004166: [GCM048] CAN MCR register check
• Issue 0004069: [RCM112] Update XCP for CANFD
• Issue 0004171: [RCM112] Update Module Images for RCM80 and RCM112
• Issue 0004137: [GCM048] Prevent JTAG spurious activation
• Issue 0004133: [GCM048] RAM SW self-test at start-up
• Issue 0004168: [UAS_M47] M47: Set Motor Driver for Synchronous 1x PWM Mode
• Issue 0004074: [General] CAN/CANFD Tx Msg Blocks don't use mailboxes
• Issue 0004044: [Build] VeeCAN targets compilation error when a "step" function isn't generated based on the model configuration
• Issue 0004071: [Documentation] Add mention of raptor_mwenum2raptorenum to the Adjustment HTML
• Issue 0004064: [VeeCAN] Warnings when VeeCAN128 template project is created
• Issue 0004046: [RCM112] CAN State Block port labels are incorrect
• Issue 0003972: [General] Update CAN Pre-Transmit hooks for CAN FD
• Issue 0003740: [RCM112] RCM112: Add CAN-FD support
• Issue 0004192: [RCM80] RCM80: Delta Time and Abs Time blocks return 0 on the RCM80-2203
• Issue 0004201: [RCM112] Frequency inputs 3, 5, 6, 11 not scaled correctly

2022a.2.1

• Issue 0003347: [Build] Including math.h can cause linker and compiler errors
• Issue 0004025: [UAS_M47] LTC Chip is not starting up correctly. reports bad temp and needs power cycle to clear
• Issue 0004041: [RCM80] J1939 build error on 2203 variant
• Issue 0004055: [Build] MATLAB 2022a changed where math.h is added in the generated code
• Issue 0004077: [RCM80] Misconfigured Input Capture ISR setup on the RCM80 2203

2022a.2.0

• Issue 0003974: [GCM048] GCM48 - Digital Inputs cannot act as Analog Inputs
• Issue 0004016: [Build] LIN Tx block code generation error when there are logical and physical ports
• Issue 0004015: [RCM112] LIN buffer is reset to 0s when messages are not received
• Issue 0004006: [Build] OBD Fault Manager Confirmed State is not healing properly
• Issue 0004003: [Build] Models in MATLAB 2022a that generate rtGenNan.c fail to compile
• Issue 0003998: [General] DBC Parse Unpack block does not update within a library
• Issue 0003996: [RCM80] RCM80: Possible issue with the free running counter aka time block.
• Issue 0003993: [VeeCAN] Improve naming error checking for custom fonts
• Issue 0003992: [RCM80] RCM80 Analog outputs doubling
• Issue 0003991: [RCM112] RCM112: 2202 Variant has the incorrect pull up/down values for some analog inputs.
• Issue 0003989: [Build] Expand the maximum buffer size of the ethernet receive blocks
• Issue 0003988: [RCM112] RCM112: Can send Raw allows id field to be set beyond the bounds of the 29 bits.
• Issue 0003987: [VeeCAN] Need to fix max pixel height in documentation to 130
• Issue 0003984: [RCM80] RTD randomly not reporting correct temperature.
• Issue 0003982: [UDS] Build warning when a single dimension port is mapped to a byte array DID when using Service 0x2E
• Issue 0003948: [UDS] Add support for functional address client requests to UDS Client
• Issue 0003933: [RCM80] need 1 ms time trigger
• Issue 0003696: [Documentation] Improve documentation for XCP Definition block
• Issue 0003694: [Documentation] Add help text stating the startup behavior of the override block.
• Issue 0003337: [Documentation] Raptor LIN Set and Get Schedule Blocs Do Not Contain Any Help Text
• Issue 0003336: [Documentation] Raptor LIN Slave Definition Does Not Contain Any Help Text
• Issue 0004032: [RCM112] RCM112-2202 Fails to shutdown on a key cycle
• Issue 0004000: [RCM80] RCM80: Add Support for the RCM80 2203 Variant.
• Issue 0003861: [RCM80] Add LIN Slave
• Issue 0003724: [Build] Support LIN 1.x by transmitting/receiving the Classic Checksum when the LDF specifies a version less than 2
• Issue 0004013: [Build] Outputting CAN Raw Data Array in raptor_sfun_canrxmsg.tlc does not work properly
• Issue 0003934: [General] DBC Parse Pack block will not update inside a library
• Issue 0003994: [RCM112] RCM112: XCP Read of bad addresses can cause a MEMORY_PROTECTION fault.
• Issue 0003482: [Documentation] Various blocks are missing help text
• Issue 0003968: [Documentation] Help page 'colors.html' is empty
• Issue 0003338: [Documentation] Raptor LIN State Block Does Not Contain Any Help Text
• Issue 0003985: [RCM112] RCM112: 1 Second Task metrics always return 0
• Issue 0003695: [Documentation] Add help text to mention global scope of raptor data store blocks.

Test reports for 2022a_2.0.14613 are available here.

2022a.1.0

• Issue 0003971: [General] Distributed Action Trigger uses wrong init function
• Issue 0003926: [General] Centralize Simulink Function cross-reference update checks?
• Issue 0003899: [Build] Raptor Data Definition needs to check for invalid parameter types
• Issue 0003895: [UDS] Add a generic Server UDS Service Rx block
• Issue 0003585: [Build] Table Update Build Error
• Issue 0003977: [RCM112] Reallocate RAM to accommodate for the EEPROM driver change
• Issue 0003963: [RCM80] RCM80 on Wake triggers Power Outputs
• Issue 0003957: [RCM112] RCM112: Calling NV Save will cause a reset of the ECU, and NV save does not occur.
• Issue 0003956: [RCM112] If all NV is specified as calibrations EE is not saved at shutdown.
• Issue 0003935: [RCM80] Add Input Capture to RCM80 DG Inputs
• Issue 0003904: [Build] Setting the mailbox to [] causes an odd error to be reported
• Issue 0003917: [GCM048] Linker error when using functions provided in external archives
• Issue 0003747: [RCM112] RCM112: Add support for the Real Time Clock
• Issue 0003979: [RCM112] RCM112: Add Model Year 22 Variant
• Issue 0003877: [Build] Remove support for MATLAB R2019b
• Issue 0003849: [Build] Remove support for MATLAB R2019a
• Issue 0003851: [VeeCAN] Raptor Screen Definition block needs to use Simulink's built in callback capability
• Issue 0003976: [General] CAN DBC blocks should check for duplicate signal names
• Issue 0003978: [Build] 2D Table Causes build error when y axis data is column vector.
• Issue 0003912: [Build] Column Vector Table Data in 1D lookup tables causes a TLC error in ML R2021b
• Issue 0003909: [Build] Add Support for Matlab 2022a
• Issue 0003765: [Build] Expand Support for Stack Monitor to RCM80, UAS48
• Issue 0003944: [RCM112] CAN Age Counts are not initialized
• Issue 0003973: [General] update the 'Update Simulink Functions' buttons
• Issue 0003127: [General] CAN message Pre-Transmit hooks for the CRC & Message Counter computation
• Issue 0003485: [Build] Support ISO14229 Service 0x19 - Snapshots
• Issue 0003919: [Build] Add Simulink Function options to CAN Trigger blocks
• Issue 0003922: [Build] Add Simulink Function options to LIN Trigger blocks
• Issue 0003951: [Build] Add Simulink function options to Serial Trigger blocks
• Issue 0003940: [RCM80] RCM80: Incorrect Bit Mask Identified for Open Load Diagnostic
• Issue 0003905: [General] raptor_get_buildNum is always one off from the actual build number
• Issue 0003927: [RCM112] RCM112 GCC compiler doesn't support the iseleq instruction
• Issue 0003930: [VeeCAN] Can no longer select None for Simulator compiler
• Issue 0003937: [RCM80] RCM80 internal measurement scale readjustment
• Issue 0003941: [Build] CAN Bus Off Recovery Block does not display resource on the block mask correctly
• Issue 0003931: [RCM112] Call to Bios_Eth_GetLinkStatus() causes build warning when set to bool output.
• Issue 0003959: [Build] OBD Fault status block returns an error when Fault Source is set to port
• Issue 0003950: [VeeCAN] VeeCAN 320L screen does not turn on for about 10s during boot up
• Issue 0003221: [Build] Linker error when using a Stateflow diagram to call a MATLAB Function inside of a Serial Rx trigger block
• Issue 0003943: [RCM112] RCM112 does not properly sleep on Key Down
• Issue 0003486: [Build] Support ISO14229 Service 0x31 - RoutineControl
• Issue 0003945: [Build] Newlines or carriage returns in the block path leads to a TLC error when using Simulink Functions
• Issue 0003938: [BCM48] Ethernet Socket block leads to TLC error
• Issue 0003907: [RCM112] LIN Linker error when building an application with HighTec compiler
• Issue 0003898: [Build] Add check for multiple XCP blocks
• Issue 0003929: [VeeCAN] Installer does not prompt to automatically install for VC800 target compiler
• Issue 0003928: [RCM112] RCM112: Internal Measurements that are API Calls should be marked not exclusive.
• Issue 0003569: [VEECAN500] Simulator does not function properly when the App Monitor is present
• Issue 0003906: [VeeCAN] Prefab Battery Block has the transition points hard coded
• Issue 0003908: [Build] Use Raptor.Parameter can lead to incorrect default value.
• Issue 0003918: [Legacy] CM0711: Allow INPUT7 and INPUT8 to be defined as both Analog and Freq input
• Issue 0003914: [Build] Mismatching breakpoint initial value and breakpoint data types leads to compile error in ML2021b
• Issue 0003840: [Build] Display Build UID in Matlab data log
• Issue 0003915: [UDS] "bytes" DIDs with only one byte leads to build warning
• Issue 0003897: [VeeCAN] Support VeeCAN 300R IO - Digital Output
• Issue 0003854: [VeeCAN] Support VeeCAN 300R IO
• Issue 0003892: [VeeCAN] Analog Input Reference block scaling - VeeCAN 320
• Issue 0002801: [General] No option for Vbatt in BCM48 Raptor_internal_measurement

Test reports for 2022a_1.0.14569 are available here.

2021b.2.0

• Issue 0003894: [UDS] Add support for a Service Process block
• Issue 0003846: [Build] Raptor Mask buttons do not function properly in MATLAB R2021a/b
• Issue 0003855: [RCM112] Configure and Test both HSO and LSO diagnostics for the 2103 variant.
• Issue 0003860: [RCM80] Add Wake on Lin and Wake on CAN sources
• Issue 0003868: [J1939] J1939 Blockset checks Fault Data Def for Size and Errors if > 1
• Issue 0003886: [RCM112] Create example project to handle wake source inputs and proper sleep
• Issue 0003843: [General] Signals defined as float-point in DBC always return 0 from DBC Unpack
• Issue 0003883: [General] DBC Pack does not output 1-bit signed integers correctly
• Issue 0003881: [GCM196] Raptor-Dev should not be preventing build based on .dbc overlapping signals
• Issue 0003885: [RCM112] Add Binding option to Ethernet UDP/TCP Client Socket
• Issue 0003842: [Simulation] DBC Pack & Unpack blocks do not simulate
• Issue 0003876: [RCM112] Implement CAN Bus Off Monitor and Restart
• Issue 0003788: [RCM112] Enable VLAN support
• Issue 0002971: [Build] Build is sluggish when there are a lot of Raptor Data Store read/writes
• Issue 0003887: [RCM112] The RCM112 does not jump to boot 100% of the time
• Issue 0003880: [General] DBC Pack block has trouble with long messages
• Issue 0003753: [RCM112] RCM112: Enable Run Time CAN Baud Rate Configuration
• Issue 0003871: [RCM112] Add Wake on LIn, Wake on CAN, and Wake in Ethernet sources
• Issue 0003867: [UDS] Service 0x19 fails to build when extended data is not included
• Issue 0003869: [VeeCAN] Add Support for new Tianmar Screen on VeeCAN320s
• Issue 0003794: [RCM112] Matlab crashes when 2 Ethernet blocks in different subsystems share a Simulink function
• Issue 0003865: [Build] The String reference block update check needs to be streamlined
• Issue 0003845: [General] Add feature to export fault map tool information to Excel
• Issue 0003859: [General] Add CTRL-D checks on Internal Measurement block
• Issue 0003863: [RCM112] Update raptor_check_storage_types for RCM-112
• Issue 0003852: [General] Add 'None' resource for Ethernet Definition block
• Issue 0003888: [RCM80] RCM80-2106 I/O integration updates
• Issue 0003891: [GCM70] "Signal Incorrectly Defined" build error when using DBC Pack block
• Issue 0003893: [J1939] J1939 stack transmits even if the Source Address has not been claimed yet
• Issue 0003900: [UDS] raptor_create_uds_project produces a project with empty m files
• Issue 0003889: [RCM112] Add support for LIN Rx Age Counts

2021b.1.0

• Issue 0003846: [Build] Raptor Mask buttons do not function properly in MATLAB R2021a/b
• Issue 0003791: [RCM80] RCM80 EST1 output - high side or low side?
• Issue 0003782: [GCM048] GCM48 LSO8 and LSO8 Fault Status to "Unavailable"
• Issue 0003757: [GCM048] GCM48: Provide Method to set the global CAN ID and mask
• Issue 0002762: [Documentation] Edge Count missing from help documentation for Freq_in
• Issue 0003847: [UAS_M47] The SPD1 Interface selection is not functioning properly
• Issue 0003801: [RCM112] RCM112 pull up values are incorrect for DG11-12
• Issue 0003759: [VeeCAN] Screen Definition Block > Select At Initialization can be true for multiple blocks without an error.
• Issue 0003857: [GCM196] LIN Set Schedule doesn't allow a change to schedule at startup
• Issue 0003805: [UDS] Add Service 0x19 - Extended Data
• Issue 0003802: [GCM048] Populating more than 9 CAN IDs as a vector into the ID parameter of a CAN RX Raw block generates a .tlc file error
• Issue 0003821: [RCM112] Add Support for RCM-58NN-1112-2103 Variant
• Issue 0002939: [GCM196] Ready port on raptor_read_checksum block behaves incorrectly when the calc_checksum is set to Continuous mode
• Issue 0003829: [Build] Fault Data definition block causes a TLC error in newer versions of MATLAB
• Issue 0003796: [RCM112] Add Support for Digital Inputs DG1-DG12
• Issue 0003807: [RCM112] Scheduler generation does not factor in trigger priority correctly
• Issue 0003803: [RCM112] Add current feedback on the LSOs
• Issue 0003784: [RCM112] RCM112: Add LIN Master support
• Issue 0003848: [RCM112] Add TCP shutdown block
• Issue 0003799: [General] CAN Tx/Rx blocks break if set to use messages with no signals
• Issue 0003762: [Build] Add file picker buttons to Target Definition Block for user-defined output locations
• Issue 0003768: [VeeCAN] Screen Definition Blocks might pick an unexpected first screen if none have 'Selected at Initialization' == true
• Issue 0003543: [RCM112] Add Support for the RCM-58NN-112-2007
• Issue 0003743: [RCM112] RCM112: Add Low Side Outputs support with diagnostics
• Issue 0003736: [RCM112] Add checksum support to RCM112
• Issue 0003781: [General] Reduce Raptor-Lite Support
• Issue 0003841: [General] Signals defined as float-point in DBC - add CAN parse warnings
• Issue 0003839: [GCM196] New GCM196 models not finding the Code Replacement library on open
• Issue 0003833: [RCM112] Add LIN Master support to LIN2 on the 2103
• Issue 0003824: [General] CAN IDs for mailboxes always set to zero
• Issue 0003835: [RCM112] Configure the Hbridges on the 2103
• Issue 0003558: [Build] Add support for MATLAB 2021b
• Issue 0003827: [RCM112] LIN fails to link when using the High Tec compiler
• Issue 0003826: [General] Optimize raptor_create_project for new S32K modules
• Issue 0003817: [General] New DBC Pack blocks break if their default DBC file is missing
• Issue 0003816: [VeeCAN] Add checks for missing/invalid custom fonts
• Issue 0003730: [GCM196] GCM196 builds that use shared utilities can generate linker errors for double precision floating point functions
• Issue 0003760: [VeeCAN] Add check for different images with the same file name.
• Issue 0003825: [[Internal] Test Framework] New S32K modules need test updates
• Issue 0003314: [General] DBC Pack/Unpack blocks don't work properly with multiplexed messages
• Issue 0003795: [RCM112] Add warnings to obsolete Ethernet blocks
• Issue 0003766: [Build] Blocks that use the UDS Create Simulink functions should check the function name is valid
• Issue 0002984: [VeeCAN] Cryptic build error when switching target between VeeCAN500 and VeeCAN800
• Issue 0003808: [GCM196] Remove Scaling feature on DBC Pack Block and CAN Tx Message block not aligning
• Issue 0003811: [RCM112] Add support for the FreeFormat schedule entry to the LIN Parser
• Issue 0003815: [Build] Add support for Assign Frame ID Range in the LDF parser
• Issue 0003207: [GCM196] GCM196: Cryptic error when a receive mask has 7e0
• Issue 0003810: [Build] Cryptic update error when "FreeFormat" identifier is used in a LIN schedule
• Issue 0003814: [Build] Add support for Save Configuration in the LDF parser
• Issue 0003809: [Build] DBC Block scaling is not working
• Issue 0003804: [J1939] PGN 65242 missing SPN
• Issue 0003800: [Build] "Scaled Signals" error with DBC Pack block
• Issue 0003775: [VEECAN500] Compiler error when a breakpoint table has an integer data type
• Issue 0003767: [General] Update masks for blocks that call Simulink functions
• Issue 0003774: [VeeCAN] Add support for the VeeCAN 800 (C7)

Test reports for 2021a_1.0.14082 are available here.

2021a.3.0

• Issue 0003830: [Build] Fault Data definition block causes a TLC error in newer versions of MATLAB
• Issue 0003806: [RCM112] Scheduler generation does not factor in trigger priority correctly
• Issue 0003793: [VeeCAN] Add support for VeeCAN800
• Issue 0003792: [GCM048] Add Support 83.3K Baud Rate on the GCM48
• Issue 0003798: [RCM80] RCM80 RTD Type Selection
• Issue 0003790: [RCM80] RCM80 Frequency Input values are incorrect
• Issue 0003797: [GCM196] GCM196 Fails to build with an output_status for MPRD resource

2021a.2.0

• Issue 0003543: [RCM112] Add Support for the RCM-58NN-112-2007
• Issue 0003714: [RCM112] RCM112: Add Non Volatile support
• Issue 0003741: [RCM112] RCM112: Add Application Monitor Support
• Issue 0003742: [RCM112] RCM112: Configure and support the Input options as defined in the schematic
• Issue 0003744: [RCM112] RCM112: Add support for internal measurements
• Issue 0003749: [RCM112] RCM112: Add STD CAN support
• Issue 0003738: [RCM112] RCM112: Add Support for High Side Outputs
• Issue 0003722: [RCM80] Add RTD support to the RCM80
• Issue 0003452: [General] Add matlab function help documentation to release version of raptor dev.
• Issue 0003752: [RCM112] RCM112: Add ability to Enter Low Power Mode / Module Off
• Issue 0003721: [General] CAN Rx & TX blocks choke if you select a message that has more than 22 signals
• Issue 0003723: [GCM196] GCM196 does not provide MPRD_SHORT_BATT replace with MPRD_STUCK
• Issue 0003779: [Build] Add J1939 Support to GCM48, RCM80, and RCM112
• Issue 0003761: [Build] Build error when empty strings are provided for the user defined build outputs
• Issue 0003566: [RCM112] Add Ethernet Support
• Issue 0003687: [VeeCAN] Button Def block: separate drawing the object from the object itself
• Issue 0003719: [VEECAN500] Resources.h and Resources.c are not generated fast enough when there are too many images
• Issue 0003720: [Build] -'s in the directory fails to parse
• Issue 0003718: [VeeCAN] Add text feature to Button Def block
• Issue 0002553: [VeeCAN] Add VeeCAN support for TrueType fonts
• Issue 0002795: [Build] DBC parser capability for SG_MUL_VAL_ to support multiplex definitions for a range
• Issue 0003710: [UAS_M47] Add UAS-5743R-047-2107
• Issue 0003715: [Build] New DBC File checks are broken on some message structures
• Issue 0002699: [VeeCAN] Add support for "HotAreas"
• Issue 0003758: [VeeCAN] (VeeCAN 320) Buttons & text for buttonbar are not well aligned
• Issue 0003763: [RCM80] DG PU/PD software selectable
• Issue 0003764: [RCM80] RCM80: Enable SBC based low power mode
• Issue 0003755: [GCM048] GCM48: Implement a basic stack monitor
• Issue 0003728: [RCM80] Trigger Config block does not properly adjust the desired trigger rate
• Issue 0003703: [General] Add option to select LDFs using a file explorer (LIN Master Def., LIN Slave Def. blocks)
• Issue 0003735: [Build] Build warning with the fault manager
• Issue 0003682: [GCM048] GCM48:Disable wake-on-CAN via app software in the powerup/down subsystem
• Issue 0003108: [Build] Create a new folder for EXE/HEX files instead of using the A2L folder
• Issue 0003497: [Build] Port issue 3020 fix to CAN Pack blocks, too
• Issue 0003726: [General] LIN Rx message block gain/offset fields aren't being read correctly.
• Issue 0003681: [UDS] Add a Success/Failure callback for Security Access request
• Issue 0003213: [General] Add Access Level to raptor_string block
• Issue 0003707: [Build] Add cross-reference checks for Input Capture blocks
• Issue 0003706: [Build] Add name checks for misc. blocks
• Issue 0003705: [Build] Table blocks don't check if their names are valid in C
• Issue 0003704: [Build] Some fault blocks don't check if their names are valid in C
• Issue 0003655: [Build] Add or modify Regression/Unit Tests to check for invalid names
• Issue 0003699: [J1939] SPN & PGN searches are inefficient
• Issue 0002326: [J1939] Update J1939 PGN Transmit and other blocks for latest SAE spec revision
• Issue 0003660: [Build] LIN: Provide feedback when improperly formatted LDFs are specified in the Definition block
• Issue 0003656: [Build] Add CTRL-D checks for CAN & LIN definition blocks when set to use the same hardware
• Issue 0003708: [Build] Add cross-reference checks for LIN blocks
• Issue 0003690: [General] New Ctrl+D update errors are nice, but they're still popping up one at a time requiring many Ctrl+D iterations
• Issue 0003646: [Build] raptor_create_project fails to build with the CSM
• Issue 0003684: [GCM196] GCM196: BSW_Cals section incorrectly sized
• Issue 0003697: [Build] Remove DEFINES_OTHER warning from build

Test reports for 2021a_2.0.14255 are available here.

2021a.1.0.14082

• Issue 0003572: [Build] Add Function-Call Collector Block
• Issue 0003449: [Build] No build warnings/errors for signals defined to overlapping bits insde a DBC file on a CAN Tx Message block
• Issue 0003570: [General] Remove blue block color for Adjustment so it matches every other Raptor block.
• Issue 0003322: [VeeCAN] VeeCAN 700 Select Color Button Redirects User Out of Current Window
• Issue 0003359: [Build] Lookup Tables do not report an error when dimensions exceed 128
• Issue 0003518: [GCM80] Cannot type to enter faults into OBD Fault Manager fault map tool
• Issue 0003538: [Build] Build Error from CAN State Block if CAN Def block CAN bus name is not 'CAN1'
• Issue 0003595: [General] Fixed NV Manager Unhandled Exception When Deleting
• Issue 0003601: [Build] Additional CTRL-D Update Time checks (duplicate names defined)
• Issue 0003602: [General] CAN RX message and CAN TX message configuration window buttons in wrong place covering up signals
• Issue 0003639: [GCM196] Code to Model and Model to Code report generation not currently supported
• Issue 0003650: [GCM048] CAN Mailbox properties box generates C variable name issues if a variable is used as the input
• Issue 0003653: [Build] Some modules won't compile if CAN bus name doesn't match the resource name
• Issue 0003654: [J1939] Some J1939 modules won't compile if CAN bus name doesn't match the resource name
• Issue 0003658: [Build] CTRL-D name check in raptor_override block doesn't catch all invalid names
• Issue 0003659: [Build] Trigger block names aren't checked for validity
• Issue 0003662: [Build] Screen blocks don't check for valid names
• Issue 0003661: [Build] Calc Checksum block doesn't check for valid names
• Issue 0003675: [Build] Upgrade Raptor Libraries to use R2019a
• Issue 0003631: [UDS] UDS Client Compiler Error on HCM-5604-36-1303
• Issue 0003596: [General] Add Support for M47 (UAS-5743R-047-2102)
• Issue 0003584: [VeeCAN] Add Support for File Logging to DISP-VC300R-2004
• Issue 0003582: [GCM196] Compiler error when using rising edge triggers
• Issue 0003571: [Simulation] Nested Timed Triggers Error for simulation
• Issue 0003547: [UDS] Add Client mode to UDS handler
• Issue 0003498: [General] Graphical bug
• Issue 0003254: [General] Hbridge Current Feedback Mask doesn't change units when not measuring "Engineering units"
• Issue 0003078: [General] Raptor isn't applying the correct scaling called out in this LIN LDF
• Issue 0002861: [Build] Make BuildUID, Raptor Version, etc available to the application software
• Issue 0001874: [ECM196] Please specify degBTDC for angle units on raptor_spark_out and raptor_injector_out
• Issue 0002752: [Documentation] GCM-5634M-070-1562 Datasheet discrepancies (isundin)
• Issue 0003179: [General] CAN State Block can reference CAN hardware that isn't defined by CAN Def block
• Issue 0003441: [Build] Adapt output does not work on the Interpolation 2D block
• Issue 0003465: [[Internal] Test Framework] Add Or Modify Regression/Unit Tests to Include Custom CAN Bus Names
• Issue 0003399: [Documentation] Datasheet update: note on GCM48 Hbridge that it PWMs the low side of the bridge
• Issue 0003290: [Build] Code placed at the top level of the model (i.e. anything in the model "step" function) is not stopped by the app monitor
• Issue 0003474: [Build] Allow for a single mask for an array of IDs in the CAN Rx Raw Block
• Issue 0003373: [VeeCAN] Add XCP connected block
• Issue 0003679: [RCM80] RCM80: Add Support for board revision 1.5
• Issue 0003565: [J1939] TLC error in ML R2021a with the J1939 DMA block
• Issue 0003561: [GCM048] Add support for the GCM-5605B-048-2104
• Issue 0003652: [VeeCAN] VeeCAN128 can not handle high CAN bus loads
• Issue 0003673: [UDS] TLC error when turning off Session Control callbacks
• Issue 0002599: [J1939] Please add options for isValid/isAvailable outports on Raptor J1939 SPN Read block
• Issue 0003568: [Build] Raptor Data Read in Vector and Matrix mode outputs the first element when connected to a measurement
• Issue 0003564: [J1939] Some blocks report a TLC error regarding expression usage in MATLAB R2020a/b
• Issue 0003516: [Build] Add support for MATLAB 2021a
• Issue 0003304: [BCM48] Behaviour of WAKE_SOURCE measurement doesn't behave like the datasheet describes
• Issue 0003641: [GCM048] GCM48 PWM Inputs do not update after the module runs after a long time
• Issue 0003190: [GCM048] GCM48: Checksum Block not supported
• Issue 0003045: [Build] Add option to XCP Def block as to what storage to use for the Id Calibrations
• Issue 0003550: [RCM80] Compiler warnings with OBDCounters in OBD Fault Manager
• Issue 0003398: [GCM048] output_status block doesn't work on GCM48
• Issue 0003205: [GCM048] H-bridge current feedback not accurate
• Issue 0003668: [GCM196] MPRD Fault Status Appears to be broken
• Issue 0003545: [VeeCAN] Compiler error when FILE_T is not included in <model>_types.h
• Issue 0003043: [ECM196] LIN Messages with unused bytes at the start of the message can report incorrect results when read
• Issue 0003657: [UDS] UDS : Generated code can have an improper header inclusion in some cases
• Issue 0002841: [Build] Additional CTRL-D Update Time checks (check for define blocks)
• Issue 0003645: [GCM70] raptor_create_project GCM70 error
• Issue 0003546: [UAS50] UNUSED macro redefined
• Issue 0003647: [General] Internal Measurements in ML2021a error
• Issue 0003504: [General] Update Raptor Getting Started Guide
• Issue 0003640: [Build] LIN Parser does not work with French Localization
• Issue 0003124: [Build] LIN Rx/Tx blocks do not generate correct code when no frame is available
• Issue 0003241: [General] Add option to CAN Rx Msg (DBC) block to output Raw Data Byte Array
• Issue 0003563: [GCM70] Enable custom security on Programming
• Issue 0003063: [GCM196] Constant data sent to a CAN Tx raw block leads to a build warning
• Issue 0003082: [Build] dec2hex input in ecu address within Target Configuration block produces cryptic error
• Issue 0003552: [Build] CAN RX Block does not allow hiding of the Age port from the GUI
• Issue 0003580: [Build] No update error when a signal that is greater than 32 bits is specified in a DBC file
• Issue 0003410: [General] Removing a variable from FixedNV is not intuitive.
• Issue 0003549: [VeeCAN] Data type conversion compiler warnings when compiling some CAN configurations
• Issue 0003548: [GCM048] Compiler warnings when compiling some CAN configurations
• Issue 0003378: [Build] Support ISO14229 Service 0x2F - InputOutputControlByIdentifier
• Issue 0003574: [Build] Revert Code efficiency for fault action function "getNextFaultByAction" due to increased RAM usage
• Issue 0003573: [GCM048] Extended CAN frames have SRR bit set incorrectly
• Issue 0003060: [Build] Table Adapts assigned to a non-editable table build successfully
• Issue 0003288: [GCM80] GCM80 Output 8 Pin Error in Controller Overview Table on Datasheet
• Issue 0003542: [RCM80] Add Support for RCM80
• Issue 0003478: [Build] Fixed NV Status block causes build errors if no Fixed NV is present
• Issue 0003664: [Build] Display buttons missing CTRL-D checks

Test reports for 2021a_1.0.14082 are available here.

2020b.2.2.13891

• Issue 0003577: [Build] Revert Code efficiency for fault action function "getNextFaultByAction" due to increased RAM usage
• Issue 0003578: [GCM048] Extended CAN frames have SRR bit set incorrectly
• Issue 0003579: [Build] Some blocks report a TLC error regarding expression usage in MATLAB R2020a/b

2020b.2.1.13853

• Issue 0003557: [GCM70] Enable custom security

2020b.2.0.13839

• Issue 0003476: [Legacy] Update Redundant NV strategy for the HCM-5604-36-1303 and HCM-5604-36-1702
• Issue 0003512: [Build] VeeCAN can report an out of bound ECU Address even if there is no Target configuration available
• Issue 0003537: [Build] UDS : Flow Control StMin is not being honored during multipacket transmit
• Issue 0003507: [BCM48] XCP CAN Transmit callback missing from build
• Issue 0002989: [VeeCAN] Add Redundant NonVolatile for the VeeCANs
• Issue 0003501: [GCM196] GCM196 Not turning off MPR after keyswitch is turn off.
• Issue 0003505: [Build] UDS : Warning when building service 0x10
• Issue 0003536: [Build] UDS: Service 0x19 compile errors when using Standard Fault Manager
• Issue 0003239: [GCM048] GCM48: add option to output fixed point datatypes from the raptor_appmonitor_measurement
• Issue 0003494: [VEECAN500] Add support for the NonVolatile Startup block to VeeCAN 320, 500, 700, and 300R
• Issue 0003509: [Build] UDS: Timing parameters missing from Session Control Service (0x10) positive response
• Issue 0003508: [Build] UDS : Extended IDs are not transmitted
• Issue 0003442: [Build] Table Lookups adapt overflow logic causes a compiler warning
• Issue 0003022: [Build] A data store with an initial value of inf or -inf leads to a build error
• Issue 0003527: [VeeCAN] Image file extensions are case sensitive
• Issue 0003520: [Build] Add Ability to pass UDS Flash Ids to Raptor-CAL from the application
• Issue 0003510: [GCM196] Code efficiency for fault action function "getNextFaultByAction"
• Issue 0003491: [General] DBC Unpack title now says Pack
• Issue 0003514: [GCM048] Build warning when using XCP handler
• Issue 0003521: [VeeCAN] Compiler error when code is inlined from a Fault State Iterator block
• Issue 0003539: [VeeCAN] Build Error when writing a nonzero value to the "KEYPAD_BACKLIGHT" PWM output
• Issue 0003480: [GCM048] GCM48: Add Support for Printf Block
• Issue 0003394: [VEECAN500] VeeCAN 500 simulator crashes if no Kvaser is connected to the PCs USB ports
• Issue 0003515: [GCM196] CAN and J1939 can cause a linker error with the initialized RAM section
• Issue 0003526: [General] "Output Engineering Units" checkbox doesn't always show when "Platform Items" is selected
• Issue 0003502: [Build] Compiler error when no NV data store is in model
• Issue 0003443: [Build] Table Lookups generate floating point numbers for index inputs which causes compiler warnings
• Issue 0003492: [GCM196] Update the XCP DAQ List count to reflect that the XCP DAQ List count must be strictly greater than the Tx Message Queue
• Issue 0003503: [General] Generated CANape A2L works with INCA

Test reports for 2020b_2.0.13389 are available here.

2020b.1.0.13770

• Issue 0003391: [GCM048] Missing dependencies / shared objects on build.
• Issue 0002838: [General] Fault Definition block allows invalid values for X and Y counts
• Issue 0003404: [VeeCAN] Move VeeCAN 300R CAN functions out of idle time
• Issue 0003447: [Build] Table axis not patched with mask conversion
• Issue 0003093: [GCM80] Spurious reset when Raptor-Cal monitoring with Priority Queues and DAQs
• Issue 0003448: [Build] Strange text in update errors in MATLAB R2019b
• Issue 0003481: [Documentation] Update Block Help Images
• Issue 0003484: [GCM048] GCM48: Regression: App monitor tripping in raptor_create_project default model
• Issue 0002613: [Documentation] Enhance help for CAN
• Issue 0003292: [Build] ISO14229 UDS blockset support Version 2.0
• Issue 0002361: [GCM196] GCM196's five frequency inputs read four different duty cycles when the same PWM wave is applied to them all
• Issue 0003036: [VEECAN500] VeeCAN 500/700/300R fails to build when using a unsigned integer lookup table
• Issue 0003462: [GCM70] Update raptor_create_project to create models for the GCM70 that follow recommended power up/down logic.
• Issue 0003395: [Build] Add "raptor_build_profile" which will automatically enable MATLAB profiling during raptor update and builds
• Issue 0003421: [VeeCAN] VeeCAN 128 fails to build with redefinition of CONSTVariables
• Issue 0003440: [VeeCAN] Digital Outputs can't be held for more than 1 second with SDK 4.10
• Issue 0003445: [GCM196] GCM 196 Can Queue Info error on mask open
• Issue 0003466: [GCM70] GCM70 CAN Bus Name change for CAN1 causes module to not be reflashable
• Issue 0003473: [GCM70] raptor_can_state block does not function in GCM70 model
• Issue 0003380: [GCM80] GCM80: Limit of 64 CAN Tx or RX slots per bus.
• Issue 0003389: [VeeCAN] Remove support of the VeeCAN 800
• Issue 0003384: [VeeCAN] Combine the 500, 700 and 300R simulator implementations into a single common implementation
• Issue 0003305: [GCM048] GCM48: CAN Queue Depth & Max depth show as uint32 on the mask but really a uint8
• Issue 0003065: [GCM048] GCM48: Logic under CAN mailbox triggers continues to execute when the app monitor trips/pauses
• Issue 0003446: [Build] Support ISO14229 Service 0x14 - ClearDiagnosticInformation
• Issue 0003463: [GCM80] GCM80 H-Bridge Output block has a broken mask
• Issue 0003361: [VEECAN500] Add support for Gestures (swipe left,right,up,down) to VeeCAN500, 700 and 300R
• Issue 0003419: [GCM80] CAN state block "State" variable is incorrect
• Issue 0003450: [Build] Build error when combining J1939 PGN Receive, Simulink Functions, and vector Data Store write
• Issue 0003251: [GCM196] Block assignment build issue
• Issue 0003464: [VeeCAN] VeeCAN 128 : Return an error if an image file with a .bmp extension is used
• Issue 0003468: [GCM80] space in path causes GCM80 build to fail
• Issue 0003454: [Build] Update Raptor-elf and Raptor-gen-a2l to work with RCM112 hightec compiled elf files
• Issue 0003455: [GCM70] MotorPhaseVSense_A/B/C as freq_in causes build error
• Issue 0003112: [GCM80] GCM80: Gateway dropping about 35% of the messages
• Issue 0003411: [VeeCAN] Port the improved CAN Rx logic on the 300R to the 500 and 320
• Issue 0003385: [Build] Support ISO14229 Service 0x19 - ReadDTCInformation SubFunction 1,2, 0xA, and 0x15
• Issue 0003372: [Build] Add ISO15031 Service 0x03, 0x07, and 0x0A to UDS blockset
• Issue 0003417: [GCM80] Build fails when building with the CRC block
• Issue 0003416: [UAS_48] Build error when using CRC block
• Issue 0003431: [General] raptor_can_rxmsg OpenFcn error for zero-byte messages
• Issue 0003017: [VEECAN500] VeeCAN CAN Tx block queues can get stuck if there is noise on the bus
• Issue 0003436: [Build] Configure the J1939, data logging, modbus, and UDS blocksets to appear in the Simulink "Quick Insert" feature
• Issue 0002614: [Documentation] CAN Rx Message block does not have a help button
• Issue 0003348: [GCM196] CAN state blocks from GCM48 build ported to GCM196 causing generated C file errors
• Issue 0003415: [VeeCAN] OBD Fault Manager causes a build failure with the VeeCANs
• Issue 0003427: [General] "extern" keywords in IS015765 code cause build errors
• Issue 0003377: [Build] Support ISO14229 Service 0x28 - Communication Control
• Issue 0003374: [VeeCAN] Build Error with Digital Inputs and Internal Measurements in newer versions of MATLAB
• Issue 0003418: [GCM80] GCM80 fails to build with custom CAN names and CAN state block
• Issue 0003424: [VeeCAN] VeeCAN 320L builds sometimes fail with TLC errors
• Issue 0003408: [VeeCAN] Eject Status with SDK 4.10 is not correct
• Issue 0003282: [VeeCAN] Add support for the DISP-VC300R-2004
• Issue 0002396: [VeeCAN] Update VeeCAN 320/L SDK to 4.1
• Issue 0003401: [Build] Support ISO14229 Service 0x85 - Control DTC Setting
• Issue 0003397: [Build] Create Method to Configure XCP CALLBACK from target XML
• Issue 0003407: [Build] Add support for MATLAB 2020b
• Issue 0003365: [Build] Build error in MATLAB 2020a and the injector, spark, xcp, J1939 CI, and knock input blocks
• Issue 0003345: [General] Can't save Raptor_Lib in 2018b
• Issue 0003369: [Build] MathWorks tools cannot find ert_main.c and displays a message in ML R2020a
• Issue 0003386: [GCM048] GCM48: Including math.h can cause linker and compiler errors
• Issue 0003375: [Legacy] FIXEDNV w/Merged cals reverts on CM711
• Issue 0003327: [Documentation] GCM80 AN4-9 circuit/pull-up voltage not accurate

Test reports for 2020b_1.0.13770 are available here.

2020a.2.0.13564

• Issue 0003356: [BCM48] Limit of 64 CAN Tx or RX slots per bus
• Issue 0003319: [Build] CAN message blocks accuracy
• Issue 0003352: [BCM48] Defining 64 or more CAN msgs on a single CAN channel, build succeeds but channel is inoperable.
• Issue 0003324: [Legacy] EEPROM, First Start flag after programming
• Issue 0003316: [VeeCAN] VeeCAN USB drive detection logic can take 30ms to execute
• Issue 0003284: [VEECAN500] Upgrade to SDK 4.1.0
• Issue 0003278: [VeeCAN] Support the DISP-VC700-2003
• Issue 0003346: [Build Machine] "U" in data.xml file causes ASAP2 generation error
• Issue 0003301: [General] Override blocks cause update failures due to raptor_get_param_eval
• Issue 0003297: [BCM48] BCM48 CANTx logic misses deadline by 10ms (foreground rate)
• Issue 0003323: [VEECAN500] Upgrade the auto-installed compiler to version 5.4.2
• Issue 0003121: [VEECAN500] USB drive not detected if inserted before the power is turned on
• Issue 0003309: [BCM48] BCM48 CAN1 / Reprogramming Baud Rate Options

Test reports for 2020a_2.0.13564_ReleaseReports.zip are available here.

2020a.1.0.13532

• Issue 0001822: [General] ISO14229 UDS blockset support Version 1.0
• Issue 0002708: [VeeCAN] VeeCAN CAN baudrate configurable at initialization
• Issue 0002775: [GCM80] GCM80 is not receiving some messages in some configurations
• Issue 0003011: [VEECAN500] Error during build when raptor_trigger_def block is in a model without the raptor_trigger_ref block
• Issue 0003038: [General] Please add "Include Raw Outputs" option/functionality to Raptor DBC Unpack block
• Issue 0003069: [Legacy] Raptor NonVolatile Status not updating
• Issue 0003110: [General] If you open a model without the DBC on your path, it disconnects all ports of all CAN blocks and won't reconnect them
• Issue 0003144: [General] MATLAB locks up when you try to resize this CAN Rx block
• Issue 0003164: [General] Raptor Dev Silent Installer Gets Hung Up By Dependencies
• Issue 0003184: [Build] Add Support for MATLAB 2020a
• Issue 0003185: [VeeCAN] Updating a VeeCAN with a different VeeCAN image (e.g. 320 onto a 500) bricks the target
• Issue 0003191: [BCM48] BCM48: Background Period is not being honored
• Issue 0003192: [GCM196] GCM196: Tasks Periods are not always honored
• Issue 0003194: [GCM80] GCM80: Tasks Periods are not always honored
• Issue 0003197: [GCM80] Total EEPROM Build Statistic Incorrect for GCM80 Without Fixed NV Used
• Issue 0003202: [GCM048] H-Bridge Current Feedback not working
• Issue 0003203: [GCM048] Remove LSO ENABLE Digital Output option within GCM48 sw
• Issue 0003206: [Build] Unit Test directories are present in the installer
• Issue 0003208: [GCM048] Some LIN configurations put module in odd state
• Issue 0003214: [General] System Variable Access Level block doesn't control the access level of the XCP_Security calibration
• Issue 0003216: [GCM048] Application build produces RPG/hex w/ missing/incorrect defaults
• Issue 0003217: [GCM048] LIN Transceiver should not be enabled if LIN isn't used in the application
• Issue 0003224: [VeeCAN] Occasional TLC errors when building VeeCAN models with some IO blocks
• Issue 0003226: [Build] Fix all the build warnings that compiling with MinGW exposes
• Issue 0003230: [GCM048] CPU idle time lower when foreground is 10 ms than 5ms with LIN Master
• Issue 0003231: [GCM048] GCM48: Each raptor_output_status block consumes 11% CPU idle time at 10msec foreground
• Issue 0003232: [VEECAN500] Remove flash at bootup
• Issue 0003233: [BCM48] BCM48 Extended IDs - block with open mask causes Matlab crash during build
• Issue 0003235: [GCM048] Master Request and Slave Response frames should always use Classic Checksum
• Issue 0003236: [Documentation] GCM48 DataSheet does not reflect the available baud rates supported.
• Issue 0003237: [General] New Eagle SDK libraries should be built from source during continuous build
• Issue 0003238: [GCM048] GCM48: Default model uses some floating point datatypes in the power up/down subsystem
• Issue 0003242: [GCM048] GCM48: Analog input 4 block mask in raptor dev doesn't match the pull up/down called out in the datasheet
• Issue 0003244: [Build] LIN Trigger block has a warning about a missing parameter in an underlying script
• Issue 0003245: [GCM048] LIN wake source measurement doesn't match datasheet
• Issue 0003247: [GCM048] Frequency inputs take too long to time-out
• Issue 0003250: [GCM048] GCM48: XCP connection unstable
• Issue 0003253: [GCM048] Application monitor doesn't turn off digital outputs, PWMs, and Hbridge when paused
• Issue 0003265: [GCM048] Bootloader CRC Check and RILPackager update
• Issue 0003266: [Build] Reduce execution time of XCP DAQ processor when there are multiple DAQs with the same multiple
• Issue 0003275: [GCM80] GCM80: Fails to read EEPROM
• Issue 0003298: [Build] DBC parser in german OS settings

Test reports for 2020a_1.0.13532 are available here.

2019b.3.0

• Issue 0003137: [GCM048] Add 10Kbps baud rate to LIN Slave and Master
• Issue 0003111: [GCM80] GCM80: CAN State blocks report gibberish data in Rx and Tx counters
• Issue 0003167: [GCM196] GCM196: Changing NV data during shutdown causes incorrect CRC calculation.
• Issue 0002946: [VeeCAN] Port VeeCAN 500 USB Data Logging updates to the VeeCAN 320/800
• Issue 0003113: [GCM80] EEPROM does not Load Default after Reprogramming
• Issue 0002811: [VeeCAN] VeeCAN 320/320L Updated Template
• Issue 0003159: [GCM80] GCM80 datastore fixed NV selection not visible
• Issue 0003094: [General] AppMonitor idle calculation for additional triggers not correct
• Issue 0003059: [ECM196] Application with no EEPROM Data Stores fails to build
• Issue 0003074: [GCM048] GCM48: triggering storeNV block while running causes a module reset
• Issue 0003174: [VEECAN500] Some VeeCAN 500s are not compatible with Raptor 2019b.2 and earlier
• Issue 0003083: [Build] Change the Application Monitor to use fixed point operations for the Overrun Percentage calculation
• Issue 0003143: [GCM048] Add 33.3k baud rate to the CAN resources
• Issue 0002646: [General] Fixed NonVolatile blocks need some help text updates
• Issue 0002852: [GCM80] Add new GCM-5607B-80-1903 target
• Issue 0003139: [GCM048] Improve LIN Slave performance
• Issue 0003120: [Build] raptor_make_rtw sometimes locks the log file if the build fails
• Issue 0003126: [Build] MATLAB crash when changing a message name in a DBC pack/unpack block
• Issue 0002848: [Documentation] Missing Help Text: Fault Trigger - Global Trigger info
• Issue 0003163: [GCM048] GCM48 does not build source files under the slprj directory
• Issue 0002975: [General] If "can_example.dbc" isn't on your MATLAB path, the raptor_can_rxmsg doesn't work
• Issue 0003123: [Build] LDF files without Node Attributes lead to update errors with the Slave Definition
• Issue 0003095: [GCM80] GCM80: If you rename the buses to anything but CAN2, CAN3, or CAN4 the baud rate is stuck at 500K
• Issue 0003183: [GCM048] Adding Timed Trigger Config block to any GCM48 model causes the model to not build

Test reports for 2019b_3.0.13355 are available [https://software.neweagle.net/reports/Raptor_2019b_3.0.13355_ReleaseReports.zip here.

2019b_2.0.13282

• Issue 0002749: [Build] Add support for GCM48 ECU
• Issue 0003024: [GCM80] GCM80 loses XCP connection every few minutes and cant recover
• Issue 0003076: [General] Spelling errors in Raptor Help and can queue info block
• Issue 0002979: [J1939] Warning for J1939 TP address vs ECUaddr
• Issue 0002990: [GCM196] Add a 10k baud option on the GCM196 LIN bus
• Issue 0002888: [Build] RPG from a fresh build says it’s corrupted when I try to use it in RaptorCal
• Issue 0003080: [ECM196] Add critical region in the XCP callback
• Issue 0002980: [General] Add LIN Slave/Master support for GCM-5605B-048-1906
• Issue 0002982: [GCM196] Lookup Tables with FLASH storage and Boolean inputs to DBC unpack blocks cause build warnings
• Issue 0003051: [GCM80] Reports the incorrect reports the size of the available EEPROM
• Issue 0002966: [Build] Standard Fault Manager does not immediately assert the Active state when the X Limits are exceeded
• Issue 0002995: [Build] Raptor.Signal needs an attribute to allow editing from Raptor Cal
• Issue 0002992: [GCM196] If the LIN Definition block TLC executes before the LIN Rx/Tx blocks you can see a build error
• Issue 0002603: [General] Please organize mask parameters like Raptor Data Def
• Issue 0003025: [VeeCAN] Add documentation for Draw Line indicating it must be placed in the Screen Create/Update functions
• Issue 0003005: [J1939] J1939 ECU ID block does not size the buffer properly
• Issue 0002826: [GCM196] CAN transmit with 0 id can cause the bus to drop, and not reinitialize
• Issue 0002863: [General] Difficulty connecting to GCM196 w/Raptor-Cal
• Issue 0003044: [Build] Build error when using MATLAB enumerations with Simulink.Parameter
• Issue 0002986: [Build] Switching targets can sometimes lead to update errors with the sample time
• Issue 0003023: [GCM80] GCM80 cannot reflash an application without using recovery if there is a wide open standard CAN ID mask
• Issue 0003033: [GCM196] GCM196 Sensor Supply not 5V
• Issue 0002963: [VEECAN500] VeeCAN 500 build error when there is a trigger definition block
• Issue 0003006: [Build] Raptor.Signal/Raptor.Parameter should report an error if there are repeat values in the enumeration
• Issue 0002996: [GCM196] GCM196 EEPROM not saving due to "Incorrect CRC" error
• Issue 0002974: [Build] Table Adapt reports an incorrect error when the parent table block does not exist
• Issue 0002976: [VEECAN500] Cryptic build error when you try to use the OBD fault manager in a VeeCAN500 project
• Issue 0002973: [General] LIN Slave Definition returns a cryptic error when the block is opened and the behavior is not supported
• Issue 0002938: [General] Some invalid characters are missed by the Data Store Definition, Read and Write update checks

Test reports for 2019b_2.0.13282 are available [https://software.neweagle.net/reports/Raptor_2019b_2.0.13282_ReleaseReports.zip here.

2019b_1.0.13170

• Issue 0002919: [VEECAN500] Add support for USB port
• Issue 0002716: [Build] LIN Rx and Tx blocks do not filter out unneeded messages
• Issue 0002932: [UAS_48] Update task scheduler to be inline with GCM48 and CSM
• Issue 0002902: [VeeCAN] VeeCan builds without error (but buttons don't work) if the button def is in the screen's foreground
• Issue 0002933: [UAS_48] C48: Update CAN to use queued transmit
• Issue 0002709: [J1939] Add update error to DM1 Rx block when the transport block is not present
• Issue 0002894: [General] GCM48 : Add LIN Slave support
• Issue 0002945: [GCM196] Build fail to link when certain trig functions are included
• Issue 0002944: [General] Enumeration field still shown on double datatypes in Adjustment block
• Issue 0002840: [GCM196] J1939 DM1 Fault to Multiple Busses not possible
• Issue 0002621: [General] Add sort option specifier to CAN TX/RX dbc based blocks
• Issue 0002818: [Legacy] CM711 App monitor halt at 90% stack usage when enabled hardcoded
• Issue 0002819: [General] Ability to save App Monitor's 'count occurrence' value over power cycle
• Issue 0002911: [UAS_48] GCM-5746R-048 INJ1 and INJ2 not outputing correct duty cycle
• Issue 0002767: [GCM80] Model path can't accept space in path
• Issue 0002685: [GCM196] HighTec compiler must be installed in the default location
• Issue 0002859: [Build] XCP DAQ rate set < min FGND causes connection instability
• Issue 0002745: [General] Remove version checks for MATLAB versions less than 9.2
• Issue 0002893: [General] GCM48 : Add LIN Master support
• Issue 0002935: [Build] BCM48 and GCM196 builds fail when "(None)" resource is selected on the LIN Definition block
• Issue 0002895: [ECM196] Application with no Data Stores fails to build
• Issue 0002429: [Build] Changing loop time doesn't auto update Simulink's discrete time step
• Issue 0002914: [General] When "Output HEX/A2L Files" chosen in Raptor Target Definition block, new folder created in C:\ECU
• Issue 0002855: [Build] Add support for MATLAB R2019b
• Issue 0002903: [General] Simulink Library Browser Configuration Block Masks
• Issue 0002234: [Build] Mask parameters window wiggle
• Issue 0002908: [BCM48] BCM48 fails to build if there is a schedule specified but no frames specified in that schedule are present in the application
• Issue 0002524: [VeeCAN] VeeCAN data sheet generation doesn't consider future additions
• Issue 0002580: [GCM80] GCM80: CANrT Regression Test fails to build
• Issue 0002839: [General] Mixed-Multiplexed CAN Rx signals are un-checking themselves in the signal selection window
• Issue 0002912: [General] Clicking "En"/"Enable" on DBC-based GUIs causes error message
• Issue 0002871: [ECM196] E/GCM modules fail to build when XCP Definition block is removed from the model
• Issue 0002901: [VeeCAN] VeeCAN800 build error if "Output Hex/A2L" box is checked in target def
• Issue 0002783: [VeeCAN] VeeCAN 320/800 Simulator gets Foreground overruns when the serial blocks are present
• Issue 0002896: [VeeCAN] Goto Screen block does not display a screen name with an "_" properly
• Issue 0002791: [Build] CAN Tx/Rx Msg blocks do not update their signal content on update (CTRL+D) when the DBC is updated
• Issue 0002854: [Build] DBC block doesn't cover some of the signal corner cases covered by CAN msg blocks
• Issue 0002877: [Build] CAN RX data output can output garbage when the received message length is 0
• Issue 0002876: [UAS_48] No CAN RX on CAN2 if CAN3 is not present
• Issue 0002873: [UAS_48] Extended IDs cannot be greater than 18 bits
• Issue 0002862: [VeeCAN] VeeCAN simulators do not claim the CAN bus as they should
• Issue 0002865: [UAS_48] Error message states that the required compiler is the selection in the mask, but it should be S32 design studio

Test reports for 2019b_3.0.13164 are available here.

2019a_3.0.13046

• Issue 0002837: [General] Override block allows a non-One gain on boolean inputs
• Issue 0002821: [General] LDF File Comments Drop Signals with Lin Message Blocks
• Issue 0002735: [VeeCAN] Fault Action Measurements are single booleans, but the VeeCAN800 XCP_map thinks they are arrays, causing build errors
• Issue 0002857: [BCM48] Increase stack size (8Kb -> 16kb)
• Issue 0002817: [Build] CAN TX block processes a negative gain on a unsigned data type improperly
• Issue 0002845: [Simulation] Data Read/Write blocks do not report an error during simulation if the index is out of bounds
• Issue 0002849: [VeeCAN] VC128 Monochrome file names need to be different than the color versions of the same file
• Issue 0002805: [Simulation] Timed Trigger Simulation incorrect
• Issue 0002230: [Build] Add new DISP-VC128-1901 target
• Issue 0002688: [VeeCAN] Add new DISP-VC500-1904 target
• Issue 0002808: [Build] DBC-based blocks return a cryptic error in certain conditions
• Issue 0002810: [VeeCAN] VeeCAN 320 builds can report a TLC error with digital inputs in MATLAB R2019a
• Issue 0002802: [Simulation] Overrides do not support 8 bit or 1 bit datatypes during simulation

Test reports for 2019a_3.0.13046 are available here.

2019a_2.0.12937

• Issue 0002772: [General] DBC-based blocks freeze MATLAB in Raptor2019a
• Issue 0002755: [Build] rtwshared.lib build error in R2019a
• Issue 0002750: [General] Compatibility issue with COLUMN_DIR for arrays in ATI VISION
• Issue 0002760: [GCM80] GCM80 locks up PC during build if a mailbox trigger is used with an extended ID message
• Issue 0002682: [Build] Measurement block should not show display as string if ASAP2 (A2l) doesn't support it
• Issue 0002771: [VeeCAN] Initialization Screen bug: Doesn't call calibration screen
• Issue 0002779: [GCM196] OUTPUT49 (Active Low) doesn't initialize if 0
• Issue 0002781: [General] Standard Fault Manager does not assert Occurred when Active is de-asserted from the Fault Set State block
• Issue 0002754: [Build] Standard Fault Manager Occurred State is not persistent
• Issue 0002787: [GCM196] LIN Definition block added to model (only) - causes build error
• Issue 0002477: [GCM80] Implement LIN
• Issue 0002774: [VeeCAN] VeeCAN 800 buttons do not function correctly when the trigger subsystems are duplicates and use the default name
• Issue 0002675: [General] DBC Pack block causing MATLAB to crash with "Dot indexing is not supported" error when signals are renamed in DBC
• Issue 0002740: [J1939] J1939 Transport Protocol Transmit block's priority input not used in message transmit
• Issue 0002765: [VeeCAN] Gauge and TouchButton blocks report a parameter missing when the buttons are pressed
• Issue 0002766: [VeeCAN] Crash when changing the name of a touchscreen button
• Issue 0002725: [J1939] Add J1939 support for TIRE2 and update TIRE1
• Issue 0002737: [GCM70] GCM70 does not update its ERI Source Address when instructed
• Issue 0002700: [General] Please add Raptor Fault Manager option to not have suspected X/Y filtering
• Issue 0002733: [BCM48] BCM48: CAN TX is gated at the Foreground rate of 10 ms
• Issue 0002741: [GCM80] CAN queue issues presenting in Raptor-Cal connection stability issues
• Issue 0002744: [VeeCAN] Display Block Masks Don't Update
• Issue 0002793: [GCM196] 'Set Input Option' for INPUT31/INPUT32 to set Resistance Measurement Switch Incorrect block mask values
• Issue 0002710: [GCM196] GCM 196 H-Bridge Mislabel
• Issue 0002794: [Build] Selecting "boolean" in an adjustment block does not always show the "Display As" property

2019a_1.0.12792

• Issue 0002696: [Simulation] Raptor Periodic trigger block sometimes executes twice in a row in simulation
• Issue 0002694: [Simulation] Raptor dT block simulation output
• Issue 0002484: [GCM70] GCM70 EEPROM_State not being used is confusing
• Issue 0002654: [VeeCAN] Display template default logic for NV store is too simplified
• Issue 0002359: [J1939] A negative response to a PGN Request to the Global Destination Address (255) results in a NACK (but it shouldn't) on some module
• Issue 0002576: [Build] Raptor Fault Mapping Tool contains Global triggers in the Trigger mapping pane when they aren't mappable
• Issue 0002574: [Build] Raptor Fault Data Read/Write blocks report a port size error when trying to edit the block and no matching fault data exists
• Issue 0002573: [General] Build Error with Custom CAN Bus Name
• Issue 0002557: [Build] Allow Raptor to schedule positive sample times specified in blocks
• Issue 0002639: [General] AppMonitorState calibration won't hold over power cycle
• Issue 0002324: [GCM196] Target definition block selection update does not restore cancelled values
• Issue 0002505: [BCM48] When BCM48 calibrations are stored in NonVolatile and the NonVolatile is no longer functional, the module doesn't boot
• Issue 0002358: [GCM196] GCM196 OUTPUT34 actuation seems inverted; no fault status
• Issue 0002577: [BCM48] Standard Fault Manager does not compile on BCM48
• Issue 0002521: [GCM70] Raptor J1939 blocks not supported with GCM70 module
• Issue 0002582: [Build] Update Standard Fault Manager to have parallel states
• Issue 0001245: [Build] BCM48 RX ID Limit
• Issue 0002509: [GCM196] GCM196 fails to build when no NonVolatile is present
• Issue 0002491: [VeeCAN] Add Raptor_Display_Lib to simulink quick search
• Issue 0002032: [General] Global, Data Dictionary View of Model data items
• Issue 0000721: [General] Support Matlab Fixed point data types
• Issue 0001991: [General] Add Enum data type to Adjustments, Measurements, and Data Stores
• Issue 0002406: [Build] Build warnings with Fault Trigger block
• Issue 0002523: [General] Multiplexed Transmit has some confusing behavior
• Issue 0002540: [Build] Add Support for MATLAB 2019a
• Issue 0002536: [GCM70] Update Documentation for LSO3 to indicate the limitation on Current Measurement
• Issue 0002394: [General] In some situations, the "string" designation on the CAN Bus property on the CAN RX Msg block is lost
• Issue 0001970: [VeeCAN] VeeCAN 320 not transmitting BuildUID correctly
• Issue 0001966: [VeeCAN] VeeCAN 320 sending unexpected XCP messages
• Issue 0002386: [Build] Add J1939 support to the GCM80
• Issue 0002503: [Build] Some header and source file inclusion mechanisms do not work properly
• Issue 0002504: [VeeCAN] VeeCAN crashes when a XCP BUILD_CHECKSUM (0xF3) command is sent to the module
• Issue 0002464: [Build] GCM70, VeeCAN, GCM196 CAN Transmit queues overwrite the beginning of the queue when there is an overflow
• Issue 0002420: [GCM196] Shorting CAN1 Hi to ground causes communication malfunction
• Issue 0002421: [GCM196] Shorting CAN2 Hi to ground causes communication malfunction
• Issue 0002463: [GCM80] GCM80 CAN Transmit queues overwrite the beginning of the queue when there is an overflow
• Issue 0002454: [Build] BCM48 CAN Transmit queues overwrite the beginning of the queue when there is an overflow
• Issue 0002458: [Build] Override block should support MathWorks Fixed Point and Enumerated types
• Issue 0002441: [BCM48] BCM48 sometimes misses CAN transmits if too many messages are sent simultaneously
• Issue 0002439: [Build] Make it easier to specify an enumeration in a Raptor block with a MathWorks enumeration
• Issue 0002440: [Build] French Windows Localization causes an issue with A2L generation and subsequent packager
• Issue 0002223: [General] If FaultOperation calibration is set to "Disabled", none of the diagnostic code should be run for that fault
• Issue 0002424: [VeeCAN] VeeCAN 800 simulator crashes when the Menu block is added
• Issue 0002349: [Build] Cryptic error when building a model with J1939 but no Time blocks present
• Issue 0002413: [General] Please make the access level of these calibrations to 1
• Issue 0002411: [Build] All targets have invalid XCP response to "FF" command
• Issue 0002366: [Build] Compiler warning occurs with 2D array initializers
• Issue 0001142: [VeeCAN] Initial Screen not being set correctly
• Issue 0002382: [J1939] PGN Request to global address should result in a response to the global address (BAM) for multipacket messages
• Issue 0002374: [Build] Have Raptor respect the Simulink.fileGenControl settings
• Issue 0002362: [General] Cryptic error when a LIN Rx block uses a name that is not used in a LIN definition block
• Issue 0002360: [J1939] GCM 80 has a build error when the J1939 transport protocol block is included in the model
• Issue 0002371: [VeeCAN] The first "Constant" variable in the "constmap" fails to load
• Issue 0001011: [Build] build does not fail w/ Matlab fixed point datatypes
• Issue 0002251: [Build] Fault State Count block is counter-intuitive
• Issue 0002388: [General] Fixed point specification combined with an adjustment with back inherit data type causes MATLAB to crash
• Issue 0002363: [General] Can't open a table in Raptor Cal
• Issue 0002241: [Build] No error when updating a model with misconfigured Row and/or Column Headers

2018b_2.1.12454

• Issue 0002506: [Build] Set Fault State block reports an error on opening the Mask.
• Issue 0002558: [Build] Fault status block causes build error when connected to iterator
• Issue 0002527: [General] Standard (non OBD) Fault Manager fault status should allow multiple statuses (Active, Occurred)
• Issue 0002511: [GCM80] GCM80 Can Baud Rates are fixed at 500K
• Issue 0002516: [BCM48] BCM48 doesn't transmit messages on CAN3 after reprogramming or cold power up (not wake pin)
• Issue 0002522: [BCM48] BCM48 Wake Source Internal Measurement Input 2 Reads Wrong Resource

2018b_2.0.12453

• Issue 0002231: [General] Add GCM-5607B-80-1901 target support
• Issue 0002367: [General] GCM-70-1559 Datasheet AI Inconsistent PU/PD
• Issue 0002403: [General] Raptor CAN block GUI doesn't open if payload mask/value set
• Issue 0002404: [General] Dropdown menu changes in Raptor CAN block change ID/Mask
• Issue 0002408: [Build] DBC Pack/Unpack Label Wires doesn't seem to have an effect
• Issue 0002409: [Build] DBC Pack/Unpack Block isn't working with Signed Big Endian signal
• Issue 0002412: [BCM48] Error in S-function raptor_ethernet_socket_state
• Issue 0002415: [GCM70] Can't reopen Freq In mask for MotorPhaseVSense resources
• Issue 0002417: [BCM48] BCM48 CAN timing imprecise for models with many messages
• Issue 0002425: [GCM70] 1559 MotorPhaseVSense frequency inputs not functional
• Issue 0002437: [Build] Images for the Help are not cropped correctly in released Raptor Versions

2018b_1.1.12443

• Issue 0002393: [Build] Multiplexed CAN Messages are not being handled correctly Raptor

2018b_1.0.12429

• Issue 0002375: [BCM48] BCM48 enable overcurrent shutdown on OUTPUT1/4/7/8, HBRIDGE11_12, HBRIDGE13_14,
• Issue 0002370: [GCM196] Please remove "Pump Diag" port on Raptor WideBand O2 Input block
• Issue 0002357: [Build] CRC_13000 models are failing regression tests
• Issue 0002275: [GCM196] Raptor Output Status Blocks
• Issue 0002323: [Build] GCM196 : build error with Table Axis and Interpolation table set to initial value of 0
• Issue 0002092: [Build] It is possible to Configure XCP DAQ list in a way that would exceed the CAN Definition TX Queue Size
• Issue 0002218: [General] Add field to J1939 ECUID Transmit block
• Issue 0002356: [GCM70] Time Block can cause a compile error on the GCM70 modules under certain conditions
• Issue 0002354: [VeeCAN] VeeCAN serial reports build warnings
• Issue 0002265: [GCM196] Bootup J1939 Address Claiming doesn't work on GCM196
• Issue 0002242: [GCM196] GCM196 : LIN Set Schedule block causes issue with slave transmit
• Issue 0002106: [GCM196] ECM196 OUT9/12, Hbridge output diagnostics not working correctly
• Issue 0002130: [Build] Allow VISION strategy creation for SR output targets
• Issue 0002342: [GCM196] Input 43 on GCM 196 datasheet mislabeled
• Issue 0002343: [GCM196] Add 'Set Input Option' for INPUT31/INPUT32 to set Resistance Measurement Switch
• Issue 0002333: [BCM48] BCM48 LIN definitions set to '(None) resource gives cryptic build error
• Issue 0002335: [GCM196] Increase User Stack from 5K to 10K
• Issue 0002320: [Build] Build fails when Embedded Coder drops code into the "shared utility" directory
• Issue 0002227: [Build] Raptor Configuration editor won't run if MATLAB installation is corrupted
• Issue 0002107: [General] Update Raptor Checksum to additionally support 32-bit CRC in addition to current 16-bit.
• Issue 0002228: [Legacy] EEPROM driver init failure not indicated in EEPROM_State measurement
• Issue 0002287: [Build] OBD Fault Manager detection is not working when XLimit = YLimit
• Issue 0002312: [Build] Improve CAN DBC file selection warning and error reporting
• Issue 0002310: [Build] Improve the DBC parser logic to be tolerate of older DBC Formats.
• Issue 0002128: [GCM70] GCM70 internal temperature monitor
• Issue 0002288: [Build] Override block reports the wrong value in simulation
• Issue 0002258: [J1939] J1939 Transport protocol block ManufacturerCode NAME data field is too small
• Issue 0002253: [GCM196] Warning in Adapt Table logic comparing signed and unsigned
• Issue 0002169: [General] Fault Action Read block always outputs the correct value, but the Fault Action Def block sometimes outputs the wrong value
• Issue 0002237: [Build] Fill Unused Bits for DBC Pack block does not function
• Issue 0000732: [Build] Header Enumerations on Raptor Adjustment and Measurement blocks
• Issue 0002238: [Build] DBC Pack Block does not handle bigendian signals correctly
• Issue 0002222: [General] Reset X/Y counters if Y > YLimit - XLimit without fault being set
• Issue 0000155: [General] Allow cell string of faults in Raptor Fault Status block
• Issue 0002216: [Build] Raptor vector data read from an item defined as a scalar should produce an update error (CTRL-D)
• Issue 0002179: [General] Custom ID on CAN Tx block changes when "Fill Unused Bits" checkbox checked/unchecked
• Issue 0001014: [General] Memory Usage table difficult to read
• Issue 0002217: [General] Add Raptor Fault Reference block
• Issue 0002224: [General] Raptor J1939 DM5 block should be more like Raptor J1939 DM26 block
• Issue 0002233: [Build] Mask parameters window wiggle
• Issue 0002254: [Build] Behavior of the inline expression on a data read is different than the non-inline
• Issue 0002255: [GCM196] Warning with can rx boolean saturation logic on GCM196
• Issue 0002262: [Build] Convert the Analog Input block to use expression folding
• Issue 0002075: [GCM196] ECM196 ignition/injector output diagnostics not working correctly
• Update to NewEagle Licensing 12.5

2018a_2.0.12251

• Issue 0002211: [Build] LIN Tx Msg block build error with BYTE_ARRAY signal type
• Issue 0002209: [GCM196] GCM196 build fails if LIN Rx outputs are not connected, but succeeds if a raptor measurement is connected
• Issue 0001483: [Build] EEPROM configuration options requested
• Issue 0001894: [General] Separate EEPROM storage for ECU ID info
• Issue 0002201: [General] CAN RX & TX blocks error out when using a multiplexed CAN message
• Issue 0002126: [Build] Failure to build RPG package from a2l and .sr file
• Issue 0002205: [Build] Build error when ECU Definition 'Calibration Location' set to FLASH
• Issue 0002200: [BCM48] BCM48 periodic CAN transmit rates not accurate
• Issue 0002199: [BCM48] BCM48 CAN State Block
• Issue 0000153: [General] Consider removing Permanent setting/calibration on OBD blocks
• Issue 0002193: [Legacy] Parker ECUs - J1939 TP receive for Proprietary A2 - PGN 0x1EF00
• Issue 0002194: [Build] Build fails with error "Unable to read file buildInfo.mat"
• Issue 0002178: [Build] On a successful build the log file can be locked
• Issue 0002007: [GCM196] GCM196: INPUT29, analog ADC values incorrect
• Issue 0002181: [Legacy] Enable Redundant Non-Volatile Storage on the HCM-5604-36
• Issue 0002141: [General] Add Signal Order option to DBC Unpack block
• Issue 0002161: [Build] Discrete derivative block output not correct in some scenarios
• Issue 0002171: [General] Add obfuscation to raptor_fixednv_mgr_gui
• Issue 0002187: [BCM48] BCM48: INPUT3/4 Pullup/Pulldown configuration options ignored
• Issue 0002186: [BCM48] BCM48: CAN receive may not work for all RX message blocks, or IDs within masked range.
• Issue 0002114: [BCM48] BCM48 TCP sockets
• Issue 0001891: [General] Implement BCM48 LIN
• Issue 0002133: [BCM48] BCM48 wake on CAN
• Issue 0002134: [BCM48] BCM48 wake on LIN
• Issue 0002184: [BCM48] BCM48 XCP on extended 29-bit CAN ids causes ECU not to run
• Issue 0002175: [GCM70] GCM70 XCP Communication stops after some time
• Issue 0002162: [Build] CAN: Allow Mask ID to be edited separately from ID
• Issue 0002155: [GCM196] raptor_table_axis_reference block causes build error
• Issue 0002157: [Build] Fault manager, extra fault trigger calibrations can be generated
• Issue 0002154: [General] Transfer Calibration "Enumeration match not found"
• Update to NewEagle Licensing 12.3

2018a_1.0.12120

• Issue 0002123: [GCM70] On GCM70-1459 datasheet, pins 30 and 31 switched on block diagram
• Issue 0002116: [GCM196] GCM/ECM196, divide by 0 possible with 0 frequency applied to HBRIDGE block
• Issue 0002113: [BCM48] BCM48 UDP Sockets
• Issue 0002103: [General] Demux out of Raptor block results in incorrect values
• Issue 0002037: [Build] LIN blocks don't support byte_array signal type
• Issue 0002101: [GCM70] On GCM70-1459 datasheet, AN16 incorrect on block diagram
• Issue 0002102: [GCM70] GCM70 Analog In block lists resource as "XDPR"... please change to "XDRP"
• Issue 0002108: [GCM196] On interim 2018a build, GCM196 occasionally stops sending messages on CAN2 for approximately 110msec
• Issue 0001484: [Build] Add calibration to enable/disable custom security
• Issue 0002109: [Build] XCP User-Defined (Custom Security) Trigger causes model build
• Issue 0001290: [Build] GCM196 build fails if checksum blocks are present
• Issue 0002075: [GCM196] ECM196 ignition/injector output diagnostics not working correctly
• Issue 0002066: [General] Data stores and adjustments that are set to CONST are available for offline calibration.
• Issue 0001926: [General] Please review application monitor for proper operation with VeeCAN modules
• Issue 0002100: [VeeCAN] DISP-IMX286 floating point math efficiency improvement
• Issue 0002065: [General] Allow custom Raptor version in Raptor Toolchain Definition block
• Issue 0002055: [Build] Add Data Type Check for Measurement block
• Issue 0000909: [Build] Files during and after Raptor Build
• Issue 0002027: [GCM196] Please include reset reason as option from Raptor Internal Measurement block
• Issue 0002096: [GCM196] ECM196: ATI VISION strategy file created with pre-merge HEX file
• Issue 0002097: [Build] Create option to allow user to select Generating ATI Vision Strategy
• Issue 0002059: [General] Please apply these default encoder calibrations for the ECM196
• Issue 0002031: [General] LIN Tx/Rx: would like more info available in the get_param() command
• Issue 0001684: [Build] More consistent build statistics after a Raptor build
• Issue 0002090: [BCM48] BCM48: Ethernet (Socket) receive data output port not correctly sizing with Socket Definition Buffer Size
• Issue 0002080: [GCM70] GCM70: Move XCP Communications to Idle Task
• Issue 0001418: [Build] Add Raptor block to set access level of all under-hood variables
• Issue 0001957: [Build] Add support for the Simulink Discrete Derivative Block
• Issue 0002079: [GCM70] GCM70: LSO Diagnostics always return no fault.
• Issue 0002023: [General] Raptor lib blocks open as blank ??? when you right click on raptor library block and select library link --> Go to Library link
• Issue 0002021: [General] Raptor library blocks no longer are showing up as options in simulink library - used to work in last version of Raptor
• Issue 0001735: [General] Need some way to report max stack usage in Raptor-Cal; integrate stack margin into application monitor also
• Issue 0001927: [General] Please have Raptor automatically save model after build
• Issue 0002082: [General] Use of > 3 DAQ lists simultaneously doesn't work
• Issue 0001925: [Build] All PWM output should be disabled if Frequency is set to 0.
• Issue 0001850: [General] Mask Parameter Window Shaking
• Issue 0001400: [Build] Add a check box on CAN rx blocks to indicate if an exact match on DLC would be required.
• Issue 0002078: [General] Add Support for MATLAB 2018a
• Issue 0002077: [GCM70] GCM70: CPUIdle Percent is not displayed correctly in the cal tool.
• Issue 0002076: [GCM70] XCP Communication is Stop when application is in shutdown.
• Issue 0002074: [GCM70] GCM70 output SR file not compatible with Raptor-Telematics remote reflash
• Issue 0002073: [GCM196] GCM/ECM196, third-party calibration tool support XCP BuildChecksum can exceed time constraints
• Issue 0002067: [Build] Stack variables optimization
• Issue 0002072: [GCM196] GCM196: Error conditions on CAN X can affect transmit on CAN Y
• Issue 0001903: [Build] We need to implement a DBC parse lib and integrate with Raptor-DEV
• Issue 0002062: [GCM196] GCM/ECM196, add stack & other additional CPU monitoring variables
• Issue 0002030: [Legacy] BCM48 : Add 667kb CAN Baud Rate for CAN2,3,4
• Issue 0002002: [GCM196] Build error when using Input Status blocks set to INPUT46 (cam) or INPUT50 (crank)
• Issue 0002058: [Build] J1939 blocks should detect bus name error on CTRL-D
• Issue 0002052: [GCM196] All application tasks should be disabled when Shutdown Event is called
• Issue 0002050: [General] Integrated help content fixes
• Issue 0002051: [Build] Add integrated help for Raptor-Telematics liib
• Issue 0000732: [Build] Header Enumerations on Raptor Adjustment and Measurement blocks
• Issue 0001210: [Build] GCM196 J1939 Implementation
• Issue 0001981: [Build] 12 bit ADC availability for GCM70
• Issue 0002010: [Build] DBC Pack/Unpack expects a description on message definition
• Issue 0002131: Rpg packaging creates an unusually small and unusable program file (local appdata not accessible)
• Issue 0001872: [General] On raptor_injector_out and raptor_spark_out block, Hardware Resource should be changed to Starting Resource
• Issue 0002038: [Build] LIN LDF parser processing error when multiple 'Signal_representation' point to the same 'Signal_encoding_type'
• Issue 0002034: [Build] Input capture block always disabled if "Always enabled even when..." checkbox unchecked
• Issue 0002035: [General] Error when attempting to copy Input Capture Trigger block
• Issue 0001897: [General] Raptor App Trigger block always disabled if "Always enabled even when..." checkbox unchecked
• Issue 0001793: [General] Even if new index name specified, index name for 1D table still _LookupX
• Issue 0002022: [GCM196] Raptor generated A2L characteristics (on LITTLE_ENDIAN targets) have incorrect BYTE_ORDER setting
• Issue 0002013: [Legacy] BCM48 EEPROM
• Issue 0002007: [GCM196] GCM196: INPUT29, analog ADC values incorrect
• Issue 0002005: [GCM70] GCM70: Non Default installations of GCC cause a build failure at the link stage.
• Issue 0002004: [GCM70] GCM70: Disable CAN Self Reception
• Issue 0002001: [Build] Special characters in Units field of Adjustment cause build error (degree symbols etc..)
• Issue 0002118: GCM70: Non Default installations of GCC cause a build failure at the link stage.
• Update to NewEagle Licensing 12.2

2017b_0.3_SP2

• Issue 0002076: [General] XCP Communication is Stop when application is in shutdown.
• Issue 0002077: [General] GCM70: CPUIdle Percent is not displayed correctly in the cal tool.
• Issue 0002074: [General] GCM70 output SR file not compatible with Raptor-Telematics remote reflash
• Issue 0001981: [General] 12 bit ADC availability for GCM70
• Issue 0002004: [General] GCM70: Disable CAN Self Reception
• Issue 0002029: [General] Add Transmit and Receive Queue Size to the CAN Definition for the GCM070
• Issue 0002079: [General] GCM70: LSO Diagnostics always return no fault

2017b_0.2_SP1

• Issue 0001982: [Build] GCM70 Default Stack Size Increase
• Issue 0001986: [VeeCAN] Add fonts for VEECAN displays (3DS, 3DS Italic, 3DS bold)
• Issue 0001983: [Build] GCM196 : XCP read issue causes ECU reset
• Issue 0001973: [General] Raw Output for DBC Unpack block
• Issue 0001979: [Build] Remove stack size message from genlcf on the GCM070 builds
• Issue 0001978: [Build] Enable Current Feedback read on LSO3 on the GCM70 1562 variant
• Issue 0001977: [Build] GCM70 Internal Measurements do not work.
• Issue 0001976: [General] GCM70 CAN rx block queues
• Issue 0001975: [General] GCM70 CAN mailbox properties issues
• Issue 0001974: [General] GCM70 CAN Rx mask and age port
• Issue 0001969: [General] Add Raptor Telematics lib (STU)
• Issue 0001968: [Build] Raptor CAN Rx Raw block - error if 'ShowAge' is unchecked
• Issue 0001956: [General] Raptor Configuration editor - Start Bit Mode: setting to Kvaser has effect but shows blank on next open.
• Issue 0001952: [General] Raptor Fault Set doesn't show state
• Issue 0001920: [General] GCM196: CAN Msg Tx block, sending data into ID port > 0x7FF can result in message not being sent
• Issue 0001982: [Build] GCM70 Default Stack Size Increase
• Issue 0001989: [Build] Add Stack Margin Overflow detection to Application Monitor for GCM70 family of modules
• Issue 0001988: [Build] Application Monitor on GCM70 falsely triggers pause
• Issue 0001990: [Build] XCP/Raptor-CAL Sync issue on GCM70
• Issue 0001996: [General] Configuration Editor loses settings
• Issue 0001980: [Build] GCM70 App Monitor Min. Stack Size Probes
• Issue 0001993: [Build] DBC Pack block calculating incorrect start bit for Big Endian Signals
• Issue 0001999: [Build] GCM196: CAN Tx Queue heuristics

2017b_0.1

• Issue 0001573: [Build] MATLAB crash (related to Raptor license?) from closing/opening laptop lid
• Issue 0001434: [Build] Add LIN Blocks
• Issue 0001881: [Build] Implement 'Lite' mode
• Issue 0001779: [General] Upgrade to New Eagle Licensing V12
• Issue 0001885: [General] raptor_create_display_project does not build when Raptor OBD fault def put in
• Issue 0001895: [General] GCM/ECM196; Digital output glitch, certain outputs show 5ms glitch
• Issue 0001896: [General] GCM/ECM196: PWM duty cycle accuracy
• Issue 0001690: [Build] Clicking on Getting Started Guide link causes error in MATLAB command window
• Issue 0001810: [General] Matlab 2017a - Routing signals in Simulink freezes Matlab for extremely long periods of time
• Issue 0001882: [General] Fault Action Measurement
• Issue 0001809: [General] Generic dbc file based parsing blocks
• Issue 0001300: [Build] GCM196 - Low side outputs sink current when module shuts off
• Issue 0001814: [General] Raptor engine blocks should reference Firing Order from Raptor Encoder block
• Issue 0001815: [General] Raptor Encoder Definition block should only include settings needed at build time
• Issue 0001769: [VeeCAN] Download error during installation of CodeSourcery installer (for Displays)
• Issue 0001679: [Build] Mask Consistency and Display Info for Data Store, Adjustment, and Data Read Blocks
• Issue 0001868: [Build] raptor_gen_a2l optimization
• Issue 0000157: [General] Setting Raptor Table Interpolation 1D inside a library block causes link to become parameterized on update
• Issue 0001268: [General] Raptor Override and Measurement blocks cannot resolve propogated input wire names
• Issue 0001857: [Build] Warning: raptor_timed_trigger1' specifies that its sample time (-1) is back-inherited
• Issue 0001582: [Build] Questions on Raptor DM3 and DM11 functionality
• Issue 0001861: [General] Build error when Raptor Output Status block set to OUTPUT62 on ECM196
• Issue 0001867: [General] GCM/ECM196: CAN bus 125K, attempting to transmit ID 0x1000 w/ ext and std Identifiers
• Issue 0001638: [Build] Possible bugs in raptor_sfun_obd_fault_manager.tlc file
• Issue 0001864: [Build] Fault Data Read/Write with FaultSource from port become disconnected during model update (CTRL-D)
• Issue 0000160: [General] Raptor Fault Data Definition option to group with individual fault calibrations
• Issue 0001863: [General] OBD FaultManager, missing Previously MIL ON for FaultState settings
• Issue 0001693: [Build] Module reset if 1 bit field set to signed data type in Raptor CAN Rx block
• Issue 0001082: [Build] Passing in a 0 value uint8 or an int8 datatype to a CAN Tx signal of 8 bits produces unexpected CAN output
• Issue 0001813: [General] Remove Epm_numFireSeg_C from appearing as a calibration
• Issue 0001817: [General] CAM is not an acronym; please change instances to Cam
• Issue 0001808: [General] Add Raptor J1939 TP Transmit block
• Issue 0001856: [Build] SwId Build Number increment doesn't occur if building offline
• Issue 0001816: [VeeCAN] CAN Rx block sending incorrect signal
• Issue 0001552: [Build] uint32 data type coming from Raptor CAN Rx block
• Issue 0001722: [General] Raptor Table Interpolation 2D block still has old measurement variables
• Issue 0001550: [VeeCAN] VeeCAN 320L pinout images incorrect
• Issue 0001700: [Build] Raptor CAN blocks: update signal line name when press OK on GUI
• Issue 0001708: [General] Change initial value of 1/z in debounce in Power_Up_Down block
• Issue 0001853: [General] Matlab 2017b Support
• Issue 0001819: [General] Matrix Data Write can't find it's DataStore block
• Issue 0001812: [General] What is the difference between NumberCylinders and Epm_numCyl_C calibrations?
• Issue 0001848: [Build] undefined reference to '__ltdf2'
• Issue 0001833: [General] Initial value from CAN Rx Raw block not 0 for VeeCAN320
• Issue 0001832: [VeeCAN] VeeCAN Splashscreen 2017 Updates
• Issue 0001831: [VeeCAN] DISP-IMX286: Add Height from port capability to display_draw_text block
• Issue 0001825: [General] ECM196: Knock sensor diagnostics
• Issue 0001826: [General] ECM196 : Injector output diagnostics
• Issue 0001827: [General] ECM196 : Ignition output diagnostics
• Issue 0001828: [General] ECM196 : Crank / Cam input diagnostics
• Issue 0001830: [General] GCM/ECM196: Add MPRD output diagnostics
• Issue 0001276: [Build] GCM196 Doesn't have XDRP measurement
• Issue 0001506: [Build] GCM196: Feature request for more voltage internal measurements (if available)
• Issue 0001799: [Build] Raptor model updates (CTRL-D) should not require a Raptor-Dev license
• Issue 0001702: [General] Implement knock block(s) for ECM196
• Issue 0001780: [General] ECM196 : Add misfire detection blocks
• Issue 0001654: [Build] It seems that all spark outputs on raptor_spark block must be enabled for any to be enabled
• Issue 0001818: [Build] CAN tx Message block does not apply offset
• Issue 0001493: [Build] HardwareType enumerated value

2017a_0.0.1_SP1

• Issue 0001762: [Build] GCM196/EMC196 CAN linker error
• Issue 0001731: [Build] Multiplexed Messages can not be read from DBC in ML 2015b and newer.
• Issue 0001759: [VeeCAN] Enable resistance measurement mode on DISP-IMX286 inputs
• Issue 0001740: [General] GCM196/ECM196 Datasheet indicate configurable options of Pullup/Pulldown resistors on INPUTS 41,43,44
• Issue 0001767: [General] German localization causes mask issues in 2017a, and data issue shown in Cal tool
• Issue 0001768: [General] In MATLAB 2017a Raptor blocks show ??? after update, goes away with another update

2017a_0.0.1

• Issue 0001710: [General] In Raptor Target Definition block, don't show ECU Address for modules which don't use it
• Issue 0001534: [General] 196 CAN messaging on 1 and 2 drops off bus when there is an error flag
• Issue 0001717: [General] J1939 NACK/ACK Dest Addr and data content
• Issue 0001716: [General] J1939: HCM modules NACK PGN request that is subsequently handled via PGN Trigger
• Issue 0001186: [Build] Bit packing in Fault Map Tool causes headaches across Raptor platform
• Issue 0001696: [Build] Allow J1939 address for desired address in Address Claim to be detected in startup trigger
• Issue 0001697: [Build] Please have an update error if Raptor Target Definition block ECU Address is set to 0xF9
• Issue 0001657: [General] Explore using FunctionName instead of ReferenceBlock in find_system
• Issue 0000160: [General] Raptor Fault Data Definition option to group with individual fault calibrations
• Issue 0001607: [General] Enum Array with Row (Col) headers doesn't show in Signal Tree
• Issue 0001154: [General] Don't automatically append _1, _2, etc. to duplicate Raptor Function groups
• Issue 0001695: [Build] Allow CAN XCP id's to be changed during init (such as if address is detected via harness)
• Issue 0000736: [Build] Calibratable Rx and Tx XCP IDs
• Issue 0001676: [Build] GCM196 - Operating XCP on CAN1 w/ 29bit IDs
• Issue 0001692: [Build] CAN Trigger does not disable if placed in Enabled Subsystem
• Issue 0001682: [Build] Raptor CAN block reverts changes made to ID when re-opening GUI
• Issue 0001683: [Build] Bosch BSW UEGO_stCJ135RTEval_C calibration changed to 7
• Issue 0001282: [Build] Suggestion to add option in ECU definition to disable generation of a2l and hex files
• Issue 0001567: [Build] Add Min Make-Up Pulse port to raptor_injector block
• Issue 0001653: [Build] raptor_spark block should display OUTPUT56-63
• Issue 0001566: [Build] Remove Max Duration and Min Duration on raptor_spark block
• Issue 0001640: [Build] Third party A2L Compatibility for auto configuration of XCP_ON_CAN
• Issue 0001409: [Build] Parallelize GCM196 build process.
• Issue 0001634: [Build] Parallelize DISP-IMX286 build process.
• Issue 0001633: [VeeCAN] File IO - File Read Block Issue
• Issue 0001630: [Build] CAN Rx Block, subsequent output ports after unconnected port don't receive value
• Issue 0001699: [Build] Make model_open file generic to support files of different names
• Issue 0001674: [Build] model_open and model_close files are .p files
• Issue 0001719: [General] Add MathWorks 2017a compatibility
• Issue 0001624: [Build] Text file from build incomplete
• Issue 0001481: [Build] Make DM3 and DM11 blocks compatible with Standard fault manager
• Issue 0000434: [Build] j1939 transport protocol and raptor target definition blocks' ecu address conflict
• Issue 0001585: [Build] J1939 address conflict makes reprogramming different
• Issue 0001502: [Build] More information in canDefinition parameter in CAN Rx/Tx blocks
• Issue 0001691: [Build] Correct CAN ids are lost when opening an older model
• Issue 0001706: [Build] GCM196 - Link error due to atan2 block
• Issue 0001503: [Build] Add checkbox for alphabetical port order on CAN Rx/Tx blocks
• Issue 0001611: [Build] Ensure nonvolatile behavior for FailedThisDriveCycle and TestCompletedThisDriveCycle OBD fault statuses
• Issue 0001632: [General] Allow Raptor libraries to be accessed with Simulink shortcut
• Issue 0001613: [Build] Raptor CAN Tx incorrect functionality based on inport data type
• Issue 0001650: [Build] Consolidate multiple "System" folders into a single folder
• Issue 0001631: [Build] Licensing commonization with other products

2016b_0.0.1_SP1

• Issue 0001589: [Build] GCM196 Add reduced reflash time for 125k, 250k, 1000k baud
• Issue 0001609: [Build] DISP-IMX286: Strings not writing on display: raptor_display_draw_text
• Issue 0001603: [Build] .NET 4.5 should be installed if not already present
• Issue 0001601: [Build] GCM196 EEPROM Size <= 120 bytes doesn't store
• Issue 0001602: [Build] CAN Msg Tx: Id reverts when first signal deselected
• Issue 0001599: [Build] OBD FaultManger - Failing status seems to behave as nonvolatile
• Issue 0001577: [Build] GCM196 Output diagnostics for OUTPUT9 and OUTPUT12
• Issue 0001586: [Build] GCM196 OUTPUT 9 and 12 not fully operable
• Issue 0001591: [Build] On mask of raptor_fault_trigger block, indicate if set to global trigger
• Issue 0001593: [Build] Error when trying to copy Raptor App Trigger into model
• Issue 0001578: [Build] Raptor Tool Chain Definition block prevents build
• Issue 0001154: [General] Don't automatically append _1, _2, etc. to duplicate Raptor Function groups

2016b_0.0.1

• Issue 0001579: [Build] EEPROM Coherent Background Write
• Issue 0001295: [Build] Data Read from vector data store can only be indexed by uint32 (not lesser uint8 or uint16)
• Issue 0001569: [Build] DISP-IMX286: Error opening serial definition block
• Issue 0001288: [Build] J1939 Address Conflict
• Issue 0001561: [Build] GCM196 Programming Time Improvement
• Issue 0001486: [Build] Add Stack / Heap configuration for all modules that will support
• Issue 0001570: [Build] Name change on raptor_cam_info block
• Issue 0001568: [Build] Name change on Wideband O2 Sensor block
• Issue 0001469: [Build] J1939 Blockset does not have TTI2 or GTFI block
• Issue 0001470: [Build] J1939 Blockset raptor_j1939_pgn_tx block does not support IO (PGN 65244)
• Issue 0001100: [General] Datasheets do not specify pull-up voltages
• Issue 0001515: [Build] Move H-bridge fault ports from H-bridge block to Fault Status block
• Issue 0001536: [Build] More default value suggestions for Raptor-Dev blocks
• Issue 0001468: [Build] Feature request for fault manager Fault Activity Trigger block to be used in conjunction with Last Fault block
• Issue 0001548: [General] GCM196: Turning OUTPUT12 resets the module
• Issue 0001562: [Build] GCM196 - Increase EEPROM size to max of 76 KB.
• Issue 0001377: [General] Add a check when starting Raptor Installer to see if Matlab is currently open or if existing version is already installed.
• Issue 0000420: [VeeCAN] Nonvolatile status block
• Issue 0001496: [Build] Raptor DEV Installer asks to install CodeSourcery\Sourcery G++ Lite even though it is already installed.
• Issue 0001411: [Build] Add ability to name LookupX and LookupY table axes
• Issue 0001259: [General] request to add enable input to raptor_pwm_out block
• Issue 0001558: [Build] Issue building DISP-IMX286 (error MSB4126) due to preexisting Platform environment variable (HP Machines)
• Issue 0001177: [Build] Integrated help documentation for Faults should be reorganized.
• Issue 0001555: [Build] Error opening Target Definition block for display if Device Compiler (CodeSourcery) not installed.
• Issue 0001516: [Build] Change default access level on Raptor blocks in Power Up_Down block
• Issue 0001554: [Build] 'Measure Output' option on Tables (1D/2D) causes compiler error when using vector inputs
• Issue 0001410: [Build] Remove unnecessary mask parameters relating to "Measure Output" on Raptor Look-up tables
• Issue 0001489: [Build] Raptor CRC Block generates inconsistent error messages for Unsupported Modules.
• Issue 0001507: [Build] Add support for Mathworks 2016b
• Issue 0001064: [General] Raptor CAN Rx and Tx blocks do not update if changes are made to dbc file
• Issue 0001543: [Build] raptor_sfun_fileIO_size error, missing tlc file
• Issue 0001513: [Build] On GCM/ECM196, CAN message queueing doesn't seem to work if CAN ID changes during event
• Issue 0001539: [Build] raptor_table_adapt (standalone block) will not adapt 2-D Table
• Issue 0001505: [Build] Add Vector Support to Referenced Table Blocks
• Issue 0001501: [Build] Raptor Toolchain Definition block prevents save
• Issue 0001525: [VeeCAN] Cannot change Quad Gauge parameters on VeeCAN 320L
• Issue 0001544: [Build] Add ECM196 O2 Blocks
• Issue 0001551: [Build] Add ECM196 Cam Info blocks to support VVT
• Issue 0000817: [Build] HCM-5534-50-1203 linker warning on build (stack/heap overlap)

2016a_0.0.2_SP1

• NOTE: This version of Raptor-Dev requires Raptor-Cal_2016a_0.0.2 or newer.
• Issue 0001508: [Build] Vector enabled Table Axis Blocks cause application not to run.
• Issue 0001514: [Build] GCM196: region ram0 is full
• Issue 0001474: [General] Trigger_def / Trigger_ref cannot change name
• Issue 0001509: [General] Cannot change CAN parameters when double clicking mask
• Issue 0001511: [Build] HCM-5534-50-1203 CAN2 Baud Rate options incorrect
• Issue 0001510: [Build] BCM48 - 'UNUSED' redefined compiler error
• Issue 0001527: [Build] GCM196: raptor_time block outputting incorrectly over long time
• Issue 0001535: CAN Tx Raw, add option to remove 'extended' (ID Type) port

2016a_0.0.2

• NOTE: This version of Raptor-Dev requires Raptor-Cal_2016a_0.0.2 or newer.
• Issue 0001487: [General] Raptor Mask Issues
• Issue 0001488: [Build] Analog output block has a uint8 input for voltage setting
• Issue 0001168: [Build] Closing/re-opening laptop lid causes Raptor license issues
• Issue 0001475: [General] ECU Address help text
• Issue 0001473: [Build] Update Modbus Lib help documents
• Issue 0001339: [Build] Add Analog In Reference Block to Raptor-Dev
• Issue 0001479: [Build] Changing Targets can cause the mask on Analog Inputs to not open, and report an error.
• Issue 0001340: [Build] Allow Vectors to Pass Through Look-up Tables
• Issue 0001402: [General] New packager does not support VeeCAN
• Issue 0001471: [Build] J1939 DM blocks, bus parameter not passed inside block to RQST Response, and PGN Request block
• Issue 0001286: [General] GCM196 Output 1 thru 11 do not output correct duty cycle
• Issue 0001466: [Build] Receive is not spelled "recieve"
• Issue 0001417: [Build] Change default access level on all Raptor blocks to 1
• Issue 0001277: [Build] GCM196 Doesn't have any info on MPRD in datasheet
• Issue 0001472: [General] Trigger Blocks Help button incorrect link
• Issue 0000908: [Build] Raptor CAN Rx/Tx Message block improvement suggestions
• Issue 0001421: [Build] Add raw output capability on CAN Rx Message blocks
• Issue 0001158: [General] Raptor dT Block does not simulate correctly
• Issue 0001435: [Build] Enhance MODBUS library to expose Modbus Slave capability
• Issue 0001338: [Build] Toolchain Definition block doesn't prevent Save
• Issue 0001348: [Build] GCM196 - H bridge diagnostics not available
• Issue 0001467: [General] GCM196 - CAN Relay (CAN3<->CAN2) message transmit issue
• Issue 0001153: [Build] Subgroup for Raptor Override
• Issue 0001461: [General] Target Definition Block should raise an update error when trying to set ECU address to 255 or 254
• Issue 0001448: [Build] Need more calibration space on GCM196
• Issue 0001403: [Build] Engine continues to run even when application monitor pauses application
• Issue 0001433: [Build] Block update checks shouldn't (all) happen when OK is pressed
• Issue 0001446: [Build] Attempting to set a parameter to an empty value causes several exceptions
• Issue 0001436: [Build] Enhance MODBUS library to enable dynamic register configuration
• Issue 0001352: [Build] GCM196: OUTPUT34 - undefined reference to `swsh_DIO_out_ECUK019'
• Issue 0001432: [Build] AppMonitorLastError can report incorrectly
• Issue 0001445: [Build] Block Parameter callbacks can set parameters to strange values when callback errors.
• Issue 0001346: [Build] GCM196 - Output 36 Info wrong in datasheet
• Issue 0000795: [General] Separate block for adapt functionality
• Issue 0001397: [Build] Table block simulation doesn't take account of adapt blocks for reference blocks.
• Issue 0001255: [General] App Monitor Measurement block description is incorrect
• Issue 0001387: [Build] "FAILLING_ZERO_CROSSING" has already been declared in the current scope
• Issue 0001392: [Build] DISP-IMX286 targets error when adding new Analog Input block (Popup Items Type not set for range)
• Issue 0001390: [Build] Replace Raptor-Package w/ RILPackager
• Issue 0001492: [Build] Standard Fault Manager build warnings
• Enhanced 'Power Up & Down' logic in the template model
• Updated to New Eagle Licensing V10
• Enhanced 'Power Up & Down' logic in the template model
• Known Issue: J1939 blockset not fully supported in this release for GCM196 target.

2016a_0.0.1

• Issue 0001349: [Build] Have modules automatically communicate BuildID and CalID during discovery process
• Issue 0001341: [Build] Allow enumeration structures with 'name' and 'value'
• Issue 0001214: [Build] Add compatibility with Mathworks 2016a
• Issue 0001380: [Build] DAQ list scheduling inconsistency
• Issue 0001356: [General] ECM196 Input Pull up/down resistors
• Issue 0001355: [Build] Datasheet for GCM/ECM196 indicates a pull-up for INPUT23; the manufacturer document shows a pull-down
• Issue 0001376: [Build] GCM196 : CAN2/3 require startup delay to activate CANbus
• Issue 0001351: [Build] HCM-ARM4-070 (CM3620) Build Memory Stats improvement
• Issue 0001260: [Build] HCM-ARM4-070 (CM3620) CAN2 Extended 29bit ID receive not working
• Issue 0001362: [Build] DISP-IMX286 targets foreground timers minimum rate is 10ms
• Issue 0001345: [Build] Update DISP-IMX286 targets to use microsecond time base
• Issue 0001357: [Build] DAQ Percent usage calculations providing inaccurate reporting
• Issue 0001360: [Build] HCM-ARM4-070-1601,HCM-5534-90-1601,HCM-5534-90-1602 recovery option doesn't work correctly in Raptor-Cal
• Issue 0001353: [Build] GCM196 : INPUT23 resistor is PD
• Issue 0001232: [General] Raptor CAN Tx and Rx blocks cause errors in command window if you cancel out of window to upload dbc file
• Issue 0001350: [Build] GCM196: CAN Definition Block Build Error
• Issue 0001296: [Build] GCM196 - ADC Range in Mask of Internal Measurement block for Battery_Voltage should read 65536
• Issue 0001299: [Build] GCM196 - Output Type 1 PWM Duty Cycle Clamp
• Issue 0001298: [Build] GCM196 - Output Type 1 does not work when used as a Digital Output
• Issue 0001297: [Build] GCM196 - No inputs have software selectable PU/PD resistors
• Issue 0001238: [Build] Specifying custom build output path corrupts RPG file
• Issue 0001258: [Build] Pinout tables in GCM196 needs to be updated
• Issue 0001257: [General] Raptor Toolchain Definition block does not have option to select latest version of Raptor (2015b_0.0.2)
• Issue 0001278: [General] GCM196 Documentation needs updated
• GCM196 : Update output_status block to show enumeration values
• Updated CAN user interface to be more responsive for large DBC files when enabling and disabling signals
• Dropped support for MathWorks 2013b or older.
• Found in the 'Documentation' folder within the installation directory:
  • Updated 'Raptor Getting Started Guide.pdf'
  • Added 'Using_ATI_Vision_with_Raptor.pdf'
  • Added 'Using_Vector_CANape_with_Raptor.pdf'
• Known Issue: J1939 blockset not fully supported in this release for GCM196 target.

2015b_0.0.2_SP1

• Issue 0001256: [Build] Parallelize raptor_gen_a2l to speed up the build process
• Issue 0001270: [Build] GCM196 analog input scaling not consistent with other ECUs
• Issue 0001269: [Build] Standard Fault Manager Iterators incorrect indexing
• Issue 0001265: [Build] GCM196: CAN3 set to 125K can affect module reprogramming
• Issue 0001263: [Build] GCM196 : Internal measurement for Battery Voltage is not accurate
• Issue 0001262: [Build] J1939 blocks caused warning for missing return function
• Issue 0001247: [General] If using custom output file name, file name is displayed in command window mutliple times every update, build, etc.
• Issue 0001248: [Build] GCM196 : uint64_T type definition required
• Issue 0001252: [Build] EE_UniqID (EE Format) algorithm needs to be revised to accommodate larger models.
• Issue 0001271: [General] GCM196: H-Bridge enable function does not work properly
• Issue 0001272: [Build] Update HCM-5604-36-1303 (CM0711) to use microsecond base
• Issue 0001279: [Build] GCM196 Build fails if there are spaces in the model directory path
• Issue 0001273: [Build] Confusing build log messages
• Issue 0001283: [Build] GCM196 H-bridges do not completely turn off when disabled.
• Issue 0001285: [Build] GCM196 build will fail if Output 12 resource is selected in PWM output block
• Issue 0001189: [General] GCM/ECM 196 Datasheet error (Compiler Version)
• Issue 0001289: [General] GCM 196 Datasheet errors (INPUT31/32 450mV offset)
• Issue 0001291: [Build] GCM196: PWM outputs used as Digital outputs cause build error
• Issue 0001292: [Build] Special 'Subsystem Parameters->Code Generation->Function Packaging' required to build in certain cases
• Datasheet updates

2015b_0.0.2

• Issue 0001019: [Build] Add initial support for GCM-1793-196-1503
• Issue 0001235: [VeeCAN] VeeCAN 320 Image transparencies
• Issue 0001114: [Build] CRC Regression test checksum capability not implemented for CM0711
• Issue 0001202: [Build] (CM3620) Build process stalls if there are errors in the model or generated code
• Issue 0001184: [Build] On Raptor CAN blocks, port order does not match order on mask display
• Issue 0001234: [Build] Target definition, change target quickly and hit 'OK' can cause error dialog.
• Issue 0000460: [Build] Change message ID in the Raptor CAN GUI
• Issue 0000184: CAN Rx / CAN Tx blocks: DBC Signal Ordering by start bit (reverted)
• Issue 0001216: [Build] HCM-90 application checksum region too small.
• Issue 0001066: [Build] Build error if input/output wire not labelled and wire name is used as override block name
• Issue 0001233: [Build] Raptor does not work with Matlab if Matlab was installed after Raptor
• Issue 0001217: [Build] HCM application checksum region too small
• Issue 0001183: [Build] Increase CM0711 flash memory access (additional 128k of flash)
• Issue 0001102: [General] Create datasheet for GCM196.
• Issue 0001215: [Build] Update HCM-5534-50-1203 (CM2115) to use microsecond time base (tick_us)
• Issue 0001212: [Build] Add HCM-5534-90-1602 target (500k CAN1)
• Issue 0001211: [Build] Add HCM-5534-90-1601 target (500k CAN1)
• Issue 0001213: [Build] Add HCM-ARM4-070-1601 target (500k CAN1)
• Issue 0000924: [Build] 'System cannot find the file specified' error on build
• Issue 0001061: [Build] command window error with CAN blocks
• Issue 0001207: [Build] Parker ECU periodic CAN Transmit accuracy
• Issue 0001199: [Build] Raptor Generated A2L file do not convey 'Max Lists per DAQ' parameter from XCP Definition
• Issue 0001195: [Build] Unused RAM variables cause the build to fail
• Issue 0001166: [Build] BCM48 CAN Mailbox (Trigger/Filtering) Implementation
• Issue 0001173: [Build] European date format displays expiration time in a confusing manner
• Issue 0001181: [General] Make DM11 option to accept destination specific messages
• Issue 0001165: [General] GCM196 Datasheet errors
• Issue 0001174: [Build] sed.exe included with installation not compatible with Windows10
• Issue 0001180: [General] Raptor is not available in Matlab 2015a SP1
• Issue 0001169: [Build] BCM48 Raptor-Test Enumeration Errors
• Issue 0001242: [Build] Cannot build model with Raptor Check Sum blocks with CM0711 as target
• Updated Modbus to request and parse multi-register length reads.
• Datasheet updates

2015b_0.0.1

• Issue 0001058: [Build] Add support for Mathworks 2015b_0.0.1 - Does not support 32bit Mathworks 2015b on 64bit machine.
• Issue 0001022: [VeeCAN] Suggestions for improvements to Gauge Block
• Issue 0001155: [Build] Fault block display retains configuration options for different Fault Manager setting
• Issue 0001117: [Build] "Power Down" subsystem hardware resources invalid for BCM48 in Raptor_2015a_0.0.3
• Issue 0001091: [Build] Strobe Diagnostics - Open Detection - when Output OFF
• Issue 0001141: [Build] BCM48 mask evaluation failing for digital input and digital output
• Issue 0001160: [Build] Set Input Option - error on open preventing use
• Issue 0001090: [Build] Hide "Display As Enumeration" option when floating point datatype is selected
• Issue 0000593: [VeeCAN] Manual hide button bar VeeCAN function
• Issue 0001099: [General] Matlab crashes if you try to simulate a model with a Raptor-Dev Adjustment block in it.
• Issue 0001159: [Build] BCM48 can't enter bootloader when CAN1 is renamed.
• Issue 0001144: [Build] Update HCM-ARM4-070-1401 to new SDK 916602_V0_20_Build_24
• Issue 0000727: [Build] Update HCM-5534-50-1203 sdk to version V0_38_Build_50
• Issue 0001118: [General] CM3620 Datasheet errors
• Issue 0001127: [General] CM3620 Fault Detection Output Status for Output 12 incorrect
• Issue 0000935: [VeeCAN] Adding USB Status block to VeeCAN320 model causes crash
• Issue 0001126: [General] IAR compiler not found by Raptor ECU definition block
• Issue 0000132: [General] CAN Tx Message block does not resolve DBC file correctly unless the block mask is opened
• Issue 0001098: [Build] Min/max in Raptor Adjustment not being created in A2L file correctly
• Issue 0000184: [General] CAN Rx / CAN Tx blocks: DBC Signal Ordering by start bit
• Issue 0001020: [VeeCAN] Rename Layers in Display Draw Text block
• Issue 0001062: [Build] two instances of help text for Application Monitor Stop, one referring to the wrong block
• Issue 0001087: [Build] App monitor defaults are too conservative
• Issue 0001083: [Build] EEPROM_State is stored in non-volatile
• Issue 0001049: [General] CM3620 internally reported battery voltage measurement inaccurate
• Issue 0000924: [Build] 'System cannot find the file specified' error on build
• Datasheet updates

2015a_0.0.3

• Issue 0001008: [General] CM2115 inputs should have option to disable pull-up/pull-down resistors
• Issue 0001004: [General] CM2115 has capability to measure 4-20mA, but not currently supported in Raptor
• Issue 0001026: [Build] Loss of power to module (uncontrolled shutdown) caused module to resort to bad calibrations
• Issue 0001042: [VeeCAN] Example template for VeeCAN800 shows pinout image of VeeCAN320
• Issue 0000404: [VeeCAN] Change VeeCAN PC Simulator window name from PC Simulator to build name
• Issue 0000930: [VeeCAN] Use SoftwareIdTxt for simulator name instead of simulator.exe
• Issue 0000973: [VeeCAN] Verify that there is at least one ScreenDef in VeeCAN models
• Issue 0001040: [General] Matlab crashes if I try to open certain subsystems with the VeeCAN display template
• Issue 0001046: [VeeCAN] Resources in Inputs and Outputs tables in VeeCAN 8000 Datasheet are listed out of order.
• Issue 0001000: [VeeCAN] Improper handling off out-of-range values in Raptor-Dev Display Gauge blocks
• Issue 0001044: [VeeCAN] Cannot set PWM output frequency
• Issue 0001038: [VeeCAN] PWM output disables if 100% duty cycled command on VeeCAN320
• Issue 0000989: [Build] Add checkbox to automatically add measurement for interpolation tables
• Issue 0000714: [VeeCAN] String Size - Simulator different than hardware
• Issue 0001009: [General] Operating Voltage and Min Current rows in Hardware Table of all datasheets can be removed
• Issue 0000950: [Build] No help text for Application Monitor Measurement
• Issue 0000713: [VeeCAN] Update non-volatile write description for VeeCAN
• Removed FileSync from FileWrite block to resolve buffering issue with VEECAN USB write
• Datasheet updates

2015a_0.0.2

• Issue 0001012: [Build] raptor_display_element block 'Next' output port datatype incorrect
• Issue 0000946: [Build] RPG expiration date
• Issue 0000923: [VeeCAN] command line error when using Raptor Display button blocks
• Issue 0000952: [General] Modifying mask parameters of Raptor blocks results in errors in command window
• Issue 0000774: [Build] Java and CELL2MAT Warnings/Errors
• Issue 0000999: [General] Input 17 of CM2115 does not have any configurable input options
• Issue 0001001: [Build] Expose max_stack_usage measurement for CM711
• Issue 0000928: [Build] Linker error upon using printf block with '%d' format string
• Issue 0000757: [Build] Add Calibration ID as a parameter to Raptor Builds
• Issue 0000368: [VeeCAN] VeeCAN Light needs check for more than one CAN def
• Issue 0000978: [VeeCAN] VC800 Build fails with minimal model
• Issue 0000998: [Build] HCM-5604-36-1303 - enable configuration of the stack size
• Issue 0000441: [VeeCAN] VeeCAN Simulator startup delay is too long
• Issue 0000982: [VeeCAN] VeeCAN320 Template does not have XCP definition
• Issue 0000920: [General] Support for WIndows 8/10
• Issue 0000773: [Build Machine] Time blocks are disconnected during build
• Issue 0000822: [Build] Update process should call out problems in the model if there are conflicts using Raptor-Dev
• Issue 0000910: [Build] More update error checking necessary
• Issue 0000522: [Build] Template touch display project has many build warnings
• Issue 0000976: [Build] significant wait time following ### Calculating Memory Usage after build
• Issue 0000868: [Build] Calibritable cycle numbers in the OBD fault manager
• Issue 0000953: [Build] Target Def mask calibration location is set to EEPROM regardless of what is selected
• Issue 0000442: [VeeCAN] Raptor packager on VeeCAN simulator-only build throws error
• Issue 0000929: [Build] Model fails to build due to app monitor when CAL location is set to Constant (FLASH)
• Issue 0000534: [Build] override block does not take parameter name from output wire name
• Issue 0000493: [General] incorrect scheduling of CAN triggered subsystem
• Issue 0000571: [General] Note to use on initial Matlab startup after Raptor Install about template projects, getting started guide.
• Issue 0000880: [Build] There is no help text for the Raptor CAN Tx Message Show ID Port option
• Issue 0000778: [General] Error at command line when changing hardware resource on Analog Input block
• Issue 0000755: [Build] Show build name on Target Definition block mask
• Issue 0000891: [Build] Images and styling missing on help when opened in MathWorks 2015a.
• Issue 0000297: [General] Common file header in generated files, showing Raptor version info
• Issue 0000922: [Build] Table 1D with an Initial Value that contains a \n will cause incorrect runtime behavior
• Issue 0000486: [VeeCAN] Gauge Background Build Error
• Issue 0000892: [Build] Raptor display 'Gauge' configured with 0 for number of Large/Small markers causes application crash
• Issue 0000158: [General] Consider "normal" defaults in mask parameters of blocks
• Issue 0000907: [Build] Raptor Timed Trigger block should automatically produce random name when copied
• Issue 0000897: [Build] Raptor packager ERROR, hex files does not exist when setting 'Minimum Characters for Build Version' in ECU definition block < 3
• updated installer to not reinstall Kvaser drivers if they are already installed
• resolved a number of build-time warnings about unused variables
• resolved zero crossing types error

2015a_0.0.1

• Issue 0000874: HCM-ARM4-70-1401 - enable configuration of the stack size.
• Issue 0000781: H-Bridge function non-operable on 4th part of H-Bridge on CM2115.
• Issue 0000853: Help Text for Fault Definition does not include definition for 'Single Trip'.
• Issue 0000871: Use of 'App Monitor Stop' causes raptor_gen_a2l to fail during build.
• Issue 0000495: Error - Need to specify Raptor needs visual studio.
• Issue 0000548: Data Read: Non-descriptive build fail error if scalar value is read as vector.
• Issue 0000515: Selecting OK on target def before mask update completes causes MATLAB crash.
• Issue 0000814: App monitor is not supported on VEECAN displays.
• Issue 0000765: Build error related to Windows SDK when building with simulator on display hardware.
• Issue 0000523: warning MSB8003: Could not find WindowsSDKDir variable from the registry.
• Issue 0000796: Change inexplicable "Display Format" syntax.
• Issue 0000572: Prevent Updates/Builds in incorrect working directory.
• Issue 0000561: Single character string causes Raptor Packager failure during build.
• Issue 0000849: VEECAN Raptor Prerequisite.
• Issue 0000823: Incorrect units portrayed in Timed Triggers display variables.
• Issue 0000857: A2L generation does not set min and max values for booleans.
• Issue 0000804: Include build datestamp in "System" properties.
• Issue 0000532: A2L min/max is wrong when a signal has a gain/offset but no min/max.
• Issue 0000156: Better documentation on automatically created vardecs when using Raptor table lookup blocks.
• Issue 0000845: model_open file as script instead of function.
• Issue 0000834: Minimum characters for version >1 causes build to error on Raptor Packager.
• Issue 0000828: raptor_create_visionStrategy breaks the build on anything that doesn't generate a .hex file.
• Issue 0000489: 'JavaFrame' will be obsoleted warning when using MathWorks 2014b.
• Issue 0000821: Resolved: Raptor-Cal overrides no longer work.
• Issue 0000840: HCM-ARM4-70-1401 IAR Compiler not found on 32bit machines.
• Issue 0000844: Add fonts to the VeeCAN sdk
• Issue 0000507: Error while selecting CAN DBC file (bad filename, contains dash '-') - added error message
• Issue 0000872: A2L files from now one will use the `proper` SwIdTxt for the project name
• Issue 0000882: Extra FaultAction columns show in Raptor-Cal
• Issue 0000883: Change names of fault actions and triggers as viewed in Raptor-Cal
• Issue 0000884: Unless initialized with Fault Data file, a Fault Data Definition does not tie data to fault
• Issue 0000886: Build error with Stateflow Diagram in triggered subsystem with Matlab 2015a
• Issue 0000885: Build error when using multiple Raptor mailbox blocks referencing message with same message ID and mask
• Issue 0000887: Raptor Analog Input blocks show uint16 on the port label, but output a double data type (see APPNOTE_2015a001_000)
• Issue 0000888: VEECAN input names are inconsistent w/ Datasheet (remapping I/O will be required on VEECAN320/VEECAN800)
• Issue 0000889: Mailbox property blocks not working on VEECAN display targets
• Issue 0000890: Improperly terminated string in Display Gauge block copy callback
• Corrected CM3620 pinout in datasheet, pull-up/down information displayed in blocks.
• Removed font size limitation of 100px in display buttonbars (max is now 480px).
• Improved scope of information provided in datasheets.
• Enhanced installation of toolchain for building models targeting displays.
• Resolved issue causing VEECAN800 resets after a period of running (memory allocation).
• Improved Fault Definition block, added more info on the block face to enhance model readability (emissions related, single trip, etc..)
• Updated libraries to show in 2014b+ MATLAB/Simulink (SLX format)
• Refreshed Raptor_Getting_Started.pdf in \Documentation folder of install directory
• Added Raptor_Training_Manual.pdf in \Documentation folder of install directory
• Notes: For an important note about changes to the ‘Analog Input’ block’s output data type please review the following application note: http://software.neweagle.net/AppNotes/Raptor/APPNOTE_2015a001_000.pdf

2014b_0.0.3

• Issue 0000535: VeeCAN 800 Analog Inputs and Digital Outputs on J3 do not work.
• Issue 0000383: Add initial (beta) support for BCM-5646-48-1404
• Issue 0000691: Update to New Eagle Licensing V0.0.9 to enable NODE-LOCKED licenses
• Issue 0000791: Hardware driver type shows <empty> in simulink on VEECAN outputs
• Issue 0000807: Quad Gauge block says "SmalR"
• Issue 0000482: Element block 'Next' and 'FnCall' ports are mismatched
• Issue 0000415: Bad DBC file causes model to crash..
• Issue 0000608: RS232 support missing from DISP-IMX286-012-1402
• Issue 0000718: EE_UniqID does not include data items set to Calibration
• Issue 0000342: All target ertTemplate files are copied at build time
• Issue 0000702: Building VeeCAN with XCP def but no simulator fails
• Issue 0000516: License check in raptorrc.m
• Issue 0000535: VeeCAN 800 Analog Inputs and Digital Outputs on J3 do not work.
• Issue 0000149: Incorrect documentation linked to Raptor Fault Manager
• Issue 0000733: Raptor Target Definition default value for Minimum Characters for Version should be 3
• Build log is now copied into the build directory.
• Added '[int32]' to the X and Y inputs and '[single]' to the Value input on the Gauge Raptor block.
• Updated note to help clarify download/install of the CodeSourcery tools for displays
• Fixed issue with GetDataStoreSize default cases
• Update in raptor_display_screen_def.tlc to remove a build warning during veecan builds

2014b_0.0.2

• Issue 0000483: HCM-5604-36-1303 documentation has pinout error
• Issue 0000595: DISP-IMX286-012-1402 getFreeSpace function call did not have proper path on FS
• Issue 0000549: Enable/Disable port for the fault definition block of the raptor library
• Issue 0000601: change request for text in the DISP-IMX286-024-1204 datasheet
• Issue 0000608: Adding missing serial resource definition to DISP-IMX286-012-1402
• Issue 0000604: Add option to specify the fill used for transmitted CAN messages in unused areas of messages.
• Issue 0000547: Incorrect module ID in vsf created with binary converter. (HCM-5534-90-1302)
• Issue 0000603: Add additional internal measurements (HCM-5534-90-1201/1302)
• Issue 0000529: Levels of the build generated parameters
• Issue 0000653: fix mask parameter validation

2014b_0.0.1

• Issue 0000350: Add MathWorks 2014b support
• Issue 0000333: Creation of a Background task multiplier
• added RaptorPackager to Tools folder
• modified raptor build scripts to generate RPG files
• Issue 0000401: Added timestamp to completed Raptor build status
• Issue 0000408: Added USER_RIGHTS and GROUP regions to A2L file for access level control
• Issue 0000439: Raptor Power Down block in example model does not store NV
• updated XCP memory range validation checks in CM0711, CM3620, both were too wide.
• Issue 0000389: Add show release notes in the final page of installer.
• Issue 0000425 added user-defined output path for RPG files
• Issue 0000384/0000468 Updating Getting Started guide to include new Matlab compatibility matrix, and info about Merlin
• Added DAQ processor usage XCP items to App monitor.
• Issue 0000391: XCP priority should be reduced when CPU utilization reaches a threshold, filled in proper max ODTs based on mask setting, added DAQ overload to EVENT (DAQ_OVERLOAD) 0xFD 0x06
• J1939
  • Updated help info on the raptor_j1939_tp_rxraw block to indicate an index vector should be used on the data[] output and not a demux.
  • Issue 0000378: J1939 License Error, does not show a good message 'nonexistent function ISEMPTY --> isempty'
  • remove warning in j1939_tprx_trigger.tlc
• DISP-IMX286
  • update to initialize VeeCAN CAN channel on send if it has not already been initialized
  • fixed extended ID transmit in VeeCAN simulator
  • adding simulator support to the DISP-IMX286-012-1402 (VEECAN320L)
  • removing duplicate button definitions from DISP-IMX286-012-1402 target file
  • resolving issues with XCP support
  • Adding unlisted memory segments to VeeCAN 800 and VeeCAN 320 Light
  • Issue 000369: Adding veecan_manifest.ini files to veecan usb templates
  • VeeCAN builds now include build_uid in veecan_manifest.ini
  • renamed raptor_veecan_run_last_simulator to raptor_display_run_last_simulator
  • makefiles - added "SHELL=C:/Windows/System32/cmd.exe" to ensure correct shell runs.
  • genbuild build.bat now uses "cd /d" to ensure simulator is ran even when it's on a separate drive
  • fixed transparencies on some VeeCAN touch buttons
  • added VeeCAN800 touchscreen template, available from raptor_create_touchscreen_project
  • Issues 0000400/0000402/0000403: Fixing the VeeCAN build process to increment and use build number whether or not it's being appended to the output file
  • Issue 0000414: Using CAN BaudRate = "AUTO DETECT ON START" causes error, Removed "AUTO DETECT ON START" from list of available options
  • Issue 0000426 Adding a function to check whether or not an image exists on disk, and adding a call for this in the VeeCAN raptor_display_create_gauge.tlc
  • Issue 0000430: Adjusting VeeCAN gauge to center background image
  • Issue 0000432: Adding three templates for each of the VeeCAN targets, as well as some functions to be able to call them by
  • Issue 0000419: Adding ability to use .png and .jpg images in VeeCAN splashscreen
  • Issue 0000435: Adding hyperlink to commandline output of raptor to open up RPG file location after a successful build
  • Issue 0000418: Configure VeeCAN foreground and background times, NOTE: SET DEFAULT FOREGROUND RATE TO 5MS, TO MATCH ALL OTHER TARGETS.
  • Issue 0000442: - modified raptor_build_rpg.m to accommodate VeeCAN projects built just for the simulator.
  • adjusting VeeCAN sdk to allow DISP-IMX286-012-1402 to run on DISP-IMX286-024-1204
  • Issue 0000482: Flipping port labels on element block and adding a few extra mask descriptions

2014a_0.0.3

• added GET_ID method 1 (ASAM-MC2 filename w/o path) per customer request, CANAPE will use this to verify A2L match if instructed
• updated data read block to allow single-element vectors
• updated template project to use WAKE_INPUT1 for the powerdown as is standard
• updated template project to show a message if model_open failed to execute, due to working directory issue etc..
• fixed 0000084: Build can fail if the current folder is not set correctly
• resolved 0000185: Only able to set ECU source address for programming via J1939 TP block, now ECU address can be set in the target definition
• updated to allow removal of unused stack/heap variable in the target definition block in ECUs that don't support setting these parameters
• added support for XCP Id Table Rev 2 (include EcuAddr: reflash id)
• update to generate correct GET_ID method 1 (ASAM-MC2 filename w/o path) per customer request, added '_CANAPE' if CANAPE A2L is being generated
• HCM-5534-90
  • updated HCM-90 units to 991602_V24_Build_27 of the platform SDK, this may require updated bootcode on existing units.
• DISP-IMX286
  • set simulator default to .NET4 to avoid issues on machines w/o Visual Studio
  • resolved issue with raptor_display_draw_text that was causing issue with measurement and adjustment blocks
  • fixed typo in VeeCAN XCP makefile
  • improved XCP support, including simulator
  • fixed typo on DISP-IMX286-024-1204 datasheet
  • fixed description for DISP-IMX286-012-1402
  • repaired Kvaser driver usage in display simulator build
  • updated simulator build to allow Kvaser virtual connection when running simulator
• J1939
  • updated DM3 RX handler to not clear emissions related previously active faults
  • updated J1939 SPN Support (DM24) and Extended Freeze Frame (DM25) to accommodate custom (Manufacturer Specific) SPNs
  • updated DM24 to allow application to pass array of SPNs to omit from DataStream
  • updated DM24 and DM30 blocks to properly update when array inputs change size
  • updated blocks to allow multiple DYNAMICALLY_SIZED inputs, PGNS: CI, DM20, SOFT, ECUID
  • changed datatype for storage of SPN bitlength from uint16 to unit8 to conserve memory.
  • updated J1939 DM11 handler to match latest J1939-73, DM11 will only clear faults when SPN190 (engine speed) is 0 (or not available)
  • DM11 will NACK all non-global requests, and NACK global request if made when engine is running (*deviation from J1939-21 per customer requested interpretation of J1939-73)
  • added missing: raptor_j1939_dtc_rxHandler.mexw64
  • fixed pgn request tlc licensing check

2014a_0.0.2

• resolved 0000147: AppMonitor calculations are off if FGND is not default
• resolved 0000148: dT block outputs total time instead of delta time since last call
• moved USBStatus and USB Eject to DataLogging lib
• deleted USBStatus and USBEject from Raptor Display library. Updated Template model.
• updated dT function for all targets, calculation was off by 1 during overflow
• changed XCP lib to use a custom scheme for reporting module id, added IdTableRev and HardwareType as measurements
• updated application monitor percent overrun and idle time calculations to use the smallest period instead of the time between foreground calls to provide better accuracy
• fixed a bug with the AppMon measurement block when CPU idle time is selected, now properly calculates idle time as a percent
• added raptor_sfun_trigger_def raptor_sfun_trigger_execute raptor_sfun_trigger_ref raptor_sfun_trigger_select blocks in Raptor_lib
• updated raptor_get_faults to work in a mask parameter as a function
• added XCP read-only flag for tables that are stored in CONST
• updated obd fault manager to minimize the workload spike when drivecycle bookkeeping occurs
• updated obd fault manager to minimize the workload spike when Clear All Faults is triggered
• resolved 0000164: DBC does not load into Raptor CAN Tx Message block
• resolved 0000166: 'Label wires with channel names' option does not label last wire
• update to not run app monitor thread in app shutdown
• updated obd fault manager to clear X & Y accumulated counts when the fault is cleared
• updated standard fault manager to clear X & Y accumulated counts when the fault is cleared
• fixed bug in raptor_sfun_calc_checksum.rlc that prevented it from finishing the calculation
• HCM-5XXX-XX-XXXX (CM Modules)
  • update to time task trigger scheduling code to utilize one platform task at fgnd rate, and schedule fgnd multiples within, improves timing accuracy and application monitoring calculation determinism
  • HCM5534-90-xxxx updated name WAKEINPUT1 to WAKE_INPUT1 to match all the other targets' wake inputs
  • fixed bug in HCM-5534-90-1302, incorrectly specified memory regions for checksum
  • HCM5534-90-1302 updated application checksum implementation to include the external flash region to assure application integrity on module boot before jumping to the app
• DISP-IMX286
  • serial_rx_%<hnds>: moved trigger function to within the buffer handling, now triggers on each byte rather than just last.
  • implemented mute of audible beep, available as digital out
  • added support to recalibrate the VeeCAN 800 touchscreen
  • updated some image functions to work with the VeeCAN 800
  • Renamed Raptor VeeCAN library components from veecan_ to display_ and updated template model to work with changes
  • added raptor_display_clear_rect
  • fixed I/O
  • updated 320L I/O for correct datasheet
  • ButtonDef bug fix where multiple buttons where not being drawn on the same screen
  • added a screen reference block
  • added raptor_display_screen_goto support for screen reference
  • added raptor_display_screen_select block
  • added eval to button definition block parameters
  • added display of color to VeeCAN drawing function block masks
  • raptor_display_image: Selected icon is now displayed on the block correctly.
  • Updated template model to fix issues giving Matlab warning messages on build.
  • added single gauge prefab block to Raptor Display library
  • updated gauge font size and allowed gauge marker color to be setable.
• J1939
  • update to remove J1939 NAME Identity option from J1939 TP block, this field is specific to the ECU target and will be automatically populated by Raptor.
  • changed J1939 licensing to be split between EMD and OBD-HD features
  • added DM-specific licensing checks for NE J1939 stack
  • added block-init license checks for J1939 OBD/EMD
  • added new J1939 block to parse DTCs from DM (dtc_rxHandler)

2014a_0.0.1

• integrated new version of xtool.exe
• added Serial folder to mex_all so Raptor releases will have mex files for the serial blocks.
• added advertisement of support for 2014a 32/64
• added note to raptor_make_rtw.m to provide note about evaluation license expiration date
• added support for VEECAN320L (DISP-IMX286-012-1402)
• added support for VEECAN800 (DISP-IMX286-036-1402)
• updates to avoid ATI Vision errors on connection
• updates for Mathworks 2014a compatibility
• 0000095: binaryconverter crashes - issue resolved
• updated BinaryConverter to include proper module ids, and relocated to \Tools directory to avoid duplicate files placed by the installer
• updated included Vansco Flashloader to released version
• added startup event block to allow app trigger startup task & to resume foreground tasks
• VEECAN parts renamed according to standard part naming convention
• added Background / Shutdown functionality to HCM-5534-50-1203, HCM-5604-36-1303, HCM-ARM4-070-1401
• update to app monitor that changes the calculation to focus w.r.t FGND rate idle capacity, adds longest run, better period precision on SDKs that support a microsecond time base, detects scheduling overruns, and allows app monitor stop for overrun
• update to make AppMonitorState a calibration
• exposed option on XCP definition block to generate A2L in special format for CANape
• DISP-IMX286 (VEECANs)
  • New blockset for use with veecan for drawing. Old blocks are no longer functional and will be removed
  • Upgraded Veecan SDK from 2.06 -> 2.10
  • Exposed ability to set Gateway IP and settings from GUI in simulator (stored in registry)
  • Added fileIO blocks back (in Datalogging library)
  • Removed hmi_primitive and hmi_staple blocks
  • Finished renaming veecan sfunctions.
  • added code generation for background trigger capability to match other ECUs
  • fixed some issues with veecan320_ertTemplate.tlc
  • Added debug messages to raptor_mask_PreSaveFcn
  • Added raptor_veecan_element block
  • Updated usbtemplate files to SDK 2.10
  • added single screen block
  • fixed some issues with Gauges and elements.
  • fixed some build warnings on the Veecan
  • fixed an issue with building the XCP library for Veecan, changed archiver command name to match the executable in the standard veecan compiler.
  • added Matlab include paths to make file and VS project for Veecan
  • disabled can_statistics_get call which was causing device to freeze with SDK 2.10
  • create appmonitor_read items for SDK values
  • changed method used to read buttons - keypad_read() is very expensive on the display.
  • added gateway application to Veecan SDK
  • added Menu blocks to veecan library.
  • adding help documentation for Veecan library.
  • added additional fileIO functions for VeeCAN (file EOF, file Position, file Read)
  • upgraded Veecan template model.
  • fixed issue with USB Eject
  • updated VEECAN320 pins diagram
  • updated hotplug script so that USB drive can be detected without .autorun or .ars file
  • removed some extra files from the usbtemplate
  • fixed the splashscreen block
  • expose option on target definition for displays to autorun the simulator
• HCM-5604-36-1303 (CM0711)
  • Upgrade to V2_05_Build_10 SDK
• HCM-5534-90-1302
  • updated mem stats for an accurate readout
• HCM-ARM4-070-1401
  • updated to remove link warnings
  • fixed linker error for XCP archive related to typedefs

2013b_0.0.6

• update: Fault Manager was not setting the model fault manager until the block mask was opened.
  • This could cause confusing operation as fault blocks did not always show correct mask.
• Added init and copy functions to Fault manager to set model fault manager type as soon

as it is placed in model.

• added generation of ADDR_EPK, EPK fields in A2L file to allow CANAPE detecting A2L compatibility with ECU software
• added missing mex32/64 files for CRC blocks, added regression test models for CRC
• added raptor_get_SwIdTxt to allow model to use the computed SwIdTxt
• added raptor_changeVSFID.m to change the module ID that a vsf file is targeting
• update to set default J1939 Module ID from value in target xml file.
• updated 'Getting Started Guide' format
• fixed issue that opening a model with a lot of data read/write blocks could cause the recursion limit to be reached and possibly crash Matlab
• added recursion level limit to raptor_datastore_check
• added regression tests for AppMonitor capability
• fixed issue with enumerated tables in raptor_gen_a2l was not handling indirect addressing properly
• updated to allow the Shutdown event to stop all application FGND tasks, background task would continue to operate to handle shutdown, eeprom etc...
• updated fault manager to remove index checks on intermediate functions,

adding index checks to codegen for const indexes and to outside blocks where index is determined at runtime for CPU efficiency

• updated to use macros (as opposed to function calls) for accessors to internal fault

manager structures for CPU efficiency

• added information about ADC resolution to datasheets
• raptor_sfun_obd_fault_def.tlc : make fault index check a code-gen step for CPU efficiency
• raptor_sfun_std_fault_def.tlc : make fault index check a code-gen step for CPU efficiency
• updated build template to allow error output consistently for compiler errors during parallel build
• HCM-ARM4-070-1401
  • update internal measurement gains to accurately convert ADC units into Amps for current sense
• HCM-5534-90-XXXX
  • update to turn on output strobe for open load fault detection on OUTPUTS 1-8
  • updated HCM-5534-90-1302 to store RAMVariable in internal RAM for CPU efficiency
• VEECAN320
  • added Draw Text function to set font color, size, position, etc, within the draw function.
  • added "Staple" functions to draw text with color, size, etc.
  • updated VeeCAN background- title bar obstructed input port names.
  • raptor_veecan_run_last_simulator.m - bugfix: reset to current directory on failed open.
  • adding HMI streaming 8-line text console blocks.
  • added displaying current file name during Veecan target compile
  • updated some Appmonitor support
  • fixed issue when compiling with only 1 CAN bus definition would create compile errors
  • added New Eagle J1939 protocol stack to support J1939
  • added some PGN timeout blocks for unavailable data to Raptor VeeCAN lib.
  • fixed debug messages in raptor_sfun_image.tlc
  • added address claiming to NE J1939 implementation for VeeCAN
• J1939
  • updated to not attempt to send a too-big message
  • updated list addition logic for J1939 to avoid block placement issues
  • updated J1939 to fix issues where the build would fail depending on where in the model the Transport Protocol block was placed.
  • resolved issue with DM25 datastore not available yet.
  • fixed compile issue when only J1939 block used is transport protocol
  • added ability to specify J1939 Name in TP mask.
  • updated help for j1939 TP block
  • update to give a default value for name fields if they are not entered.
  • added missing raptor_j1939_tp_dlgCb.m file (caused dialog errors)
  • fixed issue where order of compilation of blocks could cause TP to codegen before all blocks had registered in appropriate lists.
  • update to set default J1939 Module ID from value in xml file.
  • fixed bug with raptor_j1939_tp.rlc some rlc replacement tags were set as required and were causing warnings with the HCM modules

2013b_0.0.5

• updated datasheets generated with more information (see installation directory\Documentation)
• updated raptor_time and raptor_delta_time to deal with rollover in base time unit.
• added memory checksum blocks, presently Freescale targets are supported.
• changed storage of fault manager actionMap and triggerMap. Now uses 2 arrays instead of an array of structs.
• fixed bug in fault managers that was causing a build error if the fault manager has old fault map information in it.
• fixed issue with help files in Matlab 2013b and greater. Matlab appears to have stopped supporting the help.jar structure. Help files are now just stored in directory rather than in help.jar file.
• fixed raptor_viewhelp to use non-jar based help file locations.
• added App Triggers (Startup/Shutdown) raptor_sfun_app_trigger and raptor_sfun_shutdown
• updated Raptor Template project to include simple power-down scheme
• updated Getting Started Guide document template.
• added build unique ID to CONST data structure using an ASCII GUID
• added some enhancements to raptor_mask to allow block description to be viewed in library
• fix handling of standard ids when CAN tx message block ID port is being used
• updated to include Build_UID in A2L file.
• fixed bugs in data read/write simulation
  • data_write was incorrectly reading scalar double input as mxArray instead of real_T*
  • Added Dwork initialization for data_read and data_write to ensure that correct memory address for datastore is loaded on first step.
• Renamed faultTest to faultOperation and changed storage location from RAM to Calibration so that it can be used to disable faults through calibration.
• added raptor_sfun_appmonitor_measurement block to expose app monitor measurements such as Idle CPU, Task CPU utilization, platform statistics
• J1939
  • added missing SPN to TIRE PGN
  • Fixed issue in DM11. DM11 should only clear faults when request is sent to global address.
• HCM-5553-90-XXXX
  • reverted dT, time to use the millisecond base when outputting in Seconds as the ticks_us() call turns out to be very expensive CPU wise
• VEECAN320
  • updated CAN state info.
  • removed support for .NET compiler for Veecan 320 simulator. The .NET compiler requires Windows SDK v7.1 installed with some particular options installed. These options were not being checked when adding this compiler option.
  • Added reboot option at end of Raptor installer when CodeSourcery G++ compiler is installed.
  • 'Primitives' to be replaced by 'Staples', e.g. a draw text with font color, etc, included.
  • added HMI staple s-function sourced from primitive s-function.

2013b_0.0.4

• added raptor_get_faults script
• fixed mask labels on data read/write of vector/matrix when writing entire item
• updated mask font sizes for consistency
• updated raptor_can_gui.m to use a more efficient set_param, greatly reducing the time to open/close dialog with a large DBC file
• modified CAN gui block interface to be more readable
• updated XCP timestamp ticks to advertise proper 1ms resolution (XCP_TIMESTAMP_TICKS)
• update to resolve issue with intermittent single trip fault (incorrect states on second fail in the same drivecycle) in OBD FaultManager
• Updated raptor_elf to be able to determine function sizes from .debug_info section using GetVariableLength function
• Updated raptor_mem_usage to use .debug_info section for symbol lengths if the .symtab has a size of 0.
• update to not display 'Initializing Raptor...' twice.
• updated delta time block to provide proper output when attached to a conditional execution port
• update to allow optimization of outport on adjustment (expression compliance)
• update to allow optimization of inports on can tx msg and raw (expression compliance)
• updated vsfconverter to properly handle CM3620 files
• updated faults to use 1 based indexing (MAY REQUIRE APPLICATION UPDATE FOR FAULT ITERATORS)
• raptor_conf_editor, added 2014a, 2014b MathWorks
• updated raptor_sfun_delta_time and raptor_sfun_time to use the microsecond timebase for output in microsecond, second depending on ECU TimerPrecision_ms
• updated application monitor to utilize the microsecond timebase for enhanced precision for task time monitors
• update to parameterize pragmas for alignment (packing) of data segments as the existing pragmas were not supported by IARs (Freescale specific)
• HCM-5604-36-1303 (CM0711)
  • updated to SDK version 8
  • fixed EEPROM load logic that caused some models to brick the ECU
  • modified CanDefinition_VSCO to optionally exclude the call to set CAN bus baud rate (which is not supported in the current version of CM0711 SDK)
  • Renamed INPUT1 to WAKE_INPUT1
  • fixed AFB inputs for LSDs, added tests for AFB inputs for LSDs
  • added blocks to work with the 8M datalogging flash found in CM0711
• VEECAN320
  • Added LightingContrastCreate menu option to primitives.
  • Fixed lighting menu support with main loop lighting set.
  • Changed block background to VeeCAN background on primitive outimage and setkeyhandler blocks.
  • Added support for StateFlow in subsystems called by Screen definition.
  • Fixed compiler warning about "comparison of distinct pointer types lacks a cast"
  • Updated Raptor_VeeCAN_lib with some changes to Prefab parts (Battery, Gauges, etc.)
  • changed Button Image handlers to 1-based IDs. Also made it a block parameter instead of port.
  • Updated Raptor VEECAN Template project
  • Added message box notification after installation of CodeSourcery to restart PC.
• J1939
  • updated DM5 with clarification added in J1939-73AUG2013
  • updated DM11 to include clearing for pending, previously active, etc... in addition to confirmed
  • DM26, Update: Reserved bits are 0 per J1939-73AUG2013
  • DM24, Update: Reserved bits are 0 per J1939-73AUG2013
• HCM-ARM4-070-1401 (CM3620)
  • Files added but not available for use yet
• HCM-5534-90-XXXX
  • updated delta time block to provide proper output when attached to a conditional execution port
  • update to expose software filter options for current feedback internal measurements
  • updated CM3626 to new SDK version 991602_V0_23_Build_25 which includes a microsecond timebase

2013b_0.0.3

• updated raptor_template.mdl to point to HCM-5535-50 as default target instead of CM2115
• added missing mex64 files (some blocks previously couldn't be used on x64)
• updates for R2013b compatibility (please request Mathworks Patch if using 2013b)
• code generation settings enhancements
• update to support 2013a and forward (All index vectors returned by unique, union, intersect, setdiff, or setxor are column vectors.)
• updated supported MATLAB versions to remove 2011b
• updated make rtw to show matlab version in build log
• update to parallelize the compilation step of Raptor builds for 55xx targets (Codewarrior)
• fixed mask help on dT block
• updated CM0711 (HCM-5604-36-1303) to SDK build 6
• added CM0711 (HCM-5604-36-1303) EEPROM Support
• updated table1d and table2d to use direct library links to table_axis and interpolation table to allow reference blocks to work
• Updated the size of some labels which were cutting off some text in the raptor_can_gui.
• update to raptor_mask to provide a more expressive error message if target no longer exists (name change)
• CM0711(HCM-5604-36-1303) - fixed linker error with const-zero data
• updated J1939_PFW.xml to properly order ProtocolRxTable entries to prevent bricking the ECU.
• updated template project script to create include try/catch on model open/close callbacks
• added raptor_block_usage.m
• update to allow inlining of getFaultState on the Fault Status blocks to reduce local variable accesses
• fixed issue with Fault Status if multiple outputs where one is not in an expression compliant output
• fixed bug preventing output port label on fault status block (OBD Fault Manager)
• updated layout of data names on data def/read/write blocks to not overlay port labels
• updated Vansco Flashloader tool to show CM711 (HCM-5604-36-1303)
• updated automated regression testing of Raptor Releases to include Matlab 2012a,2012b,2013a,2013b for both x32 and x64 machine configurations
• added pinout diagrams to included datasheets ([InstallDirectory]\Documentation)
• J1939 library updates
  • updated to hide period parameter if user selects asynchronous or request only on PGN TX block
  • fixed raptor_j1939_pgn_tx block
  • update to allow two J1939 Transport protocol blocks to be defined in the model
  • update to default PGN master enable to true, if PGN Set Enable (Master) is in the model, it will zero out in the start code to function as before.
  • update to PGN tx to allow multiple instances, and to pack before send for periodic messages
  • simplified the PGN Tx block, optimize CPU utilization to pack only when a transmit will occur
  • fixed dest/src on TP raw pgn rx block
  • Update to not redefine identical PGN trigger items in the PGN trigger list
  • Update to count PGN triggers on the same PGN
  • updated PGN trigger management, if more than 1 pgn trigger is associated with 1 pgn then it will generate a parent function for the callback which calls child triggers
  • updated PGN raw rx to include a function call output to trigger when new data arrives
• VEECAN320
  • Added screen definition and screen Goto s-functions.
  • Added AlphaColor primitive.

2013b_0.0.2

• update to prevent warning on blocks held in a library link (Character/cell array of strings).
• Fixed bug in raptor_sfun_adjustment.tlc with 2d tables bad code could sometimes be generated.
• Added option to automatically probe the input/output of an override block.
• updated a2l generator to put memory segments in address order w/ segment summary
• updated vsf converter to handle extended memory CM3626
• update to make a2l generator data-driven from target XML file to enable support of HCM-5534-90-1302
• added validation to input blocks that ensures that the parameters on the block are valid for the selected target.
• added RAMEditVariables_DEFAULT to mem report in build
• updated HCM-5534-90-1302 to place EEVariables_RAMShadow and RAMEditVariables in external RAM
• update on WAKEINPUT for HCM-5534-90-xxxx, to avoid errant output
• updated raptor_rc.m to remove prior Raptor versions from path
• added sanity check for raptor_adjustment min/max values (min < max) on numeric parameters
• added raptor_sfun_fault_conf read to allow the application to read the configuration of a particular fault (EmmRelated, Permanent etc..)
• updated fault status management to match fault narrative in J1939-73 (flowchart) and customer feedback
• updated OBD Fault Manager in conjunction with customer feedback regarding OBD fault state transitions.
• added Fault state 'Previously MIL' to track OBD faults that were previously commanding MIL on.
• updated J1939 DM messages to populate DTCs according to J1939-73-AUG2013 Figure H3 (2013 ARB 13 1971.1 J1939 DIAGNOSTIC MESSAGE SIGNAL CHART)
• added configuration option on raptor_sfun_obd_fault_def for SingleTrip OBD faults per customer feedback
• added option in raptor_sfun_fault_conf_read to select reading of SingleTrip setting
• added DriveCycles and WarmupCycles count to the Fault Data Read to allow for custom clearing logic without duplicate bookkeeping.
• added raptor_sfun_table_axis_reference block
• updated interpolate 1D and 2D to accept axis reference as input
• added raptor_sfun_table_interpolate_1d_reference block
• added raptor_sfun_table_interpolate_2d_reference block
• updated Raptor block mask sizing for better readability
• updated raptor_sfun_delta_time to include options for units output (ms,sec,usec)
• updated raptor_sfun_time to include options for units output (ms, sec, usec)
• updated help with newly added blocks and logos
• updated raptor_configuration_editor support to include MathWorks 2013a, 2013b
• VEECAN320
  • additional gauges
  • added XCP support
  • added additional patchs for default image references
• HCM-5604-36-1303 (CM0711)
  • initial support w/o EEPROM or adjustable CAN baud rate(s)

2013b_0.0.1

Released 7/3/2013

• Fixed help link on Fault Blocks
• Updated ECU target naming to use PartNumber scheme to identify ECU
  • Renamed CM2115 to HCM-5534-50-1203
  • Renamed CM3626 to HCM-5534-90-1201
  • CM3626 with external FLASH/RAM exposed as HCM-5534-90-1302 (not available for use yet)
• Added the ability for user selection of a custom output file name for build
• Fixed bug allowing potential stack overflow during initiialization of models with very large number/size of data stores
• Added option for backpropagation of data type with adjustment block
• Added option to allow user selection of (Legacy, Vector, Kvaser) start bit display format on message based (DBC) CAN block masks
• Integrated V0.0.7 of New Eagle Licensing
• Fix to prevent warning: Inputs must be character arrays or cell arrays of strings.
• J1939 library updates
  • Allow use of DM1/DM2 with Standard Fault Manager vs full J1939 blockset with OBD Fault Manager
  • Fixed bug related to message buffer allocation size for dynamicly sized, multi-frame messages
• VEECAN320
  • Updated small analog gauge library block to contain data valid port & utilize Raptor strings
  • raptor_find_veecan_compilers: fix for 'version' variable not found on Module selection & build
  • Enhanced reliability of PC simulator execution
  • Updated image processing with image references to optimize code space and allow dynamic selection

2013a_0.0.4

Released 5/13/2013

• updated CM3626 to SDK 991602_V0_21_Build_23
• updated CM2115 to SDK 935605_V0_36_Build_48
• added HCM-5534-90-1302 target, a variant of CM3626 with populated external RAM (currently working) and external flash (not working yet)
• added String blocks to the library to make working with strings more efficient
• updated GettingStarted guide to include ATI Vision Setup
• added ability for inclusion of custom source in the build (/Source folder in project directory)
• added SwIdTxt variable
• added option to target definition block to define a minimum number for characters for version when appending to output files
• fix to prevent warning when override block is held in a library link
• fixed links in help to Raptor Tools
• fixed pointer issue in raptor_get_param that was causing a MATLAB crash when using Frequency Input
• updated help documentation to include string blocks
• fixed raptor_fault_data_def block EEPROM and RAM were switched
• fied issue with fault_data_def block when building a model with 0 or 1 fault definition
• J1939 library updates
  • allow PGN request of 3 or 8 byte lengths
  • fixed build errors when dm24 is included in a model by itself
  • added error checking when no DMS AS def block is present
  • fixed build error when J1939 TP block is included w/o and SPN read/write blocks
  • fixed bug when there is only one SPN read/write block
  • updated help documentation
  • fixed issue in SPN library causing a circular include
  • automatically include lamp SPNs when DTC send block(s) are included (default: Unavailable)
  • update to minimize transport protocol code if DTC send block(s) are not included
  • added custom SPN feature
  • added custom PGN feature
• VEECAN320
  • added FileIO blocks to allow working with the USB port on the back of the display
  • fixed issue with using 2 CAN busses
  • added splash screen block to allow application to define custom splash screen
  • created precompiled libraries to speed up build times
  • updated internal data from using analog blocks to internal measurements
  • updated VEECAN project template
  • updated EEPROM write count handling, removed mem stats from build output for this target

2013a_0.0.3

Released 4/3/2013

• fixed bug that prevented build when there are RAM variables, but none of them are Measurements
• fixed issue on raptor_sfun_freq_in, Frequency output port was improperly scaled
• added check to Mailbox Properties block to ensure there is not more than one per mailbox
• added support for Mailbox Properties to standard RX blocks
• J1939 library updates
  • fixed SPN write to use the IsAvailable port correctly
  • fixed SPN bit length for 3038
  • fixed send DTCs to send lamp flash status correctly when there are no faults
  • DM4 fixed buffer overflow issue
  • DM5 fixed output SPN ordering
  • added SPN1220 to spnDef.m
  • DM11 fixed duplicate ACK/NACK issue
  • DM1, DM3, DM25 addressing fix
  • DM7 fix to properly receive request
  • fixed issue where regular extended ID CAN messages could not be received if J1939 blocks were used.
  • broad documentation updates
  • DM14/15/16 cleanup from ported code
  • DM24, DM25, DM30 updates to properly respond to DM24 request
• OBD FaultManager updates
  • fixed x/y filter logic so that the Failing state gets cleared correctly
  • fixed raptor_sfun_fault_stateCount to pass the correct state flag into the sfunction
  • fixed bug that prevented Raptor build with only one OBD Counter Def block
  • added raptor_sfun_obd_counter_reset block
  • added raptor_sfun_obd_ratio_reset block
  • fixed raptor_sfun_iterator
• VEECAN320
  • added support for extended CAN RX slots
  • fix for button* hold repeated trigger event. It now triggers the button* hold action only once.
  • added VEECAN subfolders to path in raptor_rc

2013a_0.0.2

Released 3/4/2013

• Resolved known issue from 2013a_0.0.1 regarding dynamically sized transport protocol J1939 messages generated in response to a PGN request.
• Resolved issue where periodically transmitted CAN messages contained within an enabled subsystem would be transmitted if containing subsystem was initially disabled
• Moved error checks and build abortion earlier in the build to avoid extra build time for a failed build
• Updated handling of ID input port on CAN transmit message for more consistent operation and greater runtime flexibility (utilizes ID mask in conjunction with fixed ID and input port)
• VEECAN320, text block parameter is now eval'd on all blocks. Existing VEECAN320 models can be updated running raptor_veecan_update_text script
• Added J1939 support for CM2115
• Update to make 'Fault Data Definition' fields calibratible and extended configurability
• Added Row/Column headers for 'Data Definition' blocks
• Fixed bug preventing Adjustment blocks from being found if accessed via a Data Read block
• Updated Raptor Configuration Editor to allow commandline configuration of Matlab/Raptor configurations
• Added module datasheets in \Documentation folder, providing input/output configuration options exposed for each module resource

2013a_0.0.1

Released 2/19/2013

• Added Raptor J1939 library, a separate dongle flag is required to build a model containing these blocks
• Enhanced help integration, including Matlab start button navigation for Raptor and J1939 libraries
• Fixed off* by* one error causing data* type mismatch on CAN msg tx/rx blocks when showing ID
• Updated CM3626 to SDK 991602_V0_20_Build_22
• Enhanced mask logic to reduce build & update warnings
• Updated VeeCAN320 target to allow brightness and contrast outputs to work
• Changes in Raptor Configuration Editor to properly sort and display Raptor/Matlab combinations
• updated raptor_rlc.exe to prompt user to send report on application exeception

Known issue with dynamically sized transport protocol J1939 messages generated as a response to a PGN request.