1. Manuals
  2. Brands
  3. Microtronics Manuals
  4. Data Loggers
  5. myDatalogMUC
  6. User manual

Microtronics myDatalogMUC User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
User manual
myDatalogMUC
Cover
Valid from:
Firmware version: 03v002
l
Modem Version: 03v014
l
Server version: 44.1
l
Hardware version: 1.0
l
300101 | Rev.06

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the myDatalogMUC and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Microtronics myDatalogMUC

Summary of Contents for Microtronics myDatalogMUC

  • Page 1 User manual myDatalogMUC Cover Valid from: Firmware version: 03v002 Modem Version: 03v014 Server version: 44.1 Hardware version: 1.0 300101 | Rev.06...
  • Page 3 Chapter 1 Table of contents Chapter 1 Table of contents Cover Chapter 1 Table of contents Chapter 2 Declaration of conformity Chapter 3 Technical data Chapter 4 General specifications 4.1 Translation 4.2 Copyright 4.3 General descriptive names 4.4 Safety instructions 4.4.1 Use of the hazard warnings 4.4.2 General safety instructions 4.4.3 Safety and preventative measures for handling GSM/GPRS modems...
  • Page 4 6.3 Storage 6.4 Transport 6.5 Return Chapter 7 Installation 7.1 Dimensions 7.2 Installing the myDatalogMUC 7.2.1 Top-hat rail assembly 7.2.2 Assembly in a control cabinet 7.3 Safety instructions for the cabling 7.3.1 Information on preventing electrostatic discharges (ESD) 7.4 Electrical installation 7.4.1 Connecting the sensors, actuators and power supply...
  • Page 5 8.2 General principles 8.3 Placing the system into operation 8.4 Testing communication with the device Chapter 9 User interfaces 9.1 User interface on the myDatalogMUC 9.1.1 Operating elements 9.1.1.1 Button to initiate ALOHA transmission mode 9.1.1.2 Status LED 9.1.1.3 Status indication: Self-testing 9.1.1.4 Status display: buffer accu active...
  • Page 6 9.2.1.2 Comments 9.2.1.3 Control 9.2.1.4 Interfaces 9.2.1.4.1 Basis 9.2.1.4.1.1 Com1 and Com3 (modbus master, RS485, script parsing inactive) 9.2.1.4.1.2 Com1 and Com3 (modbus slave, RS485, script parsing inactive) 9.2.1.4.1.3 Com1 and Com3 (RS485, script parsing active) 9.2.1.4.1.4 Com2 (serial, RS232) 9.2.1.4.2 Config 9.2.1.4.2.1 Com1 and Com3 9.2.1.4.2.2 Com2...
  • Page 7 Chapter 1 Table of contents 9.2.1.9.2.1 Com1 and Com3 (modbus master, RS485) 9.2.1.9.2.2 Com1 and Com3 (modbus slave, RS485) 9.2.1.9.2.3 Com2 (serial, RS232) 9.2.1.9.2.4 Script 9.2.1.9.3 Scale 9.2.1.9.3.1 Com1 and Com3 (modbus, RS485) 9.2.1.9.3.2 Com2 (serial, RS232) 9.2.1.9.3.3 Script 9.2.1.10 Interface output channels 33-64 9.2.1.11 Calculated channels 9.2.1.11.1 Basis 9.2.1.11.2 Calculation...
  • Page 8 10.3.1 Reports 10.3.2 Groups 10.3.3 Map view 10.4 Recommended procedure 10.4.1 Creating the site 10.4.2 Assigning a device to the customer Chapter 11 Pawn script 11.1 General 11.1.1 Direct input of a pawn script 11.1.2 Uploading a binary file 11.2 Compiler options 11.3 API 11.3.1 Constants 11.3.2 System...
  • Page 9 Chapter 1 Table of contents 11.3.11 Console functions 11.4 Predefined log entries 11.5 Pawn script error codes 11.6 Syntax 11.6.1 General syntax 11.6.1.1 Format 11.6.1.2 Optional semicolons 11.6.1.3 Comments 11.6.1.4 Identifier 11.6.1.5 Reserved keywords 11.6.1.6 Numerical constants 11.6.1.6.1 Numerical integer constants 11.6.1.6.2 Numerical floating-point constants 11.6.2 Variables 11.6.2.1 Declaration...
  • Page 10 11.6.5.6 Comparative operators 11.6.5.7 Boolean 11.6.5.8 Other 11.6.5.9 Priority of the operators 11.6.6 Statements 11.6.6.1 Statement label 11.6.6.2 Composite statements 11.6.6.3 Expression statement 11.6.6.4 Empty statement 11.6.6.5 Assert expression 11.6.6.6 Break 11.6.6.7 Continue 11.6.6.8 Do statement while (expression) 11.6.6.9 Exit expression 11.6.6.10 For (expression 1;...
  • Page 11 Chapter 1 Table of contents 12.2.1 Übersicht Chapter 13 Maintenance 13.1 General maintenance 13.2 Fuse replacement Chapter 14 Removal/disposal Chapter 15 Troubleshooting and repair 15.1 General problems 15.2 Log entries and error codes 15.2.1 Modem error 15.3 Evaluating the device log 15.3.1 Evaluating the device log on the myDatanet server Chapter 16 Spare parts and accessories 16.1 Antennas...

  • Page 13: Chapter 2 Declaration Of Conformity

    Chapter 2 Declaration of conformity Chapter 2 Declaration of conformity Rev. 06...

  • Page 15: Chapter 3 Technical Data

    Chapter 3 Technical data Chapter 3 Technical data Voltage supply 12...30VDC (+/-10%) Additional information is provided in "Technical details regarding the energy supply" on page 70. Power consumption typ. 1W (without sensors) max. 3W (without sensors) Integrated rechargeable LiPo rechargeable battery with 900mAh to issue a message in the event of a buffer battery power supply failure.
  • Page 16 Universal inputs 8 x analogue or digital Modes: 0...20mA: Resolution 6,3µA, max. 23,7mA, load 96Ω 4...20mA: Resolution 6,3µA, max. 23,7mA, load 96Ω 0...2V: Resolution 610µV, max. 2,5V, load 10k086 0...10V: Resolution 7,97mV, max. 32V, load 4k7 PWM: 1...99%, max. 100Hz, min. pulse length 1ms, max. 32V, load 4k7 Frequency: 1...1000Hz, max.
  • Page 17 Data transmission By means of GSM/GPRS quad-band modem or per LAN interface to the respective myDatanet server The myDatalogMUC is equipped with an integrated SIM chip. Monthly data volume 2,0MB at 2 min. measurement cycle and 120 min. transmission cycle (only the 8 universal inputs are active) Additional information is provided in "Basic setting"...

  • Page 19: Chapter 4 General Specifications

    4.4 Safety instructions For the connection, commissioning and operation of the myDatalogMUC , the following information and higher legal regulations of the country (e.g. ÖVE), such as valid EX regulations as well as the applicable safety and accident prevention regulations for the respective application case must be observed.

  • Page 20: Use Of The Hazard Warnings

    4.4.1 Use of the hazard warnings DANGER: Indicates a potential or threatening hazardous situation that will result in death or serious injuries if not avoided. WARNING: Indicates a potential or threatening hazardous situation that can result in death or serious injuries if not avoided.
  • Page 21 Chapter 4 General specifications In addition to the following safety considerations, all directives of the country in which the device is installed must be complied with. Important note: No liability shall be assumed at any time and under no circumstances for connections via a GSM/GPRS modem for which wireless signals and networks are utilized.

  • Page 22: Block Diagram

    4.5 Overview Overview myDatalogMUC 1 Upper connection strip 5 Sub-D connector of the serial interface (Com2) 2 Button to initiate ALOHA transmission mode 6 LAN interface 3 Signalling LEDs 7 Antenna connector 4 Button to initiate self-testing 8 Lower connection strip 4.5.1 Block diagram...
  • Page 23 Chapter 4 General specifications Block diagram of the myDatalogMUC Rev. 06...

  • Page 24: Intended Use

    A total of 64 channels are provided for this purpose. The output data can either be specified via the input screen of the myDatanet server or can be calculated by the myDatalogMUC after each measurement cycle via the script (see "Pawn script" on page 149).

  • Page 25: Device Labelling

    Chapter 4 General specifications supply a sensor) or so that they can be switched wirelessly from a central location. The myDatalogMUC can also determine the setpoints for the relays itself by means of the script. All of the input measurement data is temporarily saved to an internal data memory along with the output states and wirelessly transmitted to a central location at freely selected intervals.

  • Page 26: Storage Of The Product

    4.10 Storage of the product To safeguard the myDatalogMUC , ensure that all of the relevant data was transmitted to the myDatanet server. If necessary initiate the ALOHA transmission mode using the button (see "ALOHA transmission mode" on page 44) and then check again that all of the relevant data has been transmitted. Then disconnect the device from the supply voltage.
  • Page 27 Chapter 4 General specifications Note: Qualified personnel In the context of these instructions and the warnings on the product itself, individuals responsible for the setup, installation, commissioning and operation of the product must have gained relevant qualifications relating to their activities, including, for example: Training, instruction and authorisation to activate/deactivate, ground and label electric circuits and devices/systems in accordance with the standards of safety engineering.

  • Page 29: Chapter 5 Functional Principle

    Functional principle myDatalogMUC with integrated managed service SIM chip (including data transmission) Router to connect the myDatalogMUC to the Internet via the LAN interface. myDatanet server to which the data is transferred Client that accesses the interface of the myDatanet server via the web browser Customer-specific server that provides clients with their own interface.
  • Page 30 Functions and components provided by myDatanet : myDatalogMUC The myDatalogMUC is a stationary device for connecting sensors (UI1-8, PT100/1000, COM1-3) and actuators (RELAY1-6, mA OUT1-2, COM1-3) to the myDatanet server (GPRS). Managed Service Managed Service is the basis for operating your devices and provides you with a wide range of services.

  • Page 31: Internal Processing Of The Measurement Values

    Chapter 5 Functional principle 5.1 Internal processing of the measurement values Diagram of the internal processing of the measurement values 1 Filter to compensate for brief signal fluctuations 7 Determination of the setpoints, script processing (see "Filter module" on page 32). The filter (see "Control module"...

  • Page 32: Filter Module

    Note: Additional explanation on universal inputs that are operated in Digital or Digital LP mode. Measurement channels -> Basis Mode Digital Measurement channels ->Config. Filter time 800ms Input signal Input signal at the universal input Input signal after filter Input signal taking the "filter time" into consideration Logic level The input signal at the universal input is analysed once per second.

  • Page 33: Overflow Module

    Chapter 5 Functional principle 5.1.2 Overflow module This module monitors the measurement range limits of the raw value. If a universal input was, for example, switched to "4-20 mA" mode, a raw value of 2 mA will violate the measurement range. The overflow module is only available for the 8 universal inputs in channel modes "Freq", "PWM", "4-20 mA", "0-20 mA", "0-2V"...

  • Page 34: Scale Module (Inputs)

    5.1.3 Scale module (inputs) This module rescales the raw value (e.g. mA) to the required measurement value (e.g. mm). The scale module is only available for the 8 universal inputs and for the interface channels (Com1 and Com3 only). The following table specifies the relevant parameters for the module: Configuration section Modus/interface Parameter Explanation...

  • Page 35: Decay Module

    Chapter 5 Functional principle 5.1.4 Decay module The decay module is designed to summarise several measurement values. The average value over a required time frame or the minimum value within a required time frame can be determined, for example. The decay module is only available for the 8 universal inputs, with the exception of "Cnt.Day"...
  • Page 36 5.1.5 Hold module With the help of the hold module, it can be determined how to proceed in the event of invalid measurement values. It ensures the last valid measurement value is retained until a new valid measurement value is available or passes the error on after a certain number of invalid measurements.
  • Page 37 Chapter 5 Functional principle measurement channel can also still be changed by the script before it is recorded by the record module. If the "Pawn" script type was selected, the alarm status of a channel can be changed via the "Mdn_SetAlarm()" function (see Mdn_SetAlarm()).

  • Page 38: Record Module

    5.1.8 Record module The record module records the measurement values. As the record interval and measurement cycle can be selected individually, a record is not saved at the time of every measurement. Depending on the global triggers set by the alarm/trigger module (see "Alarm flags" or "Trigger flags" in chapter "Constants" on page 163), the record interval is modified, if necessary, the transmission is initiated or a new measurement is triggered.

  • Page 39: Setpoint Module

    Chapter 5 Functional principle Configuration section Parameter Explanation Alarm settings On alarm Ü An immediate transmission is initiated. On warning On fault alarm On fault warning Configuration section Parameter Explanation Basic setting Record interval Time between measurement data recordings Measure quick divisor Record interval = record interval / factor (from triggering) Measure slow factor...

  • Page 40: Scale Module (Outputs)

    894 measurement cycles The internal data memory of the myDatalogMUC is designed as a circular buffer with 5 sectors. If the maximum number of data records (4.470 ) is achieved, the sector with the oldest data is deleted fully before new data can be saved in this sector again.
  • Page 41 Data memory after 4.470 +1 measurement cycles: 5.3 Use of the communication channels Two channels (LAN and GPRS) are available to the myDatalogMUC for communicating with the myDatanet server. Their use can be configured via the "Communication channel" parameter located in the "Basic settings"...
  • Page 42 The behaviour basically corresponds to that of "Interval" mode. If the GPRS interface is to be used as the preferred communication channel, the myDatalogMUC can also be placed in ALOHA transmission mode via the myDatanet server (see "ALOHA transmission mode" on page 44).

  • Page 43: Procedure In Case Of Connection Aborts

    Note: ALOHA transmission mode is not actively interrupted by myDatalogMUC , this means that any change to the connection type during ALOHA transmission mode only comes into effect following completion of the ALOHA transmission.

  • Page 44: Aloha Transmission Mode

    5.5 ALOHA transmission mode ALOHA transmission mode is a special connection mode whereby the myDatalogMUC establishes a connection to the myDatanet server for a period of time configured via the "Basic settings" configuration section (see "Aloha/wakeup duration" in chapter "Basic setting" on page 134).

  • Page 45: Automatic Selection Of The Gsm Network

    5.6 Automatic selection of the GSM network The GSM network to which the device should register must be selected, as the myDatalogMUC is equipped with a SIM chip that provides a mobile connection via a variety of international service providers (see www.microtronics.com/footprint).
  • Page 46 network selection is completed with the ban list that is now empty (see step 3 in chapter"Automatic selection of the GSM network" on page 45). The quality of the data transfer is monitored in addition to the establishment of the GPRS connection. If the data transmission fails 10 times in succession despite an existing GPRS connection, the currently selected GSM network is also added to the ban list.
  • Page 47 Chapter 5 Functional principle Basic setting Measurement cycle 60 sec. Interfaces ->Config. Warmup time 30 sec. Sequence of the serial communication Sequence of the serial communication in detail 1 Function: Mdn_SerialEvent() 4 Only when "Retry" is active Event: MDN_SERIAL_EVENT_INIT Function: Mdn_SerialEvent() Event: MDN_SERIAL_EVENT_TIMEOUT       or Mdn_SerialRx() 2 Function: Mdn_SerialEvent()
  • Page 48 Explanation of 2 If it is time to initiate a measurement, the "Mdn_SerialEvent()" callback function is called up by the system with the "MDN_SERIAL_EVENT_MEASURE" event. The internal processing of the measurement values also starts at this time (see "Internal processing of the measurement values" on page 31).
  • Page 49 Chapter 5 Functional principle Explanation of 4 (only when "Retry" is activated) In the event of a timeout, the "Mdn_SerialEvent()" callback function is called up by the system with the "MDN_SERIAL_EVENT_TIMEOUT" event. In this case, the receipt of data must be terminated by the "Mdn_SerialFinish()"...

  • Page 51: Chapter 6 Storage, Delivery And Transport

    Store the measurement technology so that it is protected against corrosive and organic solvent vapours, radioactive emissions and strong electromagnetic radiation. 6.4 Transport The myDatalogMUC should not be subjected to heavy shocks, bumps, impacts or vibrations. The original packaging must always be used for transport. Rev. 06...
  • Page 52 Support & Service Centre (see "Contact information" on page 237). The return shipment of the myDatalogMUC must occur in the original packaging and with freight and insurance paid to Microtronics Engineering GmbH (see "Contact information" on page 237). Insufficiently cleared return shipments will otherwise not be accepted! Rev.

  • Page 53: Chapter 7 Installation

    7.1 Dimensions Dimensions: Width and height Dimensions: Depth 7.2 Installing the myDatalogMUC Important note: Ensure installation is completed correctly. Comply with existing legal and/or operational directives. Improper handling can cause injuries and/or damage to the devices.
  • Page 54 1 myDatalogMUC 2 Top-hat rail 1. Place the myDatalogMUC on to the top edge of the top-hat rail. Turn slightly around the horizontal axis so that the myDatalogMUC clicks into the top-hat rail (see Figure "Top-hat rail assembly" on page 54).

  • Page 55: Safety Instructions For The Cabling

    Important note: To avoid any damage, always switch off the voltage supply to the device when performing electrical connections. When connections are made to the myDatalogMUC , the following warnings and information must be observed, in addition to the warnings and information found in the individual chapters on the installation.

  • Page 56: Information On Preventing Electrostatic Discharges (Esd)

    7.3.1 Information on preventing electrostatic discharges (ESD) Important note: Maintenance procedures that do not require the device to be connected to the power supply should only be performed once the device has been disconnected from the mains power supply to minimise hazards and ESD risks. The sensitive electronic components inside the device can be damaged by static electricity, which can impair the device performance or even cause the device to fail.
  • Page 57 Chapter 7 Installation Connection of the sensors and power supply 1 Relay 1-3 9 Dip switch (dip switch 2) for activating/deactivating the load or clamp resistances for Com3 (RS485) 2 Relay 4-6 10 Com 3 (RS485) 3 Supply (V IN, GND) 11 Connector for the external temperature sensor (PT100/1000) 4 mA Out1...
  • Page 58 Relay 1-3 CC1-3 Joint root for relay 1-3 Operating contact of relay 1 (normally open) Operating contact of relay 2 (normally open) Operating contact of relay 3 (normally open) Relay 4-6 CC4-6 Joint root for relay 4-6 Operating contact of relay 4 (normally open) Operating contact of relay 5 (normally open) Operating contact of relay 6 (normally open)
  • Page 59 Chapter 7 Installation mA Out1 Mass 0/4-20mA output signal mA Out2 Mass 0/4-20mA output signal COM1 R 1k 1k load resistance between RS485 A and R 120 R 120Ω load resistance between RS485 A and PU A 1k pull up to RS485 A PD B 1k pull down to RS485 RS485 B...
  • Page 60 2. Connect the antenna (see "Connection of the GSM antenna" on page 61). 3. Switch on the 12...30VDC supply voltage of the myDatalogMUC . The status LED should then start to flicker (see "Status LED" on page 76), indicating that a connection is being established.
  • Page 61 The standard antenna is directly attached to the antenna connector (see "Overview" on page 22) of the myDatalogMUC . In the event of a low radio signal strength, you can use the Flat antenna Smart Disc SMA-M 2,5m (206.816) or Flat Antenna Smart Disc US SMA-M 2,5m (206.818).

  • Page 62: Technical Details About The Universal Inputs

    The following step is not mandatory. 5. Check whether the connection to the myDatanet has worked correctly (see "Testing communication with the device" on page 72). 7.4.3 Technical details about the universal inputs Note: The universal inputs are not galvanically isolated. 7.4.3.1 0/4 to 20mA mode Note: Above 23,7mA, the relevant input becomes highly resistive (safety shutdown to prevent damage to the universal input).
  • Page 63 "Interfaces" on page 80). In modbus master mode, one or more slaves can be connected to the myDatalogMUC . The load or clamp resistances can be connected via dip switch 1 (Com1) or dip switch 2 (Com3) (see "Connecting the sensors, actuators and power supply" on page 56).
  • Page 64 Schematic diagram of the switchable load resistances Note: Additional explanation regarding the connection of two RS485 bus participants Schematic diagram: Connection of two RS485 bus participants A problem occurs if there is no connection between the GND potentials of the sender and recipient. A common mode voltage (V ) occurs in this case.
  • Page 65 7.4.6 Technical details about the RS232 interface (Com2) Note: The modbus interface Com2 is compatible with standard TIA/EIA-232-F. Important note: The RS232 interface of the myDatalogMUC does not support hardware handshakes. The output drivers are protected against overloading and are not damaged by a short circuit to the GND or +/- 15 V.
  • Page 66 Assignment of the Sub-D connector Signal Type O (low: -5,7V; high: 6,2V) I (low: <0,8V; high: >2,5V) I (low: <0,8V; high: >2,5V) O (low: -5,7V; high: 6,2V) max. 750mA The current firmware does not support the hardware handeshake. Supply voltage (reserved for extensions) If your sensor also comprises a SUB-D(f) connector, you can use the Gender changer 9-pin D-Sub male/male (206.684) provided as an accessory.

  • Page 67: Technical Details About The Outputs

    Chapter 7 Installation 7.4.7 Technical details about the outputs 7.4.7.1 Analogue output 1-2 (OUT, GND) Note: The analogue outputs of the myDatalogMUC are active, not galvanically isolated current outputs. Replacement circuit diagram for the analogue output Load Corresponds voltage to the supply voltage (12...30VDC...
  • Page 68 "BACKUP SUPPLY, 1" log entry. If a delay time has been configured, the myDatalogMUC , apart from the components that fail when supplied by the rechargeable buffer battery, continues to operate normally until the time delay has elapsed.
  • Page 69 The supply voltage exceeds the threshold for switching to normal operation again. The "POWER ON" log entry is created. The myDatalogMUC resumes normal operation again. The power supply is switched to the rechargeable buffer battery. The "BACKUP SUPPLY, 1" log entry is created.
  • Page 70 A current peak is caused by the input capacity at the time of activation. The myDatalogMUC is equipped with a relatively large input capacity (1000µF ) to ensure reliable switchover to the integrated rechargeable buffer battery in the event of a supply voltage failure. When selecting the power supply please ensure that it is able to supply the required initial current.

  • Page 71: Chapter 8 Initial Start-Up

    You can also use suitable test signals to simulate the sensors to establish the optimum configuration of the myDatalogMUC prior to its actual first use. This reduces the amount of time required for on- site installation to a minimum.

  • Page 72: Testing Communication With The Device

    2. Configure the created site according to your requirements (see "Site configuration" on page 78). 3. Link the myDatalogMUC with the created site (see "Site" on page 79). 4. Initiate the ALOHA transmission mode (see "ALOHA transmission mode" on page 44) so that the configuration of the site is transmitted to the myDatalogMUC .
  • Page 73 Chapter 8 Initial Start-Up Note: Supplementary explanation on evaluating the "GSM level": "GSM level" >-64dBm -64 to -73dBm -74 to -83dBm -84 to -93dBm -94 to -107dBm <= -108dBm Note: Additional explanation about evaluating the "voltage": The displayed voltage should only deviate slightly from the supply voltage applied to the device. Rev.

  • Page 75: Chapter 9 User Interfaces

    Chapter 9 User interfaces Chapter 9 User interfaces The configuration of the myDatalogMUC is carried out via the web interface on the myDatanet server (see "User interface on the myDatanet server" on page 78), which your responsible sales partner will provide to you.
  • Page 76 Solution/cause code Transport lock (GPRS OFF, measurement If the ALOHA transmission mode is initiated by OFF) button , the myDatalogMUC switches back into "RUN" mode (GPRS ON, measurement ON). Last connection OK Last transmission faulty Try again later Standby (GPRS ON, measurement OFF) see "transport lock"...
  • Page 77 Chapter 9 User interfaces 9.1.1.3 Status indication: Self-testing This status display is designed to indicate that self-testing is in progress and also shows the result of the test. Self-testing is completed automatically when the power supply (PowerOn) is established. It can also be initiated by the operator at any time by pressing the "TEST"...

  • Page 78: Site Configuration

    Further information on self-testing and diagnosing any problems is provided in "Status indication: Self-testing" on page 77. 9.1.1.6 Status display: Switching states of the relays The myDatalogMUC is equipped with LEDs that display the switching state of each of the 6 relays. RELAY x Description Lights up The operating contact of the relevant relay is closed.
  • Page 79 Activates script processing and informs the myDatalogMUC that the script is an "Instruction list" Script Input window for editing the script that is loaded in the device Pawn Activates script processing and informs the myDatalogMUC that the script is a "Pawn script" (see "Pawn script" on page 149) Script Script The script is directly entered and compiled via the server interface.
  • Page 80 9.2.1.4 Interfaces 9.2.1.4.1 Basis Note: Modbus mode (master/slave) for interfaces Com1 and Com3 is selected in the "Config" tab (see "Config" on page 90). 9.2.1.4.1.1 Com1 and Com3 (modbus master, RS485, script parsing inactive) Mode Interface deactivated Modbus activates the modbus functionality of the interface Baud rate Selection of the required baud rate (1/2)
  • Page 81 Chapter 9 User interfaces Modbus Hold Hold the last valid measurement value for x measurement cycles Function deactivated (2/2) Number of measurement cycles for which the measurement value is held until the error value is issued In the event of an error, the last valid measurement value is held until a new valid measurement value is present.
  • Page 82 Important note: Example to explain the link between the "Response timeout", "Retry" and "Measurement cycle" Basic setting Record interval 5min. Measurement cycle 1min. Interfaces -> Basis First attempt Response timeout 4sec. Retry Retry Active Explanation: In this example, seven channels are activated, however, the modbus slave does not answer.
  • Page 83 Chapter 9 User interfaces 9.2.1.4.1.2 Com1 and Com3 (modbus slave, RS485, script parsing inactive) Mode Interface deactivated Modbus activates the modbus functionality of the interface Baud rate Selection of the required baud rate 1200 2400 4800 9600 19200 38400 57600 115200 Stop bits Selection of the required stop bits...
  • Page 84 Script Activates script parsing. This means that the interface can be accessed via the "Mdn_ parsing SerialEvent()", "Mdn_SerialRx()", "Mdn_SerialTx()" and "Mdn_SerialFinish()" PAWN script functions (see "Script parsing" on page 46). This deactivates the modbus functionality of the interface. Details on configuring the "Script Parsing" are provided in "Com1 and Com3 (RS485, script parsing active)"...
  • Page 85 Chapter 9 User interfaces Script Parity None Selection of the required parity parsing (2/2) Even Data bits Number of data bits to be used Frame timeout 0...no timeout Time during which the connected digital sensor must send the full answer to a request. A communication error is detected if the time is exceeded.
  • Page 86 Important note: Example to explain the link between the "Frame timeout", "Retry" and "Measurement cycle" Basic setting Record interval 5min. Measurement cycle 1min. Interfaces -> Basis First attempt Frame timeout 12sec. Retry Retry Active Explanation: At the time of a measurement, the measurement data sequence is sent via the "Mdn_ SerialTx()"...
  • Page 87 Chapter 9 User interfaces 9.2.1.4.1.4 Com2 (serial, RS232) Mode Interface deactivated ASCII Baud rate Selection of the required baud rate 1200 2400 4800 9600 19200 38400 57600 115200 Stop bits Selection of the required stop bits Parity None Selection of the required parity Even Data bits Number of data bits to be used...
  • Page 88 Script Activates script parsing. This means that the interface can be accessed via the "Mdn_ parsing SerialEvent()", "Mdn_SerialRx()", "Mdn_SerialTx()" and "Mdn_SerialFinish()" PAWN script functions (see "Script parsing" on page 46). The option to determine via the "Config" tab of the "Interfaces" configuration section how the received characters should be evaluated is thus deactivated.
  • Page 89 Chapter 9 User interfaces Important note: Example to explain the link between the "Frame timeout", "Retry" and "Measurement cycle" Basic setting Record interval 5min. Measurement cycle 1min. Interfaces -> Basis First attempt Frame timeout 12sec. Retry Retry Active Explanation: At the time of the measurement, the measurement data sequence is sent (see "Sequences for COM2"...
  • Page 90 9.2.1.4.2 Config 9.2.1.4.2.1 Com1 and Com3 Mode Interface deactivated Modbus Modbus Master Com mode RTU Data is transferred in binary format. mode ASCII Data is transferred in ASCII format. Slave Com mode RTU Data is transferred in binary format. ASCII Data is transferred in ASCII format.
  • Page 91 Chapter 9 User interfaces 9.2.1.4.2.2 Com2 Mode Interface deactivated ASCII Warmup time Time from switching on the myDatalogMUC until the init sequence is sent. Frame structure ...[CR][LF] Each frame must be terminated with both "[CR][LF]" characters..[ETX] Each frame must be terminated with the "[ETX]"...
  • Page 92 Init sequence Initialisation command that is sent to the digital sensor following expiry of the warmup time when the myDatalogMUC is switched on. The following escape codes are supported: \a \b \f \n \r \t \v \\ \? \' \" \xhh Measurement data sequence Command that is sent to the digital sensor at the time of every measurement [0-512 characters]...
  • Page 93 Chapter 9 User interfaces Mode Basic settings for the measurement channel Universal inputs Measurement channel deactivated Digital Invert Inverts the input signal (digital modes) Cnt.Day Impulse Counted measurand of a pulse in the measurement unit Defines the upper scale end of the pointer instruments Unit String that is used as a measurement unit by all of the server display elements [0-16 characters]...
  • Page 94 Universal inputs 0-20 mA 0% Start of the measurement range in the measurement unit 100% End of the measurement range in the measurement unit (analogue modes) Unit String that is used as a measurement unit by all of the server display elements [0-16 characters] Decimal Number of decimal places that are used by all of the server places...
  • Page 95 Chapter 9 User interfaces 9.2.1.6.2 Config Universal inputs Digital Filter time Time in [ms] during which the signal must remain constant to (digital modes) initiate a level change. Used to suppress brief faults (debouncing). Decay Temporal function in the measurement cycle Decay deactivated Minimum signal length for x seconds with a rising edge...
  • Page 96 Universal inputs Cnt.Day Filter time Time in [ms] during which the signal must remain constant to initiate a level change. Used to suppress brief faults (Counter modes) (debouncing). Reset at Reset time of the day counter Cnt.Intrvl. Filter time Time in [ms] during which the signal must remain constant to initiate a level change.
  • Page 97 Chapter 9 User interfaces Universal inputs Freq Filter time Time in [ms] during which the signal must remain constant to initiate a level change. Used to suppress brief faults (Frequency mode (1/2) (debouncing). 1/2) Decay Temporal function in the measurement cycle Decay deactivated The minimum of the last x measurement values is recorded.
  • Page 98 Universal inputs Freq Overflow Procedure in the event of measurement range violations Ignore The measurement value is calculated beyond (Frequency mode (2/2) the range limits. 2/2) Silent cutoff The measurement value is truncated at the range limits. Out of If the measurement value is below 1Hz, range the error value "UF"...
  • Page 99 Chapter 9 User interfaces Universal inputs Filter time Time in [ms] during which the signal must remain constant to initiate a level change. Used to suppress brief faults (PWM mode 1/2) (1/2) (debouncing). Decay Temporal function in the measurement cycle Decay deactivated The minimum of the last x measurement values is recorded.
  • Page 100 Universal inputs Overflow Procedure in the event of measurement range violations Ignore The measurement value is calculated beyond (PWM mode 2/2) (2/2) the range limits. Silent cutoff The measurement value is truncated at the range limits. Out of If the measurement value is below 1%, range the error value "UF"...
  • Page 101 Chapter 9 User interfaces Universal inputs 0-20mA Filter time Time in [ms] during which the analogue signal is averaged for signal smoothing. Used to suppress signal noise (also (0-20mA mode 1/2) (1/2) see "Example to explain the filter time in conjunction with the ext.
  • Page 102 Universal inputs 0-20mA Overflow Procedure in the event of measurement range violations Ignore The measurement value is calculated beyond (0-20mA mode 2/2) (2/2) the range limits. Silent cutoff The measurement value is truncated at the range limits. Out of If the measurement value is above range 20.1 mA, the error value "SC"...
  • Page 103 Chapter 9 User interfaces Universal inputs 4-20 mA Filter time Time in [ms] during which the analogue signal is averaged for signal smoothing. Used to suppress signal noise (also (4-20mA mode 1/2) (1/2) see "Example to explain the filter time in conjunction with the ext.
  • Page 104 Universal inputs 4-20mA Overflow Procedure in the event of measurement range violations Ignore The measurement value is calculated beyond (4-20mA mode 2/2) (2/2) the range limits. Silent cutoff The measurement value is truncated at the range limits. Out of The error value "OL" (open loop) is range issued, if the measurement value is below 3.9mA.
  • Page 105 Chapter 9 User interfaces Universal inputs 0-2V Filter time Time in [ms] during which the analogue signal is averaged for signal smoothing. Used to suppress signal noise (also (0-2V mode) see "Example to explain the filter time in conjunction with the ext.
  • Page 106 Note: Additional explanation regarding the "Out of range" and "Namur borders" modes. "Out of range" or "Namur borders" mode Rev. 06...
  • Page 107 Chapter 9 User interfaces Universal inputs 0-10V Filter time Time in [ms] during which the analogue signal is averaged for signal smoothing. Used to suppress signal noise (also (0-10V mode) see "Example to explain the filter time in conjunction with the ext.
  • Page 108 Note: Additional explanation regarding the "Out of range" and "Namur borders" modes. "Out of range" or "Namur borders" mode Ext. temperature Measurement channel deactivated sensor Hold Hold the last valid measurement value for x measurement cycles Function deactivated Number of measurement cycles for which the measurement value is held until the error value is issued In the event of an error, the last valid...
  • Page 109 Chapter 9 User interfaces 9.2.1.6.4 Trigger If an universal input is operated in digital mode or LP digital mode, there are two different types of triggers: Event trigger (MS, XM, I1-I4) In contrast to the level triggers, the relevant operation (e.g. initiate transmission) is only executed once when the trigger event occurs.
  • Page 110 All other Event trigger XM Initiate transmission modes Level Levels for initiating the trigger. The hysteresis from the "Alarm" tab is used to determine the level to reset the trigger. Greater or The trigger is initiated, if the measurement value equal meets or exceeds this value.
  • Page 111 Chapter 9 User interfaces Interface Basis settings for the measurement channel Measurement channel deactivated Com1 Scale > Scale Defines the lower scale end of the pointer instruments Com3 (siehe "Scale" on page Defines the upper scale end of the 115) pointer instruments Config >...
  • Page 112 Script Defines the lower scale end of the pointer instruments Defines the upper scale end of the pointer instruments Unit String that is used as a measurement unit by all of the server display elements [0-16 characters]. It has no direct influence on the values Decimal places Number of decimal places that are used by all of the server display...
  • Page 113 Chapter 9 User interfaces 9.2.1.7.2.1 Com1 and Com3 (modbus master, RS485) Slave Ad. Address of the modbus slave Modbus Ad. Address of the register that should be read Format Data type Digital A digital value should be read. Function Read coils (FC 01) Read discrete inputs (FC 02) Signed A signed integer value should be read.
  • Page 114 9.2.1.7.2.2 Com1 and Com3 (modbus slave, RS485) The following table details the possible access functions depending on the data type of the interface channel: Modbus add. Data type Read function Write function 0x0000 Digital Read coils (FC 01) Write single coil (FC 05) Write multiple coils (FC 15) 0x003F 0x0000...
  • Page 115 Chapter 9 User interfaces 9.2.1.7.2.3 Com2 (serial, RS232) Column The ASCII data message from the digital sensor is split into individual measurement values by the "number delimiter" (see "Interfaces" on page 80). The "column" configuration parameter specifies which of these measurement values is linked with/recorded on the interface channel. 9.2.1.7.3 Scale Note: The following parameters are not available for an interface channel that is connected to an interface for which "Script parsing"...
  • Page 116 Note: Calculation of the measurement value during active scaling: Basis > min Basis > max 20mA Min modbus Max modbus 65535 Measurement value in the unit of 32767 the modbus slave Scaled measurement value 11.9998mA F F = ( (C - D)/(B - A) ) * (E - A) + D F = ( (20mA - 4mA) /(65535 - 0) ) * (32767 - 0) + 4mA =11.9998 mA 9.2.1.7.3.2 Com2 (serial, RS232)
  • Page 117 Chapter 9 User interfaces 9.2.1.7.5 Trigger Note: If "Script" is used as the basic setting for the measurement channel, triggers cannot be initiated automatically by the system, as the alarm/trigger module is executed before the control module in which script processing is completed (see "Internal processing of the measurement values"...
  • Page 118 9.2.1.8 Interface channels 33-64 9.2.1.8.1 Basis Title 33-64 Freely selectable channel title for the interface channels The significance of the remaining configuration parameters in this configuration section corresponds to the "Interface channels 1-32" configuration section (see "Interface channels 1-32" on page 110). 9.2.1.9 Interface output channels 1-32 Note: Some of the configuration parameters included in this configuration section also affect parameters that are not included in the tab that is currently open.
  • Page 119 Chapter 9 User interfaces Interface Basis settings for the output channel: Output channel deactivated Com1 Scale > Scale Defines the lower scale end of the pointer instruments Com3 (siehe "Scale" on page Defines the upper scale end of the pointer instruments Config >...
  • Page 120 Script Defines the lower scale end of the pointer instruments Defines the upper scale end of the pointer instruments Unit String that is used as a measurement unit by all of the server display elements [0-16 characters]. It has no direct influence on the values Decimal places Number of decimal places that are used by all of the server display...
  • Page 121 Chapter 9 User interfaces Format Data type Digital A digital value must be written. Function Write single coils (FC 05) Write multiple coils (FC 15) Signed A signed integer value should to be written. 16 16-bit integer Function Write multiple registers (FC 16) Write single register (FC 06) 32 32-bit integer.
  • Page 122 9.2.1.9.2.2 Com1 and Com3 (modbus slave, RS485) The following table details the possible access functions depending on the data type of the interface output channel: Modbus add. Data type Read function Write function 0x0800 Digital Read discrete inputs (FC 02) 0x083F 0x0800 Signed 16/32 bit Read input registers (FC 04)
  • Page 123 Chapter 9 User interfaces 9.2.1.9.2.3 Com2 (serial, RS232) Column The ASCII output string is split into individual measurement values by the "number delimiter" (see "Interfaces" on page 80). The "column"configuration parameter specifies where the output value is placed in the ASCII output string. 9.2.1.9.2.4 Script The configuration is not available for “script”...
  • Page 124 Note: Calculation of the output value during active scaling: Basis > min Basis > max 20mA Min modbus Max modbus 65535 Basis > setpoint 12mA Scaled output value 32767 E = ( (B - A)/(C - D) ) * (F - D) + A F = ( (65535 - 0) /(20mA - 4mA) ) * (12mA - 4mA) + 0 =32767 9.2.1.9.3.2 Com2 (serial, RS232) The scaling is not available for the serial interface.
  • Page 125 Chapter 9 User interfaces Mode Possible calculation modes for the calculated channels Calculated channel deactivated Table Defines the lower scale end of the pointer instruments Defines the upper scale end of the pointer instruments Unit String that is used as a measurement unit by all of the server display elements [0-16 characters].
  • Page 126 Shift element down Shift element up 9.2.1.11.2 Calculation Calculated channel deactivated Table Source Selection of the channel from which the input data is used Opens the screen for entering the values table (the table rows are interpolated linearly, values outside of the defined table are extrapolated linearly.) Digital Source Selection of the channel from which the input data is used...
  • Page 127 Chapter 9 User interfaces Note: Additional explanation: Delta mode Assumption: The source channel contains the counter reading of an infinite counter in m . The calculated channel 1 should contain the flow rate in m /s and calculated channel 2 should contain the flow rate in l/h. Required configuration Parameter Value channel 1 Value channel 2...
  • Page 128 9.2.1.12 Output channels 9.2.1.12.1 Basis Ext warmup time Indicates the amount of time that an output channel is switched on in "Ext warmup time" mode before the measurement mA OUT 1-2 title Freely selectable channel title for the analogue outputs (not galvanically isolated) [0-16 characters] Relay 1-6 title Freely selectable channel title for the relays [0-16 characters] (every 3 relays with a joint root) Mode...
  • Page 129 Chapter 9 User interfaces Note: Supplementary explanation regarding "Digital" mode Invert Setpoint Output on the device Off (low) On (high) On (high) Off (low) Note: Example to explain the burst interval in conjunction with the ext. warmup time (ext. warmup time < measurement cycle): Basic setting Record interval...
  • Page 130 Note: Example to explain the burst interval in conjunction with the ext. warmup time (ext. warmup time > measurement cycle): Basic setting Record interval 5min. Burst interval 75 sec. Measurement cycle 15 sec. Output channels Ext warmup time 30 sec. Measurement channels - Decay >Config.
  • Page 131 Chapter 9 User interfaces Note: Example to explain the filter time in conjunction with the ext. warmup time Basic setting Record interval 5min. Measurement cycle 1min. Output channels Ext warmup time 1sec. Measurement channels - Filter time 500ms >Config. Output on the device Sensor supply Explanation: The sensor supply is always activated 1 sec before expiry of the measurement cycle.
  • Page 132 9.2.1.13.3 Trigger The following two type of triggers are differentiated: Event trigger (XM) The relevant operation (e.g. initiate transmission) is only executed once when the trigger event occurs. Level trigger (QU, SL, RO, RF, ON, I1-I4) The relevant operation (e.g. activate online mode) is executed as long as the trigger is active. Event trigger XM Initiate transmission Level...
  • Page 133 Chapter 9 User interfaces 9.2.1.14 Alarm settings Acknowledgement Standard The global server setting is used to determine whether alarms must be acknowledged automatically or manually (see "myDatanet Server Manual " 805002). automatic Alarms are acknowledged automatically as soon as all of the messages have been sent.
  • Page 134 9.2.1.15 Basic setting Connection type Interval The device connects in the transmission cycle. Interval & wakeup The device connects to the server in the transmission cycle and can be placed into ALOHA transmission mode via the server. online The device does not disconnect the connection and continuously transmits the measurement data.
  • Page 135 Chapter 9 User interfaces Delay for power off alarm A relevant alarm is only triggered if the supply voltage has failed for longer than the time configured here. This prevents alarms from being triggered in the event of brief supply voltage failures. However, an entry is always added to the device log.
  • Page 136 Note: Example to clarify the record interval, measurement cycle and burst interval in conjunction with the decay As only the universal inputs have a decay module (see "Internal processing of the measurement values" on page 31), it is only wise to use the burst interval for these measurement channels. An explanation of the sequences, if an ext.
  • Page 137 Note: This configuration section is only visible, if one of the modes that the LAN interface uses is active as the communication channel in the "Basic settings" configuration section (see "Basic setting" on page 134). DHCP There is a DHCP server in the network and the myDatalogMUC is configuration automatically assigned the settings for the IP address, subnet mask and gateway.

  • Page 138: Device Configuration

    9.2.1.17 FTP export settings Note: This configuration section is only visible if the "FTP Agent Extended" licence for the myDatanet server has been enabled. FTP export profile off FTP export deactivated "Name of an List with the FTP export profiles that were created on the myDatanet FTP export server (for creating an FTP export profile, see "myDatanet Server profile"...
  • Page 139 (malfunctions cannot be excluded). Beta release Even firmware versions that have not successfully undergone all of the internal tests are installed (malfunctions may occur). Hardware version Hardware version of the myDatalogMUC 9.2.2.3 Device-specific settings Operating hold...
  • Page 140 9.2.2.4 GPRS SIM tariff Selected SIM tariff Rev. 06...

  • Page 141: Explanation Of The Symbols

    Chapter 10 myDatanet server Chapter 10 myDatanet server Note: All of the screenshots show version 44.1 of the myDatanet server using the standard colour scheme. Newer versions may include minor changes to the appearance of the server. 10.1 Overview Overview of the myDatanet server 1 Freely selectable logo 5 Opens the screen to input the global settings for the server...
  • Page 142 10.2 "Customer" area Overview of the "Customer" area 1 Area where an image file can be displayed as a "Map" and/or the OpenStreetMaps map can be displayed The sites can be manually placed on the image file used as a "map". In the OpenStreetMaps map, the sites are only displayed once GPS coordinates have been assigned to the site.
  • Page 143 Chapter 10 myDatanet server 4 Opens the input screen for configuring the customer 5 Deletes the customer 6 Comment that can be entered in the configuration of the customer 7 If a default report was defined, the default report is accessed by clicking on the name of the customer. Otherwise the "Sites"...
  • Page 144 10.3 "Site" area at customer level Overview of the "Sites" area at customer level 1 Area where an image file can be displayed as a "Map" and/or the OpenStreetMaps map can be displayed The sites can be manually placed on the image file used as a "map". In the OpenStreetMaps map, the sites are only displayed once GPS coordinates have been assigned to the site.

  • Page 145: Map View

    Chapter 10 myDatanet server 7 Symbol via which an image file can be loaded on to the server as a "Map" To remove the "Map" again, open the upload dialogue again and click on "Submit" without selecting an image file beforehand. 10.3.1 Reports The reports provide a variety of options to display graphs of the data on the web interface of the myDatanetserver or to download the data from the myDatanet server.
  • Page 146 3. Click on the "Sites / Applications" menu item of the myDatanetserver to call up the list of available application templates and sites. Create a new "myDatalogMUC " type site or a site using an application template that is compatible with the "myDatalogMUC " site type.
  • Page 147 Chapter 10 myDatanet server 4. Link the site/application with the myDatalogMUC by selecting the serial number. If the serial number of your device is not included in the list, you must first assign the device to the customer (see "Assigning a device to the customer"...
  • Page 148 2. Click on the "Pool and Aloha" menu item of the myDatanet server to access the list of devices that are in ALOHA transmission mode. Assigning a device to the customer 1 Menu item to call up the list of devices that are 4 Opens the dialogue to select the customer to in ALOHA transmission mode whom the device should be assigned...
  • Page 149 The pawn script is entered via the "Control" configuration section (see "Control" on page 79) of the input screen for configuring the site. "Pawn" must be selected as the "script type" so that myDatalogMUC interprets the commands entered in the "script" as a pawn script.

  • Page 150: Date And Time

    11.3 API 11.3.1 Constants Return codes for general purposes ERROR = -1 11.3.2 System main(); This function is executed during a PowerOn and when the PAWN script is exchanged. It should include all initialisations that only have to executed once during program start-up. forward public Mdn_CtrlFinish();...
  • Page 151 Chapter 11 Pawn script native Mdn_GetDate(&year=0, &month=0, &day=0, timestamp=0); If no time stamp was transferred (timestamp=0), the date (year, month, day) is determined for the current system time (in local time). Alternatively, the date (year, month, day) is determined for the transferred time stamp.
  • Page 152 11.3.4 Encoding native Mdn_SetPacked(data{}, pos, &{Float,Fixed,_}:value, size=4, bool:bigendian=false); Writes the transferred value to a specified position in an array Parameter Explanation data Array that should contain the data Byte offset within the array to determine the position where the value should be written value Value that should be written in the array...
  • Page 153 Chapter 11 Pawn script native Mdn_GetPacked(const data{}, pos, &{Float,Fixed,_}:value, size=4, bool:bigendian=false); Returns the value that is located at the specified position in an array Parameter Explanation data Array that contains the data Byte offset within the array to determine the position from which the data should be read value Variable to store the data to be read...
  • Page 154 11.3.5 Messkanäle 11.3.5.1 Constants Numbers of the channels MDN_CH_UI1 // Universal input 1 MDN_CH_UI8 // Universal input 8 MDN_CH_EXTTEMP // Ext. temperature sensor MDN_CH_GSM // Internal measurement channel "GSM level" MDN_CH_VIN // Internal measurement channel "Voltage" MDN_CH_IOUT1 // Analogue output 1 MDN_CH_IOUT2 // Analogue output 2 MDN_CH_REL1...
  • Page 155 Chapter 11 Pawn script // Information regarding the status of the communication with the respective extension module MDN_CH_MUCE1_COM_STATE MDN_CH_MUCE2_COM_STATE MDN_CH_MUCE3_COM_STATE // Number of channels MDN_NUM_IN_CHANNELS // Total number of interface channels MDN_NUM_OUT_CHANNELS // Total number of interface output channels MDN_NUM_CHANNELS // Total number of all channels (all of the in- and // outputs) Status of the measurement value/measurement channel...
  • Page 156 11.3.5.2 Functions native Mdn_GetCh(ch, &Float:value, &Mdn_ValueStatus:status = MDN_STATUS_OK); Reads out the current value and status of a channel Parameter Explanation Number of the channel (see "Numbers of the channels" in chapter "Constants" on page 154) value Value of the channel status Status of the channel (see "Status of the measurement value/measurement channel"...
  • Page 157 Chapter 11 Pawn script native Mdn_GetChScale(ch, &Float:min, &Float:max, &Float:scale); Reads the parameters of channel scaling and saves it in the transferred variables Parameter Explanation Number of the channel (see "Numbers of the channels" in chapter "Constants" on page 154) Channel type Mode Explanation Universal inputs...
  • Page 158 Parameter Explanation Channel type Mode Explanation Universal inputs Digital Not relevant Cnt.Day Cnt.Intervl. Freq End of the measurement range in the 4-20 mA measurement unit 0-20 mA 0-2 V 0-10 V Ext. temperature sensor Internal measurement channel Analogue outputs All modes End of the output range in the measurement unit Relay Interface channels...
  • Page 159 Chapter 11 Pawn script Parameter Explanation scale Channel type Mode Explanation Universal inputs Digital 1: Inverting "off" -1: Inverting "on" Cnt.Day Metered measurand of a pulse in the Cnt.Intervl. measurement unit Freq Factor by which the input signal is multiplied Not relevant 4-20 mA 0-20 mA...

  • Page 160: Serial Interfaces

    native Mdn_SetCh(ch, Float:value, Mdn_ValueStatus:status = MDN_STATUS_OK); Sets the value and status of a channel. This function can also be used to change the value of an input before it is saved. This is possible, as the script is processed once the measurement value has been acquired but before it is recorded (see "Internal processing of the measurement values"...
  • Page 161 Chapter 11 Pawn script 11.3.6.2 Callback functions forward public Mdn_SerialEvent(com, event); This function is the entry point for evaluating the serial events. This function must be provided by the user if script parsing is to be used. Parameter Explanation Number of the interface (see "Number of the interfaces" in chapter "Constants" on page 160) event Event that caused this function to be called up...

  • Page 162: Alarm & Trigger

    native Mdn_SerialFinish(com); Terminates the receipt of data via the specified interface. This function must always be called up once all of the required data has been received or the timeout event has occurred. Parameter Explanation Number of the interface (see "Number of the interfaces" in chapter "Constants" on page 160) Explanation Return value...
  • Page 163 Chapter 11 Pawn script Mdn_TriggerCfg Trigger configuration of a measurement channel // Mode Trigger mode (see "Trigger mode" in chapter "Constants" on page 163 ) // Flags Indicates which actions should be initiated when the trigger is active (see "Trigger flags" in chapter "Constants"...
  • Page 164 Trigger mode To evaluate the trigger configuration of a channel read by the Mdn_GetTriggerCfg() function MDN_TRG_MODE_NONE = 0, // Channel deactivated, no trigger //Relevant for all channel modes except for "Digital" MDN_TRG_MODE_LESS_OR_EQUAL = 1, // Initiation of the trigger, if // value <= level MDN_TRG_MODE_GREATER_OR_EQUAL = 2, // Initiation of the trigger, if // value >= level...
  • Page 165 Chapter 11 Pawn script native Mdn_SetAlarm(ch, alarm, Float:value, Float:level = 0.0); Sets the alarm status of a channel. The "MDN_FLG_UNDERFLOW" alarm flag must be set to indicate that the alarm/warning was triggered because the alarm/warning level was undercut. The "MDN_FLG_ UNDERFLOW"...
  • Page 166 native Mdn_GetTriggerCfg(ch, Config[Mdn_TriggerCfg]); Returns the trigger configuration of a channel Parameter Explanation Number of the channel (see "Constants" on page 154) Config Structure for storing the trigger configuration (see "Mdn_TriggerCfg" in chapter "Arrays with symbolic indices" on page 162) Explanation Return value OK, if successful ERROR, if no valid channel number was transferred...
  • Page 167 Chapter 11 Pawn script native min(value1, value2); Supplies the smaller of the two transferred values Parameter Explanation value1 Two values of which the smaller one is to be determined value2 Explanation Return value The smaller of the two transferred values native max(value1, value2);...
  • Page 168 The mode of operation of the following functions corresponds to that of the standard ANSI-C implementation: native Float:sin(Float:x); Sine of x native Float:cos(Float:x); Cosine of x native Float:tan(Float:x); Tangent of x native Float:asin(Float:x); Arcsine(x) in the range [-π/2, π/2], x element of [-1, 1] native Float:acos(Float:x);...
  • Page 169 Chapter 11 Pawn script native Float:fmod(Float:x, Float:y); Residual floating point of x/y with the same prefix as x. The result is dependent on the implementation, if y is zero. native isnan(Float:x); Returns a value that is not equal to zero, if x is not a number 11.3.9 Char &...
  • Page 170 native strcpy(dest[], const source[], maxlength=sizeof dest); Copies the source character string to the array dest (including '\0'). Parameter Explanation dest Array to store the character string that should be copied source Character string that should be copied maxlength Size (in Cells) of the array to store the string to be copied - OPTIONAL Explanation Return value Number of copied characters...
  • Page 171 Chapter 11 Pawn script native strchr(const string[], char); Searches for a character (first occurrence) in a character string Parameter Explanation string Character string that should be searched char Character that the search is looking for Explanation Return value -1, if the character that the search is looking for is not included in the character string Array index for the character that the search is looking for (first character occurring in the character string)
  • Page 172 native strcspn(const string1[], const string2[]); Searches for the position of the first character in string1 that is also included in the character string of permitted characters (string2) Parameter Explanation string1 Character string that should be searched string2 Character string of permitted characters Explanation Return value Length of string1 if no permitted character has been found...
  • Page 173 Chapter 11 Pawn script native strtol(const string[], base); Converts a character string into a value Parameter Explanation string Character string that is to be converted base Specifies the basis that must be used for the conversion 2-36: The specified basis is used 0: 8, 10 or 16 is used as the basis, depending on the character string that must be converted   Basis 8: with a leading 0...
  • Page 174 native toupper(c); Converts a character into upper case Parameter Explanation Character that should be converted to upper case Explanation Return value The upper case variant of the transferred character, if available, or the unchanged character code of "c" if the letter "c" does not have a upper case equivalent.
  • Page 175 Chapter 11 Pawn script native CRC32(data{}, len); Returns the calculated Ethernet CRC32 of the transferred data Parameter Explanation data Array that contains the data for which the CRC32 must be calculated Number of bytes that must be taken into consideration during the calculation initial Initial value for calculating the CRC32 - OPTIONAL Explanation...
  • Page 176 native Mdn_CalcTable(Float:key, &Float:value, const table[][Mdn_TablePoint], size = sizeof table); Searches for a certain value in the "key" column of the transferred reference point table and supplies the relevant value from the "value" column in the table. If the searched value is between two reference points, the returned value is interpolated linearly between the two adjacent values in the "value"...
  • Page 177 Chapter 11 Pawn script native Mdn_WriteLog(log, param); Generates an entry in the device log Parameter Explanation Log entry to be generated (valid range 0...999). Some error codes have already been predefined in chapter "Predefined log entries" on page 179. If possible, you should use these for the described error situations.

  • Page 178: Console Functions

    "index" specifies the index of the required array element. 11.3.11 Console functions Important note: The Com2 (115200 8N1) interface is used as the standard output on the myDatalogMUC if it is not being used otherwise. native print(const string[]); Prints the specified string to the standard output...
  • Page 179 Chapter 11 Pawn script native printf(const format[], {Float,Fixed,_}:...); Prints the transferred format string to the standard output. The mode of operation of the functions corresponds to that of the standard ANSI-C implementation. Parameter Explanation format[] The format character string to be used Explanation Return value Number of printed characters...
  • Page 180 11.5 Pawn script error codes The PAWN script is run through at the time of every measurement once all of the measurement values have been generated. If an error occurs during this process, the script execution is stopped and deactivated. The relevant error code is also entered in the device log and a connection to the server is established.
  • Page 181 Chapter 11 Pawn script Log entry Parameter Description Code Plain text Code Plain text 3015 reserved 3016 AMX_ERR_ Out of memory MEMORY 3017 AMX_ERR_ P-code file format is invalid/not supported FORMAT 3018 AMX_ERR_ File is for a newer version of AMX VERSION 3019 AMX_ERR_ File or function not found...
  • Page 182 11.6.1.3 Comments Text between the /* and */ symbols (both symbols can be on the same or different lines) and text following // (to the end of the line) are comments. Comments must not be nested. The compiler considers comments to be blank space.
  • Page 183 Chapter 11 Pawn script 11.6.1.6.2 Numerical floating-point constants A floating-point number is a number with numbers after the decimal point. A floating-point number starts with one or several numbers, includes a decimal point and has at least one number after the decimal point, e.g. "12.0"...

  • Page 184: Array Variables

    11.6.2.5 Static global declaration A static global variable acts in the same way as a global variable with the difference that the variable is only valid in the file in which it was declared. Replace the keyword "new" with "static" to declare a global variable as static.
  • Page 185 Chapter 11 Pawn script Example: List: valid declaration new i = 1 new j /* j is 0 */ /* k has the character code of ’a’ */ new k = ’a’ new a[] = [1,4,9,16,25] /* a has 5 elements */ /* the remaining 18 elements are 0 */ new s1[20] = [’a’,’b’] /* an unpacked string */...
  • Page 186 number of higher dimensions for "f". "sizeof f" and "sizeof e" are both 2 (see "Arrays and the "sizeof" operator" on page 186). 11.6.4.5 Arrays and the "sizeof" operator The "sizeof" operator returns the number of elements of a variable. The "sizeof" result of a simple (non array) variable is always 1.
  • Page 187 Chapter 11 Pawn script 11.6.5.2 Expressions An expression consists of one or several operands with an operator. The operand can be a variable, a constant or another expression. An expression followed by a semicolon is a statement. Examples of expressions: v++ f(a1, a2) v = (ia1 * ia2) / ia3 11.6.5.3 Arithmetic...
  • Page 188 11.6.5.5 Assignment The result of an assignment expression is the value of the operand following the assignment. Operator Example Explanation v = e Assigns the value of e to the variable v v = a Assigns the array a to variable v. v must be an array of the same size and with the same dimensions as a.
  • Page 189 Chapter 11 Pawn script 11.6.5.7 Boolean A logical "false" is represented by an integer value of 0; a logical "true" is represented by a value that is not 0. Results of a comparative expression are either 0 or 1 and the "tag" is set to "bool". Operator Example Explanation The result is a logical "true", if e is logical "false".
  • Page 190 If the evaluation of an expression is not explicitly justified with brackets, it is categorised by the association rules. For example: a*b/c is equal to (a*b)/c based on the left to right association, and a=b=c is equal to a=(b=c). Operator Explanation Reading order Function call...
  • Page 191 Chapter 11 Pawn script 11.6.6.1 Statement label A label consists of an identifier followed by a ":". A label is a "Jump target" of a "goto" statement. Each statement can be marked with a label. The label must be followed by a statement, which can also be an "empty statement".
  • Page 192 11.6.6.6 Break Terminates and leaves the smallest, encircling "do", "for" or "while" statement at any point in the loop. The "break" statement moves the program flow to the next statement outside the loop. Example: example(n) new a = 0 for(new i = 0; i < n ; i++ ) a += i if(i>10) break...
  • Page 193 Chapter 11 Pawn script 11.6.6.8 Do statement while (expression) Executes a statement before the conditional part (the "while" condition) is evaluated. The statement is repeated as long as the condition is logical "true". The statement is executed at least once. Example: example(n) new a = 0...
  • Page 194 Example: example(n) new a = 0 for(new i = 0; i < n; i++) return a The "for ( ; ; )" statement is the same as the "while (true)" statement. 11.6.6.11 Goto label Moves the program control (unconditionally) to the statement that follows the specified label. The label must be within the same function as the "goto"-statement (a "goto"-statement cannot jump out of a function).
  • Page 195 Chapter 11 Pawn script The "switch" statement shifts the sequence control to a "case" clause if a value from the list corresponds to the value of the "switch" expression. The "default" clause consists of the "default" keyword and a double point. The "default" clause is optional, however, if it is specified it must be included as the last entry in the "case"...
  • Page 196 11.6.7 Functions A function declaration specifies the name of the function and the formal parameters enclosed in brackets. A function can also return a value. A function must be defined globally, i.e. declared outside of another function and is globally available. If the function declaration is followed by a semicolon (instead of a statement), this is a forward declaration of a function.
  • Page 197 Chapter 11 Pawn script main() new v = 5 new f = faculty(v) faculty(n) assert n >= 0 new result = 1 while (n > 0) result *= n-- return result Regardless of what (positive) value the "n" variable has at the start of the "while" loop, "n" will equal zero at the end of the function.
  • Page 198 The following code example calls up the "addvector" function and adds five to each element of the "vect" variables: new vect[3] = [ 1, 2, 3 ] addvector(vect, [5, 5, 5], 3) /* vect[] now comprises the values 6, 7 and 8 */ 11.6.7.2 Named parameters versus fixed parameters In the previous examples, the order of the parameters in a function call were important as each parameter was copied to the same position of the function parameter.
  • Page 199 Chapter 11 Pawn script For example, if the "increment" function is defined as follows: increment(&value, incr=1) value += incr The following function calls are all the same: increment(a) increment(a, _) increment(a, 1) Standard values for arguments that are transferred as a reference are helpful in making these parameters optional.
  • Page 200 11.7 Example 11.7.1 Saw-tooth generator This example generates a saw-tooth on the output of a device. static Float:fCurrentValue; // Static declaration of the fCurrentValue variable of // the float type. This variable is not reset between // two measurement cycles This code is only executed once when - starting the device - changing a script.
  • Page 201 Chapter 11 Pawn script static iLastStamp; // Static declaration of the iLastStamp // variable of the integer type (is // automatically pre-initialised with 0) // This variable is not reset between two // measurement cycles. This code is executed at the end of every measurement cycle.
  • Page 202 Output signal generated by means of pawn 11.7.3 Calculating the flow rate with the table This example determines the flow rate of a wastewater system based on the fill level of the wastewater system. The fill level is measured at input 1 and the flow rate should be issued at output 1. Rev.
  • Page 203 Chapter 11 Pawn script static const Table[][Mdn_TablePoint] = // Static table for converting the height // to the flow rate [ 0.0, 0.0], [ 2.0, 1.0], [ 5.0, 3.0], [10.0, 10.0], [50.0, 15.0] This code is executed at the end of every measurement cycle.
  • Page 204 11.7.4 Script parsing The following example initially issues the device class, modem version and firmware version on the standard output. " " is then issued as the init sequence on Com1. " " is issued in the INIT COM1\r\n POLL COM1\r\n measurement cycle on Com1.
  • Page 205 Chapter 11 Pawn script public Mdn_SerialRx(com, const data{}, len) // Access point for evaluating the received // characters printf("Mdn_SerialRx( %d, \"%s\", %d)\r\n", // Issue number of the COM interface, com, data, len); // received data and number of characters via // the standard output switch(com) // Check via which COM interface the data was...
  • Page 206 The pawn supports "array assignments" with the limitation that both of the arrays must be the same length. For example, if "a" and "b" arrays have six lines, the expression "a=b" is valid. In addition to character strings, the pawn also supports literal arrays and thus expressions such as "a = {0,1,2,3,4,5}" where "a"...
  • Page 207 The API is provided to export data from the myDatanetserver and import data in to the myDatanet server. However, for "myDatalogMUC " type devices this is limited to the measurement data, the calculated channels, the setpoints of the output channels, the setpoints of the interface output channels, the transmission cycl and the record interval.
  • Page 208 12.2.1 Übersicht rapidM2M Playground 1 input field for the user name 2 input field for the password 3 List of all available HTTP-commands. The HTTP commands are grouped according to application fields. 4 Dependent on the HTTP-command selected drop down lists for the selection of the client, the user and the measurement site are displayed, which should substitute the relative wildcard (“$CID”...client, “$UID”...user, “$SID”...site) in the resource path of the HTTP command.

  • Page 209: Chapter 13 Maintenance

    The housing may only be opened by the manufacturer. If you believe that the fuse of the myDatalogMUC is defective (see "Troubleshooting and repair" on page 213), the device must be sent back in its original packaging to the manufacturer (see "Return" on page 52).

  • Page 211: Chapter 14 Removal/Disposal

    Chapter 14 Removal/disposal Chapter 14 Removal/disposal Incorrect disposal can cause environmental hazards. Dispose of the device components and packaging material in accordance with the locally valid environmental regulations for electronic products. Disconnect any charging voltage that has been used. Disconnect any connected cables using a suitable tool. Logo to the EU WEEE Directive This symbol indicates that the requirements of Directive 2012/19/EU regarding the scrap disposal of waste from electric and electronic equipment must be observed.

  • Page 213: Chapter 15 Troubleshooting And Repair

    When using a static IP address, check whether there is an IP address conflict in the network. Check whether an Internet connection is possible via the gateway connected to the myDatalogMUC . Check whether port 51241 is open in your network. Failure of the supply The alarm for the internal "voltage"...
  • Page 214 Problem Cause/solution The interface channel Check the cable connections (see "Connecting the sensors, actuators and data is not plausible power supply" on page 56) Check that the selection of the modbus address and slave address (only in (modbus, RS485). "modus master" mode) is set correctly in the interface channel configuration (see "Interface channels 1-32"...
  • Page 215 Chapter 15 Troubleshooting and repair Problem Cause/solution The pawn script is not Check that the correct script type was selected during the configuration of the being executed control (see "Control" on page 79). Load the device log from the myDatanet server and use DeviceConfig for the correctly.

  • Page 216: Log Entries And Error Codes

    15.2 Log entries and error codes Log entry Parameter Description Code Plain text Code Plain text 1000 POWER ON System start completed > 0 Internal system error Restart due to internal system error. There may be a hardware problem if the "POWER ON" log entry with a parameter code of >0 is contained in the device log several times.
  • Page 217 Chapter 15 Troubleshooting and repair Log entry Parameter Description Code Plain text Code Plain text 1111 ALOHA STOP End of ALOHA transmission mode ALOHA transmission mode was stopped unexpectedly. The parameter specifies how many more seconds ALOHA transmission mode should have lasted. 1114 BACKUP SUPPLY The power supply was switched to the rechargeable buffer battery.
  • Page 218 Log entry Parameter Description Code Plain text Code Plain text 1281 ZLIB Internal error STREAMPROCESS Contact the manufacturer if the device log includes this error several times (see "Contact information" on page 237). 1282 ZLIB Internal error STREAMFINISH Contact the manufacturer if the device log includes this error several times (see "Contact information"...
  • Page 219 Chapter 15 Troubleshooting and repair Log entry Parameter Description Code Plain text Code Plain text 1321 LAN_SOCK_STATE 23 LAN SOCK Socket connection disconnected. ESTABLISHED LAN SOCK FIN WAIT LAN SOCK CLOSING LAN SOCK TIME WAIT LAN SOCK CLOSE WAIT LAN SOCK LAST 1440 DECAY MEM ERR Too many measurement values are being taken into consideration during the decay (see...
  • Page 220 Check the connection between the device and sensor. HOLD Standby (GPRS ON, measurement OFF) If ALOHA transmission mode is initiated on the device, the myDatalogMUC switches back into "RUN" mode (GPRS ON, measurement ON). TRANSPORT Transport lock (GPRS OFF, measurement OFF) see "Standby"...
  • Page 221 Chapter 15 Troubleshooting and repair Log entry Parameter Description Code Plain text Code Plain text 2000 MODULE ERR Module-specific error (see "Error codes of the RS232 interface " on page 66) or area for customer-specific error codes, that can be written in the device log by means of the "Mdn_ 2999 WriteLog()"...
  • Page 222 Try again later BEARER NO -992 --- No answer ANSWER Try again later Check whether the device is in the coverage area (www.microtronics.com/footprint). BEARER NO -991 --- No carrier CARRIER Try again later Check whether the device is in the coverage area (www.microtronics.com/footprint).
  • Page 223 Error when selecting the network FAILURE Check whether the device is in the coverage area (www.microtronics.com/footprint). 1200 BAND SEL FAILED -969 --- A network could not be found on the GSM900/1800 or on the GSM850/1900 band. Try to improve the position of the antenna.
  • Page 224 Log entry Parameter Description Code Plain text Code Plain text TCP channel error (2/2) 1200 CHANNEL OUT OF -962 --- The optional value is outside the permissible RANGE range. Try again later CHANNEL -961 --- Internal error MEMORY CHANNEL -960 --- Internal error INTERNAL CHANNEL INVALID -959 ---...

  • Page 225: Evaluating The Device Log

    Chapter 15 Troubleshooting and repair 15.3 Evaluating the device log 15.3.1 Evaluating the device log on the myDatanet server The last 300 log entries on the myDatanet server can be called up via the button shown below that is located in the measurement device list.

  • Page 227: Chapter 16 Spare Parts And Accessories

    Chapter 16 Spare parts and accessories Chapter 16 Spare parts and accessories 16.1 Antennas Description Quantity Order number Antenna 900 SMA-M angled 300026 Antenna 900 SMA-M 206.806 Extension cable for antenna SMA-M/SMA-F 2,5m 206.807 Flat antenna Smart Disc SMA-M 2,5m 206.816 Flat Antenna Smart Disc US SMA-M 2,5m 206.818...

  • Page 229: Chapter 17 Document History

    Chapter 17 Document history Chapter 17 Document history Rev. Date Changes 16.10.2012 Chapter "Technical data" on page 15 Number of available "Interface channels" and "Interface output channels" added Chapter "Block diagram" on page 22 Chapter added Chapter "General product information" on page 24 Explanation of the "Interface output channels"...
  • Page 230 Rev. Date Changes 14.06.2013 Chapter "Connection examples" on page 61 Chapter added. (2/3) (2/3) Chapter "Technical details about the modbus interfaces (Com1, Com3)" on page 63 Detailed explanation regarding the permissible signal levels added. Chapter "Technical details about the RS232 interface (Com2)" on page 65 Detailed explanation regarding the signal levels has been added.
  • Page 231 Chapter 17 Document history Rev. Date Changes 14.06.2013 Chapter "Script parsing" on page 204 Chapter added (3/3) (3/3) Chapter "XML interface" on page 227 Chapter added Chapter "Log entries and error codes " on page 216 Explanation regarding the range for customer-specific error codes added Chapter "Power supply"...
  • Page 232 Rev. Date Changes 18.02.2014 Chapter "Basic setting" on page 134 Explanation for configuring the communication channel added (2/2) (2/2) Chapter "General" on page 149 Source for additional information on the PAWN script language added Chapter "Functions" on page 193 Specification of the include file is now only required for string functions (PAWN API level 2) Chapter "Example"...
  • Page 233 Chapter 17 Document history Rev. Date Changes 23.01.2018 Chapter "Installing the myDatalogMUC " on page 53 Further information on the correct installation added (2/3) (2/3) Chapter "Technical details about the modbus interfaces (Com1, Com3)" on page 63 List of the possible access functions for the modbus slave mode added.
  • Page 234 Rev. Date Changes 23.01.2018 Chapter "Basic setting" on page 134 Explanation of the "Report template" parameter has been added (3/3) (3/3) Chapter "FTP export settings" on page 138 Explanation of the parameter for entering the time stamp of the last FTP export added Chapter "Measurement instrument"...

  • Page 235: Chapter 18 Glossary

    The manufacturer's devices are equipped with subscriber identity modules (SIM) ex-works for the purpose of mobile data transmission. The footprint describes the countries and regions, in which a mobile connection is available (see www.microtronics.com/footprint). NaN value The myDatanet  uses special encoding to display different error statuses in the measurement values, for example.

  • Page 237: Chapter 19 Contact Information

    Chapter 19 Contact information Chapter 19 Contact information Support & Service: Microtronics Engineering GmbH Hauptstrasse 7 3244 Ruprechtshofen Austria, Europe Tel. +43 (0)2756 7718023 support@microtronics.com www.microtronics.com Microtronics Engineering GmbH (Headquarters) Hauptstrasse 7 3244 Ruprechtshofen Austria, Europe Tel. +43 (0)2756 77180 Fax.
  • Page 238 © 2018 Microtronics Engineering GmbH. All rights reserved. Photos: Microtronics Microtronics Engineering GmbH | www.microtronics.com Hauptstrasse 7 | 3244 Ruprechtshofen | Austria | +43 2756 77180 | office@microtronics.com 300101 | Rev.06...

Table of Contents