Archive for May, 2007

CTC WebHMI Software

Published by Steven May 29th, 2007 in CTC, HMI, Scott Cosby and Web. 0 Comments

newbanner_r1_c1.gifControl Technology Corporation (CTC) has developed a reliable, web-based controller software package for automation activities called “WebHMI“. This software package will provide the user with a real-time, interactive, graphical interface for the access and control of automation activities within the browser environment of today.

CTC WebHMI offers a variety of features in this product for the automation industry. CTC provides the user with a variety of interactive panel media (i.e. switches, dials, displays, and etc.) at various sizes to remotely view and adjust automation activities from any workstation through the Internet. The interactive WebHMI panel media are created with CTC’s HMIBuilder software and developed into webpages on an embedded webserver, such as the company’s Blue Fusion 5100 series controller. CTC WebHMI will then allow the user to access the webpage from an Internet or Ethernet connection. CTC does require the user to have version 5 or later of Internet Explorer and Java Virtual Machine (JVM) version 1.4.2 for the WebHMI pages. The proper versions of these required programs are available at no charge to the user from CTC’s website. Adjustable security levels are included in WebHMI to maintain the stability of the user’s automation processes. The CTC website offers specific software information and downloads in the site’s support tab.

Human Machine Interface (HMI) is part of the Supervisory Control And Data Acquisition (SCADA) system. SCADA is described as a macro-scale system to monitor and control automation processes, and recognized as a link in the engineering of industrial instrumentation. HMI is the actual means in which the user accesses and controls the automation processes through a Programmable Logic Controller (PLC) or other such device over some form of network, which presents process data to the user. Some HMI packages offer the option to be linked to a database that provides other detailed information (i.e. device schematics, diagnostic and/or management information, etc.) to further enhance automation processes for the user. HMI/SCADA products have been used by a variety of engineers and technicians because of its simple implementation and reliability qualities.

Control Technology Corporation is headquartered in Hopkinton, Massachusetts with offices in Wisconsin, Michigan, and California. CTC is a premier designer and manufacturer of products that access and control automation process. CTC was founded in 1975, provides automation solutions to a wide customer base for over 30 years. CTC has maintained expertise in digital and analog circuit design, language technology, control software engineering, and other aspects for the automation industry.

Written by:

Scott Cosby is an Engineering Technician and experienced writer at a state agency in Oklahoma for over 10 years. Mr. Cosby holds a B.S. degree in Geography from Oklahoma State University (OSU), studies in Engineering and Electronic Technology at the OSU campus in Oklahoma City.

© Chipkin Automation Systems 2007

Did you like this post?

Subscribe To The RSS Feed!
To catch many more articles like this in the future, make it easy on yourself and subscribe to me via RSS. You will not regret it!

Do you have a question?
We will do our best to try and solve any building automation, protocol, integration problem you may have

Moxa MB3000 Series Gateways

Published by Steven May 22nd, 2007 in Modbus, Moxa, RS485 and Scott Cosby. 0 Comments

moxa_logo.gifMoxa will soon introduce its new MB3000 series gateways to the market. This series of network gateways includes the MB3180, MB3480, and MB3280. All of these devices offers various specifications and features to the user. The MB3000 series provides conversion between Transmission Control Protocol (TCP) and Remote Terminal Unit (RTU) and ASCII protocol based on Modbus. The features of these devices all include one Ethernet port, four serial ports that supports RS-232, RS-422, and RS-485 configurations, and up to sixteen simultaneous-supported TCP masters that provides a maximum of thirty-two requests per master. Another feature of the MB3000 series is it requires no modification of a customer’s existing technology with Moxa’s “smart-routing” capability. Some other Modbus gateways require a separate socket connection for each serial port, making them useless for TCP masters that can only open one connection. The MB3000 series supports smart routing, where only one socket connection is used to control slaves on every serial port. All of the devices in the MB3000 series can be described as compact, durable products with superior multi-protection, at suitable operational and storage temperatures, and includes Moxa’s five year warranty as well.

logomodbus.gifThe Modbus protocol was developed in the late 1970s by Modicon. Modbus is essentially a messaging service between server devices. The basic structure of Modbus states that a “master” sends a message to the “slave”, and depending on the message contents, the “slave/ client” will acknowledge and perform the requested task. These messages contain the address of the device, function code, data, and an error check. The device address is the location of recipient. The function code defines the type of message being sent. Data is a block of information to the recipient. The error check consists of numbers that refers to the quality of communication. The advantage of Modbus includes its flexible nature and simple implementation. This protocol has benefits for various users in building automation, wireless communication, energy, transportation, and many other applications.

Moxa is a leader of data network products for various industry users. The company’s product line includes serial boards, servers, Ethernet switches, and others. Moxa has an excellent sales staff that focuses on the users’ needs and requirements with offices in the United States, Taiwan, China, and Germany. In 2003, Moxa developed two branches of the company. The Moxa Technologies branch provides serial to PC and serial to Ethernet options. The Moxa Networking branch focuses on industrial Ethernet and fiber options to the potential user.

For more information;

Written by:

Scott Cosby is an Engineering Technician and experienced writer at a state agency in Oklahoma for over 10 years. Mr. Cosby holds a B.S. degree in Geography from Oklahoma State University (OSU), studies in Engineering and Electronic Technology at the OSU campus in Oklahoma City.

© Chipkin Automation Systems 2007

Did you like this post?

Subscribe To The RSS Feed!
To catch many more articles like this in the future, make it easy on yourself and subscribe to me via RSS. You will not regret it!

Do you have a question?
We will do our best to try and solve any building automation, protocol, integration problem you may have

TAC ACX Series Controllers

Published by Steven May 15th, 2007 in Andover Continuum and Scott Cosby. 0 Comments

acx.jpgTAC has produced a superior, compact, and competitively priced access controller for the security concerns of today’s world in their new ACX Series Controllers. These controllers are among the most powerful and complete devices in the building automation industry.

The ACX Series Controllers contains the most recent Andover Continuum software and TAC’s Net Controller II, which is a network-managed controller. The ACX Series will offer a building administrator control of up to 8 access points (i.e. interior or exterior doors, dock entrances, etc.) and supports almost 500,000 personnel records. This series of controllers can be web-enabled for simple installation and control through a single workstation or automatically with program control.

The ACX Series Controllers offers other features as well. For example, the ACX Series will allow the user to adjust access rights during variable threat levels. Another feature will provide a total lockdown of a building from disabling card readers to physically sealing off access points. The ACX Series will additionally provide the user with complex encryption. Including 192-bit Internet Protocol Security (IPsec) and Internet Key Exchange Protocol (IKE) to ensure effective and safe communication between the access controllers and user workstations.

These access controllers were developed by TAC primarily in response to the U.S. government standards relating to security needs. This includes the Homeland Security Presidential Directive 12 and the Federal Information Processing Standards (FIPS) 201 project. The FIPS 201 project is a uniform standard for identification badges concerning building access and terminal login. Homeland Security Presidential Directive 12 was drafted by the White House, and a policy for a common identification standard for federal employees and contractors. TAC was also influenced by private sector customers who required more extensive security needs for their buildings.

TAC is a leader in building automation, security systems and energy solutions for both public and private sector clients. TAC’s products are based on standard non-proprietary technology such as TCP/IP, LonWorks, BacNet, and Ethernet. Besides security products, TAC produces systems that integrate such functions as environmental (i.e. heating, cooling, and ventilation), fire control, and lighting as well. Similar to the ACX Series Controllers, these other automation products can enable total control at a single workstation for a single or multiple buildings. TAC products have an advantage over others in that their products are compatible with a majority of other systems in the industry. This advantage gives the customer more options and prevents them from being restricted to another’s technology.

TAC has offices in the United States, Asia, and in several countries in Europe.

For more information on TAC and ACX series controllers

Written by:

Scott Cosby is an Engineering Technician and experienced writer at a state agency in Oklahoma for over 10 years. Mr. Cosby holds a B.S. degree in Geography from Oklahoma State University (OSU), studies in Engineering and Electronic Technology at the OSU campus in Oklahoma City.

© Chipkin Automation Systems 2007

Did you like this post?

Subscribe To The RSS Feed!
To catch many more articles like this in the future, make it easy on yourself and subscribe to me via RSS. You will not regret it!

Do you have a question?
We will do our best to try and solve any building automation, protocol, integration problem you may have

Echelon PowerLine Smart Transceivers

Published by Steven May 8th, 2007 in Echelon and Scott Cosby. 0 Comments

echelon_logo.gifEchelon has developed a premier product for automation applications. The PowerLine Smart Transceivers are described as durable, and low in cost compared to other similar products. These transceivers are capable of communication over either Alternate Current (AC) or Direct Current (DC) lines with varying voltage levels.

This product offers a variety of specific operations including power management, load control, interior and exterior lighting, and the control and monitoring of utilities through Echelon’s power line signaling technology.

A special feature of these transceivers is switched-leg technology. A majority of electrical devices requires a line (or “leg”) and neutral wire. The current comes through the line or leg wire, and the return path through the neutral wire. The wiring styles for most lighting fixtures have the line sent to a switch, then connected to the fixture. The neutral wire’s location is at the fixtures itself. Echelon’s newest generation of switched-leg technology gives the customer a better two-way directional pathway over this wiring style for a variety of lighting types (i.e. halogen, fluorescent, or incandescent).

Another feature is the incorporated Interoperable Self-Installation (ISI) technology, which would be an asset to the home customer when adding perimeter lighting, extensive environmental controls, or pool/spa controls. This simple and easy to use feature requires no additional software or programming by the homeowner. When the devices are plugged in, they will locate one another and configure themselves. The homeowner can make any alterations at any time without extra cost or additional training.

Echelon’s transceivers are part of the LonWorks protocol, which allows the control devices to be in direct contact with each other. This aspect can prevent total system failures, because the system does not rely on a single control device. PowerLine Smart Transceivers have uses in the residential and the commercial sectors. Recently, they have made an appearance in large Korean companies of Samsung and KyungDong Networks for their automation requirements.

Echelon offers other products to further enhance the transceivers including support kits, micro-servers, and others to aid in the customer’s automation needs. Among these are the enhanced design tools for the PL 3120 and PL 3150 PowerLine Smart Transceivers. The mini EVK Evaluation Kit can be used by the engineer to examine the company’s power line technology or develop devices for a project. The engineer can set-up and run a power line based network in minutes and develop new codes with this low-cost kit. The Echelon development support kit is another valuable tool in that its supplies the customer with schematics, PCB layouts, and sample integrated circuits for the development hardware based on power line technology.

For more information see Echelon PowerLine Smart

Written by:

Scott Cosby is an Engineering Technician at a state agency in Oklahoma for over 10 years. Mr. Cosby holds a B.S. degree in Geography from Oklahoma State University (OSU), studies in Engineering and Electronic Technology at the OSU campus in Oklahoma City.

© Chipkin Automation Systems 2007

Did you like this post?

Subscribe To The RSS Feed!
To catch many more articles like this in the future, make it easy on yourself and subscribe to me via RSS. You will not regret it!

Do you have a question?
We will do our best to try and solve any building automation, protocol, integration problem you may have

2 BACnet MSTP devices with the same device ID

Published by Steven May 4th, 2007 in BACnet MSTP and RS485. 0 Comments

I was ask this question to day
What would happen if you had two BACnet MSTP devices with different MAC address but the same BACnet Device ID (Node ID) on the same network and you send a Broadcast Who-is message.

This would be an illegal configuration ( no two devices shall have the same Device ID..) but the rules for address binding say the last one wins. If new information arrives saying “I-AM Device 7″ the old information is replaced.

To understand this answer you must know a thing or two about a token ring networks.
Basically a token ring networks works by passing a token around the network, whoever has the token may send message out, and when they are done with the token they pass it on to the next person in line.

For example
Device A has the MAC address of 0×03
Device B has the MAC address of 0×04
Device C has the MAC address of 0×05

Device A has the token,
Device A responses to any messages it got since the last time it got the token, then sends any custom messages it may have in queue.
Device A sends the token to device B
Device B has the token,
Device B responses to any messages it got since the last time it got the token, then sends any custom messages it may have in queue.
Device B sends the token to device B
Device C has the token,
Device C responses to any messages it got since the last time it got the token, then sends any custom messages it may have in queue.
Device C has the token but there is no one with a higher MAC address then Device C so Device C sends it’s token to Device A.
Repeat.

If you have two different MSTP devices with the same MAC address your network will become unstable and unpredictable results will occur. Both devices will think that they received the token and both devices will attempt to talk at the same time. There will be collisions and you will not be able to determine what device will respond to what poll or what device has the token.

If you have two different MSTP devices with different MAC address and the same Node ID, the device next in line in the token ring will respond first to your requests. This happens because it will be the first device to be passed the token and the first device able to respond. When the token gets passed to the next device ready to respond it will also send a response. any values set by Device A will probably be over written by Device B.

For example
Device A has the MAC address of 0×03 Node ID 7
Device B has the MAC address of 0×04 Node ID 7
Device C has the MAC address of 0×05 Node ID 13

Device C sends a broadcast request for the properties of Node 7
All devices on the network receive the message and Device A and B start to compile a response.
Device C sends the token to the next device in line, this happens to be Device A.
Device A responses to the poll from Device C and passes the token to Device B
Device C processes the response.
Device B responses to the poll from Device C and passes the token to Device C
Device C gets the response from device B and overwrites the results of device A

So inclusion, having two BACnet MSTP devices with the same MAC address will produce unpredictable results and should be avoided. While having two BACnet MSTP devices with different MAC address and the same node ID will produce a predictable result it should be avoided because of the rule (no two devices shale have the same Device ID)

If you have any other questions relating to BACnet or MSTP feel free to contact us

© Chipkin Automation Systems 2007

Did you like this post?

Subscribe To The RSS Feed!
To catch many more articles like this in the future, make it easy on yourself and subscribe to me via RSS. You will not regret it!

Do you have a question?
We will do our best to try and solve any building automation, protocol, integration problem you may have