Chell MicroDAQ-Mk2 Instrucciones de funcionamiento

Chell Instruments Ltd

Folgate House

Folgate Road

North Walsham

Norfolk NR28 0AJ

ENGLAND

Tel: 01692 500555

Fax: 01692 500088

MicroDaq-Mk2

Covering MicroDaq2,

FlightDaq2, CANdaq5 and

FlightDAQ-TL

USER PROGRAMMING

GUIDE

e-mail:- info@chell.co.uk

Visit the Chell website at:

http://www.chell.co.uk

900204-1.7

Please read this manual carefully before using the instrument.

Use of this equipment in a manner not specified in this

manual may impair the user’s protection.

Chell Document No. 900204 : Issue 1.7

ECO: 3802 Date: 16th June 2020

Chell’s policy of continuously updating and improving products means that this manual may contain minor

1. Introduction. .......................................................................................................................... 1

2. User Command Protocol. ....................................................................................................... 2

2.1. Command Packet.......................................................................................................................... 2

2.2. Acknowledgement........................................................................................................................ 2

2.3. User Commands. .......................................................................................................................... 2

3. Status Data Format. .............................................................................................................. 6

3.1. MicroDaq & FlightDaq .................................................................................................................. 6

3.2. FlightDaq-TL ................................................................................................................................. 6

4. Communication Channels. ..................................................................................................... 7

4.1. TCP ............................................................................................................................................... 7

4.1.1 Overview. .................................................................................................................................................... 7

4.1.2 Connection. ................................................................................................................................................. 7

4.1.3 TCP Protocol. ............................................................................................................................................... 7

4.1.4 TCP Data Rate. ........................................................................................................................................... 10

4.1.5 Control Via TCP. ......................................................................................................................................... 10

4.2. UDP ............................................................................................................................................ 11

4.2.1 Overview ................................................................................................................................................... 11

4.2.2 Connection ................................................................................................................................................ 11

4.2.3 Chell UDP Protocol ..................................................................................................................................... 11

4.2.4 UDP Data Rate. .......................................................................................................................................... 13

4.2.5 Control Via UDP. ........................................................................................................................................ 13

4.3. Timestamping ............................................................................................................................. 14

4.4. IENA specification ....................................................................................................................... 14

4.5. CAN ............................................................................................................................................ 16

4.5.1 Overview ................................................................................................................................................... 16

4.5.2 CAN Baudrate ............................................................................................................................................ 16

4.5.3 CAN Protocol ............................................................................................................................................. 16

4.5.4 CAN Data Rate ........................................................................................................................................... 18

4.5.5 Control Via CAN ......................................................................................................................................... 18

4.6. Internal RAM .............................................................................................................................. 19

4.6.1 Overview ................................................................................................................................................... 19

4.6.2 Internal RAM Protocol ................................................................................................................................ 19

4.6.3 Internal RAM Data Rate ............................................................................................................................. 19

4.6.4 Internal RAM Dump ................................................................................................................................... 19

5. Valve Control user commands ................................................................................................... 21

Page 1

1. Introduction.

This manual covers the microDAQ (Mk2), flightDAQ (Mk2) and flightDAQ-TL products. The communication

protocol is common across all ranges although not all options are available for all products.

The manual specifically refers to the microDAQ product although this applies to all the products listed above.

From power up, the microDAQ reads its non volatile setup information and calibration, and after applying

these settings is then ‘up and running’, reading the scanner/transducers and delivering calibrated data.

Although for many applications this is enough, more demanding applications may need to control the data

delivery, request data rezero operations and more.

The microDAQ-Mk2 has the same user interface protocol taken from the microDAQ system, allowing remote

access to the essential commands required when integrating the unit into an instrumentation system.

Commands may be sent over any of the unit’s communication channels, whether the current active data

channel or not. A simple block parity check adds security to the command protocol, and a correctly received

command may be acknowledged if required.

The following sets out the essentials of the command protocol, the data packet format for all channels in

addition to the message identifier arrangement for the CAN channel.

This document also details the user commands for valve controls that are found in the flightDAQ and the

microQDVP module which use the same command protocol.

This document version supports V2.0.4 of the microDAQ-Mk2 firmware, V2.0.10 of the flightDAQ firmware

and V1.0.0 of the flightDAQ-TL firmware. If using earlier firmware then some user commands and/or

parameters may be invalid.

Page 2

2. User Command Protocol.

2.1. Command Packet.

The command protocol is based around a simple delimited control packet, allowing easy identification of

command start and end. The packet includes a block parity byte increasing the robustness of transmission;

the packet format is shown in Figure 2.1.

> (ASCII 62)

Command

Parameter

Parity

< (ASCII 60)

Figure 2.1 Command Frame Format.

The command byte values are defined in the following section, and may or may not require a parameter byte,

for example data rate. The parity byte is an even block parity of all bytes (other than itself), including the

delimiters. Calculation for parity bit n is therefore the sum of each bit n using modulo 2 arithmetic.

For a command not requiring a parameter, an arbitrary dummy byte should be used. This can be any value as

the number is not processed other than in determining the parity of the command packet.

2.2. Acknowledgement.

A command packet is positively acknowledged if it is correctly formatted and the parity byte is correct. A

positive acknowledgement is denoted by the transmission of ASCII 42 ('*'), a negative acknowledge indicating

an invalid command by ASCII 33 ('!'). Recognised command values are then acted upon, though unrecognised

values are discarded.

2.3. User Commands.

The available user command set is summarised in Figure 2.2.

Command (*

DTC only)

Byte,

Char/

ASCII

Parameter

Description

Standby

S/83

None

Set all data streaming off.

Reset

R/82

None

Request a soft device reset - microDAQ is reinitialised.

Rezero

Z/90

0: All channels

1 to 32: rezero specified

channel

Request a rezero.

Channel parameter is only supported on the flightDAQ-TL models,

where no parameter is specified a ‘0’ is implemented.

Derange *

D/68

None

Calibration is rebuilt with the appropriate deranging factor applied, the

DTC scanner deranging gain is switched into circuit. This command is

not valid for flightDAQ-TL.

Rebuild

Calibration

C/67

None

The calibration is rebuilt for the current temperature, using the active

microDAQ settings. This command is not valid for flightDAQ-TL.

Rezero and

Rebuild

G/71

None

Requests a rezero followed by a calibration table rebuild, with the

calculated zero offsets being applied to the calibration data.. Note

these rezero offsets are separate from any normal rezero that may be

performed afterwards. This command is not valid for flightDAQ-TL.

Page 3

Rate

V/86

byte = 0xab

a = 1 TCP / UDP

a = 2 CAN

a = 3 Internal RAM

For TCP / UDP:

b = 0 : Off

b = 1 : 1000Hz

b = 2 : 625Hz

b = 3 : 500 Hz

b = 4 : 400 Hz

b = 5 : 312 Hz

b = 6 : 225 Hz

b = 7 : 200 Hz

b = 8 : 150 Hz

b = 9 : 100 Hz

b = 10 : 50 Hz

b = 11 : 25 Hz

b = 12 : 20 Hz

b = 13 : 10 Hz

b = 14 : 5 Hz

b = 15 : 1 Hz

For CAN & Internal

RAM:

b = 0 : Off

b = 1 : 1000 Hz

b = 2 : 750 Hz

b = 3 : 625 Hz

b = 4 : 500 Hz

b = 5 : 312 Hz

b = 6 : 100 Hz

b = 7 : 50 Hz

b = 8 : 25 Hz

b = 9 : 10 Hz

b = 10 : 5 Hz

b = 11 : 2 Hz

b = 12 : 1 Hz

flightDAQ-TL TCP/UDP

b = 0 : Off

b = 1 : n/a (250Hz)

b = 2 : n/a (250Hz)

b = 3 : n/a (250Hz)

b = 4 : n/a (250Hz)

b = 5 : 250 Hz

b = 6 : 200 Hz

b = 7 : 150 Hz

b = 8 : 100 Hz

b = 9 : 50 Hz

b = 10 : 33 Hz

b = 11 : 25 Hz

b = 12 : 20 Hz

b = 13 : 10 Hz

b = 14 : 5 Hz

b = 15 : 1 Hz

Adjust the data delivery rate for each communication channel. The

upper nibble of the parameter byte selects which communication

channel, while the lower selects its data rate.

CAN & Internal RAM ‘comms’ have the same available data rates. CAN

& RAM commands are not supported on flightDAQ-TL

Protocol

P/80

byte = 0xab

a = 1: TCP / UDP

a = 2 :CAN

Permits the changing of the data protocol. The abbreviations LE and BE

in the table refer to little and big endian respectively, denoting whether

the less significant byte is sent first or last.

Page 4

b = 0 : 16 bit LE

b = 1 : 16 bit BE

b = 2 : Engineering

Units

b = 3 : 32 bit LE

b = 4 : 32 bit BE

Pressure data is available in engineering units over UDP, TCP and RS232

connections, though only binary data is available with CAN and Internal

RAM.

flightDAQ-TL only supports TCP and UDP.

Binary data provides pressure scaled as unsigned integers to the

operating full scale, eg for 16 bit resolution, 0 to 65535 represents -FSD

to +FSD.

Stream ON

1/49

1 – TCP / UDP

2 - CAN

3 - Internal RAM

4 - Internal RAM (stop

on full)

Enable the data delivery for the chosen channel. The delivery rate is as

selected in microDAQ Setup, unless it is modified via the Rate

command.

Internal RAM data streaming will either log continuously, wrapping

when the end of available RAM is reached, or will stop when the RAM

is full, depending on parameter.

flightDAQ-TL only supports TCP and UDP

Stream OFF

0/48

1 - TCP / UDP

2 - CAN

3 - Internal RAM

Disable the data delivery for the chosen channel.

flightDAQ-TL only supports TCP and UDP

Get Status

?/63

0 : Short

1 : With temp.

2 : Full

3 : Pressure reading

4 : Temp. readings

5 : Excitation reading

6 : Hall sensor read

7 : Firmware ID

8 : Unit serial number

9 : Scanner serial

number

For flightDAQ-TL

0 : Short

1 : Internal pressure

and temperature

2 : Full

3 : undefined

4 : undefined

5 : Excitation reading

6 : Sensor type

7 : Firmware ID

8 : Unit serial number

9 : Connector serial

numbers

Return a status packet from the microDAQ. Three main versions are

available, 'short', 'with temp.' and 'full'. Short returns status byte

information showing current operating state only, whereas 'full' returns

microDAQ setup options and temperature data in addition. 'With

temp.' returns the status and temperature information intended for

continuous temperature monitoring applications. The data format is

documented in a separate section.

Additional readings poll raw values for temperature and pressure as

read from the scanner, as well as other fields as indicated in the table

The flightDAQ-TL responds in a different manner to the microDAQ and

flightDAQ.

Channels

H/72

byte = 0xab

a = 1 TCP / UDP

a = 2 CAN

a = 3 Internal RAM

b = 0 - 16

b = 1 - 32

b = 2 - 48

b = 3 - 64

Set the number of active channels returned to the user for a data

channel. Setting a value greater than the current system maximum

channels (set via setup/dtc scanner read or by the Maximum Channels

command) results in the maximum channels value being used.

For flightDAQ-TL channels 1-16 are primary channels, 17-32 are

secondary channels.

flightDAQ-TL does not support CAN or RAM

Maximum

Channels

M/77

0 - 16

1 - 32

2 - 64

Set the system maximum channels, ie the number of channels read

from the scanner. Allows the dynamic alteration of the effective per

channel sampling rate. This command is not valid for flightDAQ-TL

Page 5

Poll

O/79

1 - TCP / UDP

2 – CAN

Request a single data packet (in the current active format) for the

channel selected. Data streaming should be set off before using this

command. Note that there is no positive acknowledge for this

command. This command is not valid for logging to Internal RAM. CAN

is not supported on flightDAQ-TL

Span

A/65

None

Request a ‘span’ operation. The unit should have been recently

rezeroed, then the appropriate span pressure (as selected from the

setup software) applied to the scanner. Requesting a span operation

will then calculate the span correction coefficient for each channel. All

rezero values and span coefficients are then written to the unit’s

EEPROM (NOT to the scanner), and the calibration tables rebuilt using

these new values.

Reset Linear

Calibration

E/69

None

Resets the linear calibration (ie zero and span values) held within the

unit to 0 and 1.0 respectively for all channels. A calibration table rebuild

is then performed.

Hardware

Trigger

T/84

byte = 0xab

a = 0 Disable

a = 1 Enable

b = 1 TCP / UDP

b = 2 CAN

b = 3 Internal RAM

b = 4 Internal RAM

(stop on full)

Enables or disables the hardware trigger on the selected channel. Note

that there is no positive acknowledge for this command.

Assuming a valid hardware trigger is detected for the duration, Internal

RAM data streaming will either log continuously, wrapping (and

therefore overwriting) when the end of available RAM is reached, or

will stop when the RAM is full (and automatically disable the hardware

trigger), depending on the parameter.

flightDAQ-TL does not support hardware trigger.

Start Internal

RAM Dump

I/73

1 - TCP / UDP

2 - CAN

Starts the internal RAM dump, sending data using the comms channel

chosen by the parameter. The first packet is sent immediately and

consists of a 9 byte header (only 6 bytes for CAN - see later). This

command is not valid for flightDAQ-TL

Internal RAM

Dump

Handshake

J/74

None

Handshake command to indicate previous packet was received. Must

be sent after header packet & all subsequent data packets. This

command is not valid for flightDAQ-TL

Figure 2.2, The Available User Command Set for the microDAQ.

Page 6

3. Status Data Format.

3.1. MicroDaq & FlightDaq

Status data is not currently supported over the CAN channel, however for TCP connections, status data may

be requested from the microDAQ as three forms – ‘short’, ‘full’ and ‘with temp’. The short form returns 4

bytes, the 16 bit status word delimited by the ASCII characters ">" and "<", the less significant byte is returned

before the more significant. The bit assignment is shown in figure 3.1.

I-daq

conn.

Hardware

Trigger

Active

Derange

acvtive

DTC

conn.

CAN

Active

TCP

Active

Reserv

Cal.

table

Span

Rezero

Figure 3.1, Status word bit assignment.

Requesting the status 'with temp.' returns the short status 4 bytes, followed by the temperature data. For a

non DTC scanner, a single value (ASCII unsigned 14 bit) representing the read temperature voltage is appended

to the status bytes. For a DTC application, all active channels are returned in ascending order as comma

delimited ASCII engineering units (ie degrees C).

The 'full' status data contains the above, followed by fields for the setup options of the microDAQ. Each field

is comma delimited, and its function is indicated in plain text between square parentheses. On/off is indicated

by 1/0. An example 'full' status string is shown in figure 3.2 for a microDAQ with a non DTC scanner. Note that

the figure for full scale includes the derange constant (ie scanner full scale x derange constant) if the derange

option has been selected in setup.

Figure 3.2, Full status information.

3.2. FlightDaq-TL

Status data is currently not defined . .

*>Mó<8198,[Full scale] 15.00000000,[Active channels] 32,[DTC active] 0,[CAN

channels] 32,[TCP channels] 32,[CAN rate] OFF,[TCP rate] OFF,[CAN protocol] 16 LE,[TCP

protocol] 16 LE,[Press. input impulse] 1,[Temp. input impulse] 0,[Press. input power]

3,[Temp. input power] 0,[Press. output power] 0,[Reset on delivery] 0,[Temp.

compensation] 0,[Period] 10m,[IP] 0.0.0.0,[Mask] 0.0.0.0,[Gateway] 0.0.0.0,[CAN

timing] (BRP) 5 (TSEG1) 2 (TSEG2) 0 (SJW) 1,[CAN message] 00n,[Rezero order] 4,

Page 7

4. Communication Channels.

4.1. TCP

4.1.1 Overview.

The microDAQ’s TCP channel affords it the ability to stream real time data at high speed over standard 100Mbit

Ethernet connections.

4.1.2 Connection.

When using the TCP/IP channel, the microDAQ is programmed to listen on its local port number 101. It will

respond to a connection request, connect and immediately start streaming data if it has been setup to use the

TCP channel. Note that the microDAQ only supports one TCP connection.

Setup requires the microDAQ to be given an IP address, and the network’s subnet mask. It is possible either

to run the microDAQ over a local Ethernet connection, or directly from a PC’s network card, as long as a

crossover cable is used. A dual network card (or 2 cards) may be used, however care should be taken about

network routing, as similar subnets for two network connections on a single Windows ® machine can cause

the microDAQ not to be seen on the second card. The microDAQ will respond to a ‘ping’ instruction for the

purposes of setup and troubleshooting.

4.1.3 TCP Protocol.

With TCP channel selected calibrated pressure data are streamed continuously over the TCP interface.

Depending on the device variant, TCP supports a range of different data formats as shown in Figure 4.1. The

binary data formats scale the data to 0 to 65535 bits which represent either -/+ full scale respectively (IEEE

754 representation for 32 bit). Binary protocols require less communications bandwidth as well as less

processor overhead within the microDAQ; it is recommended that engineering unit conversions be applied at

the client. Note that the flightDAQ-Mk2 can be configured to stream absolute or differential pressure channel

data. When configured for absolute pressure, the binary representation is 0 bits = approx. 2 psi (15000Pa) &

65535 bits = approx. (scanner full scale value + 15psi). E.g. for a 15psi scanner, 65535 bits = 30psi (or more

precisely 207000Pa). Note: The current firmware release (V2.0.10) currently supports absolute representation

for 2psi, 8psi and 15psi fullscales only – more will follow in future firmware releases.

In the case of the TCP channel, the engineering unit protocol should be avoided if possible, due to the need to

declock the microDAQ’s internal clock and scanner addressing to half of the chosen acquisition rate (due to

internal issues regarding string handling). The 16 bit little ended protocol is most efficient from the

microDAQ’s viewpoint, the data being calibrated and spanned to 0 to 65535 (zero at 32767). Scaling to floating

point full scale is better achieved within a PC client application where there is more processing power

available.

16bit, little endian (microDAQ-Mk2)

Header

Channel1 Data

Channel 2 Data

Channel 3 Data

0x00

0xFF

0x00

LSB

MSB

LSB

MSB

LSB

MSB

….

Channel ’N’ Data

LSB

MSB

3 byte header identifies the start of the packet, followed by all channels (1 to ‘N’ where ‘N’ = 16, 32 or

64 depending on setting), LSB first, with no delimiters.

Otros manuales para microDAQ-Mk2

Este manual sirve para los siguientes modelos

Tabla de contenidos

Otros manuales de Escáner de Chell

Chell

Chell microQDVP Manual de usuario

Chell

Chell FlightDaq-TL Manual de usuario

Chell

Chell microDAQ Instrucciones de funcionamiento

Chell

Chell Q-Daq Manual de usuario

Chell

Chell microDAQ-Mk2 Manual de usuario

Chell

Chell flightDAQ-Mk2 Manual de usuario

Chell

Chell MicroDAQ3 Manual de usuario

Manuales populares de Escáner de otras marcas

Plustek

Plustek Scanner Manual de usuario

Z/I Imaging

Z/I Imaging PhotoScan 2001 Manual de usuario

Renkforce

Renkforce DS100-5M Manual de usuario

Image Access

Image Access WideTEK A2 Manual de usuario

Canon

Canon imageFORMULA CR-120N Manual de usuario

Fujitsu

Fujitsu FI-4860C2 Manual de usuario

GeoSlam

GeoSlam ZEB Horizon Instrucciones de instalación

Kodak

Kodak i5800 Scanner Manual de usuario

Kodak

Kodak i7300 Manual de usuario

Revopoint

Revopoint POP Manual de usuario

Fujitsu

Fujitsu fi-4860C Manual de usuario

Eddyfi Technologies

Eddyfi Technologies Floormap X Manual de usuario

Faselase

Faselase F6 Manual de usuario

Fujitsu

Fujitsu CardMinder Manual de usuario

Uniden

Uniden BC340CRS Manual de usuario

Infinite Peripherals

Infinite Peripherals INFINEA TAB M Manual de usuario

Mustek

Mustek PageExpress 4800 Pro Manual de usuario

Optex

Optex 750830 Manual de usuario

Chell microDAQ-Mk2 Instrucciones de funcionamiento

Manuales populares de Escáner de otras marcas