-
Notifications
You must be signed in to change notification settings - Fork 130
X10 Homebuilt signal analyzer
Lieven Hollevoet edited this page Sep 22, 2014
·
1 revision
I recently ran across a problem of unexpected activity of some X10 devices - turning on logging in my software package did not help since nothing out of the ordinary was being sent - I wanted to see actually what was on the line. Like most people that have been using X10 for a while I have a drawer of unused or out of date X10 modules that I cobbled together with some software and spreadsheets to make a X10 Line Protocol Analyzer.
- An old laptop to run the software. (This is for a windows XP solution).
- An old IBM Home Director CM11A Module
- A copy of IBM Home Director Software (Similar to ActiveHome)
- A SerialMon shareware application version 1.4 to generate logs.
- An excel spreadsheet to analyze the logs. (I had to write it in formulae - complex but possible, should have written something in perl in retrospect).
- The laptop had the IBM Home Director software installed - which caused a server process that monitors the serial port #1 to start up a boot.
- SerialMon shareware was installed.
- Laptop was rebooted.
- The CM11A was connected to the laptop port #1 and plugged into the wall outlet.
- SerialMon shareware was started and the preferences menu was used to set the "cable type" to #6 which is software "tap" on a live serial port.
- The serialMon software was set to record and also to drop logs of the traffic every hour.
- The logs were loaded into the spreadsheet and the traffic displayed.
- =image:screenshot_copy.JPG width="800" height="579"