Pc6d Single Point Manual en
Pc6d Single Point Manual en
Technical Manual
Flintec GmbH
Bemannsbruch 9
74909 Meckesheim
GERMANY
Page 2 Manual PC6D CANopen
Contents
Part A: CANopen .................................................................................... pages 4 - 24
PART A................................................................................................................................. 5
1 INTRODUCTION............................................................................................................ 5
1.1 IDENTIFICATION AND SCOPE ..................................................................................... 5
1.2 PURPOSE ................................................................................................................. 5
1.3 ACRONYMS AND DEFINITIONS ................................................................................... 5
1.3.1 Acronyms........................................................................................................ 5
2 SYSTEM DETAILED DESIGN..................................................................................... 6
2.1 GENERAL ................................................................................................................. 6
2.2 CANOPEN ................................................................................................................ 7
3 CANOPEN PROFILE................................................................................................... 8
3.1 THE PDOS ............................................................................................................... 8
3.2 NETWORK MANAGEMENT .......................................................................................... 9
3.3 COMMUNICATION PROFILE ...................................................................................... 10
3.4 OBJECT DIRECTORY ............................................................................................... 10
3.5 QUICK START GUIDE .............................................................................................. 22
3.5.1 Process data objects .................................................................................... 22
3.5.2 Service data objects ..................................................................................... 23
4 NOTES ........................................................................................................................ 24
4.1 FIRMWARE UPDATE (VIA CANOPEN) ....................................................................... 24
4.2 FIRMWARE UPDATE (VIA PC) .................................................................................. 24
1 Introduction
This document describes the system design for a CANopen interface of the PC6D. It
describes the protocol used and the CAN open profile used to access the PC6D
1.2 Purpose
The purpose of this document is to specify the functionality, and performance of the PC6D
CANopen interface.
1.3.1 Acronyms
This section includes a list of all abbreviations and acronyms used throughout the document
in alphabetical order.
2.1 General
This software connects a physical load cell to a CANopen network. The PC6D digitizes, filters
and processes the analog inputs. It transports commands, responses and results from and to
the CANbus.
CANopen
Network
Load Cell Sensor
&
Power
The PC6D follows the CAN2.0B recommendation. It receives both 11-bit identifiers, and
tolerates 29-bit identifiers. It only transmits 11-bit identifiers.
The PC6D is always quiet on the CANbus until the NMT Start command is received, except
for the very first ‘node guard’ message.
When started, the TPDO1 is used to send current status information. The TPDO1 holds the
module status and either net or gross weight, depending on the SDO selection. The default is
the Net value.
The TDPO2 is used for reporting ‘on-demand’ average measurements and reporting set-point
events.
In case of an overrun, error or failure an EMERGENCY message is sent to the CAN controller
indicating the nature of the error or failure.
EMERGENCY messages are transmitted when the CAN controller tries to set up a module
not present, or not functioning, when a module fails to answer the normal backplane scan and
when a module comes back online.
The RPDO1 can be used to set/reset Zero and Tare, and for quick selection of the Net weight
(default) or Gross weight as the data contained in TPDO1.
The RPDO2 can be used to send software triggers to start average measurements.
The weight and status is sent constantly to the CANbus. The TPDO1 is sent 20 times per
second. The TPDO2 is sent every time the PC6D finishes a triggered measurement or a Set-
Point is crossed. The TPDO3 is sent every time the Tare value is changed.
The first field is carrying weight information Gross or Net value if it is a TDPO1, Average
or Set-Point weight if it is a TPDO2.
Tare value if TPDO3.
Then module state follows as a 16 bit field width the following values:
$0001 - Under range
$0002 - Over range
$0004 - Not within Zero range (not yet implemented, zero)
$0008 - Exactly zero
$0010 - No motion, still stand, steady state
$0020 - Tare set
$0040 - Preset tare (0=tare is measured, 1=tare is set by user)
$0080 - Invalid weighing (wire-break, A/D ref. out of range)
$0100 - Set-point 1 (source>limit)
$0200 - Set-point 2
$0400 - Set-point 3
$0800 - Set-point 4
$1000 - Unused, zero
$2000 - Unused, zero
$4000 - Unused, zero
$8000 - Cold start
Source is zero in TPDO1 and TPDO3, and has the following meaning in TPDO2:
0 – (zero) Average result
1 – Setpoint 1 crossed
2 – Setpoint 2 crossed
3 – Setpoint 3 crossed
4 – Setpoint 4 crossed
Where
- SnG means select Gross Weight
- SnN means select Net Weight
- ST means Set Tare
- RT means Reset (Clear) Tare
- SZ means Set Zero
- RZ means Reset (Clear) Zero
Where
- TR is a software trigger that starts an average measurement.
- TS Trigger Stop; stop triggered measurement(s).
The PC6D implements the Network Management protocol with the node guarding protocol.
The PC6D also implements an address setup feature. The network controller may change a
PC6D node address using COB-ID = 0.
The frame must be sent while the PC6D is in its PRE-OPERATIONAL state and it must have
the following contents:
8 bits 8 Bit 48 bit (12 BCD digits)
Hex: 55 New CAN-ID BCD coded serial number
The serial number must be BCD coded and right-justified with as many leading zeros as
needed to make 12 BCD digits.
All PC6D on the CANbus will receive the message, but only the PC6D with the serial number
given will react to, and echo the frame with 55h changed to AAh. The PC6D will save the new
setting immediately and then restart itself.
The parameters which are critical for communication are determined in the communication
profile.
This includes the data for manufacturer's product nomenclature, for identification, or the
parameters for object mapping.
ro read only
rw read / write
write only
wo
(read will not be regarded as an error, but returns undefined results)
UI8 Unsigned8
UI16 Unsigned16
UI32 Unsigned32
I32 Signed32
VS Visible String
1005 0 COB-ID Sync messg. UI32 rw 80H COB-ID of the SYNC object
1006 0 Communication cycle UI32 rw 50000 Minimum interval between TDPO1 (default 20Hz).
Period Min=833 (1200Hz rate).
100C 0 Guard Time UI16 rw 320 Cycle time in ms, set by the NMT Master or the configuration tool.
100D 0 Life Time Factor UI8 rw 3 Wait time is set by the NMT Master or the configuration tool.
100E 0 Node guarding UI32 rw 0x700 + Node guarding identifier
identifier NodeID
1014 0 COB-ID Emergency UI32 rw 80H + COB-ID of the Emergency Object
Message NodeID
1017 0 Heartbeat Time UI16 rw 0 Producer Heartbeat time. If index 1017h is nonzero Heartbeat is
used, else Node-guard protocol is used.
1018 0 Identity Object UI8 ro 4 Number of entries
1 Vendor ID UI32 ro Vendor ID
2 Product Code UI32 ro Product Code
3 Revision Number UI32 ro Revision Number
4 Serial Number UI32 ro Serial Number
1400 0 Number of elements UI8 ro 2 Communication parameters of 1st Receive PDO
1 COB-ID UI32 ro 80000200H Determined using the CANopen minimum system ID assignment
+ NodeID procedure.
2 Transmission type UI8 ro FFH Asynchronous communication.
1401 0 Number of elements UI8 ro 2 Communication parameters of 2nd Receive PDO
1 COB-ID UI32 ro 80000300H Determined using the CANopen minimum system ID assignment
+ NodeID procedure.
2 Transmission type UI8 ro FFH Asynchronous communication.
1602 0 Number of mapped UI8 ro 0 Mapping parameters of the 3rd Receive- PDO (disabled)
Entries in Rx PDO 3
1603 0 Number of mapped UI8 ro 0 Mapping parameters of the 4th Receive-PDO (disabled)
Entries in Rx PDO 4
1A02 0 Number of mapped UI8 ro 2 Mapping parameters of the 3rd Transmit- PDO
Entries in Tx PDO 3
1st Object UI32 ro 20010320H 32 bit Integer (default) or float tare value.
2nd Object UI32 ro 20020110H Module Status
1A03 0 Number of mapped UI8 ro 0 Mapping parameters of the 4th Transmit-PDO (disabled)
Entries in Tx PDO 4
2006 0 Number of entries UI8 ro 4 Index 2006 is only for mapping reference (do not access).
1 LDM select [0..63] UI8 wo
2 Factory Default UI8 wo Restores the factory defaults, if the TAC is enabled.
3 Direct command 1 UI8 wo Direct bitwise command byte 1 to LDM
4 Direct command 2 UI8 wo Direct bitwise command byte 2 to LDM
6402 0 Number of entries UI8 ro 7 Number of entries in the 32 bit analog input module
1 Gross weight I32 ro These values are the internal long integer representation of the
2 Net Weight I32 ro weight (the integer values are multiplied by 10^dp [2300sub0B]).
3 Tare I32 ro Index 6402 is a sub-set of index 2001.
4 Dosed weight I32 ro
5 Dosed tare I32 ro Dosed values always read 0 (zero) on PC6D
6 Average weight I32 ro
7 A/D sample I32 ro
6403 0 Number of entries UI8 ro 6 Number of entries in the float analog input module
1 Gross weight REAL32 ro These values are the floating-point representation of the weight as
2 Net Weight REAL32 ro they are transmitted in the PDO1(tx).
3 Tare REAL32 ro Index 6403 is a replica of index 2000.
4 Dosed weight REAL32 ro
5 Dosed tare REAL32 ro Dosed values always read 0 (zero) on PC6D
6 Average weight REAL32 ro
• The PC6D is always quiet on the CANbus until the NMT Start command is received,
except for the very first ‘node guard’ message.
• Default setting for PC6D is CANopen address 1 @ 500 kbit/sec.
TPDO1
Weight values are available at all times (see page 7 or 9)
The following table shows the information of TPDO1 (8 byte, firmware 102.183):
32 bit 16 Bit 8 Bit 8 Bit
Weight Module Status Module number Gateway State
Remark: special firmware (version 102.186) supporting 6 byte available on request
Weight Module Status 0 0
Note:
A timer is controlled by index 1006 which is a silence time after transmission of a TPDO1 in
which no further TPDO1 messages is sent regardless of the output rate from the ADC and
filter system. This timer only applies to TPDO1.
This means that the default filter setting FL=3, type IIR, UR=0 produces 1200 samples. But
the default value 50000 µs in index 1006 means that only every 60th sample is actually
transmitted, the 59 others are blocked by this timer.
On the other hand if you use a FIR filter with FL=8 you will only get a maximum of 150
measurements per second even if you try to set the index 1006 to 100 µs (10kHz). UR will
have the usual effect.
TPDO2
0 => Average weight (is available and refreshes when a new value is ready)
1=> Setpoint 1 crossed
2=> Setpoint 2 crossed
3=> Setpoint 3 crossed
4=> Setpoint 4 crossed
8 byte format as TPDO1. It is sent every time the tare changes and value set is the new tare
value.
32 bit 16 Bit 8 Bit 8 Bit
Weight Module Status 0 0
RPDO1
The following commands can be executed direct (see Index 1600):
Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
Cmd: SG SN ST RT SZ RZ
128 64 08 04 02 01
Examples:
- Setting tare for channel 2: transmit RPDO1 [01 08]
- Setting gross weight in TPDO1 for channel 1: transmit RPDO1 [00 128]
RPDO2
The following commands can be executed direct (see Index 1601):
Bit7 Bit6 Bit5 Bit4 Bit3 Bit2 Bit1 Bit0
Cmd: TR TS
128 01
Example:
- Setting trigger start for channel 5: transmit RPDO1 [04 128]
SDO’s
Are only available on request
Can be used for complete setup of the System MCS-64 via CANbus master, e.g.:
- Filter setting channel 1: Index 2100, Subindex 4
- Filter Mode setting channel 3: Index 2102, Subindex 9
Can be used to get information regarding all the commands available, e.g.:
- Net weight channel 1: Index 2900, Subindex 2
- AD sample channel 3: Index 2902, Subindex 7
Note: Index 2000 and 2001 refer to the CANbus standards (document DS 301, which is
available on request). Using Index 2000 and 2001 you will only get the weight information (no
channel info). Using Index 2900 – 293F you get the weight and channel information.
• via CANopen or
• via PC.
This piece of firmware resides in Flash memory block 0 and 5. Its primary function is
to load new software versions to Flash blocks 1 … 4.
This is used to allow firmware update through the CANbus using a special protocol.
Please ask Flintec for the description.
For this purpose we have a special programmer software for an easy download of the
firmware. Additional you need a converter “RS232/CANbus” or “USB/CANbus”. We
recommend the a converter “USB/CANbus”.
For CANbus communication via PC (Win2000/XP) with USB-port you can use:
PCAN-USB-Adapter
www.peak-system.com / [email protected]
5 COMMANDS
These pages describe the ASCII commands as they must be used e.g. by the DOP software.
At each command the equivalent CAN index and sub-index are given for reference.
For better clarity, all commands are divided into groups as described on the following pages.
PART B............................................................................................................................... 25
5 COMMANDS................................................................................................................ 25
5.1 SYSTEM DIAGNOSIS COMMANDS – ID, IV, IS .......................................................... 26
5.2 CALIBRATION COMMANDS – CE, CM, DS, DP, CZ, CG, ZT, FD, CS ...................... 27
5.3 MOTION DETECTION COMMANDS – NR, NT ............................................................. 30
5.4 FILTER SETTING COMMANDS – FM, FL, UR ............................................................ 31
5.5 SET ZERO/TARE AND RESET ZERO/TARE COMMANDS – SZ, RZ, ST, RT................. 33
5.6 OUTPUT COMMANDS – GG, GN, GT, GS ............................................................... 35
5.7 SETPOINT COMMANDS - SN, HN, AN ....................................................................... 36
5.8 COMMUNICATION SETUP COMMANDS – AD, BR, TERMINAL RESISTOR ..................... 38
5.9 TRIGGER COMMANDS – SD, MT, GA, TE, TR, TL .................................................. 39
5.10 TRIGGER SPECIAL COMMANDS– RW, TT, TS, DT, TW, TI, HT ............................... 42
5.11 SAVE CALIBRATION, SETUP & SETPOINT PARAMETERS COMMANDS – CS, WP, SS ... 45
Use these commands to get type, firmware version or device status of PC6D. These
commands are sent without parameters.
The response to this request gives the actual identity of the active device. This is particularly
useful when trying to identify different device types on a bus.
IV Request of firmware version [ 2900sub09 ]
Master (PC / PLC) sends Device responds
IV V:0100
The response to this request gives the firmware version of the active device.
The response to this request comprises of two 3-digit decimal values, which can be
decoded according to the table below:
Total 67
Note: the bits that are not used are set to zero.
With this command you get the TAC counter reading or you can enable a calibration
sequence.
This command must be issued PRIOR to any attempt to set the calibration parameters
CZ, CG etc. In legal for trade applications the TAC counter can be used to check if critical
parameters have been changed without re-verification. After each calibration the TAC
counter increases by 1.
This command is used for setup the maximum output value. Permitted values are
between 1…200000.
This command allows the output to step up or down by a unit other than 1. Permitted
values are 1, 2, 5, 10, 20, 50, 100 and 200.
This command allows the decimal point to be positioned anywhere between leftmost and
rightmost digits of the 5-digit output result. Position 0 means no decimal point.
This is the reference point for calibration under load, and is subject to TAC control.
Permitted values are 1…250000.
For calibration an input signal near the display maximum (CM) will give the best system
performance. The minimum calibration load of at least 20% is recommended.
Factory correct calibration default: 200000 d = 2.000 mV/V input signal = 20 kg
This command puts the PC6D back to a known state. The data will be written to the
EEPROM and the TAC will be incremented by 1.
Note: All calibration and setup information will be lost by issuing this command!
Only the factory temperature correction table and serial number are preserved.
This command results in the calibration values being saved to EEPROM, and causes the
TAC to be incremented by 1.
The CS command saves all of the calibration group values, as set by CZ, CG, CM, DS, DP
and ZT. The command returns ERR and has no updating action unless it is preceded by the
CE_XXXXX.
The motion detection facility provides a means of disabling certain functions whenever a
condition of instability, or “motion”, is detected. The “no-motion”, or “stable” condition is
achieved whenever the signal is steady for the period of time set by NT, during which it
cannot fluctuate by more than NR increments.The stable condition activates the relevant bit
of responses to “Info Status” (IS).
The following functions are disabled if motion is detected: “Calibrate Zero” (CZ) “Calibrate
Gain” (CG) “Set Zero” (SZ) and “Set Tare” (ST).
This is the range within which the weighing signal is allowed to fluctuate and still be
considered as “stable”. Permitted values are between 0 and 65535.
Factory default: NR = 1.
This sets the time (in milliseconds) over which the weight signal is checked to see if it is
“stable” or has “no-motion“. The weight signal has to vary by less than NR divisions over the
time period NT to be considered ‘stable’.
Permitted range 0-65535 milliseconds.
If the value of NT =500 milliseconds, the output must not fluctuate more than NR
increments within 500 milliseconds in order to be considered “stable”.
The digital IIR filter works as a low-pass filter of 2nd order with Gaussian characteristic,
damping is 40 dB/decade; see table mode 0.
The digital FIR filter works as a low-pass filter with quick response; damping see table
mode 1.
Factory default: 0
UR 0 1 2 3 4 5 6 7
No. of samples 1 2 4 8 16 32 64 128
The SZ command is issued without any parameters and will return either the OK or ERR
response. If the SZ command is accepted the PC6D responds with OK and the “zero action
performed” bit of the device status (IS) response will be active.
Is the command acknowledged by the PC6D with OK, the status bit for Zero (request IS) is
set to 1. A renewed SZ command or the reset zero command [ RZ ] changes the current zero
point. The command is not implemented, if the current measured value is more than ±2% of
the maximum display value [ CM ] of calibrated zero point [ CZ ].
PC6D response is ERR (error).
The PC6D responds to the RZ command with either OK or ERR. If OK is returned then the
“zero action performed” bit in the Device Status (IS) response will be set to “0”.
This command will activate the net weighing function by storing the current weight value as a
tare.
The weight signal must be “stable” within the limits set by NR (No Motion Range) and NT (No
Motion Time) commands for the “signal stable” bit to be active and set tare command to be
accepted.
If the weight signal is “stable”, the response to the IS command (Device Status) will show the
“signal stable” bit active and the ST command will be accepted (OK). If the “signal stable” bit
is not active, the ST command will be rejected and the LDU will respond with ERR (error).
The PC6D responds to the RT command with either OK or ERR. If OK is returned then the
“tare active” bit in the Device Status (IS) response will be set to “0”.
The following commands “Get” the Gross, Net, Tare and ADC (Sample) values from the
PC6D. Available on the CAN profile index 2000 and 2001 in floating point and integer
respectively.
This command gets the actual Analogue to Digital Converter (ADC) value. This can be useful
during development or when calibrating to see how much of the ADC range is being used.
For service applications, it is helpful to note the GS values for the “no-load” or “zero” output
and when the “calibration load” is applied.
The PC6D has 4 setpoints where the status is dependent on the weight value. Each of them
can be assigned as an independent setpoint value (Sn) with a corresponding
hysteresis/switch action (Hn) and base (An – switch on the gross or the net weight).
S1 Setpoint 1 [ 2600sub01 ]
Request / Setting
Using the H1 command, the hysteresis on the setpoint value is set by the numeric value and
the polarity of this numeric value defines whether the setpoint switches on or off when the
setpoint value is reached.
Example
When the weight is increasing between 0 kg and 21.00 kg the setpoint is “ON”. Once the
weight increases above 21.00 kg then the logic output is “OFF”. The setpoint will come “ON”
again when the weight value drops below 20.00 kg.
When the weight is increasing between 0 kg and 19.99 kg the setpoint is “OFF”. Once the
weight increases above 19.99 kg then the setpoint is “ON”. The setpoint will switch “OFF”
again when the weight value drops below 19.00 kg.
Similarly to read or set the setpoint 1 hysteresis, use H2 instead of H1 etc. (2700sub02)
The A1 command defines the base on which the setpoint value acts. If A1 is set to “0”
then setpoint 1 acts on the unfiltered gross weight. If A1 is set to “1” then setpoint 1 acts on
the unfiltered net weight.
Similarly to read or set the setpoint 1 base, use A2 instead of A1 etc. (2800sub02)
The PC6D transmits one TPDO2 every time a setpoint changes state. The weight sent in the
TPDO2 is the weight that caused the TPDO2 to be transmitted, Net or Gross as selected for
the actual setpoint. The TPDO2 also holds the Weighing status flags and the setpoint
Number.
If two (or more) setpoint have exactly the same settings the setpoint with the higher number
will be “hidden”.
NOTE: All changes to the setpoint settings have to be stored in EEPROM using the SS
command. See section 5.10.
NOTE: These settings will only take effect after a power on reset (remember to store the
settings using the WP command [2004sub03] before turning the power off.)
It is possible to set the network address of the device using the AD command. (Address
range between 1 and 126).
Note: Setting the device address to 0 or 127 are not allowed. Address 0 is used by the
Network Management Protocol (NMT).
Request
Set the delay between falling/rising edge of trigger pulse and start of measurement.
Permitted values are 0 … 65535 ms.
Set the time over which the average value will be built.
Permitted values are 0 …65535 ms.
Factory default: 0
Issuing the GA command the PC6D returns the latest average weight value by using the MT
setup. On PC6D it is not necessary to ask for this. The average result is sent in a TPDO2
when ready, or re-triggered.
Note: During the time between the trigger condition being accepted and the average
value being updated, the GA command will return the value 99999 when it has been
triggered or 88888 when it has been retriggered or 99996 when the system tried to
change Tare or Zero before end of measurement.
[ Remark: When started this function, the latest average weight is availabe in TPDO2. ]
Set the trigger level for rising edge start of measurement. Permitted values are in the
range 0…262143.
With regard to the trigger commands SD and MT, a check weighing will automatically start
when the weight overshoots by e.g. 1.000d (increments), e.g. 100,0 g.
Issuing the TE command selects rising or falling edge trigger. Parameter = 0 select falling
edge and parameter = 1 select rising edge.
TR Trigger RPDO2 [ 00 80 ]
[This command will start the measuring cycle in the same way as the hardware trigger
input.]
Note: This function can be used as a soft trigger in a check weigher application (firmware
102.183).
DX : 1 (full duplex)
UR : 0 (max. 600 meas./s)
TL : 65535 (off)
RT : 65535 (off)
TW t
Tare
Window
TI SD MT
Tare Interval Start Delay Measuring Time
Page 41
5.10 Trigger Special Commands– RW, TT, TS, DT, TW, TI, HT
Remark: These commands are only available in firmware 102.183.v.1.10.
Note: All setups should be stored with the WP command before power off.
Set the Tare Window in in counts (digits) without decimal point. Tare window (TW) allows an
automatic Tare update. If TW = 0 this function is not active. If TW = 100, this means a new
tare value will be taken when the net average weight of an empty scale is within 100 counts
or division of zero. The new average tare value is calculated over the average tare time
defined by TI. If the tare average is outside tare window, the tare will not be updated.
Permitted values are 0 …65535 counts.
Set the Tare Time in milliseconds [ms]. During the Tare Time a “tare-average” will be
calculated by the system. Permitted values are 0 …65535 ms.
Set the Hold Time in milliseconds [ms]. During the Hold Time the weight value must be over
setpoint that a digital output can be switched. This means that a short signal peak will not
lead to the switching of a digital output. Permitted values are 0 …65535 ms.
Calibration parameter: CZ, CG, DS, DP & ZT are saved by the CS command.
Setup parameters (other than setpoint): FL, FM, NR, NT, BR, AD, etc. are saved by the
WP command.
Note: Calibration parameters can only be saved if the TAC code is known and precedes the
CS command. See the CE and CS commands on page 27 / 29.
Both the setup parameters and the setpoint parameters are stored in EEPROM using the WP
and SS commands respectively.
With this command the settings of the “Filter” (FL, FM) , the “No-Motion” (NR, NT) and the
communication (AD, BR) will be saved in the EEPROM.
With this command the settings of the setpoints (Sn), the “setpoint hysteresis” (Hn) and the
“setpoint action” (An) will be saved in the EEPROM.
0
Product: Digital load cell
As manufacturer of the article we herewith assures that the article meets the requirements of
the European legislation covering technical instruments, the standard safety rules, other
safeguard regulations as well as the generally approved rules for technical safety,
environmental protection and electromagnetic compatibility. It is further assured that the
articles are in accordance with the supporting documents as supplied by the manufacturer.
To ensure this the necessary monitoring measures during production have been met.
We, the manufacturer, are under obligation to produce to relevant parties upon request
written supporting evidence or by other means i.e. factory visits, spot checks etc. that the
production requirements have been met.
Electronic articles have been manufactured and tested according to the following regulations:
Signature: