What happened to the serial port on my laptop? Indeed it seems that our PCs are upgrading faster than the industrial devices we still use. Being an Industrial IT company, on a daily basis we still have to use HyperTerminal and other serial based software to configure devices and get information out of systems such as belt scales and gateways.
So what if I need to get a device that speaks serial onto an industrial Ethernet based protocol such as PROFINET, MODBUS TCP, EtherCat or Ethernet/IP? Well for that we can use the Anybus Communicator, which we have spoken about before. That is a protocol converter. Incidentally, this device is easily configured using a serial port, but for that I need to have a serial port on my PC. (The new generations of these gateways are moving to USB, but what about all those thousands that are in the field already?)
One solution is too buy a USB to Serial Converter, but anyone that has used one of these will most likely agree that they can be quite troublesome. So what’s my other option? My other option is to get an Serial to Ethernet converter such as the Anybus Serial Server. It can convert RS 232 to Ethernet or RS 485 to Ethernet. It’s also so easy to use:
Step 1) Power it up with 24V and connect it to your LAN or to your Ethernet port
Step 2) Install and run the free AnybusIP config tool. It scans by MAC address so you can use this to discover what the IP address of your serial server is. Here you can change the IP address and open up its web interface from your browser.
Step 3) Click on "Configuration" and configure the ports you are going to use. I used port 2000 for the RS-232 port, and port 2001 for the RS-485 port. The server is now ready to use.
Step 4) Now we have to tell our computer where these virtual com ports are. Install and run the Serial/IP driver. You can find it in the Control Panel.
Step 5) Choose your COM port and fill in its IP address and port number.
Here’s a tip: Choose port numbers that are less than 10!
Now I’m ready to use my COM ports. In the below example I am now able to program my Anybus Communicator through a LAN with either COM7 or COM8. Since COM 8 is actually an RS485 port, I won’t be able to use that to program my Anybus communicator, but it is useful for other applications. In our Anybus Communicator and Modbus training, we use it to run a slave simulator through this port.
Making Serial COM ports available through a LAN, means that you are able to program devices that are located long distances away. We used the Serial Server to program an Anybus Communicator which was located on a distant conveyor belt, from the comfort of an air conditioned control room.
Popular posts from this blog
Last week IDX were called to site at a large commercial residence building in Pretoria, South Africa. Where our client was implementing an IoT solution for remote monitoring and control of various HVAC and power systems in the building. The control system the SI chose in this case was a Modbus enabled Industrial Micro PC called the Revolution PI. The client had Modbus sensors connected to boilers, air conditioning systems, ventilation systems and power meters. The Modbus communications between the controller and the sensors were intermittently failing due to various installation and implementation faults: 1. Earthing and Shielding Within any fieldbus communication installation, one of the requirements to ensure uninterrupted operation is to implement adequate grounding and shielding techniques. Effective grounding and Shielding help to prevent electrostatic and electromagnetic pickup, which can lead to failed communications. Some of the shielding and grounding req
Tag management of real-time data systems can prove challenging. As an industrial IT company we frequently come across the problem where tags need to be migrated from one system to another or where tags need to be synchronised and maintained between systems including historians. Generally, this ends up being a manual process, often involving Excel and much diligence and patience of the maintainer’s behalf. IDX Unifig was the first incarnation of a tool we designed with the aim to simplify the migration and management of tags between systems. The tool worked, but with as with most first editions of software tools, we could see the need for improvement and refinement of the approach used. Thus Tag Manager was born, and has become the key stone in the IDX 8 software suite. All other IDX 8 modules, such as Data Exchange, Alarms and Events and the Historian use Tag Manager to store and reference tags. The comparison result we like to see - no changes. Tag Manager employs a plug
Quick guide to get access to the P+F advanced diagnostic module via RS485 and COM converter. In order to do this, you need an RS485 converter which can convert RS485 to either ethernet or USB. I used a device from HMS (Anybus) called the Serial Server ( AB7701 ). This device connects to RS232, 422 or 485 and makes the data available over ethernet to your computer using a virtual com port. Connect the converter to the Diagnostic bus connection on the Pepperl & Fuchs fieldbus power hub 1. Once you have the com port available on your PC, Check the comport number via “manage my computer” Make sure that the FieldConnexd Diagnostic server (FDS) is running. Go to “Windows button”>“All programs” > “Pepperl+Fuchs” and start FDS control center In case the FDS is not running click onto “Start FDS” (in case it is running nothing is left to do here) click onto “Hide”. To avoid that this piece of software will be forgotten in future click onto settings and choose un