Nokeval FTR970-PRO User manual

User manual
18.02.2008
V 1.06
FTR970-PRO
RADIO RECEIVER WITH LOGGER
Nokeval

RS-485 or RS-232
PromoLog
2
FTR970-PRO is radio data receiver with data logging used with Nokeval MTR and FTR series radio
transmitters. Device can receive, unpack and buffer data packets into its memory from transmit-
ters. It identifies automatically type of a transmitter, so it can be used simultaneously with different
transmitters and with different transmit periods. FTR970-PRO uses license free frequency range of
433.92 MHz, so it can be used freely in areas where this so called ISM-frequency range is allowed,
covering almost whole of Europe.
Receiver can be connected to computer using either RS-485 or RS-232 bus and it needs an appli-
cation program (PromoLog), which fetches processed data from the receiver’s memory.
Nokeval SCL or Modbus RTU protocols are used for data transfer. When RS-485 is used there can
be several FTR970-PRO devices on the bus and they can be positioned to cover larger receive area.
Receiver has four diagnostics leds and it needs operating voltage between 8..28 VDC.
Manufacturer
Nokeval Oy Tel [phone]
Yrittäjäkatu 12 Fax [phone]
FI-37100 www.nokeval.com
Finland Sales: [email protected]
Technical support: [email protected]
Contents
General....................................................................................................................................... 2
Installing ..................................................................................................................................... 3
Settings ...................................................................................................................................... 8
Use with PromoLog .................................................................................................................... 11
Channels .................................................................................................................................... 17
Realtime data buffer ................................................................................................................... 20
Flash........................................................................................................................................... 23
SCL protocol............................................................................................................................... 27
Modbus protocol......................................................................................................................... 28
Nopsa language ......................................................................................................................... 31
Applications ................................................................................................................................ 36
Technical data ............................................................................................................................ 37
GENERAL

1 2 3 4
+
-
+ - D1 D09V
RS RF
USB
5 6 7
- RxD TxD
Power LED
J11
J7
Installation method
Best coverage is achieved when receiver has line of sight to the transmitters. Every obstacle be-
tween the devices will attenuate the signal and thus decrease range. On the other hand metal planes
will cause reflections which can in some cases increase the range.
3
INSTALLING
Device can be connected using either RS-485 or RS-232 buses. Each
of these is described in its own subchapter. Power supply connections
are also described separately in each subchapter.
USB bus can be used in case that the standard cable gland is replaced
by large one (not delivered). If it’s desirable to use either RS-485 or
RS-232 buses the device must be jumpered accordingly.
Connections
Power
The supply voltage 8...28 VDC is connected using 1.3 mm DC jack (centre connector positive) or
by using detachable screw post connector terminals 1 (+) and 2 (-). Both supply voltage connec-
tors are internally connected. The receiver is protected against wrong polarity of the supply volta-
ge. The supply voltage’s negative terminal is also used as ground for RS-485 and RS-232.
RS-485
When used with RS-485 bus jumper J11 has to be set according to following picture.
Device needs 8...28 VDC power supply which is connected either with 1.3mm DC-jack, with
positive center pole, or with terminal connections 1 (+) and 2 (-). DC-jack and terminal con-
nector is connected in parallel. Device is protected against wrong polarity of power supply.
RS-485 can be easily added to computer using Nokeval DCS770 or DCS771 USB – RS-485 con-
verter or RCS770 USB/RS-232 – RS-485 converter. RS-485 is connected to terminal connections 3
(D1), 4 (D0) and 2 (Gnd). Wrong connection of polarity doesn’t harm the device.
Antenna connection
Antenna is connected to device’s BNC connector. Antenna is first pushed into the BNC connector
by aligning it with two guide posts after which it is turned 90 degrees clockwise.
RS485
RS232
Power supply
8...28 VDC

4
Termination
Off
On
2-wire-485
Yes
No
Settings for jumper J7
If RS-485 bus master has ground connection available, then jumper called ”2-wire-485” has to be in
position ”No”. If master lacks the connection, then potential equalization has to be done via D1- data
line by putting the jumper to position ”Yes”.
Last device on bus should have termination jumper on. It makes AC-termination for the line, which
means that there is 1nF capacitance and 110 ohm resistance in series between the lines.
Maximum length for the bus is 1km, and it allows 32 devices, more devices can be connected by
using repeaters.
RS-232
When used with RS-232 bus jumper J11 has to be set according to following picture. Jumper J7 has
no effect when RS-232 is used.
Device needs 8...28VDC power supply which is connected either with 1.3mm DC-jack, with
positive center pole, or with terminal connections 1 (+) and 2 (-). DC-jack and terminal con-
nector is connected in parallel. Device is protected against wrong polarity of power supply.
RS-232 bus is not recommended because it is easily disturbed by EMC and maximum cable length
is only 15m in good conditions. RS-485 is recommended for longer ranges.
USB
USB bus can be used if the standard cable gland in the enclosure is replaced by larger one (not
delivered) or circuit board is installed into a customer’s enclosure.
When used with USB-bus jumper J11 has to be set according to following picture. Jumper J7 has
no effect when USB is used.
Device is powered from USB, but if the device should function when computer is turned off then exter-
nal power supply is required. Device needs 8...28 VDC power supply which is connected either with
1.3mm DC-jack, with positive center pole, or with terminal connections 1 (+) and 2 (-). DC-jack and
terminal connector is connected in parallel. Device is protected against wrong polarity of power supply.

PRO Radio Memory Error
J11
J7
1 2 3 4
+
-
+ - D1 D09V
RS RF
USB
5 6 7
- RxD TxD
Power LED
5
Indicator lights
Indicator lights
PRO: Means that device is operating.
RADIO: Means that device is processing serial communi-
cation command.
MEMORY: Means that device is writing data to flash mem-
ory.
ERROR: When power is applied to the device first time er-
ror is light almost certainly, since the real time clock is out
of time in device. This error disappears when new time is
set to clock either automatically with PromoLog or manu-
ally with MekuWin. Note! In case that flash logging is dis-
abled the time loss of real time clock does not lit error led.
Other than above this normally means that there is some
error. Meku monitor will give more descriptive error infor-
mation. Possible error causes are: flash memory broken,
radio coprocessor not responding, real time clock circuit
not responding or real time clock time has been lost, or
EEPROM memory has been cleared.
If the error is caused by EEPROM memory, then error goes
off when new settings are saved to EEPROM.
If reason is that real time clock has lost time, error is con-
tinuously on, until new time is set to device.
All other errors will be automatically cleared if the reason
for error disappears, but if error light is on continuously
and cause of error is not some of the above mentioned
then the device must be sent for service.
Side indicator lights
RS: Informs about internal communication of device. This
should blink constantly.
RF: Informs about received radio packets. This light should
blink randomly depending on the number of radio transmit-
ters within range.
Behind: Power led is positioned behind the two lights, and
it lights if the device is powered. This light is visible when
viewed directly from the front.

6
Installing drivers when using USB
USB interface circuit needs two drivers for PC. First of them opens communication for the USB and
the other generates virtual serial port.
When PromoLog is installed on the computer it also installs these drivers automatically, but if
PromoLog is not installed then you can follow instructions below to install the drivers.
Drivers can be installed either from Nokeval Software CD or latest drivers can be downloaded di-
rectly from the web site of interface circuit manufacturer www.ftdichip.com (Drivers, FT232BM). This
install guide describes the installation from the CD, but it mostly applies with downloaded drivers
too.
Insert Nokeval Software CD in the CD drive and plug the device to the PC. Windows should auto-
matically notice the device and start the installation.
Installation for windows 2000 Installation for windows XP
First you get prompt to search for the drivers
from windows updata, if you have internet
connection available selet “Yes this time only”
and drivers will be installed automatically. Do
this for both drivers.
If you dont have internet connection available
do the following.

7
After USB bus driver ftdibus.inf has been in-
stalled, Windows will begin installation of virtual
port driver, which enables FTR970-PRO to look
like regular serial port, for example COM3.
Finally one must figure out on which COM-port
the device was attached. Open Control Panel/
Hardware/Device Manager. Open ports from the
device tree, and there should be USB Serial Port
in some of the COM ports.
Repeat this procedure for other driver (usb
serial port). And finally check from device
manager in which com port device was
detached.

Realtime
Channels
Other periodic
Sporadic
Unknown
Logger
Channels
Other periodic
Sporadic
Unknown
Channel
interval [s]
Flash erase
Clock Clock
Run
Year
Month
Day
Hour
Min
Sec
Ch1
ID
Type
Linearization
Alarm Group
Reading
Battery
Signal
Age [min]
Serial
Mode
Baud
Bits
Address
Conf
Serial
Channels
Logger
Realtime
Channels
Timeout [min]
Count
Ch1
Ch2
Ch3
Ch4
Ch5
Ch6
Ch7
Ch8
Ch9
Ch10
...
Ch90
8
SETTINGS
Communication settings
Settings for the device are done with PC using Mekuwin configuration software. Mekuwin has its
own instruction manual.
Default settings for serial communication are:
• baud rate 115200
• protocol SCL
• bits 8N1
• address 0
Men

Serial
Mode
Baud
Bits
Address
Jumper for
clearing settings
9
Serial submenu
Mode
Setting for serial mode.
• SCL slave: Nokeval SCL protocol
• Modbus slave: Modbus RTU protocol
Baud
Setting for baud rate.
• 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, 230400
Bits
Setting for bits.
• 7E1, 8N1, 8E1, 8O1, 8N2
Note! SCL protocol always uses 8N1 and Modbus RTU uses commonly 8E1.
Address
Setting for serial address.
Allowed SCL addresses are 0..123. Allowed Modbus RTU addresses are 1..247.
Resetting serial communication settings
In case serial settings are for some reason not known, they can be reset by setting jumper in the
position indicated by the following picture when the device is powered up.
Settings will be cleared as follows:
• baud rate 115200
• protocol SCL
• bits 8N1
• address 0

10
Meku monitor shows, how long the device has
been powered on, how many radio packets has
been received, and shows the mean latency for
serial communication.
Also 10 most recently received radio packets are
shown, which helps configuration and trouble-
shooting. Monitor shows device ID, type, signal
strength and also how long time since reception.
Asterisk before line indicates the most recent
packet.
Signal strength -100dBm is just above noise and
about -65dBm is the maximum signal strength.
At the bottom there are ”Error” lights, which indi-
cate where exactly there is error in device if any.
If any of these are lit, then also the front panel
error light is lit.
In all error conditions it is advisable to reboot the
device and check if the error condition persists.
Error lights
Meku Monitor
Error FLASH: Indicates that flash memory circuitry is malfunctioning. If the error won’t go off
then the device must be sent for service.
Error EEPROM: Indicates that device settings have been cleared, because of an error. Make
new settings and press ”Save to EEPROM”, which clears the error.
Error Radio: Indicates that radio coprocessor is malfunctioning. If the error won’t go off then
the device must be sent for service.
Error Clock: Indicates that real time clock circuitry is unreachable or time has been lost. If
error don’t go off by setting new time to the device then the device must be sent
for service.
Flash and clock errors dont harm other functions of the device, if flash and packetbuffers are not
needed.

11
USE WITH PROMOLOG
Creating new serial interface
New serial connection can be created by choos-
ing ”1. Interfaces” from Design menu. This will
open communication interface setup dialog.
Click blue plus button from the dialog to create
new serial interface.
Write a name for the interface and set protocol
to correspond settings in the device. Device sup-
ports SCL and Modbus RTU protocols. After set-
tings are done press OK. Now there is a new
row in the previous window which represents the
newly created serial interface. Double click the
row to change the settings for the interface.
Transport layer can also be USB, if the device is
connected via USB to computer. In that case in
next phase choose the serial number of the de-
vice instead of the COM port.
Choose the correct COM port in the parameter
editor. Autoscan function scans all available COM
ports in the computer, which is helpful if you don’t
already know at which port the device is connect-
ed. If you’re using USB the COM port number
should be 3 or higher.
Set baud rate and data parity to correspond de-
vice settings. Factory setting for the device is
115200 baud.
PromoLog settings

12
Creating new radio receiver unit
Choose ”2. Inputs” from the Design menu. This
opens input module library.
Create new ”Nokeval Radio Data Receiver”
module by dragging it on the active sheet. You
can also press the blue plus button or double
click the module name.
Double click the module on sheet to open pa-
rameter editor for it.
Choose recently created serial interface to Inter-
face item. Check also from under Interface that
serial address corresponds device settings. You
can close the window.

13
Module list button
Stop button
Module usage
Nokeval Radio Data Receiver module doesn’t
need any other than serial settings, which were
just made.
Nokeval Data Receiver module is split in two
sections. Upper section consists of status in-
formation of serial interface and receiver unit.
Lower section shows most recently received
data packets.
PromoLog gets new information from device only
when application is in running state.
Explanations for lower section columns:
Column Description
Age Time from receive
Device Type of the device
ID ID number of the device
Signal Received signal strength
Battery Battery voltage of the device
Adding new transmitter on screen
Press start button and module list button to start
the application and to open the module list win-
dow.
When application is running Nokeval Radio Data
Receiver module automatically adds all detected
transmitters on the list.
Some of the settings are disabled when appli-
cation is running, therefore its recommended
that when all the transmitters are on the list, the
application is stopped before application building
is continued.
Device type and
serial number
Interface name
and state
Response from
the device
Device
state
Start button

14
Transmitters can be added on a sheet by drag-
ging them, clicking blue plus button or double
clicking them.
See PromoLog user manual for more information
about data manipulation and representation.

15
Quick setting guide for device
FTR970-PRO supports two different methods for saving normal periodic transmitter data packets to
its flash memory: every packet separately or interval logging. Default setting is every packet sepa-
rately.
Every packet separately
If it’s ok to save all radio packets to flash memory, then the device works with PromoLog with de-
fault settings. Drawback of this approach is that every radio packet uses up flash memory and thus
memory will fill up faster and oldest records gets overwritten.
Memory fill rate can be approximated using formula 150000*I/N, where I is transmit period and N is
the number of transmitters. For example, if there are 10 devices in range, which all transmit once in
every 60 seconds: memory fill rate is 150000*60/10 = 900000s = 10 days. If this is not enough then
transmit period can be set longer or the receiver changed to interval logging mode.
Device works this way with factory settings. Device can be set back in this mode using Mekuwin by
setting “Channel Interval “ to 0 from Logger submenu and setting “Channels”, “Other periodic” and
“Sporadic” settings on.
Interval logging
Interval logging means that at certain period device will save user selected transmitters to flash
memory as one record. Logging interval is freely selectable and thus it affects the memory fill rate.
Selected transmitters are chosen to be channels under channels submenu by using MekuWin pro-
gram. Number of transmitters is entered to “Count” setting. ID number for the first device is entered
to ID setting under Ch1 submenu. If the transmitter is of type MTR262, MTR264 or MTR265 and the
sensor is thermocouple, then the type of the element has to be entered in “Linearization” setting.
Otherwise the setting is left as None.
Channels setting is selected from the Logger submenu (so that chosen channels go to flash memo-
ry), and “Channel Interval” setting is set to chosen logging period in seconds, with maximum being
65535 seconds.
Suitable logging period can be approximated by using formula T*(7+6*N)/2000000, where T is want-
ed fill rate in days and N is the number of channels. For example, 10 transmitter are going to be
logged for 30 days: Channel Interval=30*(7+6*10)/2000000 = 0.001 days = 87 seconds.

16
End of basic user part of the manual.
Start of expert user part of the manual.

Ch1
ID
Type
Linearization
Reading
Battery
Signal
Age [min]
Channels
Timeout [min]
Count
Ch1
...
Ch90
17
Device processes data in 3 different ways, one of which is channels.
Device can handle 90 channels simultaneously. Channel is a real time data container, which con-
sists of one fully processed wireless transmitter. Some transmitter types can not be handled as
channels. Every transmitter whose measurement result can be expressed as a single numeric value
can be a channel.
Following devices can be channels:
MTR260, MTR262/FTR262, MTR264, MTR265, MTR165, FTR860 and CSR260.
Following devices can not be channels:
CSR264, KMR260
Channel contains all available information of a transmitter: Value, device type, ID, battery voltage,
signal strength and information how long has passed since last data reception. When configuring
device as a channel, only the device ID needs to be known, other information updates automatically.
However used thermocouple type must be configured when using devices which are configured to
measure with thermocouples.
Channels submenu
Timeout
Tells how many minutes have to pass since last
reception until it is determined that device is not
transmitting and its value is set to NaN (Not A Number).
For Ex. If Timeout = 10 min then channel value is
set to NaN when more than 10 minutes but
less than 11 minutes have passed since
last reception.
Count
Tells how many channels are used (0..90)
ID
Identification number of the transmitter (1..65535).
ID 0 means that channel is not in use.
Type (updated automatically)
Tells the type of the device. For ex. MTR260.
Linearization
Used thermocouple linearization, this setting is visible only if device in question can measure tem-
perature with thermocouples but cannot perform the necessary linearization by itself.
(MTR262/FTR262, MTR264, MTR265)
Possible thermocouple types are: B, C, D, E, G, J, K, L, N, R, S, T, or None in case thermocouple is
not used.
CHANNELS

18
Reading (updated automatically)
Channel reading
Battery (updated automatically)
Battery voltage of the device
Signal (updated automatically)
Received signal strength.
(About -100dBm = barely receivable, -65dBm = maximum strength)
Age (updated automatically)
Tells how many minutes has passed since last reception. Note! This value is updated once in a min-
ute for all channels simultaneously, which means that value can increment any time after 1-60s after
packet reception.
Serial commands
In case PromoLog is not used for reading data from the device, following commands can be used
to read data.
Following commands are usable for reading channel information. Different protocols are fully ex-
plained in their own chapters, here is a quick summary of each protocols available commands.
Nokeval SCL protocol
MEA CH Read channel reading
Modbus RTU protocol
03 (Read Holding Registers) Readings mixed with settings
04 (Read Input Registers) Read readings and other channel information either as float-
ing point or integer number.
Modbus register map in Modbus chapter.
Nokeval Nopsa commands (transport protocol SCL or Modbus RTU)
2/0 (Out value request) Read channel reading
2/1 (Out resource request) Read channel meta information (name, data type)
4/32 (Channel count) Channel count
4/33 (Changed channels) Bit field of changed channels after last read operation
4/34 (Read channels with index) Read all channel information of certain channel
4/35 (Read next channel) Read all channel information of next changed channel
Data structure
Data structure of Nopsa commands (4/34, 4/35).
ID 2 bytes, 16bit integer, least significant byte first.
Reading 4 bytes, IEEE floating point number.
Type 1 byte, integer. See following table for types.
Signal strength 1 byte, integer. Subtract 127 and result is in dBm.
Battery voltage 1 byte, integer. Divide with 10 and result is in Voltage.

19
Table for possible device types
Type Value
MTR260 0
MTR262/FTR262 2
MTR264 4
MTR265 5
MTR165 6
FTR860 7
CSR264S 8
CSR264L 9
CSR264A 10
CSR260 11
KMR260 12
Machine to machine communication
Channel information can be used so that some other device is used to read information and further
process it.
Nokeval 7470 serial transmitter can read maximum of 4 channels via serial communication using
Nokeval SCL protocol and then convert these into mA- or V-signals.
See chapter Applications

Realtime
Channels
Other periodic
Sporadic
Unknown
20
Device processes data in 3 different ways, one of which is real time data buffer. This data buffer is
completely independent of other functions of the device. Real time data buffer preserves most recent
radio packets until PC-program has time to read them.
Data buffer has room for 90 packets. Menu has a setting called “Realtime” which dictates which kind
of data is saved to this buffer.
Table how data is saved to the real time data buffer depending on device type and settings.
Channels Other periodic Sporadic Unknown
MTR260 Processed Processed
MTR262/FTR262 Processed Unprocessed
MTR264 Processed Unprocessed
MTR265 Processed Unprocessed
MTR165 Processed Processed
FTR860 Processed Processed
CSR260 Processed Processed
Unprocessed
KMR260 Unprocessed
X Unprocessed
Note! Cells in gray are not possible options.
Realtime submenu
Channels
Choose whether channels are saved in real time data buffer.
Channels are devices whose IDs have been configured in the channel
table in menu and are of type which can be used as channels.
See previous table.
Other Periodic
Choose whether devices, which could be channels but are not configured
in channel table in menu, are saved in real time data buffer.
Sporadic
Choose whether devices, which could not be channels, are saved in real time data buffer.
These devices are mostly kind of devices which send burst data when stimulated, and not periodi-
cally like the devices that can be classified as channels. For these purposes the FTR970-PRO has
also so called burst trap buffer, which removes multiple copies of burst data.
Unknown
Choose whether devices which are unknown (those devices which are designed after FTR970-PRO
software version) are saved in real time data buffer.
REALTIME DATA BUFFER