GCM70: Difference between revisions

Latest revision as of 15:51, 28 August 2023

Overview

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.

Datasheets

GCM-5634M-070-1759

Datasheet

Obsolete

GCM-5634M-70-1459

Datasheet

GCM-5634M-070-1559

Datasheet

GCM-5634M-070-1562

Datasheet

GCM-5642A-070-1702

Datasheet

Pins and Crimping

Need to make a harness? Click here to get started.

Want to buy a pre-made harness? Click here to order.

Compiler

GCC PowerPC EABI 4.6.0 SPE

https://wiki.neweagle.net/ProductDocumentation/MotoTron/MotoHawk/gcc-powerpc-eabispe-4_6_0.exe

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)).

Calibrations

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.

Bootstrap

The GCM70 can be forced to remain in the firmware bootloader by applying a bootstrap sequence. The bootstrap sequence is:

Pin	State for Boot
AN1	High
AN2	High
AN3	High
AN4
AN5
AN6
AN7
AN8
AN9	Low
AN10	Low
AN11	Low

Raptor GCM70 Power Up Process

A product review and development tutorial:

Raptor GCM70 Power Up Process

Difference Between 1459 and 1559 Variants

Pins 39, 40, 41, 59 and 60 have different pull-up resistors.

SPD1 Limit

The frequency speed limit in the SPD1 resource is designed for 10K.

@@ Line 1: / Line 1: @@
-=Raptor GCM70=
+==Overview==
 [[File:GCM70.png|300px]]
-The GCM70 is a general purpose control module. The module has 2 CAN buses, and sports a 3-phase motor driver. The eclectic inputs and outputs make this module suitable for a wide variety of general purpose applications.
+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.
+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.
-==Variants==
+==<div style="font-size:21px; width:75%; font-weight:bold; text-align:left; padding-top:7px; padding-bottom:7px; background:#800020; color:white;">Datasheets</div>==
-:'''GCM-5634M-70-1459'''
+'''GCM-5634M-070-1759'''
-:'''GCM-5634M-70-1559'''
+:'''[https://www.neweagle.net/support/wiki/ProductDocumentation/Raptor/Controllers/GCM-5634M-070-1759_DataSheet.pdf Datasheet]'''
-:'''GCM-5634M-70-1562'''
-==Datasheets==
-*'''GCM-5634M-70-1459'''
-:'''[https://www.neweagle.net/support/wiki/ProductDocumentation/Raptor/Controllers/GCM-5634M-070-1459_DataSheet.pdf Datasheet]'''
-*'''GCM-5634M-70-1559'''
+===Obsolete===
+'''GCM-5634M-70-1459'''
+:'''[https://wiki.neweagle.net/ProductDocumentation/Raptor/Controllers/GCM-5634M-070-1459_DataSheet.pdf Datasheet]'''
+'''GCM-5634M-070-1559'''
 :'''[https://www.neweagle.net/support/wiki/ProductDocumentation/Raptor/Controllers/GCM-5634M-070-1559_DataSheet.pdf Datasheet]'''
-*'''GCM-5634M-70-1562'''
+'''GCM-5634M-070-1562'''
 :'''[https://www.neweagle.net/support/wiki/ProductDocumentation/Raptor/Controllers/GCM-5634M-070-1562_DataSheet.pdf Datasheet]'''
+'''GCM-5642A-070-1702'''
+:'''[https://www.neweagle.net/support/wiki/ProductDocumentation/Raptor/Controllers/GCM-5642A-070-1702_DataSheet.pdf Datasheet]'''
 ==Pins and Crimping==
 Need to make a harness? Click '''[https://store.neweagle.net/product/connector-kit-ecm70/ here]''' to get started.
-Want to buy a pre-made harness? Click '''[https://store.neweagle.net/product/harness-ecm70-pigtail-12-ft/ here]''' to order.
+Want to buy a pre-made harness? Click '''[https://store.neweagle.net/shop/products/connectors-tools/harnesses-connectors-connectors-tools/for-raptor-controllers-harnesses-connectors-connectors-tools/gcm70/harness-ecm70-pigtail-12-ft/ here]''' to order.
 == Compiler ==
 '''GCC PowerPC EABI 4.6.0 SPE'''
-:[http://www.neweagle.net/support/wiki/ProductDocumentation/MotoTron/MotoHawk/gcc-powerpc-eabispe-4_6_0.exe Download Now]
+:https://wiki.neweagle.net/ProductDocumentation/MotoTron/MotoHawk/gcc-powerpc-eabispe-4_6_0.exe
-<br/>
+''If opening with Chrome, please copy the download link and paste in the URL bar.
-== FAQ ==
+== Frequently Asked Questions (FAQ) ==
 ===Non-Volatile Memory Corruption===
-Non-Volatile memory can be corrupted during a write if the module is improperly powered off (ie removing power from Batt+ (Pin 68)).
+Non-Volatile memory can be corrupted during a write if the module is improperly powered off (i.e., removing power from Batt+ (Pin 68)).
 ===Calibrations===
-It is recommended to store all calibrations in Flash memory (available within the "raptor_target_def" block).
+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 on our '''[https://store.neweagle.net/product/boot-key-for-ecm555-48-80-gcm563-48-hcm563-48-ecm565-128-and-ecm5554-112/ store page]'''
+The GCM70 requires a boot key to recover the module. These can be found in our '''[https://store.neweagle.net/product/boot-key-for-ecm555-48-80-gcm563-48-hcm563-48-ecm565-128-and-ecm5554-112/ webstore]'''.
-The use the boot key to recover the malfunctioned module, please follow the Raptor-Cal MotoHawk Module Recovery steps provided: '''[[Raptor-Cal-FAQ#MotoHawk_Module_Recovery|Boot Key Recovery]]''' and '''below'''.
+To use the boot key to recover the malfunctioned module, please follow the Raptor-Cal MotoHawk Module Recovery steps provided '''[[Raptor-Cal-FAQ#MotoHawk_Module_Recovery|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. <br>Once the boot key is used, the module will default to a CAN baud rate of 250K, so update the Raptor-Cal settings accordingly.
-Notes: <br>The Boot Key signal (Pin E on the Smartcraft connector) needs to be connected to the '''SWG4''' pin for the GCM70. <br>Once the bootkey is used, the module will default to a '''CAN baud rate of 250k''', so update the Raptor-Cal settings accordingly.
 '''Power Cycle Instructions:'''
-*Step 1: Remove all power to the module by turning off Key switch and then power supply. Connect the Boot Key to the bus.
+#Remove all power to the module by turning off the key-switch and then the power supply. Connect the boot key to the bus.
-*Step 2: From Raptor-CAL/Service: Select Program, then the recover check box, MotoHawk, Select the .RPG file.
+#From Raptor-CAL/Service: Select Program -> click the Recover checkbox -> MotoHawk -> select the RPG file.
-*Step 3: Click OK, turn on power supply, then key switch.
+#Click OK, turn on the power supply, then the key-switch.
-For a full list of steps, see the '''[[Raptor-Cal-FAQ#How_do_I_recover_a_bricked_module.3F|Raptor-CAL FAQ Page]]'''
+For a full list of steps, see the '''[[Raptor-Cal-FAQ#How_do_I_recover_a_bricked_module.3F|Raptor-CAL FAQ Page]]'''.
-<br/>
 ===Bootstrap===
 The GCM70 can be forced to remain in the firmware bootloader by applying a bootstrap sequence.  The bootstrap sequence is:
 {| class="wikitable"
+!scope="col" style="width:100px;"|Pin
+!scope="col" style="width:100px;"|State for Boot
 |-
-! &nbsp;&nbsp;Pin&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; !! State for Boot
+|style="text-align:center;"|AN1
+|style="text-align:center;"|High
 |-
-| &nbsp;&nbsp;AN1 || &nbsp;&nbsp;High
+|style="text-align:center;"|AN2
+|style="text-align:center;"|High
 |-
-| &nbsp;&nbsp;AN2 || &nbsp;&nbsp;High
+|style="text-align:center;"|AN3
+|style="text-align:center;"|High
 |-
-| &nbsp;&nbsp;AN3 || &nbsp;&nbsp;High
+|style="text-align:center;"|AN4
+|
 |-
-| &nbsp;&nbsp;AN4 ||
+|style="text-align:center;"|AN5
+|
 |-
-| &nbsp;&nbsp;AN5 ||
+|style="text-align:center;"|AN6
+|
 |-
-| &nbsp;&nbsp;AN6 ||
+|style="text-align:center;"|AN7
+|
 |-
-| &nbsp;&nbsp;AN7 ||
+|style="text-align:center;"|AN8
+|
 |-
-| &nbsp;&nbsp;AN8 ||
+|style="text-align:center;"|AN9
+|style="text-align:center;"|Low
 |-
-| &nbsp;&nbsp;AN9 || &nbsp;&nbsp;Low
+|style="text-align:center;"|AN10
+|style="text-align:center;"|Low
 |-
-| &nbsp;&nbsp;AN10 || &nbsp;&nbsp;Low
+|style="text-align:center;"|AN11
-|-
+|style="text-align:center;"|Low
-| &nbsp;&nbsp;AN11 || &nbsp;&nbsp;Low
 |}
-===Raptor™ GCM 70 Power Up Process===
+===Raptor GCM70 Power Up Process===
-'''[https://www.neweagle.net/support/wiki/ProductDocumentation/Raptor/Controllers/GCM70PowerUp.pdf Raptor™ GCM 70 Power Up Process]''', a product review and development tutorial.
+A product review and development tutorial:
+:'''[https://www.neweagle.net/support/wiki/ProductDocumentation/Raptor/Controllers/GCM70PowerUp.pdf Raptor GCM70 Power Up Process]'''
-===Difference Between 1459 and 1559 variants ===
+===Difference Between 1459 and 1559 Variants ===
-Pins 39, 40, 41, 59, & 60 have different pull-up resistors
+Pins 39, 40, 41, 59 and 60 have different pull-up resistors.
 ===SPD1 Limit===
 The frequency speed limit in the SPD1 resource is designed for '''10K'''.

GCM70: Difference between revisions

Latest revision as of 15:51, 28 August 2023

Contents

Overview

Datasheets

Obsolete

Pins and Crimping

Compiler

Frequently Asked Questions (FAQ)

Non-Volatile Memory Corruption

Calibrations

Recovery Procedure (Boot Key)

Bootstrap

Raptor GCM70 Power Up Process

Difference Between 1459 and 1559 Variants

SPD1 Limit

Navigation menu