EasyManua.ls Logo

Curtis Instruments 1351 User Manual

Default Icon
144 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #85 background imageLoading...
Page #85 background image
5 — VEHICLE CONTROL LANGUAGE (VCL)
pg. 79
Return to TOC Curtis Model 1351 – December 2018
Variables and Constants
All 1351 VCL user variables and parameters are 32-bit signed integers. is greatly simplies many
mathematical operations, as the risk of integer overow is greatly reduced. Note that Constants are
limited to 16 bits.
VCL VARIABLE TYPES AND MEMORY
VCL provides dedicated memory space to store custom variables. e variable type determines whether
they are stored and used in volatile memory or stored non-volatile memory.
VCL uses 2 types of memory.
1. RAM (Random Access Memory) which is volatile memory for the VCL run-time variables.
2. FRAM, (Flash Random Access Memory) is non-volatile memory (NVM) for retaining variable
values for power-up/down logs.
RAM variables are stored only while power is on; they are lost at power-down. ey must be initialized
upon power-up by explicit VCL assignments. e user and autouser variables are in this category (i.e.,
User1 = 12).
FRAM variables can be saved at power-down and restored at power-on. e P_Users (parameters)
and NVUser variables are in this category (i.e., P_User12 and NVUser12).
At power-up, all variables values are loaded in to RAM for run-time operation.
P_User parameters are a special type of variable that is intended to be used to create OEM dened
CSS/1313 HHP programmer parameters. ese parameters can be dened up to 32-bit by using the
P_User (1-300) variables. ese variables are typically written to FRAM through the CSS or 1313
HHP Programmer app (i.e., when a dealership technician changes these created parameter settings
using the 1313 HHP). ese P_User variables can be used/changed in the VCL code, but changing
a P_User value with VCL will only change the variable value in RAM and will not change the value in
FRAM. us, these variables are intended for creating and dening CSS and 1313 HHP Programmer
app parameters only.
VCL can modify the control mode parameters in RAM by using the VCL variable name for the
programmable parameter. For example,
Driver_1_Ramp_Up_Time = 300 ; Change Ramp-up Rate to 300 ms
will change the RAM value of the Driver 1 Ramp Up; the new value will be used in determining the ramp-
up rate during operation. However, the value of the parameter’s stored in FRAM remains unchanged; so
when the controller is turned o, the run-time RAM value will be lost. e next time the 1351 system
controller is powered back on, the “old” value of Ramp Up will be restored from FRAM memory. To
save this RAM value in VCL, the VCL writer must use the NVM_Write_Parameter function ((i.e.,
NVM_Write_Parameter(Driver_1_Ramp_Up_Time)).
Once again, Parameter values that are changed by using the CSS or 1313 HHP programmer are saved
directly to FRAM memory. e CSS and 1313 HHP changes will be retained and restored the next time
the 1351 system controller is powered back on.
Table 21 summaries the available 1351 system controller VCL variables by memory type.

Table of Contents

Questions and Answers:

Curtis Instruments 1351 Specifications

General IconGeneral
CategoryI/O Systems
Model1351
Operating Temperature Range-40°C to +85°C
Protection FeaturesOvervoltage, Short Circuit
Communication InterfaceCAN 2.0B

Summary

1 — OVERVIEW

How to Use This Manual

Explains how to use the manual's content and structure.

Getting the Most Out of Your Curtis Controller

Tips for optimal use and contact for technical support.

2 — INSTALLATION SPECIFICATIONS AND WIRING

Mounting and Safety Precautions

Guidelines for physical mounting and general safety warnings.

Wiring and Connections

Details on AMPSEAL connector, battery, low-power wiring, and voltages.

Input/Output Configuration

Overview of various input and output types and their configurations.

Communication Ports and Power

Details on CAN ports, power supply outputs, and keyswitch connections.

3 — PROGRAMMABLE PARAMETERS

Programming Menus and Format

Overview of parameter menus, chart format, and terminology.

System Controller Parameters

Parameters for power, BDI, external supplies, and temperature.

Input Parameters

Configuration for switches, virtual switches, analog, pot, RTD, high-speed, encoder inputs.

Output Parameters

Configuration for PWM drivers, half-bridge, digital drivers, safety, and analog outputs.

CAN Parameters

Settings for CAN ports and communication protocols.

4 — MONITOR VARIABLES

System Controller Monitor Variables

Read-only variables for system controller status and measurements.

Input Monitor Variables

Read-only variables for various input types like switches, analog, and encoders.

Output Monitor Variables

Read-only variables for PWM drivers, half-bridge drivers, and digital outputs.

Accelerometer Monitor Variables

Read-only variables for the 3-axis accelerometer data.

5 — VEHICLE CONTROL LANGUAGE (VCL)

VCL Overview and Basics

Introduction to VCL, its capabilities, and fundamental programming rules.

Variables and Constants

Explanation of VCL variable types, memory storage, and constants.

VCL, Watchdog Timer and Faults

Setting up watchdog timers and defining fault actions within VCL code.

CAN Functions (VCL Setup)

VCL functions for CAN setup, message handling, and NMT control.

SDO Management

VCL functions for managing Service Data Objects (SDOs) read/write operations.

CAN Mailbox Operations

Functions for allocating and configuring CAN mailboxes for data transmission/reception.

SRDO Functions

VCL functions for Safety Related Data Objects transmission and reception.

6 — INITIAL SETUP & COMMISSIONING

Initial Setup and Preparation

Steps for initial setup, safety, and preparation before commissioning.

Parameter Settings Method Overview

Recommended sequence for setting hardware and software parameters.

Output Parameter Configuration

Procedure for configuring PWM, half-bridge, digital, and analog outputs.

Fault Clearing Procedure

Steps to check, clear, and resolve controller faults and history.

7 — DIAGNOSTIC AND TROUBLESHOOTING

The Diagnostics Process

Methods for obtaining diagnostics information via LEDs, software, or CAN messages.

Error Flash Code Interpretation

Explanation of LED flash patterns and their meanings for fault codes.

8 — MAINTENANCE

Cleaning Procedures

Recommended procedure for cleaning the controller exterior.

Fault History Management

Accessing, checking, and clearing the controller's fault history file.

APPENDIX A — VCL FUNCTIONS

General VCL Functions

Core VCL functions for various operations like interpolation, timing, and scaling.

CANopen Functions

VCL functions for CANopen mailbox setup and configuration.

SRDO Functions

VCL functions for Safety Related Data Objects transmission and reception.

APPENDIX B — VEHICLE SYSTEM DESIGN CONSIDERATIONS-&-RECYCLING

Electromagnetic Compatibility (EMC)

Guidelines for EMC performance, emissions, RF immunity, and noise reduction.

Decommissioning and Recycling the Controller

Procedures for controller removal from OEM vehicle and disposal.

APPENDIX C — PROGRAMMING DEVICES FOR THE 1351

Curtis Software Suite™

PC-based software for controller setup, parameter adjustment, and diagnostics.

Curtis 1313 Handheld Programmer

Standalone programmer and diagnostic tool for the system controller.

APPENDIX D — EN 13849 COMPLIANCE

Safety-Related Performance Analysis

Summary of safety performance levels (PL, MTTFd, DC) for controller circuits.

APPENDIX E — 1351 MODELS AND SPECIFICATIONS

Table E Model Chart and Specifications

Technical specifications, model comparison, and environmental ratings.