Drivers Mircom

Posted on  by admin

Classic QuickServer Gateway (Serial-Ethernet)

QuickServer is a high performance, fully configurable, cost-effective Building and Industrial Automation gateway for integrators to easily interface devices to networks in commercial buildings and industrial plants.

System integrators worldwide have benefitted from the value of the powerful line of interoperability gateways offered by FieldServer. Now, QuickServer adds to that value by running the same robust FieldServer protocol conversion software on a highly cost-effective platform backed by the experience, engineering expertise and proven technical support that integrators have come to expect from FieldServer.

QuickServer (Serial-Ethernet) is available in two series:

  • Thanks for you answer, but I cannot find this 'Gadget' driver manually. There is only this 'ELMO' driver and it is best available driver. In instruction is that use with 'SAM-BA' driver 'atm6124cdcsigned' driver.
  • The Mircom is a brand of life safety and communications systems including fire detection & alarm, voice evacuation, controlled access and security solutions Javascript is disabled on your browser. To view this site, you must enable JavaScript or upgrade to a JavaScript-capable browser.

During the registration process, the Instadose+ driver and client are installed on the users’ computer and their dosimeter is initialized for use. Users also have the option of downloading the Instadose ® mobile app to a smart device (phone or tablet) for online account access.

The FS-QS-1X10 Series is preloaded with two BAS drivers (two RS485 serial ports and one Ethernet port) Drivers from a list of over 150 protocols. There is a basic QuickServer that can handle up to 250 points and an enhanced QuickServer that can handle 500 points.

The FS-QS-1220 Series is preloaded with two BAS drivers (one RS485 serial port, one RS232 serial port, and one Ethernet port) Drivers from a list of over 150 protocols. Each QuickServer can handle up to 500 points.

Each QuickServer includes browser-based tools to make it easy to set-up QuickServer and perform diagnostics including determination of status, network settings, node information, map descriptors and more. The USB flash drive also includes the Discovery utility to determine what FieldServers are on a network.

Quickserver Gateway (Serial-Ethernet)

The QuickServer is a high performance, fully configurable, cost effective Building and Industrial Automation gateway forintegrators to easily interface devices to networks in commercial buildings and industrial plants.

System integrators world-wide have benefitted from the value of the powerful line of interoperability gateways offered byFieldServer. Now, QuickServer adds to that value by running the same robust FieldServer protocol conversion softwareon a highly cost effective platform backed by the experience, engineering expertise and proven technical support thatintegrators have come to expect from FieldServer.

QuickServer (Serial-Ethernet) is available in two series:

The QuickServer FS-QS-2X10 series is available at four different point capacities. Each QuickServer is preloaded with twodrivers (serial and/or Ethernet) from a customer’s choice of 140 different drivers, E.G. Modbus, BACnet, SNMP, EtherNet/IPand many more.

The FS-QS-2010 with 2 RS485 and 1 ethernet port can support up to 250 points. The FS-QS-2210 can support up to 500 points.The FS-QS-2310 can support up to 3,000 points. The FS-QS-2410 can support up to 5,000 points.

Equivalently the FS-QS-2020 with 1 RS485, 1 RS232 and 1 ethernet port can support up to 250 points. The FS-QS-2220 can support up to 500 points.The FS-QS-2320 can support up to 3,000 points. The FS-QS-2420 can support up to 5,000 points.

Every QuickServer includes browser-based tools to make it easy to set-up QuickServer and perform diagnostics including determinationof status, network settings, node information, map descriptors and more. The USB flash drive also includes the Discoveryutility to determine what FieldServers are on a network.

Modbus TCP

The Modbus TCP Driver allows the FieldServer to transfer data to and from devices over Ethernet using Modbus TCP Protocol. The Modbus TCP driver uses port 502. This port is not configurable. The driver was developed for Modbus Application Protocol Specification V1.1a' from Modbus-IDA. The specification can be found at www.modbus.org. The FieldServer can emulate both a Client and a Server simultaneously on the same ethernet port.

The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer.

There are various register mapping models being followed by various vendors. To cover all these models FieldServer uses the following three Models

  • Modicon_5digit – Use this format where addresses are defined in 0xxxx, 1xxxx, 3xxxx or 4xxxx format. A maximum of 9999 registers can be mapped of each type. This is FieldServer driver’s default format.
  • ADU –Application Data Unit address. Use this format where addresses of each type are defined in the range 1-65536
  • PDU –Protocol Data unit address. Use this format where addresses of each type are defined in the range 0-65535.

The key difference between ADU and PDU is for example if Address_Type is ADU and address is 1, the driver will poll for register 0. If Address_Type is PDU, the driver will poll for address 1.

Note 1: If vendor document shows addresses in extended Modicon (i.e. 6 digit) format like 4xxxxx then consider these addresses as xxxxx (omit the first digit) and use either ADU or PDU

Note 2: The purpose of providing 3 different ways of addressing the Modbus registers is to allow the user to choose the addressing system most compatible with the address list being used. At the protocol level, the same protocol specification is used for all three with the exception of the limited address range for Modicon_5digit.

Mircom FX2000

The FX2000 driver is a passive client driver intended for connection to the serial printer port of aFX2000 Panel. A passive client driver waits for messages to be sent to it (by the panel). Thedriver cannot send messages to the panel and hence it cannot request the state of any point in thepanel.

The driver can process alarm and trouble events and the system reset message. All othermessages and events are ignored.

Mircom

The driver can only be used as a client. Minimal server functionality is provided only to supportour ongoing quality assurance program by facilitating automated testing of the driver. It is notdocumented or supported.

Synchronization

A consequence of the fact that this is a passive client driver, is that the FieldServer must besynchronized with the panel by clearing all abnormal states, resetting the panel and thenrestarting the FieldServer/Sending the FieldServer a command to reset the data.

Driver Functionality

When an alarm occurs the panel reports the alarm with a message which identifies the loop andaddress. The driver will store a 1 in a Data Array location mapped for that point. When thecondition causing alarm is cleared, the panel does not send a message reporting this. Thus thedriver will not know the condition has been cleared until a panel reset is performed. When a resetis performed the driver will clear all the alarm states, previsouly stored, to zero. For those pointswhere the alarm condition has not been cleared, the panel sends a new alarm notification whichthe driver will recognize and store a 1 in a Data Array location mapped for that point.

I'd like to inquire about the Mircom FX2000 to Modbus TCP QuickServer Gateway CAS-QS-xxx0-3066.Please provide me with a quote for this product.

Specifications

Classic QuickServer Gateway (Serial-Ethernet)

Classic QuickServer Specs: FS-QS-1XX0

Depending on what hardware you require, the specifications will contain different options. For Example, M-bus section is only available on the FS-QS-1x50/FS-QS-1x51 devices where x is A for 16 devices, B for 32 devices and C for 64 devices. See images below for Port Support and product code check.


Environment
  • Operating Temperature: -40 to 75oC (-40 to 167oF)
  • Relative Humidity: 5-90% RH non-condensing
Power Requirements

9-30V DC or 12-24V AC, RS-422 = 15-30V DC or 12-24V AC, M-Bus = 12-24V DC (Slave: 550 mA, Master (1 Slave): 580 mA, Master (64 Slave):980 mA); 240 mA

Drivers
Physical Dimensions
  • Dimensions (WxDxH): 4.5x2.9x1.6 in (11.5x7.4x4.1cm)
  • Weight: 0.4 lbs (0.2 Kg)
Other
  • Configuration/Diagnostic utilities
  • Capacity, max points: 250 for QS-10XX, 500 for QS-12XX, 3000 for QS-13XX, 5000 for QS-14XX
  • Table, Wall or DIN rail mount
Communication
  • Baud: 4800, 9600, 19200, 38400, 57600, 115200
  • Start Bit: 7, 8; Stop Bit: 1, 2
  • Parity: Even, Odd, None
LonMark Certification (FS-QS-1XX1)
  • SPID: 80:00:95:46:00:84:04:01
  • Profiles: 0000 - Node object, 0001 - Open Loop Sensor Object, 0003 - Open Loop Actuator Object
  • Ethernet: 1, 2
  • Parity: 10/100 BaseT
Approvals
  • TUV Approved: to UL 916, EN 60950-1, EN 50491-3 and CSA C22.2 standards
  • BTL Mark, RoHS Compliant, GOST-R Certified, CE and FCC
  • LonMark Certified: (FS-QS-1011/FS-QS-12X1)

Drivers Microphone

Quickserver Gateway (Serial-Ethernet)

QuickServer Specs: FS-QS-2XX0


Environment
  • Operating Temperature: -20 to 70°C (-4 to 158oF)
  • Relative Humidity: 10-95% RH non-condensing
Power Requirements
  • Intput: 24VAC 0.125A, 12-24VDC 0.25A @12 VDC
  • Max Power: 3W

Physical Dimensions
  • Dimensions (WxDxH): 4 x 1.1 x 2.7 in (10.16 x 2.8 x 6.8cm)
  • Weight: 0.4 lbs (0.2 Kg)
Other

Web configuration
On-board diagnostics
DIN rail mount included

  • Capacity: 250 points FS-QS-20XX, 500 points FS-QS-22XX, 3000 points FS-QS-23XX, 5000 points FS-QS-24XX
Communication

FS-QS-2XX0

  • Baud: 9600, 19200, 34800, 57600, 76800
  • Serial (Galvanic Isolation) Ports: 1 x RS485, 1 x RS232/RS485
  • Ethernet Port: 10/100baseT, MDIX, DHCP
Drivers Mircom
Approvals
  • UL 60950
  • IC Canada
  • RoHS Compliant
  • WEEE compliant
  • RoHS compliant
  • CE and FCC class B and C part 15

Block Diagrams

Manuals

Datasheets

Case Studies

Tools

Resources

Additional Information

Modbus - MK10 and 32 Bits Numbers

Scaling in Modbus

Modbus does not provide a method for transporting large or Floating Point numbers or a mechanism for scaling analog values. A 16 bit word can only contain values in the range 0-65535. Only whole numbers are permitted. To work around this many server device manufacturers use multipliers and document them in their manuals. For example, to report a temperature of 58.5 the device reports a value of 585, and makes a note in the manual that the master should scale by 10. This scaling is achieved by adopting a convention between the client and the server.
What about large numbers > 65535
Modbus does not provide a mechanism but 3 important schemes are widely used.

Long Integers – Two consecutive 16 bit words are interpreted as a 32 bit long integer.

MK10 values – Two consecutive words are used. The 1st reports the number of units and the 2nd reports the number of 10,000’s.

Floating Point Numbers – Two consecutive words are used and a scheme. These schemes are conventions and not all servers or clients support them.

The protocol does not identify these big numbers. Only the vendor docs do.
What we mean by this is – if you look at the byte stream in a Modbus message there is no way of telling whether you are looking at two consecutive 16 bit words, or two consecutive words that should be interpreted as floating point, long or MK10 formats. Because of this you always have to look to the vendor docs.

Modbus - Reading Vendor Modbus Maps

Reading Vendor Modbus Maps

Drivers

Drivers Mirror

If you are reading the documentation for sensor blocks, valves, and other devices, you must keep in mind that some vendors may document their hardware in different ways.

According to the Modbus standard, addresses are simply integers from 0 to 65,535 with the different address ranges being referred to as coils, holding registers, etc. However, some vendors will document their hardware using numerical prefixes which are not actually part of the Modbus address. This originated from some models of PLCs which used the Modbus communications protocol, and which also used numerical prefixes in their internal data table. This is similar to using “I”, “Q”, “V”, etc. as address prefixes in IEC type PLCs.

However, it is important to remember that these numerical prefixes are documentation methods and are not part of what the Modbus protocol itself sends as part of the messages. A difference in documentation methods does not affect the compatibility of the protocol itself.

These prefixes are they mentioned anywhere in the Modbus standard, but the following shows how they are typically used in documentation based on this older convention:

  • 0xxxx – Coils.
  • 1xxxx – Discrete inputs.
  • 3xxxx – Input registers.
  • 4xxxx – Holding registers.
Drivers mirror for 2004 chevrolet silverado

Note that there is no 2xxxx address prefix.

In addition to numerical prefixes, some documentation will refer to protocol addresses (addresses start at 0), while other documentation will refer to data model addresses (addresses start at 1). That is, the first holding register may be 0 or 1 (or 40000 versus 40001 using prefixes). However, this has no bearing on what gets sent over the wire as a Modbus message. For a Modbus protocol message, the lowest address is always “0”, not “1”.

Modbus - Protocol Specifications
Modbus - Flavors of Modbus

Flavors of Modbus

RTU:

Common
Binary Protocol.
Active Master-passive Slave
Serial
Supported by FieldServers, QuickServers, CAS gateways

ASCII:

Similar to ModbusRTU but for each byte in an RTU message, there are 2 bytes in an ASCII message. The 2 bytes are the humand readable form of the single hex byte.
Eg RTU byte = 0x03 (Hex). ASCII bytes = ‘0’ and ‘3’ ie 0x30 and 0x33
Active Master-passive Slave
Serial
Supported by FieldServers, QuickServers

Jbus:

Modbus had the limitation of a max of 9999 items of each type. Ie only 9999 holding registers. However the protocol message allows 65k items to be addressed. JBUS allows all 65k items to be read/written. Other than that it is identical to RTU
Active Master-passive Slave
Serial
Supported by FieldServers, QuickServers, CAS gateways

TCP/IP:

Uses TCP/IP connection based Ethernet communications
Encapsulates RTU messages and adds a header.
A single slave can respond to multiple masters
Many slaves ignore the NodeID field in the message.
Supported by FieldServers, QuickServers, CAS gateways

MB Plus:

Proprietary coax networking layer
2 Mbits/sec
Supported by FieldServers, CAS gateways

Drivers Microsoft

Articles

Table 2 Modbus Registers
Modbus - Minimum Function Implementation
Modbus - Convert between Modbus Flavors
How Real (Floating Point) and 32-bit Data is Encoded in Modbus RTU Messages
Modbus - C#
Modbus - Modhopper
Modbus - 32 bit numbers
Modbus - Multiple Masters of one slave
ModbusTCP - Modbus Transaction Identifier
Modbus - There are (were) a Max of 9999 points of each data type
ModbusTCP - What type of protocol is Modbus TCP
ModbusTCP - What do you have that can help me convert my Modbus TCP data
ModbusTCP - We want to check the communication between our device and personal computer, so we need the 232 communication software
ModbusTCP - If I am converting from Modbus to Modbus, how difficult is it to Convert Serial (RTU) to TCP/IP and TCP/IP to Serial (RTU)
ModbusTCP - Can you give me an example of a Modbus/TCP to BACnet/IP configuration
ModbusTCP - How can I use Modbus Scanner to Write Registers of Digitrip 3000 (Protective Relays) Controls
Modbus - What is Modbus? (extended article)
Modbus - What is the Modbus Transaction Identifier
Modbus - Can you give me a list of Useful tools and applications for Modbus
Using PuTTY for serial COM connections (HyperTerminal replacement)
Modbus: Testing Modbus communication
Low Power Wireless Modbus
Modbus FAQ
FS-8704-03 – Modbus TCP
Modbus: Minimum Function Implementation
Modbus Protocol Specification
Modbus Specifications and Implementation Guides
MODBUS Exception Responses

Useful Links

Logos