Can't find the protocol you are looking for? Give us a call. We regularly add new drivers to our protocol library and may already support what you are looking for. Even if we do not currently support it, we develop custom drivers on demand. Give us a call, we can write drivers for just about any device.
Below is a list of potential Protocols. Many of them, we already have and the rest, we can develop.
Allen-Bradley CSP, Armstrong FA403, ATMI ACM and TGM, BACnet Arcnet, Barrington MicroSTAR, Barrington LanSTAR, Canatal, Caterpillar, ControlNet, Cummins, Data Highway Plus (DH), Data Highway Plus (DH+), DeviceNet, DF1, DNP3, Edwards, Federal Signal Ultravoice, Fike Cheetah, Gamewell FCI, GE SNP (SNPx), GE SRTP, GE TLC, GE-EGD, HTTP, KNX, Kohler, M-Bus, McQuay Microtech, MetOne Particle Counters, Mircom FX2000, Modbus ASCII, Modbus Plus (MB), Modbus Plus (MB+), Multistack Compu25, National Time and Signal, Notifer 320/640, Notifer Legacy Panels, Notifier 3030, Omron FINS, OPC, Optomux Opto22, Profibus, Rapid Engineering ICSII, SIA Security Industry, Siemens Fire Safety, Silent Knight Fire, SNMP, Stulz, TAC I-Net, Telnet, TL1, TOA VS900, XML, Cleaver-Brooks Hawk, Carrier DataLink, EST3 Serial, Veeder Root, DNP 3.0, Mudbus Jbus, Profibus DP Slave, Notifier INA, Data Aire DAP, Data Aire DART, Secutron, RussElectric Model 2000, Notifier Italia AM6000, Notifier 200/300/400, Lutron Machine, Gardner Denver, Grinnell TFX Minerva, Modbus Tek-Air, Hochiki Serial Driver, Notifier 1010/2020, Zellweger Infratox, Notifier NCA, Notifier Onyx 640, Metasys N2, BACnet PTP Serial
This driver is used to exchange data between a FieldServer and a ‘MicroSTAR’ devices by polling the LanStar they are connected to. When this driver is used the gateway must be connected to 1 of the 4 ports on the LanSTAR.
Each MicroSTAR device has 4x AO, 4x AI, 4x DI, 4x DO and 4x Counters. Setpoints, virtual Digital Outputs, any virtual points or virtual Microstars all reside in the memory of the LanStar and are thus accessible using this driver.
The driver can monitor the status of these points and write to the outputs.
This is an active client driver. The FieldServer is the client. The LanSTAR devices are the passive servers. The Client sends messages and processes responses from the LanSTAR’s.
The driver is a serial driver using the RS232 serial ports to connect between the FieldServer and the LanSTAR’s..
The driver is fully compatible with other FieldServer drivers and meets FieldServer’s quality assurance standards. The driver was developed by Chipkin Automation Systems, an Approved FieldServer Integrator.
Only Client functionality has been implemented. This means that you can use the driver as a client to monitor/command the devices. Server functionality is not supported thus you cannot use it a server to make another type of device appear as if it were a LanSTAR device.