en:strumenti:qmoveplus:c1r11:mimc1r11fx

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:strumenti:qmoveplus:c1r11:mimc1r11fx [2019/02/19 14:46] – [Hardware versions] qem103en:strumenti:qmoveplus:c1r11:mimc1r11fx [2019/08/29 17:01] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +~~BOZZA~~
 +PRELIMINARE/
  
 +====== C1-R11-Fx ======
 +
 +{{strumenti:QmovePlus:c1R11:c1R11_3d_02.png?nolink&500|C1-R11}}
 +
 +<html><pagebreak /></html>
 +
 +====== - Information ======
 +
 +===== Release =====
 +
 +^ Document release ^ Description ^ Notes ^ Date ^
 +|  01  | New manual | Valido per release hardware a partire da 02 e major release firmware a partire da 5 FIXME  |23/04/2012|
 +|  02  | Inserito modello FF | |08/04/2013|
 +|  03  | Cancellato modello FC | |16/04/2013|
 +|  04  | Add 1MG5F card | |  29/10/2013  |
 +
 +{{page>en:lib:mdl:mdl-h-cemarce-010}}
 +
 +<html><pagebreak /></html>
 +
 +====== - Description ======
 +**C1-R11-F** è un controllore compatto da retroquadro della gamma Qmove+ che, nella sua massima configurazione, può essere dotato di:
 +
 +^  Standard Hardware||
 +|{{Icone:Icona_prog.png?nolink&50}}|1 PROG serial port for programming (For use with interface accessory  [[Strumenti:Accessori:IQ009]])|
 +|{{Icone:Icona_seriale.png?nolink&50}}|1 multistandard serial port (RS232/422/485) - USER PORT|
 +|{{Icone:Icona_mmc.png?nolink&50}}|1 MMC/SD card slot|
 +|{{Icone:Icona_led.png?nolink&50}}|4 signal led's|
 +|{{Icone:Icona_led.png?nolink&50}}|8 system led's|
 +|{{Icone:Icona_morsetti.png?nolink&50}}|Anti-vibration spring clip terminals|
 +|{{Icone:Icona_orologio.jpg?nolink&50}}|Clock calendar|
 +^  Optional hardware (Consult the table: [[#Hardware Versions]])  ||
 +|{{Icone:Icona_seriale.png?nolink&50}}|1 multistandard serial port (RS232/422/485) – AUX1 PORT|
 +|{{Icone:Icona_seriale.png?nolink&50}}|1 RS485 serial port - AUX2 PORT|
 +|{{Icone:Icona_canbus.png?nolink&50}}|2 CANbus ports [(the second CANbus port is not enabled)]|
 +|{{Icone:Icona_usb.png?nolink&50}}|1 USB PORT[(not enabled)]|
 +|{{Icone:Icona_ethernet.png?nolink&50}}|1 ETHERNET port|
 +|{{Icone:Icona_rmk.png?nolink&50}}|1 qem remote keypad port|
 +|{{Icone:Icona_digital-in.png?nolink&50}}|32 standard digital inputs (+16 inputs instead of 8 count inputs)|
 +|{{Icone:Icona_analog-in.png?nolink&50}}|4 analog inputs|
 +|{{Icone:Icona_fast-in.png?nolink&50}}|4 fast inputs|
 +|{{Icone:Icona_cnt-abz.png?nolink&50}}|8 two-way count inputs|
 +|{{Icone:Icona_digital-out.png?nolink&50}}|32 digital outputs|
 +|{{Icone:Icona_analog-out.png?nolink&50}}|8 analog outputs|
 +|{{Icone:Icona_stepper-out.png?nolink&50}}|5 pulse-direction outputs for stepper motors|
 +~~REFNOTES~~
 +
 +===== Product Identification ===== 
 +<WRAP center round tip 60%>
 +The Ordering Code provides the exact product characteristics.
 +Make sure that the product characteristics meet your requirements.
 +</WRAP>
 +
 +==== Product Label ====
 +{{strumenti:qmoveplus:c1r11:c1r11_etichetta-prodotto_01.png?nolink&400}}
 +
 +  * **a - Ordering Code**
 +  * **b - Week made**: indicates the week and year of manufacture
 +  * **c - Part number**: unique code that identifies an ordering code
 +  * **d - Serial number**: product serial number, different for individual product 
 +  * **e - Hardware release**: version of hardware release
 +
 +<html><pagebreak /></html>
 +
 +===== Ordering Code =====
 +
 +|Model||| |Features|||
 +^**C1**|-^**R11**|-^**FA**|-^**10**|
 +|      | |       | |      | |**10** = Firmware version  (00 = not installed)|
 +|      | |       | |**F**  = Technologic level\\ **A**  = Hardware version|||
 +|      | |**R**  = Cabinet mounted\\ **1**  = Dimensions (198x178mm)\\ **1**  = Firmware-Hardware combination|||||
 +|**C1** = Qmove+ "PLC+Motion" family|||||||
 +
 +<html><pagebreak /></html>
 +
 +==== Hardware versions ====
 +
 +There are currently 8 hardware versions available:
 +
 +| |^  Hardware Versions  ||||||||
 +| |^A^B^C^D^E^F^Y^Z^
 +^SLOT 2\\ (Base Card)^USER PORT (RS232, RS422, RS485)|1|1|1|1|1|1|1|1|
 +^:::^AUX1 PORT (RS232, RS422, RS485)|-|-|-|-|-|-|-|1|
 +^:::^AUX2 PORT (RS485)|1|1|1|1|1|1|1|1|
 +^:::^CAN1 PORT|1|1|1|1|1|1|1|1|
 +^:::^CAN2 PORT[(option not yet enabled)]|-|-|-|-|-|-|-|1|
 +^:::^ETHERNET PORT|1|1|1|1|1|1|1|1|
 +^:::^USB PORT[(#1)]|-|-|-|-|-|-|-|-|1
 +^SLOT 3\\ (Specialist\\ card)^Standard digital inputs|-|16|16|16|16|16|16|16|
 +^:::^Fast Digital inputs [(The fast inputs can be used as frequency meters inside the "FREQ" device)]|-|2|2|2|2|2|2|2|
 +^:::^12bit analog inputs|-|2|2|2|2|2|2|2|
 +^:::^16bit analog inputs|-|-|-|-|-|-|-|-|
 +^:::^PT100 inputs [(#1)]|-|-|-|-|-|-|-|-|
 +^:::^Thermocouple inputs [(#1)]|-|-|-|-|-|-|-|-|
 +^:::^20kHz two-way count inputs, ABZ\\ (24V-PP, 5V-LD)|-|-|-|-|-|-|-|-|
 +^:::^200kHz two-way count inputs, ABZ\\ (24V-PP, 5V-LD)|-|2[(CN7 e CN8)]|2[(#3)]|4|4|4|2|4|
 +^:::^Protected digital outputs|-|8|16|8|16|8|8|8|
 +^:::^Digital relay outputs|-|-|-|-|-|-|-|-|
 +^:::^0-10V, 12bit analog outputs|-|-|-|-|-|-|-|-|
 +^:::^+/-10V, 16bit analog outputs|-|2|2|2|4|4|4|4|
 +^:::^Stepper outputs|-|-|-|2|-|-|4|4|
 +^:::^Connector for remote control panels [(#1)]|-|-|-|-|-|-|1|1|
 +^Card software code\\ declared in SLOT 3^|-|1MG3F|1MG5F|1MG3F|1MG5F|1MG3F|1MG3F|1MG3F|
 +~~REFNOTES~~
 +
 +==== Firmware Versions ====
 +
 +^Version^Description^
 +|  10  |Fully programmable with PLC functions|
 +|  20  |Fully programmable with PLC and Motion control functions|
 +|  30  |Fully programmable with PLC, Motion control, Camming and Interpolation functions|
 +
 +For more details about the various characteristics of the firmware, consult the table [[software:devices#Devices enabled in the controllers]].
 +
 +===== Product Configuration =====
 +==== Front Panel ====
 +
 +C1-R11-F is configured with a specialist card installed in slot 3.
 +
 +{{strumenti:qmoveplus:C1R11:C1R11_slots_01.png?nolink&400}}
 +
 +^Slot^Description^
 +|[[#Slot Supply]]|Power connector on Base card|
 +|[[#Slot 2]]|Base card|
 +|[[#Slot 3 – 1MG4F card connector|Slot 3]]|Expansion card|
 +
 +<html><pagebreak /></html>
 +
 +====== - Technical Features ======
 +===== General Characteristics =====
 +^Weight (full hardware)|1Kg|
 +^Housing|Sheet metal|
 +^System led's|8|
 +^System keys|3|
 +^Operating temperature|0 - 50°C|
 +^Relative humidity|90% condensate free|
 +^Altitude|0 - 2000m a.s.l.|
 +^Transport and storage temperature|-25 - +70   °C|
 +^Protection rating|IP20|
 +
 +===== CPU (F Technologic level) =====
 +^RISC microprocessor (32 bit)^^
 +^Work frequency|  200MHz|
 +^RAM|  16MB|
 +^Flash|  8MB|
 +
 +<WRAP center round info 60%>
 +For more information on use of the memory consult  
 +[[sezioni:funzionamento:info_programmazione:Memorie_utilizzate|Memories used]]
 +</WRAP>
 +
 +===== Dimensions =====
 +<WRAP round info 300px>
 +Lengths in mm.
 +</WRAP>
 +
 +{{strumenti:qmoveplus:c1R11:c1R11_dimensioni_01.png?nolink&500}}
 +
 +===== Hole template =====
 +{{strumenti:qmoveplus:c1R11:c1R11_dima_01.png?nolink&400 }}\\
 +
 +{{page>en:lib:mdl:mdl-h-mccabla-010}}
 +
 +<html><pagebreak /></html>
 +
 +====== - Electrical features and wiring ======
 +===== Slot Supply =====
 +{{strumenti:qmoveplus:j1k31:j1k31_slot-supply_01.png?nolink&300 }}\\
 +
 +{{page>en:lib:mdl:mdl-h-cnalim-010}}
 +
 +<html><pagebreak /></html>
 +
 +===== Slot 2 =====
 +{{strumenti:qmoveplus:c1r11:c1r11_slot2_01.png?nolink&700}}
 +
 +==== Serial connections ====
 +
 +{{page>en:lib:mdl:mdl-h-cnprogp-010}}
 +
 +{{page>en:lib:mdl:mdl-h-cnuserp-010}}
 +
 +{{page>en:lib:mdl:mdl-h-cnaux1-010}}
 +
 +{{page>en:lib:mdl:mdl-h-cnaux2-010}}
 +
 +{{page>en:lib:mdl:mdl-h-cncan-010}}
 +
 +{{page>en:lib:mdl:mdl-h-cneth-010}}
 +
 +{{page>en:lib:mdl:mdl-h-cnmmc-010}}
 +
 +==== Serial connection features ====
 +
 +{{page>en:lib:mdl:mdl-h-ceprog-010}}
 +
 +{{page>en:lib:mdl:mdl-h-cers232-010}}
 +
 +{{page>en:lib:mdl:mdl-h-cers422-010}}
 +
 +{{page>en:lib:mdl:mdl-h-cers485-010}}
 +
 +{{page>en:lib:mdl:mdl-h-cecan-010}}
 +
 +{{page>en:lib:mdl:mdl-h-ceeth-010}}
 +
 +{{page>en:lib:mdl:mdl-h-cemmc-010}}
 +
 +<html><pagebreak /></html>
 +
 +/*--------------------------------------------1MG3F-----------------------------------------------*/
 +
 +===== Slot 3 – 1MG3F card connectors =====
 +
 +{{strumenti:qmoveplus:c1r11:c1r11_1mg3f_01.png?nolink&600|Rear view of SLOT 3 - Card 1MG3F}}
 +
 +==== Digital inputs ====
 +{{page>en:lib:mdl:mdl-h-cndiginp-010}}
 +
 +{{page>en:lib:mdl:mdl-h-cncount-010}}
 +
 +==== Analog inputs ====
 +{{page>en:lib:mdl:mdl-h-cnanimp-010}}
 +
 +==== Digital outputs ====
 +{{page>en:lib:mdl:mdl-h-cndigout-010}}
 +
 +{{page>en:lib:mdl:mdl-h-cnstep-010}}
 +
 +==== Analog outputs ====
 +{{page>en:lib:mdl:mdl-h-cnanout-010}}
 +
 +
 +/*--------------------------------------------1MG5F-----------------------------------------------*/
 +
 +===== Slot 3 – 1MG5F card connectors =====
 +{{strumenti:qmoveplus:c1r11:c1r11_1mg5f_01.png?direct&700|Rear view of SLOT 3 - Card 1MG5F}}
 +
 +==== Digital inputs ====
 +
 +{{page>en:lib:mdl:mdl-h-cndiginp-030}}
 +
 +{{page>en:lib:mdl:mdl-h-cncount-030}}
 +
 +{{page>en:lib:mdl:mdl-h-cncntssi-010}}
 +
 +
 +==== Analog inputs ====
 +
 +{{page>en:lib:mdl:mdl-h-cnaninp-030}}
 +
 +==== Digital outputs ====
 +
 +{{page>en:lib:mdl:mdl-h-cndigout-030}}
 +
 +
 +{{page>en:lib:mdl:mdl-h-cnstep-030}}
 +
 +==== Analog outputs ====
 +{{page>en:lib:mdl:mdl-h-cnabcdef-030}}
 +
 +/*--------------------------------------Slot3 Electrical features-----------------------------------------*/
 +
 +{{page>en:lib:mdl:mdl-h-ceqmplus-010}}
 +
 +<html><pagebreak /></html>
 +
 +{{page>en:lib:mdl:mdl-h-ecqmplus-010}}
 +
 +<html><pagebreak /></html>
 +
 +====== - Settings, procedures and signals ======
 +{{strumenti:qmoveplus:j1k31:j1k31_settaggi_01.png?direct&200|Rear view to identify the dispositivi illustrated in this chapter.}}
 +
 +{{page>en:lib:mdl:mdl-h-sebaud-020}}
 +
 +{{page>en:lib:mdl:mdl-h-sebaud-010}}
 +
 +
 +===== Led =====
 +The system led's **"pow, run, stop, err"**:
 +
 +{{led:led_sistema-retro_01.png?direct&180}}
 +
 +The user led's **"L1, L2, L3 **e** L4"**:
 +
 +{{led:led_utente-retro_01.png?direct&200}}
 +
 +====“System Led” Signals====
 +=== Leggend: ===
 +{{led:led_on.jpg?direct&30}} Led ON
 +
 +{{led:led_off.jpg?direct&30}} Led OFF
 +
 +{{led:led_lamp.jpg?direct&30}} Led Flashing
 +
 +^Led^Colour^Status^Description^
 +|**pow**|Green|{{led:led_on.jpg?20}}|Power on|
 +|:::|:::|{{led:led_on.jpg?20}}|When it is the only led on, it signals the CPU reset status|
 +|**run**|Green|{{led:led_on.jpg?20}}|CPU in RUN status|
 +|:::|:::|{{led:led_lamp.jpg?20}}|CPU in READY status|
 +|**stop**|Yellow|{{led:led_on.jpg?20}}|When the **pow** is on, it signals the STOP status of the CPU\\ If the **pow** led is off, it signals the BOOT status of the CPU|
 +|**err**|Red|{{led:led_lamp.jpg?20}}|When the **pow** led is off, it signals a hardware error. See paragraph [[#Hardware Error codes]]\\ If the **pow** led is flashes, the flash rate indicates the type of error. See paragraph **err** led signals|
 +
 +
 +===err led signals===
 +|**N.**\\ **flashes**|**Error**|**Description**|**Recommended action**|
 +|  **1**  |**Bus error**|Bus is not configured as described in the application software.|Check the correspondence between the QMOVE application (BUS section of configuration unit) and the product  configurations (cards mounted in BUS).|
 +|  **2**  |**CheckSum Error**|The integrity control on retentive variables ha dato esito negative. (see chapter Reset Error Checksum)|The machine data must be restored from a backup (.DAT file) or cancel the error with the specific system function and enter the values manually.|
 +|  **3**  |**Index Out of Bound**|An array index is pointing on an inexistent element|With the Qview development environment open the editor of a unit and use the "Edit->Go to PC" command to highlight the program line that has caused the error. In general the value used as index has a value lower than 1 or over the array dimension.|
 +|  **4**  |**Program Over Range**|The program selection index in the DATAGROUP has attempted to access an inexistent program.|With the Qview development environment open the editor of a unit and user the "Edit->Go to PC" command to highlight the program line that has caused the error. In general the value used as index is lower than 1 or over the array dimension.|
 +|  **5**  |**Step Over Range**|The step selection index in the DATAGROUP has attempted to access an inexistent step.|With the Qview development environment open the editor of a unit and user the "Edit->Go to PC" command to highlight the program line that has caused the error. In general the value used as index is lower than 1 or over the array dimension.|
 +|  **6**  |**Division By Zero**|The denominator of a division operation of the application program has a zero value.|With the Qview development environment open the editor of a unit and user the "Edit->Go to PC" command to highlight the program line that has caused the error.|
 +|  **7**  |**Syntax Error**|The application program has an invalid instruction|This error may appear because the program counter has met the QCL END instruction.|
 +|  **8**  |**Watch Dog Error**|A CAN module does not function correctly, or a specialist card has a hardware problem|With the Qview development environment open the "Monitor->Bus" panel and the righthand column called "Watchdog Bus" indicates the card that caused the problem.|
 +|  **9**  |**Stack Error**|The applciation program has used all permitted levels of calls to subroutines|With the Qview software environment open the editor of a unit and use the "Edit->Go to PC" command to highlight the program line that caused the error. Analyse the unit execution flow, the call to subroutines nestings have a limit, over which this error is generated.|
 +
 +
 +===Hardware error codes===
 +During the startup sequence, if a malfunction of any peripheral is detected, the system blocks and the error is signaled by the flashing led  {{led:led_lamp.jpg?direct&20}}err  while the other system led's remain off.
 +
 +The number of flashes indicates the type of error according to the following table :
 +
 +^Number of flashes^Error^
 +|  1  |Display|
 +|  2  |FPGA|
 +|  3  |Media|
 +|  4  |Bootloader|
 +|  5  |FW|
 +|  6  |Bus|
 +|  7  |//Signal not active//|
 +|  8  |//Signal not active//|
 +|  9  |Exception|
 +<WRAP center round important 80%>
 +Each of these signals indicates a serious error situation. The product must be sent to the QEM aftersales service.
 +</WRAP>
 +
 +
 +====“User Led” signal====
 +{{led:led_utente-retro_01.png?direct&200}}
 +
 +^Led^Colour^Description^
 +|{{led:led_on.jpg?20}} **L1**|Yellow|Programmable in the application program by the QMOVE system variable:sys003 and used by the system functions|
 +|{{led:led_on.jpg?20}} **L2**|:::|:::|
 +|{{led:led_on.jpg?20}} **L3**|:::|:::|
 +|{{led:led_on.jpg?20}} **L4**|:::|:::|
 +
 +=====Keys=====
 +{{strumenti:qmoveplus:pmq3_pulsanti_01.png?direct&400}}
 +
 +^Nome^Descrizione^
 +|{{varie:pulsante_6x6.jpg?40}}FUNC|Press on startup of the controller to access the  [[#Funzioni di sistema|System functions]]|
 +|{{varie:pulsante_6x6.jpg?40}}BOOT|Press on startup of the controller to set the CPU in Boot status and then access the firmware update functions|
 +|{{varie:pulsante_6x6.jpg?40}}RESET|Reset CPU. the system is restarted restoring the initial conditions (after a startup )|
 +
 +<html><pagebreak /></html>
 +
 +====== - Operating Overview ======
 +=====Foreword=====
 +This chapter covers aspects and descriptions of the product functionalities that are often related to the firmware, which enable the functionalities that enable its operation as a QEM Qmove+ programmable system. 
 +
 +=====Organisation of data and memories=====
 +To best understand the terms used in this chapter, it is important to know the organisation of data and memory in a QMOVE application. QMOVE applications are programs written in QCL language that, translated in binary code, are transferred onto QMOVE hardware and saved there. In the hardware, the microprocessor runs has a program called firmware that interprets the above binary code instructions and performs the operations associated to them.
 +
 +A QCL application, in addition to the instructions, is also composed of variables that the QCL instructions act on.. Some of these variables are retentive, i.e. their values remain unaltered from shut-off to start up. The flow chart below illustrates the organisation of data in a QCL application transferred to the memory of any QMOVE hardware:
 +
 +{{sezioni:funzionamento:organizzazione_dati-mem_01.png?nolink&500}}
 +
 +It can be noted that, the QMOVE hardware has several mass storage devices with different technology (e.g. the non volatile data memory may be a §ram tamponata rather than an eeprom or a magneto-resistiva ram, …), they have been divided in the following categories:
 +
 +**"Nonvolatile memory"**, where the following is saved:
 +  * **QCL Program:** the series of QCL instructions translated into binary by the compiler.
 +  * **HMI program:** the series of HMI screens translated into binary by the compiler. This program only exists when the QMOVE hardware has a display.
 +  * **Configuration data:** the calibration and configuration data, e.g. the touch-screen calibration settings, the ethernet communication configuration data (IP address, etc). This data can be entered by both system functions and specigic PC software utilities.
 +
 +**"Non volatile data memory"**, which stores:
 +  * **Retentive variables:** the group of variables that remains unaltered on a shut-off and startup (e.g. SYSTEM, ARRAYS, DATAGROUP, etc).
 +**"Volatile data memory"**, which stores:
 +  * **Non retentive variables:** the group of variables that is set to 0 at each startup (e.g. GLOBAL, ARRGBL, etc).
 +The volatile data memory is also used as dynamic memory. i.e. the memory used by the firmwarefor internal operations and active HMI screen management.
 +
 +**"Internal mass memory" **is managed by a standard filesystem and is useful to save information by the DATASTORE device (read - write binary or csv files with recipes, logs, variuous setups, etc).\\
 +E' inoltre utilizzato per memorizzare il backup dell'applicativo QMOVE.
 +
 +**"External mass storage"** is managed by a standard filesystem and is useful for loading the QMOVE application, data loading/saving, firmware update or to save information by the DATASTORE device.
 +
 +
 +=====CPU Status=====
 +The CPU has several operating statuses. The figure below shows the main status changes from the controller startup.\\
 +The main operatiing statuses are RESET, READY, RUN and STOP.\\
 +The CPU events that determine a transition from one status to another are mainly linked to commands being sent by the development environment: **Run, Reset, Stop ** and **Restart.**\\
 +**Application download** is the development environment procedure that allows to transfer a QMOVE application to the CPU.
 +
 +{{varie:staticpu_en.png?nolink&400|Stati della CPU}}
 +
 +**Application download** is the development environment procedure that allows to transfer a QMOVE application to the CPU.
 +
 +{{page>en:lib:mdl:mdl-f-scboot-010}}
 +
 +{{page>en:lib:mdl:mdl-f-scautboo-010}}
 +
 +{{page>en:lib:mdl:mdl-f-scfunsis-010}}
 +
 +{{page>en:lib:mdl:mdl-f-screset-010}}
 +
 +{{page>en:lib:mdl:mdl-f-scready-010}}
 +
 +{{page>en:lib:mdl:mdl-f-scrun-010}}
 +
 +{{page>en:lib:mdl:mdl-f-scstop-010}}
 +
 +
 +=====System Functions=====
 +<WRAP center round important 80%>
 +IMPORTANT: The use of these procedures could represent a risk (e.g. see deletion of application), therefore it is highly recommended that they are performed by qualified experts.
 +</WRAP>
 +
 +The system functions are spefici procedures that allow the user to perform various operations, e.g. the configuration/calibration of peripherals, data and application save/restore on/from removable mass memory, deletion of the application and management of the mass memories.\\
 +Controllers with display have some system functions that are only accessible by password and if access attempts are made the  **"Function is locked"** message is given.
 +
 +{{page>en:lib:mdl:mdl-f-fselenco-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fsproced-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fsmsgerr-010}}
 +
 +
 +==== Descrizione ====
 +{{page>en:lib:mdl:mdl-f-fsreschk-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fsmctona-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fsnatomc-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fsappdel-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fsappupl-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fssetdat-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fsdatomc-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fssetpsw-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fsremnan-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fsshonan-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fstouch-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fsseteth-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fsbacnan-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fsrstnan-010}}
 +
 +{{page>en:lib:mdl:mdl-f-fsbacres-010}}
 +
 +===== Information on programming =====
 +This chapter outlines all product information that is necessary for programming, in other words during the development of a QCL application. 
 +
 +==== Development Environments ====
 +The product programming requires the Qview-5 environments to program the QCL code and if the product has a graphic display, also the Q paint-5 environment to design the screen graphics. Noth these softwares are available in the Qworkbench software package that can be downloaded as freeware from the Qem website.
 +
 +The contoller has 3 slots, as indicated in chapter  [[.:descrizione#Back terminal blocks]].
 +
 +The slots 4 to 12  can be declared and must be used to address recources installed in the Canopen modules.
 +
 +A typical BUS declaration to use in the BUS section of the configuration unit:
 +
 +<code QCL>
 +BUS
 +1 1R11F 10
 +2 . .
 +3 1MG3F .
 +</code>
 +
 +The firmware version must naturally correspond and the specialist card name at slot 3 must be correct. This name can be obtained from the far raight column of the table:  [[.:descrizione#versioni hardware|Hardware Versions]].
 +
 +To program with the QPaint-5 development environment it is important to select the correct target. To do so, in the environment select //Project// ? //Target Configuration// then select the right controller according to the ordering code.
 +
 +{{page>en:lib:mdl:mdl-s-ipmemuti-010}}
 +
 +{{page>en:lib:mdl:mdl-s-ipcom-010}}
 +
 +{{page>lib:mdl:mdl-s-iplingpr-010} }
 +
 +{{page>en:lib:mdl:mdl-s-ipfirerr-010}}
 +
 +{{page>en:lib:mdl:mdl-s-ipvarsis-010}}
 +
 +{{page>en:lib:mdl:mdl-s-ipdevice-010}}
 +
 +<html><pagebreak /></html>
 +
 +====== - Accessories available ======
 +
 +  * [[en:Strumenti:Accessori:IQ009]]
 +  * [[en:Strumenti:Accessori:IQ013]]
 +  * [[en:Strumenti:Accessori:IQ011]]
 +  * [[en:Strumenti:Accessori:IQ016]]
 +  * [[en:Strumenti:Accessori:kit polarizzazione connettori|Connector polarisation kit]]
 +