Document: | MIMJ1P31F BASE | |||
---|---|---|---|---|
Description: | Installation and maintenance manual | |||
Editor: | Riccardo Furlato | |||
Approver | Gabriele Bazzi | |||
Link: | http://www.qem.eu/doku/doku.php/en/strumenti/qmoveplus/j1P31/mimj1P31fx_base | |||
Language: | English | |||
Document release | Hardware release | Description | Note | Date |
01 | 02 | New manual | Valid from software release 1P31F-xx.5.3 | 05/12/2012 |
02 | 02 | Adding the 1MG5F card | / | 06/03/2013 |
03 | 02 | New “BASE” varsion of this manual | / | 12/02/2015 |
04 | 02 | Added the section “General information” | / | 03/11/2015 |
The controller has been designed for industral environments in conformity to EC directive 2004/108/CE.
The J1-P31-F is a combo HMI-PAC controller of the Qmove+ range.
The Ordering Code provides the exact product features. Make sure that the product characteristics meet your requirements. |
---|
Model | Features | |||||||
J1 | - | P31 | - | FA | - | 10 | / | TP01 |
---|---|---|---|---|---|---|---|---|
TP00 = Keypad code (TP00 = panel with resistive, logo and custom function keys); TP01 = panel with resistive touch-screen, logo and QEM standard function keys |
||||||||
10 = Firmware version (00 = not installed) | ||||||||
F = Technology level A = Hardware version |
||||||||
P = Basic keypad (only function keys) 3 = 7” LCD graphic display, TFT-256 COLORS-800x480px; front panel dimensions (216x168mm); keypad 7 keys + 11 led; housing to DIN 43700; 1 = Firmware-hardware correspondence |
||||||||
J1 = “HMI+PLC” Qmove family |
These are hardware versions currently available:
Hardware versions | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | G | H | I | J | K | L | M | Y | W | Z | ||
SLOT 2 (Base card) | USER PORT | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
AUX1 PORT (RS232, RS422, RS485) | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | 1 | |
AUX2 PORT (RS485) | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | 1 | |
CAN1 PORT | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |
CAN2 PORT1) | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
ETHERNET PORT | - | - | - | - | 1 | 1 | - | 1 | - | - | 1 | 1 | 1 | 1 | 1 | 1 | |
USB PORT2) | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
SLOT 3 (Specialization cards) | Standard digital inputs | - | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | - | 16 |
Rapid digital inputs3) | - | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | - | 2 | |
Analog inputs 12bit | - | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 4 | 2 | 2 | - | 2 | |
Analog inputs 16bit | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
PT100 inputs4) | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
Termocouple inputs5) | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
Bidirectional counters 20KHz ABZ (24V-PP, 5V-LD) | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
Bidirectional counters 200KHz ABZ (24V-PP, 5V-LD) | - | 2 | 4 | 2 | 2 | 4 | 4 | 2 | 2 | 4 | 4 | 2 | - | 4 | - | 4 | |
SSI absolute counters | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
Protected digital outputs | - | 8 | 8 | 8 | 8 | 8 | 8 | 16 | 16 | 16 | 16 | 16 | 16 | 8 | - | 8 | |
Relay digital outputs | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
Analog outputs 0-10V-12bit | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
Analog outputs +/-10V-16bit | - | 2 | 4 | 2 | 2 | 4 | 4 | 2 | 2 | 4 | 4 | 2 | - | 4 | - | 4 | |
Stepper outputs | - | - | - | 2 | - | - | 4 | - | 2 | - | - | - | - | 4 | - | 4 | |
Remote keyboards connector6) | - | - | - | - | - | - | - | - | - | - | - | - | - | 1 | - | 1 | |
Card software code declared in SLOT 3 | - |
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 firmware, consult Devices enabled in the controllers.
A) Function keys and led's
B) System led's
The J1-P31-F s composed of a “base” card and an “expansion” card.
Weight (full hardware) | 1Kg |
---|---|
Housing | Sheet metal |
Front panel | Alluminium |
Outer Frame | Self-extinguishing Noryl |
Display | LCD 7'' TFT 256 colors - 800 x 480px |
Touch screen | wire Resistive |
Display dimensions | 152,4 x 91,4mm / 7“ |
User led's | 14 |
System led's | 8 |
Function keys | 7 |
System keys | 3 |
Operating temperature | 0 ÷ 50°C |
Transport and storage temperature | -25 ÷ +70 °C |
Relative humidity | 90% condensate free |
Altitude | 0 - 2000m s.l.m. |
Front protection rating | IP64 |
RISC microprocessor (32 bit) | |
---|---|
Work frequency | 200MHz |
RAM | 16MB |
Flash | 8MB |
Lengths in mm |
---|
Fit the controller in the hole.
Apply the brackets.
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.
Warning: after putting the pin of fixing, do only half rotation to not tear the frame! |
---|
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 | 30W |
CN1 | Terminal | Symbol | Description | |
---|---|---|---|---|
1 | + | DC power positive | ||
2 | GROUND | Gnd-PE (signals) | ||
3 | - | DC power 0V |
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 |
CN2 | Terminal | RS232 | RS422 | RS485 | Description |
---|---|---|---|---|---|
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 | Terra | ||||
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 |
CN3 | Terminal | RS232 | RS422 | RS485 | Description |
---|---|---|---|---|---|
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 |
CN4 | Terminal | Symbol | Description |
---|---|---|---|
1 | 0V | RS485 serial common | |
2 | B | Terminal RS485 B | |
3 | A | Terminal RS485 A |
CN5-CAN1 PORT CN6-CAN2 PORT | Terminal | Symbol | Description |
---|---|---|---|
1 | 0V | CAN common | |
2 | CAN L | Terminal CAN L | |
3 | CAN H | Terminal CAN H |
SW5 | Num. Dip | Name Dip | Setting of DIP | Function |
---|---|---|---|---|
1 | JP1 | ON | CAN1 Termination | |
2 | JP2 | ON | ||
3 | JP1 | ON | CAN2 Termination | |
4 | JP2 | ON |
When activating the CAN1 port termination, set dip's JP1 and JP2 to ON. When activating the CAN1 port termination, set dip's JP1 and JP2 to ON. |
---|
ETHERNET PORT | Description |
---|---|
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 slot (marked by an arrow) |
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 “QMOVE:sys004” section variables of system.
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 speed | Min. 9.6 Kbaud - max 115200 Kbaud settable by dip1 and 2 of the switch SW1 |
Insulation | None |
.
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 speed | 4800, 9600, 19200, 38400, 57600, 115200 baud |
---|---|
Communication mode | Full duplex |
Operating mode | Referred to 0V |
Max. number of devices connected on the line | 1 |
Max. cable length | 15 m |
Input impedence | > 3 Kohm |
Short-circuit current limit | 7 mA |
Communication speed | 4800, 9600, 19200, 38400, 57600, 115200 baud |
---|---|
Communication mode | Full duplex |
Operating mode | Differential |
Max. number of devices connected on the line | 1 |
Max. cable length | 1200 m |
Input impedence | > 12 Kohm |
Short-circuit current limit | 35 mA |
To activate the internal termination resistance see paragraph Setup of USER PORT electric standard, Setup of AUX1 PORT electric standard or Setup of AUX2 PORT polarization and termination resistances |
---|
.
Communication speed | 4800 baud (only if used with SERCOM and/or MODBUS device), 9600 baud, 19200 baud, 38400 baud, 57600 baud |
---|---|
Communication mode | Half duplex |
Operating mode | Differential |
Max. number of devices connected on the line | 32 |
Max. cable length | 1200 m |
Input impedence | > 12 Kohm |
Short-circuit current limit | 35 mA |
To activate the internal termination resistance see paragraph Setup Termination resistances
.
Communication speed | 125, 250, 500, 1000 Kbit/s |
---|---|
Max. number of Drivers/Receivers on the line | 100 |
Max. cable lengths | 500m @ 125Kbit/s, 250m @ 250Kbit/s, 100m @ 500Kbit/s, 25m @ 1000Kbit/s |
Input impedence | >15Kohm |
Short-circuit current limit | 45mA |
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:
Type of Memory Card to use | MMC, 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). |
.
To use the Memory Cards they must first be formatted with FAT16 or FAT32 file system. |
---|
SW1 | Dip | DIP settings | Function | |||
---|---|---|---|---|---|---|
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 devices | PROG 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 normal | PROG PORT on USER PORT connector |
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:
Led | Colour | Status | Description |
---|---|---|---|
pow | Green | Power on | |
Only this led on, signals the CPU reset status | |||
run | Green | CPU in RUN status | |
CPU in READY status | |||
stop | Yellow | With pow on, signals the STOP status of the CPU With pow off, signals the BOOT status of the CPU |
|
err | Red | With 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 |
N. flashes | Error | Description | Recommended action |
1 | Bus error | Bus 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 Error | Negative 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 Bound | An array index is pointing on an inexistent element | Open 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 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. |
During the startup sequence, if a malfunction of any peripheral is detected, the system blocks and the error is signaled by the flashing led 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 |
.
Each of these signals indicates a serious error situation. The product must be sent to the QEM aftersales service. |
---|
Name | Description |
---|---|
FUNC | Press on startup of the controller to access the System functions |
BOOT | Press on startup of the controller to set the CPU in Boot status and then access the firmware update functions |
RESET | Reset CPU. the system is restarted restoring the initial conditions (after a startup ) |
This chapter will introduce some concepts and describes some operations of the product. These contents are partly related and implemented in firmware. This software implements all features that allow the product to be a component of the system programmable Qmove.
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:
“Non volatile memory”, which stores:
“Volatile memory”, which stores:
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.
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).
n. | Led ON | System Message (if display present) | Description | Type |
---|---|---|---|---|
1 | L1 | System Data WRITE ERROR | Indicates that a write error has occurred during the configuration data saving. | B |
2 | L2 | System Data IS RESTORED FROM DEFAULT | Indicates that the configuration data has been restores to the default settings. | C |
3 | L1 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 |
4 | L3 | Firmware is updated | 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 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:
WARNING: The values shown in the figure are examples and may vary according to the instrument. |
---|
n. | Message | Description |
---|---|---|
1 | Boot status: POWER-ON | It 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.6 | They 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: 12345678 | This displays the serial number of the instrument. |
4 | Date(DMY)/Time: 31/12/2010 - 12:34:56 | The clock/calendar is displayed in the format: DD/MM/YYYY - hh:mm:ss |
5 | Dip-Switch = 0x2E | It 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 KB | If 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 KB | It 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: PRESENT | Instruments 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 | 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 | 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 Functions | The 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 !!! | 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 !!! | 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 status | pow run |
Status cause | No application in memory. |
The condition that can put the CPU in this status | RESET command. |
This condition can only pass onto a READY status by downloading the applicaiton, using the Qview6 development environment.
Led status | pow run |
Status cause | Application valid and waiting for execution. |
Conditions that can put the CPU in this status | Application download. |
This condition can pass onto to the RUN or RESET statuses.
Led status | pow run |
Status cause | Application in execution. |
Condition that can put the CPU in this status | RUN command. |
This condition can pass onto all other CPU statuses.
Led status | pow stop » run |
Status cause | Stop on application in execution. |
Condition that can put the CPU in this status | A breakpoint has been encountered in the application code interpretation. |
This condition can pass onto all other CPU statuses.
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 ON | System Functions | PWD | Description |
---|---|---|---|---|
1 | L1 | 01 - Reset Error Checksum | - | Reset checksum error. NOTE: if the checksum error is present, the led L1 flashes. |
2 | L2 | 02 - Copy all files DEVICE → NAND | - | Copy all files from DEVICE to NAND Flash memory. |
3 | L1 L2 | 03 - Copy all files NAND → DEVICE | - | Copy all files from NAND Flash memory to DEVICE. |
4 | L3 | 04 - Application delete | Y | Delete the application. |
5 | L1 L3 | 05 - Application upload from DEVICE | Y | Upload the application from DEVICE. |
6 | L2 L3 | 06 - System Settings | - | Adjust the system clock and selection of the DEVICE (only for hardware that possess both ports). |
7 | L1 L2 L3 | 07 - Downl. retentive data to DEVICE | - | Save the retentive data on DEVICE. |
8 | L4 | 08 - Set NEW Password | Y | Set a new password to access the “locked” system functions. |
9 | L1 L4 | 09 - Remove all files from NAND Flash | Y | Cancel all files stored on the NAND Flash memory. |
10 | L2 L4 | 10 - Show NAND Flash files | - | List the files stored on the NAND Flash memory. |
11 | L1 L2 L4 | 11 - Touch Calibration | - | Run the calibration procedure of the Touch Screen, if present. |
12 | L3 L4 | 12 - Set Ethernet communic. parameter | - | Run the setup procedure for the Ethernet communication parameters (IP address,…, etc.). |
13 | L1 L3 L4 | 13 - Backup to NAND | - | Run the backup of the QCL application, data and HMI application on NAND memory. |
14 | L2 L3 L4 | 14 - Restore from NAND | Y | Run the restore of the QCL application, data and HMI application from NAND memory. |
15 | L1 L2 L3 L4 | 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.
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”.
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.
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.
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 err indicates the type of error.
If there is a display, a message is given to describe the cause of the error.
Error/Number of ERR led flashes | Message |
---|---|
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 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:
“Clear power down data…”
fino al termine della procedura.“Clear power down data…”
until the end of the procedure.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:
Message | Description | Possible errors |
---|---|---|
Check DEVICE presence | Checking 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 card | Device not present or unformatted |
Searching files… | Searching for compatible files | No 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:
Message | Description | Possible errors |
---|---|---|
Check DEVICE presence | Checking 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 device | Device not present or unformatted |
Searching files… | Searching for compatible files | No 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:
Message | Description | Possible errors |
---|---|---|
Reset retentive data | Empty nonvolatible data memory | Write file error |
Delete QCL application | Deletion of the QCL program | Write file error |
Delete HMI application | Delection 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:
Message | Description | Possible errors |
---|---|---|
Check DEVICE presence | Checking 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 card | Device not present or unformatted |
If the applic.bin is present:
Message | Description | Possible errors |
---|---|---|
Upload QCL application | Uploading the QCL program | Open/Exist/Create file 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:
Message | Description | Possible errors |
---|---|---|
Upload retentive data | Uploading retentive data to the nonvolatile data memory | Open/Exist/Create file error |
The procedure performs the following steps:
“Check DEVICE presence”
message is given.“Upload QCL application”
message is given.“Upload retentive data”
message is given.“Upload HMI application”
message is given.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 DEVICE presence”
message is given.“Mounting device…”
message is given.“Checking application presence…”
message is given.“Checking retentive data…”
message is given.“Open destination file…”
message is given.“Write headers to destination file”
message is given.“Write data to destination file”
.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.
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:
“Searching files…”
message is given.“No Files Found”
message is given and the function ends, otherwise the “Delete <filename>”
is given indicating the delection of every file found.This procedure views the name and size of all files found in the internal NAND flash mass storage.
The procedure performs the following steps:
“Searching files…”
message is given.“No Files Found”
message is given and the procedure ends.“<filename> - <size>B”
of each file found is shown.“Press BOOT or F2 to show next filename”
message is given.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.
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:
The procedure performs the following steps:
“Checking application presence…”
message is given.“Write QCL application”
message is given with the percentage progress of the operation.“Checking retentive data…”
message is given.“Write QCL data”
message is given with the percentage progress of the operation.“Write QTP application”
message is given with the percentage progress of the operation.“QTP application error”
message is given.“HMI application not present”
message is given.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 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:
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:
In this chapter are collected all the product information for programming.
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 Project → Target Configuration then select the right controller according to the ordering code.
Example of a statement of the BUS to use on the BUS unit's configuration:
BUS 1 1P31F 10 2 . . 3 1MG5F .
The firmware versione must coincide, and if available, the specialization card name to the 3 slot must be correct. See the dedicate section.
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 5.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 819KB.
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 USER, 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.
Possible error message | Description |
---|---|
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 device term identifies a category of software capable of supporting and monitoring activities, more or less complex, to solve the automation systems problems.
The list of implemented devices in the firmware depends from the firmware version.
The firmware version 10 include following device:
Device name | Minimum sampling time (msec) | Maximum sampling time (msec) | Execution time (%) |
---|---|---|---|
ABSCNT | 1 | 250 | 8,31 |
ANINP | 1 | 250 | 14,25 |
CALENDAR | - | - | 0 |
CANOPEN | 1 | 250 | 100 |
COUNTER3 | 1 | 250 | 5,94 |
DAC | - | - | 0 |
DATASTORE | 1 | 20 | 90,5 |
FREQ | 1 | 250 | 4,75 |
MMIQ2 | 1 | 10 | 90,5 |
MODBUS | 1 | 250 | 32,07 |
QMOS | - | - | 0 |
RECDATA | 1 | 250 | 5,34 |
SERCOM | 1 | 250 | 9,26 |
The firmware version 20 include also following device:
Device name | Minimum sampling time (msec) | Maximum sampling time (msec) | Execution time (%) |
---|---|---|---|
ANPOS2 | 1 | 250 | 8,31 |
EANPOS | 1 | 250 | 55,94 |
HEAD2 | 1 | 250 | 23,75 |
OOPOS3 | 1 | 250 | 27,91 |
The firmware version 30 include also following device:
Device name | Minimum sampling time (msec) | Maximum sampling time (msec) | Execution time (%) |
---|---|---|---|
CAMMING3 | 1 | 250 | 55,94 |
INTERP | 1 | 250 | 35,63 |
JOINT1) | 1 | 250 | 95,01 |
This section describes the additional information of the devices. This information complement and complete the maintenance manual of the device available on the Qem site. These are the information related to the implementation of the devices in this product.
If in the device declaration CANOPEN set the 0 speed then it becomes can be set by means of SW1 dip.
The first slot of the target resources that reside within the Canopen is the 4.
The firmware capture the input interrupt while this is located in a Canopen module.
You can enter the 2 value in the Declaration of the device on the relative sector to the port. This setting makes it possible for the startup of the QCL DS402 drives through a request (QDO number 10). This function is essential in cases where there are driver without enable input and the power supply logical is in common with main power supply. If the main power supply is turn off, the drive ot communicating in CANOPEN because also the logic section are turned off.
The files used from the device DATASTORE are contain in the /DS folder. If this folder does not exist it is created automatically.
The DATASTORE device can can operate with MMC/SD or USB NAND memory inside the product (not removable). To define how your device used the parameter value priority (0=MMC/SD, 1=NAND, 2=USB). If your application needs to frequently access to the MMC/SD or USB device and do not require physical removal, you can use a particular priority parameter setting that avoids continually MOUNT UMOUNT devices. Before execute the UMOUNT command to set the “priority = -1”.
A QCL code example to change device may be:
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
Check for the existence of a file on the external memory. Do you use the “filenum” set to the -1 value and use the OPENFILE command. If you set again the -1 value in “filenum” and use the OPENFILE command will search for the name of the next file, and so on. Whenever we will use a different -1 value with OPENFILE the search loop filenum will be closes. When the search is complete and there will be no more files, then the device will response to the OPENFILE command “filenum = -2”. The successful execution of the command will be indicated by flag st_busy = 0. If the file extension is not HEX or CSV file itself is ignored by the search. In the case that the file name is not compatible with those managed by DATASTORE (numbers from 0 to 9999999) then the “filenum” will remain set to -1 value and will report a warning.
The “disksize” and “diskfree” parameters are represented in KB.
The device can store 10000 step maximum.
The “frwuvalue01” parameter contains the numeric value of the serial number of the product.
To define the input associated to the device FREQ use the appropriate numeric field on the device. The availability of frequency inputs must be verified with the hardware version of the product. To derive the relationship between numerical value and terminal pin use the information in the “address” column in the tables in the illustration of the terminal.
The parameters in the fields sector (CodeQm, CodeQs…) are not ritentive. At power-up they take always value 0.