The GCM70 is a general-purpose control module. The module has two CAN buses and sports a three-phase motor driver. The eclectic inputs and outputs make this module suitable for a wide variety of general-purpose applications.
The GCM70 is part of a family of rugged, automotive-grade production controllers that use a software development process based on MATLAB/Simulink, known as Raptor-Dev. Raptor-Dev significantly speeds up algorithm development by using automatic code generation. In addition, developers can quickly test application software on their PCs with a built-in onscreen PC simulation.
Pins and Crimping
Need to make a harness? Click here to get started.
Want to buy a pre-made harness? Click here to order.
GCC PowerPC EABI 4.6.0 SPE
If opening with Chrome, please copy the download link and paste in the URL bar.
Frequently Asked Questions (FAQ)
Non-Volatile Memory Corruption
Non-Volatile memory can be corrupted during a write if the module is improperly powered off (i.e., removing power from Batt+ (Pin 68)).
In production programs, it is recommended to store all calibrations in Flash memory (available within the "raptor_target_def" block).
Recovery Procedure (Boot Key)
The GCM70 requires a boot key to recover the module. These can be found in our webstore.
To use the boot key to recover the malfunctioned module, please follow the Raptor-Cal MotoHawk Module Recovery steps provided here and below.
Note: The boot key signal (Pin E on the SmartCraft connector) needs to be connected to the SWG4 pin for the GCM70.
Once the boot key is used, the module will default to a CAN baud rate of 250K, so update the Raptor-Cal settings accordingly.
Power Cycle Instructions:
- Remove all power to the module by turning off the key-switch and then the power supply. Connect the boot key to the bus.
- From Raptor-CAL/Service: Select Program -> click the Recover checkbox -> MotoHawk -> select the RPG file.
- Click OK, turn on the power supply, then the key-switch.
For a full list of steps, see the Raptor-CAL FAQ Page.
The GCM70 can be forced to remain in the firmware bootloader by applying a bootstrap sequence. The bootstrap sequence is:
|State for Boot
Raptor GCM70 Power Up Process
A product review and development tutorial:
Difference Between 1459 and 1559 Variants
Pins 39, 40, 41, 59 and 60 have different pull-up resistors.
The frequency speed limit in the SPD1 resource is designed for 10K.