Houselinc
From Smarthome
HouseLinc 2 is a software application that allows you to set up and manage all the home automation devices in the home. HouseLinc 2 runs on Windows based PCs. The current version, HouseLinc 2, requires that a powerline interface (PowerLinc) be connected to the computer, either by means of a USB cable or Serial cable. HouseLinc 2 also requires that the PC be running in order for timers or triggered events to function.
Contents |
Product Revision History
HouseLinc Desktop was first shipped in August of 2006.
- 1.00.104.186 - released in 2007
- HouseLinc 2 - released in October of 2008 -> HouseLinc 2 - INSTEON Desktop Software User's Guide
- HouseLinc 2.0.1.76 - released on September 10, 2009
- Added email alert feature. Users now can set up an event to send email to their email accounts.
- HL can now download Devices.xml automatically without re-installing it.
- Prompt to synchronize devices upon startup.
- Added a new driver for I/O Linc with Firmware 0x33 or newer to support longer momentary delay settings.
- Digitally signed HouseLinc and the installer to identify SmartLabs as the publisher on Windows Vista and newer.
- Centralized data (device definitions, settings and logs) location to better support online updates.
- Removed 9 minute ramp rate option as the Firmware no longer supports it.
- Improved Thermostat Adapter User Interface.
- Improved Installer wizard.
- Fixed bugs in Diagnostics tool.
Product Page(s)
http://www.smarthome.com/2412UH/HouseLinc-2-INSTEON-Desktop-Software-w-USB-Interface/p.aspx
Tips and Tricks
Here is a little tech-tip for HouseLinc 2 users, who may not care for the current "device found" or other audible sounds and alerts from HouseLinc.
Locate the sound .wav file you prefer. Search for *.wav on your PC or search the web for many free files. (use only reputable sites, or do virus scan on any file downloaded)
Place the file in C:\Program Files\SmartLabs\HouseLinc2\Media, if HouseLinc was installed in the default directory. If not, then modify using the directory that was used during install.
Rename the file to be replaced to something new, for example I renamed "DeviceFound.wav" to "DeviceFoundfoghorn.wav".
Rename the new file to replace the old sound file, I used "tada.wav" and renamed it "DeviceFound.wav".
Now when I autolink a device I hear the familiar windows 'tada'.
=
Releasing COM Ports in Windows Operating Systems
Overview: Windows operating systems will assign COM ports to devices that have been attached to the computer. This most commonly happens with “virtual COM port drivers” that are actually USB products, but “look” like COM ports to the computer.
Power Line Modems with USB ports work similar to this.
When the PLM is first connected to the computer, the operating system automatically assigns a COM port number. This COM port number might be high, such as COM 11. A problem can arise if the software only allows a limited range of COM ports, for example, COM 1 through 8. Additionally, each PLM USB product contains a unique serial number burned into the USB interface chip by the IC manufacturer. If different PLM USB interfaces are connected to a computer, each one attached will cause a new COM port to be reserved by Windows.
Solution: It is possible to release Windows-reserved COM ports from previously released hardware that is no longer in use.
1. Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
2. At a command prompt, type the following command and then press ENTER: set devmgr_show_nonpresent_devices=1
3. Type the following command at command prompt, and then press ENTER: start devmgmt.msc
4. Click View > Show hidden devices. This will display devices that are not connected to the computer but Windows still reserves space for them.
5. Go to Ports (COM & LPT) and expand that section.
6. Remove all devices in the list of ports that are grayed out but have a specific COM port number assigned to them. Right click on the grayed out device, choose Uninstall, and then OK in the dialog box that appears.
7. When finished troubleshooting, close the Device Manager.
8. Type exit in the Command Prompt
==
Where can I find ports in the registry?
You can find the information on FTDI VCP devices in the registry under the following paths -
For Windows XP and Windows 2000:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\FTDIBUS\VID_VID+PID_PID+Serial_Number\00 00\DeviceParameters\PortName where VID is the VID used, PID is the PID used and Serial_Number is the device serial number.
=
(The procedure below was copied from a pdf file that had quite a few images. The images did not get copied yet, more to come. Please use the best you can)
How to Configure a Computer to Not Assign a COM Port for Each PLM-USB Connected
Explanation: When testing Power Linc Modem interfaces with a FTDI USB chip, the Windows operating system will attempt to assign a dedicated COM port for each PLM-U connected. This can cause the COM port assigned to be beyond a software program’s addressable range (i.e. COM:9, COM: 73, etc.)
This procedure will inhibit Windows from assigning more than one COM ports for each USB channel on the computer.
This procedure has only been tested on Windows XP-operating systems although it is expected that Windows 2000 and Vista operating systems will be similar.
At the conclusion of this procedure, all PLM interfaces with the FTDI chip and are using the original unmodified USB VID and PID will use the same COM port.
Please note that if the USB cable is plugged into a different port on the computer, a new COM port will be assigned.
Resources Unzip the drivers, and utility program to the computer Required CDM 2.02.06 Modified.zip
== HouseLinc can use this driver (you can also download the latest from the FTDI website):
http://www.insteon.net/software/HL2/drivers/CDM%202.04.06.zip ==
References: FTDI Knowledgebase:
http://www.ftdichip.com/Support/Knowledgebase/index.html
AN232B-07 Configuring FTDI's VCP Drivers to use Location Ids http://www.ftdichip.com/Documents/AppNotes/AN232B-07_LocIDs.pdf Configuration
Step 1: Run Ftclean.exe (http://www.insteon.net/software/HL2/drivers/FTClean.zip ) to remove any old FDTI drivers on the computer. Leave the PID field blank and click “Clean System”
Note: the program asks you three times if you want to continue or cancel.
Be sure to select the right options:
Click OK
Click Yes
Click No
Run this program twice to insure all traces of the old driver are removed.
Step 2: Remove any old and reserved COM ports by Windows.
Start “ComPort.bat” to run a MS-DOS batch program that will expose reserved and hidden COM ports.
In the example below, there are reserved and hidden COM ports on this machine before removal.
Here are the commands that are sent.
set devmgr_show_nonpresent_devices=1
start devmgmt.msc
echo After COM ports are deleted
pause
exit
Right-Click on the hidden COM Port to remove and select “Un-install”
After removing reserved COM ports
Close Device Manager and the MS-DOS batch file window if it is still open:
Step 3: Installing new drivers
It is important that a set of specially modified drivers be installed for this procedure to work. As of October 2007, use the drivers in this zip set from
SmartLabs: CDM 2.02.04 Modified.zip
Plug in a PLM–U module. The system will auto detect it and ask for drivers: The “Found New Hardware Wizard” window will open Important: Check “No, not this time”, then click “Next” Select “Installed from a list or specific location (Advanced)“and click “Next”.
Un-check “Search removable media” Browse to the location of the drivers on the computer. Click “Next” This warning will appear because the drivers were modified by John to help prevent runaway COM ports. Click “Continue Anyway”.
The driver installation will continue and take you to this screen: Click “Finished” The computer will now detect a new COM port: The computer will want to install a second set of drivers. Proceed exactly as before and install the drivers a second time. At the conclusion, it will display this screen: Click “Finished”.
Windows XP shows the following in the lower right corner: Follow the recommendation and re-boot the computer. Click “YES”
Step 4: Check PLM-U COM port is present. Upon re-start, check Device Manager to make sure the computer has assigned a COM port for the PLM-U that was plugged in originally. Here is an example: COM 3 is the PLM-U At this point, the new driver is installed and plugging in more PLM-U will still cause Windows to assign new COM ports:
Step 5: Modifying the Registry file to ignore hardware serial numbers Run “RegEdit” from the Start, Run menu Go to this key location: HKEY_LOCAL_MACHINE \SYSTEM \CurrentControlSet \Control \UsbFlags In this example, there is already an entry to ignore hardware serial numbers of some other USB device. You will need to create a new enter for the computer to ignore the PLM-U interfaces.
Create a new Binary Value:
Click Edit
Select New
Choose Binary Value
Change the highlighted “New Value #1” to “IgnoreHWSerNum04036001”
Page 12 Preventing COM Port Runaway
Right click on “IgnoreHWSerNum04036001” and select “Modify”
Type in “01”
Click OK
It should now look like this: Exit the Registry Editor.
Restart the computer and from now on, the computer will ignore the hardware serial number burned into the USB chip in the PLM.
