Security system working with mControl via NPort
So yesterday and today I spent time installing the NPort 5250A Serial to IP Server and hooking it up to my DSC security system. After the hardware was setup, I enabled the “DSC PS” driver in mControl Service Manager and configured it with the right IP address and port. Then I added a new device in mControl Editor. Once done, I was able to arm/disarm the security system without issue. What I like about mControl is that once the hard work of installing the hardware is done, there is no struggle on the automation software side; only add or change some settings/configurations and it just works! Next task is to get the NPort to talk RS485 to my ION6200 power meters and write the corresponding mControl driver.
In the next couple of weeks I will be posting more information on:
- how to create a meter enclosure for your smart/revenue meter;
- how to start writing mControl drivers;
- a project page on how to create you own Arduino power meter reader (the APMR project), that uses a real-time clock (RTC) and RS485/MODBUS.
One thing to note is that I am trying to get the “DSC PS” driver in mControl modified. My security system has 4 partitions and the driver, in its current form, only support 2.
Related articles
- Installing mControl v3 (eco-sustain.org)
- mControl Device Drivers (eco-sustain.org)
Insteon communication issues
Looks like I have some issues with Insteon communication. The mControl log is recording error such as:
!!! PowerLinc possible data loss: 0x02 not found at beginning of data !!! PowerLinc communication error - NAK received (B) !!! PowerLinc possible data loss: 0x02 not found at beginning of data
And the device summary shows a lot of “reachable=false, hops=3″ which is not good. If I change where the Insteom PLM is plugged in then I get somewhat better results. Looks like I need to:
- couple the phases with a SignaLinc hardwired phase coupler;
- a filter out any noise from my computer UPS with a 10A FilterLinc.
Hopefully this will do the trick. I have ordered the equipment and will update you on how I resolve this issue…
mControl Device Drivers
I just finished having a meeting with Ted and Roger from Embedded Automation on how to write device drivers for mControl. It was great that they took some time out of their busy day to meet with me at the SFU Surrey Campus. Now that I have a handle on this I am looking to create a number of drivers that can:
- talk to RS485/Modbus devices, in this case my power meters;
- receive consumption data from the AcquiLite about water and natural gas usage;
- update my ambient display, Elements of Consumption.
These devices that I will be adding to mControl will allow me to start monitoring my energy consumption more closely. I will using a new service in mControl v3 to capture and store data in a database. That data will be analyzed by machine learning algorithms to find patterns of usage and to identify what appliances were used. If you are interested in learning more about this project feel free to contact me. Soon I will announce a way for anyone that uses mControl v3 to participate…
Insteon equipment is here
Well, I just received my shipment of Insteon devices. Now I have to plan out where to install them. I only ordered a small sample to install around the house, these include on/off switches, dimmer switches, iMeters, and modem. Next week I plan to set up mControl as my home automation system to communicate/control the Insteon devices. I am still waiting for my Dell Zino to be delivered. Version 3 of mControl will be out soon, but in the mean time I will be using the Beta 2 version. I will have a post on how the mControl install when, so stay tuned…

