Difference between revisions of "CAL Components"

From Flowcode Help
Jump to navigationJump to search
Line 1: Line 1:
 
<sidebar>Sidebar: Flowcode Help Overview:Components</sidebar>
 
<sidebar>Sidebar: Flowcode Help Overview:Components</sidebar>
 +
 +
 +
[[_TOC_]]
 +
 +
 
The '''CAL''' (Code Abstraction Layer) components are designed to simplify the creation of controller programs or other related components.
 
The '''CAL''' (Code Abstraction Layer) components are designed to simplify the creation of controller programs or other related components.
  
Line 10: Line 15:
 
==CAL Components==
 
==CAL Components==
  
*[[Component:_ID_e77a4e40_e0df_431a_98f8_7ae4d8ebfbeb|CAL ADC Component]]
+
 
*[[Component:_ID_8a1cca2f_7df1_4b3a_b24b_ca575fe84348|CAL CAN Component]]
+
===CAL ADC===
*[[Component:_ID_18738948_277c_4ed2_8be0_becc616cb0b9|CAL EEPROM Component]]
+
 
 +
The [[Component: ID e77a4e40 e0df 431a 98f8 7ae4d8ebfbeb|ADC (CAL)]] component enables you to use any available ADC (Analogue to Digital Converter) functionality of the target device in a simplified way.
 +
Via this component a voltage present on an analogue input can be read as a digital value.
 +
This enables your project to include analogue inputs from potentiometers through to more complex measuring instruments and sensors that output an analogue voltage.
 +
 
 +
The ADC CAL component is the basis of other ADC components that then further add visual effects to aid simulation, such as representing the analogue input as sliders or dials.
 +
 
 +
 
 +
 
 +
===CAL CAN===
 +
 
 +
The [[Component: ID 8a1cca2f 7df1 4b3a b24b ca575fe84348|CAN (CAL)]] component enables simplified use of, if available, the CAN (Controller Area Network) functionality of the target device.
 +
 
 +
A CAN is a rugged digital serial communications bus and is designed specifically to allow micro-controllers and devices to communicate with each other within a vehicle.
 +
 
 +
 
 +
Devices typically used in CAN networks mainly consist of sensors, actuators and other control devices which are connected through a host processor and CAN controller and not directly through the bus.
 +
 
 +
 
 +
CAN features an automatic arbitration-free transmission. A CAN message that is transmitted with highest priority will succeed, and the node transmitting the lower priority message will sense this and back off and wait. Message IDs must be unique on a single CAN bus, otherwise two nodes would continue transmission beyond the end of the arbitration field (ID) causing an error.
 +
 
 +
 
 +
 
 +
===CAL EEPROM===
 +
 
 +
The [[Component: ID 18738948 277c 4ed2 8be0 becc616cb0b9|EEPROM (CAL)]] component provides a common application interface to any on-board EEPROM (Electrically Erasable Programmable Read-Only Memory) such that it can easily be used for non-volatile data and parameter storage. EEPROMs are used to store and save data when the power is removed, this is important to use to store calibration tables or device configuration.
 +
 
 +
 
 +
There are different types of electrical interfaces to EEPROM devices which consist of two main categories, serial bus and parallel bus. The most common serial interface types are [[CAL - SPI|SPI]], [[CAL - I2C|I2C]], Microwire, UNI/O, and 1-Wire.
 +
 
 +
 
 +
EEPROM memory is used to enable features in other types of products aren't strictly memory products, e.g. real-time clocks, digital potentiometers, digital temperature sensors etc.
 +
 
 +
 
 
*[[Component:_ID_ed3a5141_43bb_43e0_86b0_2243fd1147ca|CAL I2C Component]]
 
*[[Component:_ID_ed3a5141_43bb_43e0_86b0_2243fd1147ca|CAL I2C Component]]
 +
 
*[[Component:_ID_068080a0_b949_4a7e_b370_c45430e0c9de|CAL PWM Component]]
 
*[[Component:_ID_068080a0_b949_4a7e_b370_c45430e0c9de|CAL PWM Component]]
 +
 
*[[Component:_ID_c67171df_0ad6_4b11_8361_cfe14b072847|CAL SPI Component]]
 
*[[Component:_ID_c67171df_0ad6_4b11_8361_cfe14b072847|CAL SPI Component]]
*[[Component:_ID_91b64b1d_b8b2_40f1_b073_e953a91fa234|CAL UART Component]]
+
 
 +
 
 +
 
 +
===CAL UART===
 +
 
 +
The [[Component: ID 91b64b1d b8b2 40f1 b073 e953a91fa234|UART (CAL)]] component provides a UART (Universal Asynchronous Receiver/Transmitter) channel by either interfacing with a microcontroller based hardware feature or by using the I/O pins of the microcontroller driven in software mode.
 +
 
 +
A UART is an asynchronous serial communication device that has a Transmit output, a Receive input and optionally additional handshake lines such as CTS (Clear To Send) and RTS (Request To Send).
 +
 
 +
A UART is typically used to transmit and receive data over longer distances, in which case electric signalling levels and methods are applied external to the UART. These are implemented in the form of communication standards such as RS-232 and RS-485. The choice of standard depends upon requirements such as distance, noise immunity, Full-Duplex transfer ability etc.

Revision as of 11:00, 1 September 2014

<sidebar>Sidebar: Flowcode Help Overview:Components</sidebar>


_TOC_


The CAL (Code Abstraction Layer) components are designed to simplify the creation of controller programs or other related components.


They encapsulate the internal functionality of the supported micro-controller device features.

In this way your Flowcode program, or component, uses a consistent interface to the functionality irrespective of the actual target micro-controller device.


CAL Components

CAL ADC

The ADC (CAL) component enables you to use any available ADC (Analogue to Digital Converter) functionality of the target device in a simplified way. Via this component a voltage present on an analogue input can be read as a digital value. This enables your project to include analogue inputs from potentiometers through to more complex measuring instruments and sensors that output an analogue voltage.

The ADC CAL component is the basis of other ADC components that then further add visual effects to aid simulation, such as representing the analogue input as sliders or dials.


CAL CAN

The CAN (CAL) component enables simplified use of, if available, the CAN (Controller Area Network) functionality of the target device.

A CAN is a rugged digital serial communications bus and is designed specifically to allow micro-controllers and devices to communicate with each other within a vehicle.


Devices typically used in CAN networks mainly consist of sensors, actuators and other control devices which are connected through a host processor and CAN controller and not directly through the bus.


CAN features an automatic arbitration-free transmission. A CAN message that is transmitted with highest priority will succeed, and the node transmitting the lower priority message will sense this and back off and wait. Message IDs must be unique on a single CAN bus, otherwise two nodes would continue transmission beyond the end of the arbitration field (ID) causing an error.


CAL EEPROM

The EEPROM (CAL) component provides a common application interface to any on-board EEPROM (Electrically Erasable Programmable Read-Only Memory) such that it can easily be used for non-volatile data and parameter storage. EEPROMs are used to store and save data when the power is removed, this is important to use to store calibration tables or device configuration.


There are different types of electrical interfaces to EEPROM devices which consist of two main categories, serial bus and parallel bus. The most common serial interface types are SPI, I2C, Microwire, UNI/O, and 1-Wire.


EEPROM memory is used to enable features in other types of products aren't strictly memory products, e.g. real-time clocks, digital potentiometers, digital temperature sensors etc.



CAL UART

The UART (CAL) component provides a UART (Universal Asynchronous Receiver/Transmitter) channel by either interfacing with a microcontroller based hardware feature or by using the I/O pins of the microcontroller driven in software mode.

A UART is an asynchronous serial communication device that has a Transmit output, a Receive input and optionally additional handshake lines such as CTS (Clear To Send) and RTS (Request To Send).

A UART is typically used to transmit and receive data over longer distances, in which case electric signalling levels and methods are applied external to the UART. These are implemented in the form of communication standards such as RS-232 and RS-485. The choice of standard depends upon requirements such as distance, noise immunity, Full-Duplex transfer ability etc.