IDX has been a certified KNX training centre since 2011 – offering both Basic and advanced courses. Due to our vendor neutrality, we have also become known as a valuable source of independent advice and knowledge in the building automation industry. In 2013, IDX was invited by the KNX association to become a certified KNX test lab. After a year of preparation, and following a rigorous on-site audit by the KNX association, IDX succeeded in achieving the status of certified KNX test laboratory. In terms of our service offering as a test laboratory, IDX is able to offer interworking testing according to volume 8/7/1 of the KNX standard. Our hourly rates are extremely competitive, and we are committed to offering service of the highest quality. Although based in South Africa, we can accept devices for testing from all around the world.
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
In this blog, I will discuss the steps involved in getting the Netbiter to record and display values coming out of the ComAp Generator Panel, so that one can do remote monitoring and control of the generator. The Netbiter Model used in this case is the EC220 and the panel used is the InteliLite AMF 26 P. The steps followed here can be applied to any MODBUS device due to the generic nature of the Netbiter. S tep 1 - Physical Connection Check that the Control Panel has a communication module attached to the back of it. You will need to establish the medium (RS458/RS232) and the protocol spoken (MODBUS RTU/ASCII) - all of this information will come from the user manual of the generator. Finally confirm the communication settings (baud rate, parity, stop bits, etc) - these can sometimes be changed so check what they are on the actual panel. In this case, we have the following settings: MOUBUS RTU over RS232 (you'll need an external converter to convert the RS232 to RS
Time to dust off the cobwebs and do some "legacy" development! In this blog, I'm going to show you how to get to a point where you can start writing Java code on the HMS Anybus Communicator. I find that it doesn't matter what language you code in, the tricky bit is getting to the point where you can simply create and run the time-honoured "Hello World!" program. Using new editors, sorting out dependencies, making physical hardware connections can take up a big chunk of your time. First, some information on the hardware platform: The Anybus brand from HMS contains hundreds of gateways (or protocol converters) that can be used to convert between common industrial communications protocols such as PROFIBUS, MODBUS, Ethernet/IP, ControlNet, DeviceNet, PROFINET, CANOpen, J1939, etc. Check out anybus.com for a full list of protocols supported out of the box. Using these gateways you can for instance read registers from a MODBUS device and make them available