en:strumenti:qmoveplus:j1p20:mimj1p20fx_base

This translation is older than the original page and might be outdated. See what has changed.

J1-P20-Fx BASE

J1-P20


All rights reserved on this manual. No part of this document can be copied or reproduced in any form without prior written authorisation. QEM does not insure or guarantee its contents and explicitly declines all liability related to the guarantee of its suitability for any purpose. The information in this document can be changed without notice. QEM shall not be held liable for any error or omission in this document. QEM® is a registered trademark.


Information

Document MIMJ1P20Fx BASE
DescriptionInstallation and maintenance manual
Drawn up by Riccardo Furlato
Approved by Gabriele Bazzi
Linkhttp://www.qem.eu/doku/doku.php/en/strumenti/qmoveplus/j1p20/mimj1p20fx_base
LanguageEnglish
Document Release Hardware release Description Notes Date
01 02 New Manual 07/27/2015

The controller has been designed for industral environments in conformity to EC directive 2004/108/CE.

  • EN 61000-6-4: Electromagnetic compatibility - Generic standard on emission for industrial environments
    • EN55011 Class A: Limits and measurement methods
  • EN 61000-6-2: Electromagnetic compatibility - Generic standard on immunity for industrial environments
    • EN 61000-4-2: Electromagnetic compatibility - Electrostatic discharge immunity
    • EN 61000-4-3: Immunity to radiated, radio-frequency electromagnetic field
    • EN 61000-4-4: Electrical fast transients
    • EN 61000-4-5: Surge immunity
    • EN 61000-4-6: Conducted disturbance induced by radio-frequency
  • Moreover the product is conform to the following standards:
    • EN 60529: Housing protection rating IP64
    • EN 60068-2-1: Environmental testing: Cold
    • EN 60068-2-2: Environmental testing: Dry heat
    • EN 60068-2-14: Environmental testing: Change of temperature
    • EN 60068-2-30: Environmental testing: Cyclic damp heat
    • EN 60068-2-6: Environmental testing: Sinusoidal vibration
    • EN 60068-2-27: Environmental testing: Shock vibration
    • EN 60068-2-64: Environmental testing: Random vibration


1. Description

J1-P20-F is a combo HMI-PLC controller of the Qmove+ family.

:tip:The Product Ordering Code provides its exact characteristics.
Verify that the product characteristics comply with your requirements.

  • 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


Model Caratteristics
J1-P20-FA-10/TP01
TP00 = Keypad Code (TP00 = pannel with resistive touchscreen , custom logo and function keys);
TP01 = panel with resistive touchscreen, Qem standard logo and function keys
10 = Firmware version (00 = not installed)
F = Technological level
A = Hardware version
P = Only function keys
2 = 5“ LCD graphic display, TFT display-256 COLOUR-800x480px; front panel size (168x144mm); keypad 7 keys + 11 led; housing to DIN 43700;
0 = Firmware-hardware correspondence
J1 = “HMI+PLC” Qmove family


These are the currently hardware versions available:

Versioni hardware
A B C D E F G H I J K L M N P W Y Z
Base
card
USER PORT (RS232-422-485) - - - - - - - 1 - 1 - - - - - 1 1 1
CAN PORT - - - 1 1 1 1 1 1 1 1 1 - 1 - 1 1 1
ETHERNET PORT - - - - - - - 1 1 - 1 1 1 1 1 1 1 1
Standard digital inputs 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 - 16 16
Fast digital inputs (also designed for use as frequency meters) - 2 2 - 2 2 2 2 - - 2 2 - - 2 - 2 2
Two-way count inputs, 200KHz ABZ (24V-PP, 5V-LD) - 2 2 - 2 2 2 2 - - 2 2 - - 2 - 2 2
Protected digital outputs 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 - 16 16
0-10V-12bit analog outputs - - - - - - - - - - - - - - - - - -
+/-10V-16bit analog outputs - - 2 - - 2 - 2 - - - 2 - - 2 - 2 2
Card software code declared as base card 1MD1F
Expansion
card
Standard digital inputs - - - - - - 8 8 - - - - 8 8 - - - 8
12bit analog inputs - - - - - - - - - - - - - - - - -
16bit selectable analog inputs(0-10V, 0-20mA, potenz, thermocouples, PT100) - - - - - - - - - - - 2 - - - - - 2
Protected digital outputs - - - - - - 8 8 - - - - 8 8 - - - 8
0-10V-12bit analog outputs - - - - - - - - - - - - - - - - - -
+/-10V-16bit analog outputs - - - - - - - - - - - - - - - - - -
AUX PORT (RS485) - - - - - - - - - - - - - - - - - -
Expansion card software code declared in SLOT 3 - - - - - - - - - - - -


VersionDescription
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 firmware, consult Devices enabled in the controllers.


A) Function keys and leds
B) System leds


J1-P20-F has a specialist card.

  • c = Base card
  • a = Expansion card


2. Technical Characteristics

Weight (full hardware)1Kg
HousingSheet metal
Front panelAluminium
Outer FrameSelf-extinguishing Noryl
DisplayLCD 5'' TFT 256 colori - 800 x 480px
Touch screen4-wire Resistive
Display dimensions108 x 64,8mm / 5“
User led's7
System led's4
Function keys7
System keys3
Operating temperature0 ÷ 50°C
Transport and storage temperature-25 ÷ +70 °C
Relative humidity90% condensate free
Altitude0 - 2000m a.s.l.
Front protection ratingIP64
RISC Miscroprocessor (32 bit)
Work Frequency 200MHz
RAM 8MB
Flash 8MB


:info:Dimensions in mm.



Fit the controller in the hole.

Apply the brackets.

:important: Before fixing the controller, check it is mounted firmly in the hole and the gasket under the frame makes a good seal. No liquids must enter and the frame must not deform.

Screw the controller in place.

:important:Warning: after putting the pin of fixing, do only half rotation to not tear the frame!


3. Base card connections

:tip:For details about cable sections and connectors, see application note AN021


:important:The cabling must be carried out by specialist personnel and fitted with suitable anti-static precautions.
Before handling the controller, disconnect the power and all parts connected to it.
To guarantee compliance with EC regulations, the power supply must have a galvanic isolation of at least 1500Vac.

.

Power supply 24 Vdc
Voltage range 22 - 27 Vdc
Max. absorption 10W

Connector

CN1 TerminalSymbolDescription
1 DC power positive
2 GROUND Gnd-PE (signals)
3 DC power 0V

:important:Use an isolated power unit with 24Vdc +/-5% output conform to EN60950-1.

.

Use two separate power units: one for the control circuit and one for the power circuit
For a single power unit, use two separate lines: one for the control and one for the power
DO NOT use the same lines for the power circuit and the controller


PROG PORTDescription
Serial port used for the transfer and debugging of the application program in the CPU.
Use only with IQ009 or IQ013.
Connector
CN8 TerminalRS232RS422RS485Description
1A - - A Terminal A - RS485
2A - - B Terminal B - RS485
3A 0V 0V 0V USER PORT common
4A 0V 0V 0V USER PORT common
5A TX - - Terminal TX - RS232
6A Ground
1B - RX - Terminal RX - RS422
2B - RXN - Terminal RX N - RS422
3B - TX - Terminal TX - RS422
4B - TXN - Terminal TX N - RS422
5B RX - - Terminal RX - RS232
6B Ground
Setting USER PORT electric standard
SW2 Num.
Dip
Name
DIP
Setting
of DIP
Function
1 JP2 ON X1) X2) Termination RS485
2 JP3 ON X3) X4) Polarisation RS485
3 JP1 ON X5) X6)
4 OFF ON OFF Selection of USER PORT electric standard
5 ON OFF OFF
6 OFF OFF ON
RS485 RS422 RS2327)

1), 2), 3), 4), 5), 6) X = setting not significant
7) the USER PORT can be used as PROG PORT with RS232 electric standard, setting ON in DIP-8 of SW1 and OFF in DIP-6 of SW2


Connector
CN2 TerminalSymbolDescription
1 CAN H CAN H terminal
2 CAN L CAN L terminal
3 0V CAN common
Termination resistances setup
Jumper
name
SettingFunction
JP1 JP2
JP1 INSERTED CAN Termination activated
JP2


ETHERNET PORTDescription
Connector RJ45.

LED:
* LINK: green led = cable connected (led on signals the cable is connected to both ends)
* DATA: yellow led = data transmission (flashing led signals data transmission)


Memory card connector (indicated by the arrow)


CN6 TerminalSymbolDescriptionAddres
1 0V Common for digital inputs
2 I1 Input I1 2.INP01
3 I2 Input I2 2.INP02
4 I3 Input I3 2.INP03
5 I4 Input I4 2.INP04
6 I5 Input I5 2.INP05
7 I6 Input I6 2.INP06
8 I7 Input I7 2.INP07
9 I8 Input I8 2.INP08

.

CN5 TerminalSymbolDescriptionAddress
1 0V Common for digital inputs
2 I9 Input I9 2.INP09
3 I10 Input I10 2.INP10
4 I11 Input I11 2.INP11
5 I12 Input I12 2.INP12
6 I13 Input I13 2.INP13
7 I14 Input I14 2.INP14
8 I15 Input I15 2.INP15
9 I16 Input I16 2.INP16


:tip:The electrical characteristics are given in paragraph Electrical features.
The wiring examples are given in paragraph Connection examples

.

CN9 Terminal Symbol Description Address
1A Uscita +24V dc1)
2A PHA1 Phase A Count 1
PNP Push-Pull2)
2.INP17 2.CNT01
3A PHB1 Phase B 2.INP18
4A Z1 Z 1.INT01
5A 0V Common for count inputs
6A 0V
7A 0V
1B +24Vdc out3)
2B PHA1+ + PHA Count 1
Line Driver
2.INP17 2.CNT01
3B PHB1+ + PHB 2.INP18
4B Z1+ + Z 1.INT01
5B PHA1- - PHA
6B PHB1- - PHB
7B Z1- - Z

1), 3) Used to power the encoder. See Connection examples.
2) PNP/Push-Pull type count input configuration:
Terminal 5B: connect to terminal 5A
Terminal 6B: connect to terminal 6A
Terminal 7B: connect to terminal 7A
CN10 Terminal Symbol Description Address
1A Uscita +24V dc1)
2A PHA2 Phase A Count 2
PNP Push-Pull2)
2.INP19 2.CNT02
3A PHB2 Phase B 2.INP20
4A Z2 Z 1.INT02
5A 0V Common for count inputs
6A 0V
7A 0V
1B +24Vdc out3)
2B PHA2+ + PHA Count 2
Line Driver
2.INP19 2.CNT02
3B PHB2+ + PHB 2.INP20
4B Z2+ + Z 1.INT02
5B PHA2- - PHA
6B PHB2- - PHB
7B Z2- - Z

1), 3) Used to power the encoder. See Connection examples.
2) PNP/Push-Pull type count input configuration:
Terminal 5B: connect to terminal 5A
Terminal 6B: connect to terminal 6A
Terminal 7B: connect to terminal 7A


CN7 TerminalSymbolDescriptionAddress
1 V+ Outputs power input O1÷O4 (12÷28V dc)
2 O1 Digital output 12.OUT01
3 O2 Digital output 22.OUT02
4 O3 Digital output 3 2.OUT03
5 O4 Digital output 4 2.OUT04
6 V+ Outputs power input O5÷O8(12÷28V dc)
7 O5 Digital output 5 2.OUT05
8 O6 Digital output 6 2.OUT06
9 O7 Digital output 7 2.OUT07
10 O8 Digital output 82.OUT08
11 V- Outputs power in (0V dc)

.

CN4 TerminalSymbolDescriptionAddress
1 V+ Outputs power input O9÷O12(12÷28V dc)
2 O9 Digital output 92.OUT09
3 O10 Digital output 102.OUT10
4 O11 Digital output 11 2.OUT11
5 O12 Digital output 12 2.OUT12
6 V+ Outputs power input O13÷O16(12÷28V dc)
7 O13 Digital output 13 2.OUT13
8 O14 Digital output 14 2.OUT14
9 O15 Digital output 15 2.OUT15
10 O16 Digital output 162.OUT16
11 V- Outputs power in (0V dc)


CN3 TerminalSymbolDescriptionAddress
1 GAO Common for analog outputs
2 AO1 Analog output 12.AN01
3 AO2 Analog output 22.AN02
4 GAO Common for analog outputs


4. Connection Examples

:todo:On the first (1) and on the last (3) device of the chain, the termination resistances must be inserted.
The cable shoes must be connected to ground by the fastons provided on the metal body.

.

:info:To activate the internal termination resistance see paragraph Termination resistor setting


Esempio di collegamento di ingressi standard, più ingresso veloce PNP


Esempio di collegamento di un ingresso di conteggio Line Driver


Esempio di collegamento di un ingresso di conteggio PNP/Push Pull


Esempio di collegamento di uscite protette


Esempio di collegamento di uscite analogiche


5. Electrical features

The electrical characteristics of the hardware are given below.
The maximum and minimum frequencies, and real acquisition times, may depend on eventual additional software filters, for example see the system variable “QMOVE:sys004” at paragraph System variables.

Connector for IQ009 or IQ013

:important: The USB mini-B connector does not support USB electrical standards, it can only be used with an interface IQ009 or IQ013.

It is used for the transfer and debugging of the application program in the CPU.

Electrical standard TTL (Use serial interface IQ009 or IQ013)
Communication speedMin. 9.6 Kbaud - max 115200 Kbaud
settable by dip1 and 2 of the switch SW1
InsulationNone

.

Connection between Qmove+ e PC using the accessory IQ009

.

Connection between Qmove+ and a device fitted with a RS232 serial port (e.g. a MODEM), using the interface IQ013


Communication speed4800, 9600, 19200, 38400, 57600, 115200 baud
Communication modeFull duplex
Operating modeReferred to 0V
Max. number of devices connected on the line1
Max. cable length15 m
Input impedence> 3 Kohm
Short-circuit current limit7 mA

Internal wiring diagram of RS232

Cable connection diagram of RS232


Communication speed4800, 9600, 19200, 38400, 57600, 115200 baud
Communication modeFull duplex
Operating modeDifferential
Max. number of devices connected on the line1
Max. cable length1200 m
Input impedence> 12 Kohm
Short-circuit current limit35 mA

Internal wiring diagram of RS422

Cable connection diagram of RS422

Cable connection diagram of RS422


.

Communication speed4800 baud (only if used with SERCOM and/or MODBUS device),
9600 baud, 19200 baud, 38400 baud, 57600 baud
Communication modeHalf duplex
Operating modeDifferential
Max. number of devices connected on the line32
Max. cable length1200 m
Input impedence> 12 Kohm
Short-circuit current limit35 mA

Internal wiring diagram of RS485

Cable connection diagram of RS485


To activate the internal termination resistance see paragraph Setup Termination resistances

.

Communication speed125, 250, 500, 1000 Kbit/s
Max. number of Drivers/Receivers on the line100
Max. cable lengths500m @ 125Kbit/s, 250m @ 250Kbit/s, 100m @ 500Kbit/s, 25m @ 1000Kbit/s
Input impedence>15Kohm
Short-circuit current limit45mA

Schema elettrico interno canbus

Schema del cavo di collegamento canbus

Esempio di collegamento CANbus

CAN BUS connection examples.

Caution:
Close DIP's JP1 and JP2 and insert the termination resistances (RL, RH) on the last device of the chain.


Ethernet Interface 10/100 Base T (IEEE 802.3) on RJ45 connector.

Connection between Qmove + and PC:

Qmove+ Cross-over cable EIA/TIA-568A/B PC


Type of Memory Card to useMMC, SD and SDHC up to 8GB
For proper operation it is necessary that the device conforms to the standards set by “SD Association” (www.sdcard.org) or “Multi Media Card Association” (www.mmca.org).

.

:important:To use the Memory Cards they must first be formatted with FAT16 or FAT32 file system.


Type of polarisation PNP
Min. acquisition time (hardware) 3ms
Isolation 1000Vrms
Rated operating voltage 24Vdc
Voltage of logic state 0 0-2 V
Voltage of logic state 1 10.5 - 26.5 V
Internal voltage drop 5V
Input resistance (Ri) 2700Ω
Sink current2mA ÷ 8mA1)

1) CAUTION: If the device connected to the inputs needs a higher minimum current, inputs may not work properly.

Internal diagram of standard digital input.


The values given in the table refer to input signals A, B and Z.
The max. frequency given in the table refers to A and B phase signals with a DutyCycle = 50%
With count frequencies over 50KHz the use of Line-Driver type encoders is recommended.

Type of polarisation PNP/PP
Max frequency 200KHz
Min. acquisition time 5µs
Insulation 1000Vrms
Rated operating voltage 24Vdc
Voltage of logic status 0 0 - 2 V
Voltage of logic status 1 10.5 - 26.5 V
Internal voltage drop 1.2V
Input resistance 3100Ω

Line-Driver

Type of polarisation Line-Driver
Max. frequency 200KHz
Min. acquisition time 5µs
Insulation 1000Vrms
Rated operating voltage (PHx+ ? PHx-) 5Vdc
Voltage of logic status 0 (PHx+ ? PHx-) 0-1.5 V
Voltage of logic status 1 (PHx+ ? PHx-) 2-5 V
Internal voltage drop 1.2V
Input restistance 150Ω

Internal diagram of count inputs.


Switchable load Dc (PNP)
Max. operating voltage 28V
Insulation 1000VRMS
Max. internal voltage drop 600mV
Max internal resistance @ON 90mO
Max. protection current 12A
Max. operating current 500mA
Max. current @OFF 5µA
Max switching time from ON to OFF 270µs
Max switching time from OFF to ON 250µs

Internal diagram of protected outputs


Type of connection Common mode
Insulation 1000Vrms
Voltage range (minimum no load) -9.8V - +9.8V
Max. offset variation depending on temperature* +/- 5mV
Resolution 16bit
Max. current 1mA
Output variation depending on load 100 µV/mA
Output resistence 249Ω

Internal diagram of analog outputs


6. Settings, procedures and signals

Rear view to identify the dispositivi illustrated in this chapter.

SW1 DipDIP settingsFunction
dip-8.jpg 1 OFF OFF ON ON Select PROG PORT transmission speed
2 OFF ON OFF ON
Baud-rate
38400
Baud-rate
115200
Baud-rate
19200
Baud-rate
57600
3 OFF OFF ON ON Select USER PORT transmission speed
4 OFF ON OFF ON
Baud-rate
38400
Baud-rate
115200
Baud-rate
19200
Baud-rate
57600
5 CANbus baud-rate selector. See paragraph CANbus baud-rate selector
6 OFF ON Select PROG PORT functioning mode
PROG PORT can also be used by SERCOM and MODBUS devicesPROG PORT cannot be used by SERCOM and MODBUS devices
7 CANbus baud-rate selector. See paragraph CANbus baud-rate selector
8 OFF ON Select the USER PORT as PROG PORT1)
PROG PORT normalPROG PORT on USER PORT connector

1) It is possible to use the USER PORT connector as PROG PORT with RS232 electric standard, doing this the mini-USB connector of the PROG PORT is disconnected (Setting USER PORT electric standard). For this function mode also set dip 6 of SW2 to OFF.


SW1 DipDIP settingsFunction
dip-8.jpg 1 - -
2 - -
3 - -
4 - -
5 OFF ON OFF ON Select speed of
CANbus transmission
7 OFF OFF ON ON
Baud-rate
125KB/S
Baud-rate
250KB/S
Baud-rate
500KB/S
Baud-rate
1MB/S
6 - -
8 - -


The system leds “pow, run, stop, err” are found on the front panel and on the rear of controllers with display and only on the top of controllers without display.

The user leds “L1, L2, L3 e L4” are found on the rear:

Leggend:

led_on.jpg Led ON

led_off.jpg Led OFF

led_lamp.jpg Led Blinking

LedColourStatusDescription
powGreenled_on.jpgPower on
led_on.jpgOnly this led on, signals the CPU reset status
runGreenled_on.jpgCPU in RUN status
led_lamp.jpgCPU in READY status
stopYellowled_on.jpgWith pow on, signals the STOP status of the CPU
With pow off, signals the BOOT status of the CPU
errRedled_lamp.jpgWith pow off, signals a hardware error. See paragraph Hardware Error codes
With pow blinking, the flash rate gives the type of error. See paragraph err led signals

Err led signals

N.
flashes
ErrorDescriptionRecommended action
1 Bus errorBus configuration different to application software.Check the correspondence between the QMOVE application (BUS section of configuration unit) and the product configurations (cards mounted in BUS).
2 CheckSum ErrorNegative outcome on the integrity control of retentive variables . (see Reset Error Checksum)Restore the machine data from a backup (.DAT file) or cancel the error with in system functions and enter the values manually.
3 Index Out of BoundAn array index is pointing on an inexistent elementOpen a unit editor in Qview development environment and use the “Edit→Go to PC” command to find the program line that is cause of the error. In general the index value has a value <1 or >array dimension.
4 Program Over RangeThe 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 RangeThe 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 ZeroThe 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 ErrorThe application program has an invalid instructionThis error may appear because the program counter has met the QCL END instruction.
8 Watch Dog ErrorA CAN module does not function correctly, or a specialist card has a hardware problemWith 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 ErrorThe applciation program has used all permitted levels of calls to subroutinesWith 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_lamp.jpgerr while the other system led's remain off.

The number of flashes indicates the type of error according to the following table :

Number of flashesError
1 Display
2 FPGA
3 Media
4 Bootloader
5 FW
6 Bus
7 Signal not active
8 Signal not active
9 Exception

.

:important:Each of these signals indicates a serious error situation. The product must be sent to the QEM aftersales service.

LedColourDescription
led_on.jpg L1YellowProgrammable in the application program by the QMOVE system variable:sys003 and used by the system functions
led_on.jpg L2
led_on.jpg L3
led_on.jpg L4


NameDescription
pulsante_6x6.jpgFUNCPress on startup of the controller to access the System functions
pulsante_6x6.jpgBOOTPress on startup of the controller to set the CPU in Boot status and then access the firmware update functions
pulsante_6x6.jpgRESETReset CPU. the system is restarted restoring the initial conditions (after a startup )


7. Operating Overview

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.

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:

It can be noted that, the QMOVE hardware has several mass storage devices:

“Flash 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, the touch-screen calibration settings, the ethernet communication configuration data (IP address, etc…), etc.

“Non volatile 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 memory”, which stores:

  • Not 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 firmware for internal operations and active HMI screen management.

“Mass storage internal device” 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).
It 'also used to store the backup of the application QMOVE and other service files.

“Mass storage external device” is managed by a standard filesystem and is useful for loading the QMOVE application, data loading/saving, firmware update or to save informations by the DATASTORE device.

The CPU has several operating statuses. The figure below shows the main status changes from the controller startup.
The main operating 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.

Stati della CPU

The BOOT state can be used to access the firmware updating functions.

During the startup, after scanning the system led's, the controller performs a series of self-diagnostic operations. When any faults are detected or the operator has to be informed of any given situation, the self-doagnosis procedure is temporarily interrupted, signalling the event.
The fault signal is made by led's L1, L2 and a message is given on display (if present).

System Messages
n.Led ONSystem Message (if display present)DescriptionType
1led_on.jpg L1System Data WRITE ERRORIndicates that a write error has occurred during the configuration data saving. B
2led_on.jpg L2System Data IS RESTORED FROM DEFAULTIndicates that the configuration data has been restores to the default settings. C
3led_on.jpg L1
led_on.jpg L2
System Data is updated
Please verify new data
Indicates that the configuration data has been converted into a new format. Check that the previous settings have been maintained. C
4led_on.jpg L3Firmware is updated
old: 1K31F10 1.001
new: 1K31F10 1.002
Indicates that a firmware update has been made. C

When the condition detected allows to continue to the start stage (type C) and waits for the FUNC button or for the F1 key to be pressed to continue the boot procedure.

If not provided with a display, the controller waits 5 seconds before continuing with the startup stage, without waiting for a button to be pressed.

When the situation does not allow to continue the startup stage (tipo B), the controller, if provided with a display, shows the message“PLEASE TURN OFF AND TURN ON THE SYSTEM” and remains in this state until you turn off. If the controller is not provided with a display, the led led_lamp.jpg err flashes continuously.

During the SYSTEM BOOTING state instruments with displays, displays some important information about the system as in the example shown in the following figure:

:important:WARNING: The values shown in the figure are examples and may vary according to the instrument.
List of the information displayed
n.MessageDescription
1 Boot status: POWER-ONIt displays the status of the boot:
POWER-ON Switching on the instrument
INIT Download application initialization
RESTART Restarting the instrument software
BACKUP Performing the Backup
RESTORE Performing the Restore
2 Firmware: 1K31F-30.5.6They show the name, version, major releases and minor releases of firmware. In the example we have:
1K31F Firmware name
30 Version
5 Major release
6 Minor release (build)
3 S/N: 12345678This displays the serial number of the instrument.
4 Date(DMY)/Time: 31/12/2010 - 12:34:56The clock/calendar is displayed in the format:
DD/MM/YYYY - hh:mm:ss
5 Dip-Switch = 0x2EIt displays a hexadecimal value representing the status of the switch SW1.
It is equivalent to the value of the system variable SYS002.
6 MMC: PRESENT 510/31250 KBIf a MMC/SD is inserted into the slot, at this stage we are displayed device data such as KB used (510) and KB total (31250).
In the case where the device is not present is displayed “not present !”
7 NAND: PRESENT 40510/63794 KBIt checks for all of the internal NAND, and then displays the KB used and KB total.
In the case where the device is not detected, an error is reported and is displayed “NAND: NOT PRESENT !”
8 Touch Screen: PRESENTInstruments equipped with a touch screen, it is detected and then are verified the calibration data.
In the event that has yet to be performed calibration, the message diplayed is “CALIBRATION REQUIRED !”.
The touchscreen calibration is possible with the system function “Touch Calibration”.
9 ETHERNET: IP = 192.168.0.253
NM = 255.255.255.0
GW = 0.0.0.0
On instruments equipped with Ethernet interface, displays the parameters IP address (IP), subnet mask (NM) and Gateway (GW).
Changing these values is possible with the system function “Set Ethernet communic. parameter” or through special programs available within the development environment.
10 BACKUP: VALID
QCL App: 25/04/2001 - 16:58:07 MATCH
QCL Dat: 25/04/2001 - 16:58:37 MATCH
QTP App: 25/04/2001 - 17:01:15 MATCH
It is checked for a valid backup in NAND and then displays the data of date and time of backup files relating to the application QCL (QCL App), the application data QCL (QCL Dat) and to the application QTP (QTP App).
If after “BACKUP” is displayed “VALID” means that the backup can be successfully restored by system function “Restore from NAND”.
If after “BACKUP” appears “NOT PRESENT” it means that the backup is not present.
If after “BACKUP” is displayed “NOT VALID” means that the backup can not be restored properly as the checksum of the three files that make up are not consistent with each other. After each file (QCL App, QCL Dat and QTP App), in addition to the information of the date and time of creation, is also displayed further information:
“MATCH” indicates that the file is consistent with the running application.
“NO MATCH” indicates that the file is not consistent with the running application.
“SIZE ERROR” indicates that the size of the file is invalid, possibly because the writing procedure was not completed correctly.
“NOT PRESENT” indicates that the file is not present.
11 Press F1/FUNC for 2s to System FunctionsThe display of this message indicates that the pressure for at least 2 seconds of the F1 key or the FUNC button provides access to system functions as described in the procedure. The message is displayed for 4 seconds.
12 !!! WARNING detected !!!
Press FUNC or F1 to continue
If during the previous phases, they are displayed some warning messages, which do not affect the operation of the system, to allow the operator to easily read the screen is waited a time of about 20 seconds.
To not wait and go before, press the F1 key or the FUNC button.
13 !!! ERROR detected !!!
Press FUNC or F1 to continue
Message displayed if the previous phases are displayed some error messages.
To continue, press the F1 key or the FUNC button.

The SYSTEM FUNCTIONS status can be used to access the SYSTEM FUNCTIONS, which are special procedures that allow the user to perform various operations. For more details see the System Functions chapter.



Led statusled_on.jpgpow
led_off.jpgrun
Status causeNo application in memory.
The condition that can put the CPU in this statusRESET command.

This condition can only pass onto a READY status by downloading the applicaiton, using the Qview6 development environment.



Led statusled_on.jpgpow
led_lamp.jpgrun
Status causeApplication valid and waiting for execution.
Conditions that can put the CPU in this statusApplication download.

This condition can pass onto to the RUN or RESET statuses.



Led statusled_on.jpgpow
led_on.jpgrun
Status causeApplication in execution.
Condition that can put the CPU in this statusRUN command.

This condition can pass onto all other CPU statuses.



Led statusled_on.jpgpow
led_on.jpgstop » led_off.jpgrun
Status causeStop on application in execution.
Condition that can put the CPU in this statusA breakpoint has been encountered in the application code interpretation.

This condition can pass onto all other CPU statuses.

:important: IMPORTANT: The use of these procedures could represent a risk (e.g. deletion of application), therefore it is highly recommended that they are performed by qualified experts.

The system functions are speficic 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.

All the system functions are listed below.
If the “PWD” column shows 'Y', this means that the function requires a system password (default: “123”).
DEVICE indicates an external storage media. MMC / SD or USB for hardware that they have the port.

System Functions

n.Led ONSystem FunctionsPWDDescription
1led_on.jpgL101 - Reset Error Checksum - Reset checksum error.
NOTE: if the checksum error is present, the led led_on.jpg L1 flashes.
2led_on.jpgL202 - Copy all files DEVICE → NAND - Copy all files from DEVICE to NAND Flash memory.
3led_on.jpgL1
led_on.jpgL2
03 - Copy all files NAND → DEVICE - Copy all files from NAND Flash memory to DEVICE.
4led_on.jpgL304 - Application delete Y Delete the application.
5led_on.jpgL1
led_on.jpgL3
05 - Application upload from DEVICE Y Upload the application from DEVICE.
6led_on.jpgL2
led_on.jpgL3
06 - System Settings - Adjust the system clock and selection of the DEVICE (only for hardware that possess both ports).
7led_on.jpgL1
led_on.jpgL2
led_on.jpgL3
07 - Downl. retentive data to DEVICE - Save the retentive data on DEVICE.
8led_on.jpgL408 - Set NEW Password Y Set a new password to access the “locked” system functions.
9led_on.jpgL1
led_on.jpgL4
09 - Remove all files from NAND Flash Y Cancel all files stored on the NAND Flash memory.
10led_on.jpgL2
led_on.jpgL4
10 - Show NAND Flash files - List the files stored on the NAND Flash memory.
11led_on.jpgL1
led_on.jpgL2
led_on.jpgL4
11 - Touch Calibration - Run the calibration procedure of the Touch Screen, if present.
12led_on.jpgL3
led_on.jpgL4
12 - Set Ethernet communic. parameter - Run the setup procedure for the Ethernet communication parameters (IP address,…, etc.).
13led_on.jpgL1
led_on.jpgL3
led_on.jpgL4
13 - Backup to NAND - Run the backup of the QCL application, data and HMI application on NAND memory.
14led_on.jpgL2
led_on.jpgL3
led_on.jpgL4
14 - Restore from NAND Y Run the restore of the QCL application, data and HMI application from NAND memory.
15led_on.jpgL1
led_on.jpgL2
led_on.jpgL3
led_on.jpgL4
15 - Firmware Upgrade Y Run the firmware upgrade from DEVICE.
Available only in some hardware.

Note: To exit system functions press the keep the F1 key or FUNC button for at least two seconds.

:tip:To access the System Functions, start up the controller with FUNC button or F1 key pressed.

The QMOVE application, if present, it not executed and the led L1 lights up.
Tools that have a display appears “SYSTEM FUNCTIONS”.

:tip:Use FUNC button or F1 key to scroll through the functions.
The selected function is indicated by the combination of L1-L2-L3-L4 leds lighted up and in instruments that have a display, you see the selected function in the “SYSTEM FUNCTIONS”.

The “System Functions” table gives the list of system functions and related led combinations.

:tip:Press BOOT button or F2 key for 2 seconds to execute the selected function.
The POW led starts flashing to indicate that the selected function is being executed.

Instruments that have a display, you see the page “SYSTEM FUNCTIONS” as in the figure below.

When the function ends the POW led stops flashing.
Instruments that have a display, you see the page “SYSTEM FUNCTIONS” as in the figure below.

:tip:Press FUNC button or F1 key to restart the controller.

If the function does not complete properly the POW stops and the ERR starts flashing.

The number of flashes indicates the type of error as shown in the table System Function Error Messages.



When a system function ends with an error, the number of led flashes led_lamp.jpg err indicates the type of error.
If there is a display, a message is given to describe the cause of the error.

System Function Error Messages
Error/Number of ERR led flashesMessage
1 Generic error
2 Open/Exist/Create file error
3 Read file error
4 Write file error
5 Out of Memory error
6 QMos Version error
7 Checksum Error
8 Symbols checksum No Match
9 Configuration / Symbols error
10 File format error
11 Format error
12 Device not present or unformatted
13 Application not present error
14 Touch calibration failure
15 File compression type not support
16 Target don't match project !
17 Fw version don't match project !
18 File copy error
19 File size error
20 Crypt operation error
21 Invalid Product Serial Number
22 Function is locked
23 Function not enabled



The system runs an integrity control of retentive variables by the applicaiton of a CRC to the nonvolatile data memory. This detects any corruption and prevents the application from starting up, signalling the situation by flashing the led led_lamp.jpg err as shown in Err led signals.
For the application to function again, a new download of the application must be performed with the development environment, or the “Reset Error Checksum” system function. These operations delete the error status and zero-setsall retentive variables.

The procedure:

  • Check the error status and end the funciton if no error is present.
    In microQMove products, the presence of the QCL application is also checked.
  • Vengono azzerati i dati ritentivi e viene visualizzato il messaggio “Clear power down data…” fino al termine della procedura.
  • Resets the retentive data and the message “Clear power down data…” until the end of the procedure.
  • End of operation

This procedure copies all files in the root and “DS” directory of the external MMC/SD or USB card to the NAND internal mass storage.

The following table gives the sequence of operations and any possible errors:

MessageDescriptionPossible errors
Check DEVICE presenceChecking for the presence of the external mass storage card
On DEVICE appears MMC or USB, depending on what is selected
Device not present or unformatted
Mounting device…Mounting the external mass storage cardDevice not present or unformatted
Searching files…Searching for compatible filesNo Files Found
Copy <filename>….Making a copy of the files indicating the name currently in copy

This procedure copies all files contained in the root and “DS” directory of the NAND internal mass storage to the external MMC/SD or USB card memory.

The following table gives the sequence of operations and any possible errors:

MessageDescriptionPossible errors
Check DEVICE presenceChecking for the presence of the external mass storage card
On DEVICE appears MMC or USB, depending on what is selected
Device not present or unformatted
Mounting device…Mounting external mass storage deviceDevice not present or unformatted
Searching files…Searching for compatible filesNo Files Found
Copy <filename>….Copying the files indicating the name of the one currently in copy

This deletes the application and empties the nonvolatible data memory, deleting the QCL program and, if present, deleting the HMI program.

The following table gives the sequence of operations performed and any possible errors:

MessageDescriptionPossible errors
Reset retentive dataEmpty nonvolatible data memoryWrite file error
Delete QCL applicationDeletion of the QCL programWrite file error
Delete HMI applicationDelection of the HMI program (if display installed)Write file error



This loads an application from the external MMC/SD or USB mass memory card to the non volatile memory.

This allows to load all or one of the QCL program, HMI program and retentive data.

The external MMC/SD or USB mass memory card must contain at least one of the following files:

  • applic.bin for the compiled QCL program generated by the Qview development environment
  • applic.dat for the data file generated by the “Save Data…” procedure of the Qview development environment or by the Downl system function. for retentive data to DEVICE;
  • appqtp.bin for the compiled HMI program generated by the Qpaint development environment; it is generated by the special function “Download the project to File…”.
MessageDescriptionPossible errors
Check DEVICE presenceChecking for the presence of the external mass storage card
On DEVICE appears MMC or USB, depending on what is selected
Device not present or unformatted
Mounting device…Mounting external mass storage cardDevice not present or unformatted

If the applic.bin is present:

MessageDescriptionPossible errors
Upload QCL applicationUploading the QCL programOpen/Exist/Create file error
Write file error
Read file error
Out of Memory Error
QMos Version Error
Checksum Error
Symbols checksum No Match
Configuration / Symbols Error

If the applic.bin file is not present, an application must already be loaded in the nonvolatile memory otherwise the “Application not present” message is given.

If the applic.dat file is present:

MessageDescriptionPossible errors
Upload retentive dataUploading retentive data to the nonvolatile data memoryOpen/Exist/Create file error
Write file error
Read file error
Out of Memory Error
QMos Version Error
Checksum Error
Symbols checksum No Match
Configuration / Symbols Error
QTP File format error

The procedure performs the following steps:

  • Check the presence of the MMC/SD or USB card.
    The “Check DEVICE presence” message is given.
    On DEVICE appears MMC or USB, depending on what is selected.
  • Mounting MMC/SD or USB card.\\The “Mounting device…” message is given.
  • Uploading the QCL program (applic.bin), if contained in the removable mass storage device
    The “Upload QCL application” message is given.
  • Uploading retentive data of the QCL program (applic.dat), if contained in the removable mass storage device
    The “Upload retentive data” message is given.
    NOTE: if the applic.dat file is not found, the data in the system is maintained so long as the Symbol and Configuration checksums have not been varied. If they are varied all data will be set to zero.
  • Uploading the HMI program (appqtp.bin), if contained in the removable mass storage device
    The “Upload HMI application” message is given.
  • The file is closed and the operation ends.

System Settings

This procedure sets the system clock/calendar and selects the type of external memory to be used.

The string Removable device is not present in hardware that does not have a USB port.
Press F2 key or BOOT button to enter a new setting in the boxes. Each time a setting is confirmed the next box is accessed for modification. At the last box the new settings are saved.



This function creates a file on external mass storage (MMD/SD or USB) containing the retentive data values.
The file created is named “applic.dat” and is the same as the file obtained by the “Save Data…” procedure in the QView development environment. The function can only be performed if there is a valid QCL application in the controller.

The procedure performs the following steps:

  • Check the presence of the MMC/SD or USB card.
    The “Check DEVICE presence” message is given.
    On DEVICE appears MMC or USB, depending on what is selected.
  • Mounting the MMC/SD or USB card.
    The “Mounting device…” message is given.
  • Check the presence of the QCL program
    The “Checking application presence…” message is given.
  • Check the validity of the retentive data
    The “Checking retentive data…” message is given.
  • Open the applic.dat destination file on the external MMC/SD or USB card
    The “Open destination file…” message is given.
  • Write the headers in the destination file
    The “Write headers to destination file” message is given.
  • Write the retentive data in the destination file
    The “Write data to destination file”.
    NOTE: the percentage progress of the operation is given during this step
  • Close the file and end the operation

Set NEW Password

This modifies the password to access the system functions. The password is a number. The default password is: 123 The procedure first asks for the current password (Actual Pwd) and, if correct, then allows a new password to be entered (New Pwd).

When the new password has been entered the “saving data…” message is given to indicate that the new data is being saved.

:tip:If 0 (zero) is entered as a new password, the password request is disabled.



Delete all files contained on the internal NAND flash mass storage.
Unlike the “Format NAND Flash” function, this acts at a filesystem level aqnd can therefore be performed as many times as necessary.

The procedure performs the following steps:

  • Calculation of the number of files contained in the internal mass storage.
  • The “Searching files…” message is given.
  • If zero files are found, the “No Files Found” message is given and the function ends, otherwise the “Delete <filename>” is given indicating the delection of every file found.
  • Close the internal storage and end procedure

Show NAND Flash files

This procedure views the name and size of all files found in the internal NAND flash mass storage.

The procedure performs the following steps:

  • Calculate the number of files in the internal mass storage.
  • The “Searching files…” message is given.
  • If zero files are found the “No Files Found” message is given and the procedure ends.
  • The file name and size in bytes “<filename> - <size>B” of each file found is shown.
  • Press the BOOT button or the F2 key again to continue with the next file when the “Press BOOT or F2 to show next filename” message is given.
  • Close the internal storage device and end procedure.

This procedure is used to calibrate the touch-screen device, if it's present.

At the entrance of the procedure, it is presented with a screen where there is a blue cross.
Press the center of the cross until the progress bar has reached completion.

At this point, the message “COMPLETED” and you can release the pressure.

Note: if the pressure is released before the completion of the progress bar, the procedure is aborted and the message “!! OPERATION ABORTED !!” is given.

Repeat for the other two crosses green and cyan.

Set Ethernet communic. parameter

This procedure views and modifies the communication parameters of the ETHERNET port.
When the function is accessed all data saved on the controller is shown.

To change a parameter press F2 and introduce the new setting.
Press ENTER to go to and change the next box.
When the last box is confirmed, the data is saved and the “saving data…” message is given.

If the Ethernet port is not present on the hardware, the message “Function not enabled” is given.



The backup procedure creates a copy of the QCL and HMI applications in execution and a dump of the retentive data, as files saved in the NAND mass storage. The files created have the following names:

  • applic.qcy identifies the file containing the QCL application (CPU)
  • appdat.qcy identifies the file containing the retentive data of the QCL application
  • appqtp.qcy identifies the file containing the HMI application

The procedure performs the following steps:

  • Check the presence of the QCL application
    The “Checking application presence…” message is given.
  • Create and write in NAND the QCL application backup file: applic.qcy
    The “Write QCL application” message is given with the percentage progress of the operation.
  • Check the presence and validity of retentive data of the QCL application
    The “Checking retentive data…” message is given.
  • Create and write in NAND the retentive data backup file of the QCL application: appdat.qcy
    The “Write QCL data” message is given with the percentage progress of the operation.
  • If the controller has a display, a check is made for the presence of the HMI application:
    If the HMI application is correct the backup file appqtp.qcy is created in NAND and the “Write QTP application” message is given with the percentage progress of the operation.
    If the application contains errors, the “QTP application error” message is given.
    If the HMI application is not found, the “HMI application not present” message is given.
  • Procedure end and system reboot.

The restore procedure allows to recover from the NAND mass storage, the saved backup files of the QCL and HMI applications and an dump of the retentive data.

The procedure :

  • The message “Restore NAND backup” is given.
  • The NAND backup file of the QCL Application is read: applic.qcy
    The message “Upload QCL application” is given, the percentage progress of the operation and the procedure step number.
  • The NAND backup file of the QCL Application retentive data is read : appdat.qcy
    The message “Upload retentive data” is given, the percentage progress of the operation.
  • If the controller has a display, the presence of the HMI application is checked and read from the NAND back up file: appqtp.qcy.
    The message “Upload HMI application” is given, the percentage progress of the operation and the procedure step number
  • Procedure end and system reboot.



The use of system functions Backup to NAND and Restore from NAND allows to save in backup and restore a QMOVE application.

The backup and restore operations use the NAND internal memory device. The backup procedure creates a file copy of the QCL program, the HMI program (if the controller has a Qem display) and an image of the ritentive data.

The files created:

  • applic.qcy containing the QCL program (QCL App)
  • appdat.qcy containing the ritentive data image (QCL Dat)
  • appqtp.qcy containing the HMI program (QTP App)

The files are encrypted and only the controller that generated them can run the Restore procedure so as to safeguard unauthorised data copies. The backup file copied to external memory such as MMC/SD or USB card can be carried out with the system function Copy all NAND files -> DEVICE. A directory named “QBK” is created in the MMC/SD or USB that contains the above files. In the same way backup files can be transferred to the controller using the system function Copy all files DEVICE -> NAND. In this case, the files in the MMC/SD or USB must always be contained in the directory “QBK”.

Backup/restore is an important function that can be used in the following cases:

  1. to restore the QMOVE application to a known situation (the situation at the time of the backup), if data has been changed by an operator or if the machine data has been altered for any reason.
  2. when testing a new application, a backup can be made of the original, stable version. If the new application being tested is not satisfactory, the restore command will recover the original version.

This chapter outlines all product information that is necessary for programming, in other words during the development of a QCL application.

The product programming requires the Qview-6 environments to program the QCL code and if the product has a graphic display, also the QPaint-6 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 (in “Support” section).

The contoller has 3 slots. The slots 4 to 32 can be declared and must be used to address recources installed in the Canopen modules.

To use the terminal in a product that has a display, you must declare under INTDEVICE the device MMIQ2.

INTDEVICE
   Hmi	MMIQ2	2

To program with the QPaint-6 development environment it is important to select the correct target. To do so, in the environment select ProjectTarget Configuration then select the right controller according to the ordering code.

A typical BUS declaration to use in the BUS section of the configuration unit:

BUS
   1	1P20F	10
   2	1MD1F	.

The firmware version must naturally correspond and the specialist card name at slot 3 must be correct. See the right chapter.

This paragraph looks at how to measure an estimate of use of the product's memories. The non volatile memory is available to memorise the QCL program and has a capacity of 512KB.
The memory space occupied is equal to the size of the .BIN file generated by Qview. The percentage memory occupied can be viewed in the CPU panel of Qview under “Used CODE memory”, or this information can be obtained from the value of parameter “sizeapp” of the QMOS device.

The non volatile memory available to memorise the HMI program has a capacity of 1.5MB.
The memory space occupied is equal to the size of the .BIN file generated by Qpaint, whose value (in bytes) is viewed in parameter “memqtp” of the MMIQ2 device.

The non volatile data memory used to memorise retentive variables, has a capacity of 400KB.
The percentage memory occupied can be viewed in the CPU panel of Qview, under “Used RETENTIVE”, or this information can be obtained from the value of parameter “sizeret” of the QMOS device.

The volatile data memory used to memorise non ritentive variables has a capacity that depends on various factors (e.g. the HMI and QCL program sizes, the HMI screen being viewed, etc)
The free system general memory, available as volatile data memory, is indicated by parameter “memfree” in the MMIQ2 device.

The PROG and USER serial ports implement the QEM proprietary communication protocol called BIN1.

The SERCOM and MODBUS devices can be used with all communication serial ports including PROG PORT. Use the following number settings during the device declaration to select the communication channel:

  0		PROG PORT
  1		USER PORT
  2		AUX1 PORT
  3		AUX2 PORT    (if available for this hardware)

When the SERCOM and MODBUS devices use the PROG PORT or USER PORT, they address the channel only if the communication status of the device is open (st_opencom = 1). When the channel of the device is closed (st_opencom = 0) in the serial, the BIN1 protocol returns active. To force the BIN1 protocol on the PROG port (thereby preventing the SERCOM device from occupying the channel) active the SW1 dip 6.

When using the MODBUS RTU protocol on serial port AUX1 e AUX2 with RS485 electric configuration, remember that when the serial port is transmitting, the controller maintains the channel (DE) active for a longer time than the “MODBUS RTU” specification. To this must be consider a minimum time of 5 milliseconds after which it is possible to receive a new message. Also the SERCOM device, when it ends a transmission, has the same time the channel is active (DE).

The Ethernet communication port use the transport protocol TCP/IP, where the BIN1 protocol packets are encapsulated within TCP/IP data packets. There are two active connections identified by two communication ports can be freely set in the communication parameters of the Ethernet port. If the instrument is provided with a display, these values are displayed and modified using the system function 12 - Set Ethernet communic. parameter. Other ways to view and set these figures can be realized through special programs available within the development environment (QConfigurator-1 and QConfigurator-2).

The port set in “Port nr.1:” represents a communication channel equivalent to PROG PORT. The port set in “Port nr.2:” represents a channel equivalente to USER PORT. The ports 3 e 4 are not used.

The Ethernet port can also be used to establish a communication type Modbus TCP/IP with other networked devices. In this case the channel that identifies the Ethernet port can be set by entering the number 43.

mdbs   MODBUS   2   43

The 3 channels of Ethernet communication port (two with BIN protocol and one MODBUS TCP/IP) can be active simultaneously.

When downloading the Qmove application, the QView-6 development environment can give error messages that are not described in the development environment manual. These errors are special and the description string given by QView-6 is generated directly by the firmware.

The table below describes possible error messages generated by the firmware.

Firmware error messages
Possible error messageDescription
Error: SYSTEM + ARRSYS + DATAGROUP + INTDEVICE size overflow by 234bytes.Given when the retentive variables exceed the maximum limit.
Error: serial port not avaliable in SERCOM or MODBUS device declaration.Given when the wrong number is used during the device declaration to select the communication channel.
Error: CANOPEN device required if you use more than 3 slots.In the BUS definition more than 3 slots are being used and so the application requests the use of Canopen modules. To manage this, a CANOPEN device must be declared.
Error: incorrect bus fault mode in CANOPEN declaration.The CANOPEN device declaration indicates a fault mode (last value in the declaration) that is not supported.
Error: incorrect canbus speed in CANOPEN declaration.The CANOPEN device declaration indicates an invalid speed.
Error: too much CANOPEN device declaration.Only one CANOPEN device can be declared.
Error: absol. encoder resource num in ABSCNT device declar. is not avail.The ABSCNT device declaration indicates an inexistent resource.
Error: COUNT in ABSCNT device declaration is not a simulated counter.The counter address used in the ABSCNT device declaration cannot be a simulated type (e.g. 1.CNT01).
QMos version error. Unsupported instructions set.One or more statements in the project QCL are not supported by the firmware.
Error: compression file type not support.The compression of the compiled QCL program is not supported by the firmware.
Error: too mutch slots in bus declarations.They were declared under BUS more slots than those allowed by the hardware.



The development environment provides a series of ready-made variables that can be used by putting the word “QMOVE.” before the name. For example “QMOVE.is_suspend”, “QMOVE.sys001”, etc. This paragraph is designed to illustrate the 16 system variables called sys001-sys016, whose meaning depends on the firmware that is being used.

sys001

This is a read only variable that indicates the status of the FUNC (bit 0) and BOOT (bit 1) buttons. The following settings are possible:
0 = no button pressed.
1 = FUNC button pressed.
2 = BOOT button pressed.
3 = FUNC and BOOT buttons pressed.

sys002

This variabile allows to read a dump of the SW1 dip-switches. The dump is acquired only after the controller is powered. The Bit 0 corresponds to dip 1 and so on.

NOTE: Some dips are not connected to the microprocessor and is therefore always read at logic level 0.

sys003

This variable allows the command of led's L1-L2-L3-L4. The bit 0 corresponds to L1, the bit1 to L2 and so on.

sys004

This variable allows toxet the anti-glitch filter on the phase signals in the two-way counters. The setting is expressed in KHz and refers to the signal frequency of one phase. The setting range is 30-220. The default setting is 220KHz. The variable can also be reread. The filter can be modified at any time.

sys005-16

Not used.

The term device identifies a category of software devices designed to perform more or less complex support and control actions, to solve problems tied to the automation of systems. There are two types of device: internal and external. Internal devices have their codes residing and performed by the firmware of the actual product. External devices have the code residing and executed in the “intelligent” specialist cards that have their own calculation capability. The controller can only manage internal type devices . The list of devices implemented in the firmware depends on the firmware version. This paragraph is designed to illustrate the list and characteristics of the devices available.

Firmware version 10 implements the following devices:

Device nameSampling time
minimum (msec)
Sampling time
maximum (msec)
Execution time (%)
ANINP125014,25
CALENDAR--0
CANOPEN1250100
COUNTER312505,94
DAC--0
DATASTORE12090,5
FREQ12504,75
MMIQ211090,5
MODBUS125032,07
QMOS--0
RECDATA12505,34
SERCOM12509,26

Firmware version 20 implements the following extra devices:

Device nameSampling time
minimum (msec)
Sampling time
maximum (msec)
Execution time (%)
ANPOS212508,31
EANPOS125055,94
HEAD2125023,75
OOPOS3125027,91

Firmware version 30 also implements the following devices:

Device nameSampling time
minimum (msec)
Sampling time
maximum (msec)
Execution time (%)
CAMMING3125055,94
INTERP125035,63
JOINT1)125095,01

1) The effective sampling time is double the actual setting

Details of devices

This section describes additional information about the devices. This information will complement and complete the device of user manual available in the QEM site. Information related to the device in this particular product.

CANOPEN

If the device declaration CANOPEN indicates the zero speed, then it can be set by SW1 dip's 5 and 7. The first slot to address resources that reside in Canopen modules is 4.

DATASTORE

The files processed by the device DATASTORE are all contained in the /DS directoty. If this directory does not exist, it is created automatically. The device DATASTORE can operate both with the MMC/SD card and with the internal NAND memory (not removable). To define which mass memory to operate the priority paramenter is used (0=MMC/SD, 1=NAND). If the application has to access the two supported devices frequently and the physical removal of the MMC/SD card is not required, a special setup can be used for the priority parameter that avoids having to continuously run the memory MOUNT UMOUNT. In pratice, when wanting to change memory, before running the UMOUNT command, set “priority = -1”. This avoids the UMOUNT phase is avoided in the device, making the next MOUNT command to the memory very fast.

An example of QCL code to change device:

SUB SETMMC
  WAIT NOT data.st_busy
  IF data.st_mount
    data.priority = -1
    data.UMOUNT
    WAIT NOT data.st_mount
    CALL CHECK_ERR_WRN
  ENDIF
  data.priority = 0
  data.MOUNT
  WAIT data.st_mount
ENDSUB
 
SUB SETNAND
  WAIT NOT data.st_busy
  IF data.st_mount
    data.priority = -1
    data.UMOUNT
    WAIT NOT data.st_mount
    CALL CHECK_ERR_WRN
  ENDIF
  data.priority = 1
  data.MOUNT
  WAIT data.st_mount
  CALL CHECK_ERR_WRN
ENDSUB

There is a particular setting of the parameters that allows to check the existence of a file in the device. Use the “filenum” parameter set to -1 and with the OPENFILE command the device, instead of opening the file, it searches for the first file in the ”/DS/“ directory of the selected memory. When it is found, the file name is set by the device in the parameter “filenum” (and its type in the parameter “filetype”). Setting -1 in “filenum” again and running the OPENFILE command, the next file name is found and so on. Every time an OPENFILE operation is run with filenum different to -1, the search loog is closed. When the search has ended and there are no more files present, then the device will set as answer to the command OPENFILE “filenum = -2”. The execution of the command is signalled by the flag st_busy = 0. If the file extension is not HEX or CSV, the file is ignored by the search. If the file name is not compatible with those managed by DATASTORE (numbers 0 to 9999999) then “filenum” will remain set to -1 and a warning is given.

The “disk size” and “diskfree” parameters are represented in KB.

RECDATA

The device can memorise up to 10000 step.

QMOS

The parameter “frwuvalue01” contains the number value of the product serial number.

FREQ

To define the input associated to the device FREQ use the number field provided in the device declaration. The availability of frequency inputs has to be checked with the hardware version of the product. To ricavare the relation between number and terminal pin, use the information contained in the “Address” column given in the terminal tables.

CAMMING3

The parameters related to the sectors (CodeQm, CodeQs…) are not retentive. On startup they always take on the value 0.


8. Accessories available

  • Last modified: 2019/08/29 17:01