1. Manuals
  2. Brands
  3. Nokeval Manuals
  4. Receiver
  5. FTR970-PRO
  6. User manual

Nokeval FTR970-PRO User Manual

Radio receiver with logger
Hide thumbs
Table of Contents

Advertisement

Quick Links

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

Advertisement

Table of Contents
loading

Related Manuals for Nokeval FTR970-PRO

Summary of Contents for Nokeval FTR970-PRO

  • Page 1 User manual 18.02.2008 V 1.06 FTR970-PRO RADIO RECEIVER WITH LOGGER Nokeval...

  • Page 2: Table Of Contents

    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.

  • Page 3: Installing

    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...
  • Page 4 Termination 2-wire-485 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.
  • Page 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 fl ash mem- ory. ERROR: When power is applied to the device fi rst time er- ror is light almost certainly, since the real time clock is out of time in device.
  • Page 6 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.
  • Page 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 fi gure out on which COM-port Repeat this procedure for other driver (usb the device was attached.

  • Page 8: Settings

    SETTINGS Communication settings Settings for the device are done with PC using Mekuwin confi guration software. Mekuwin has its own instruction manual. Default settings for serial communication are: • baud rate 115200 • protocol • bits • address Serial Mode Baud Conf Bits...
  • Page 9 Serial submenu Mode Setting for serial mode. Serial Mode • SCL slave: Nokeval SCL protocol • Modbus slave: Modbus RTU protocol Baud Baud Bits Setting for baud rate. Address • 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, 230400 Bits Setting for bits.
  • Page 10 Meku Monitor 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 confi guration and trouble- shooting.

  • Page 11: Use With Promolog

    USE WITH PROMOLOG PromoLog settings 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.
  • Page 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.
  • Page 13 Response from the device 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.
  • Page 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.
  • Page 15 Quick setting guide for device FTR970-PRO supports two different methods for saving normal periodic transmitter data packets to its fl ash 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 fl ash memory, then the device works with PromoLog with de- fault settings.
  • Page 16 End of basic user part of the manual. Start of expert user part of the manual.

  • Page 17: Channels

    CHANNELS 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.
  • Page 18 Read readings and other channel information either as fl oat- 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)
  • Page 19 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.

  • Page 20: Realtime 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 classifi ed as channels. For these purposes the FTR970-PRO has also so called burst trap buffer, which removes multiple copies of burst data.
  • Page 21 Reading with Nopsa command over SCL protocol. Modbus RTU protocol Reading with Nopsa command over Modbus RTU protocol. Nokeval Nopsa commands (transport protocol SCL or Modbus RTU) 4/0 (Buffer info) Read buffer size and current write position 4/1 (Find oldest from buffer)
  • Page 22 Data type STRUCT Struct type 1 (processed radio data packet) Device type 1 byte, integer. See table on page 19 Signal strength 1 byte, integer. Subtract 127 to get result in dBm. Bytes + battery 1 byte, 3 msb data bytes, 5 lsb battery voltage. Divide battery by 10 to get result in volts.

  • Page 23: Flash

    FLASH Device processes data in 3 different ways, one of which is fl ash memory write. Device has 2 MB of fl ash memory for data recording. Data can be saved in fl ash memory in 3 differ- ent formats: processed, unprocessed and interval logged. Interval logging is described in “Channel Interval”...
  • Page 24 Month Unknown Choose whether devices which are unknown (those de- Hour vices which are designed after FTR970-PRO software version) are to be saved in fl ash memory. Channel interval This setting sets whether interval logging is on. If setting is 0, interval logging is not in use. Any other value enables interval logging and sets the interval time in seconds.
  • Page 25 Reading with Nopsa command over SCL protocol. Modbus RTU protocol Reading with Nopsa command over Modbus protocol. Nokeval Nopsa commands (transport protocol SCL or Modbus RTU) 4/16 (Read fl ash from location) Read data from given location 4/17 (Find time from fl ash) Give location from fl...
  • Page 26 Data structure Data is saved to fl ash in the following format. Byte order is least signifi cant byte fi rst (little-endian) Every packet has a header which informs where the packet footer is and also packet footer informs where packet header is, so data is organized as a two way linked list. There are 3 kinds of packets and every packet has a recognition byte which tell the type of a pack- Processed data: Length-1...

  • Page 27: Scl Protocol

    SCL PROTOCOL Nokeval SCL-protocol and commands are presented in separate SCL-manual, which can be down- loaded from Nokeval web site. Device accepts following commands: TYPE ? Device returns its type and software version information. SN ? Device returns its serial number. For ex. “A123456”.

  • Page 28: Modbus Protocol

    MODBUS PROTOCOL Supported Modbus RTU commands: • 3 Read Holding Registers: Read settings • 4 Read Input Registers: Read result values • 6 Write Single Register: Change settings • 16 Write Multiple registers: Change multiple settings at once. • 17 Report Slave ID: Device type information. •...
  • Page 29 Holding registers Table E2 Register Name Type Values 2000 Conf\Serial\Mode ENUM See table E1 Value Baud 2001 Conf\Serial\Baud ENUM See table E2 1200 2002 Conf\Serial\Bits ENUM See table E3 2400 2003 Conf\Serial\Address BYTE Unsigned 0...247 4800 2015 Conf\Channels\Timeout [min] BYTE Unsigned 1...127 9600 2016...
  • Page 30 Input registers Table E5 Register Name Type Values 0..1 Ch1\Reading FLOAT (LSW, MSB) Signed Value Type 2..3 Ch2\Reading FLOAT (LSW, MSB) Signed MTR260 MTR262 178..179 Ch90\Reading FLOAT (LSW, MSB) Signed MTR264 MTR265 200..201 Ch1\Reading FLOAT (MSW, MSB) Signed MTR165 202..203 Ch2\Reading FLOAT (MSW, MSB) Signed...

  • Page 31: Nopsa Language

    Nopsa can be used to transfer data between devices or from host to device. Nopsa needs some transfer layer protocol, which take care of addresses, transfer error manage- ment and packet length. Device supports Nopsa commands either on Nokeval SCL or Modbus RTU protocols.
  • Page 32 Transport protocol SCL When Nopsa packets are transported on SCL data is converted to hexadecimal notation (0-9 and A-F). One Nopsa byte will become 2 bytes. No spaces between characters. Packet starts with SCL command N and a space. ’N’ ’ ’ Nopsa-packet in hexadecimal ETX BCC Response is transferred also same way in hexadecimal, but N command is not appended.
  • Page 33 Nopsa command group 1 - basic commands Command Response 1/0 (Type) 0x01 | 0x00 status | string String: Device type as string -> RTR970PRO Command Response 1/1 (Version) 0x01 | 0x01 status | string String: Device version as string -> V1.0 Command Response 1/2 (Serial number)
  • Page 34 Nopsa command group 4 - logger commands Real time buffer commands Command Response 4/0 (Buffer info) 0x04 | 0x00 status | size*2 | write position*2 size: Ring buffer size (90), write position: position next to be written Command Response 4/1 (Find oldest) 0x04 | 0x01 status | read position*2 | lap counter Read position: position where is oldest data,...
  • Page 35 Command Response 4/18 (Give write pos.) 0x04 | 0x12 status | address*4 address: address where fl ash write is progressing Command Response 4/19 (Flash size) 0x04 | 0x13 status | size*4 size: size of the fl ash memory Command Response 4/20 (Flash erase) 0x04 | 0x14 status...

  • Page 36: Applications

    DCS770. FTR970-PRO and 7470 output device FTR970-PRO receiver can be used in conjunction with 7470 output unit. Devices are connected to same RS-485 bus and confi gured using Mekuwin program or 6790 handheld programmer. (Note: 2-wire-485 jumper is recommended to be on, see chapter Installing)

  • Page 37: Technical Data

    3 D1, pole 4 D0 Settings Wire length maximum 1000 m. Connection: RS-485 or RS-232 Protocol: Nokeval SCL, Modbus RTU, Nopsa Protocol: Nokeval SCL-Meku 1 Baud rate: 1200 / 2400 / 4800 / 9600 / 19200 / Program: Mekuwin for Windows 98...XP...

Table of Contents