![]() |
|
|||||||
| Using INSTEON with mControl Tips and tricks on how to use INSTEON with mControl |
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
||||
|
||||
|
Background
There are essentially two ways to talk to an INSTEON network: - Smarthome INSTEON PowerLinc 2x14x Power Line Controller (PLC) - Smarthome INSTEON PowerLinc 2x12x Power Line Modem (PLM) This discussion is related to the former devices (PLCs). This includes: - 2414S - PowerLinc Serial - 2414U - PowerLinc USB - 2814S - PowerLinc (Timer) Serial - 2814U - PowerLinc (Timer) USB By default, these INSTEON PLCs include an embedded software engine called the “SALad CoreApp” or “SALad TimerCoreApp”, which performs the following functions: - The CoreApp acts as the bridge between the adapter's serial/USB interface and the INSTEON firmware - The CoreApp can manage timer events - The CoreApp manages links to other devices SmartLabs continues to refine this "CoreApp" and it has become very stable, but occasionally, and especially older versions, could fail. How to tell if your PLC is not working properly There are essentially two types of issues that can arise with the PLC: 1. USB communication problems Occassionally, after heavy communications, USB-based PLCs may stop responding. While mControl can continue to send messages to the PLC, the PLC may not send the messages out over the INSTEON network and no incoming INSTEON messages are delivered back to the PC/mControl. How to read this in the log files: mControl sends Automation Commands, but no incoming messages are seen In this case, often all you need to do is unplug the PLC and plug it back in.2. CoreApp corruption problems Corruption of the "CoreApp" can cause adverse symptoms, such as: - Failure to receive incoming commands, particularly X10 commands. For example, you may no longer receive proper status updates. - Failure to send commands from mControl. CoreApp failure can be accompanied by “flashing” of the PowerLinc’s LED at a continuous periodic rate of approximately once a second. This should not be confused with general flashing/blinking while sending/receiving commands. How to read this in the log files: mControl sends Automation Commands, but only INSTEON Events seem to be seen. In the case of CoreApp corruptions, it may be necessary to "factory reset" the PLC.Factory resetting the PLC If the PLC has been corrupted, then it is possible to reset it back to factory conditions using the following steps: 1. General reset of the PLC Often, the only step required is to reset the PowerLinc adapter. This will restart the CoreApp. To do this, unplug the PowerLinc adapter for a minimum of 10 seconds, and then while holding down the Set button, plug in the PowerLinc adapter. Let go of the Set button 5 seconds after plugging it back in and it will complete its reset. 2. Re-download the CoreApp to the PLC There are a couple of ways to re-download the CoreApp to the PLC: Use HouseLinc software - Smarthome sells this software utility to manage your INSTEON network. We recommend this software utility, as a complement to mControl, because of its INSTEON network diagnostics and device linking features. Use the SALad Downloader software - Smarthome has a free utility for strictly downloading the CoreApp - use the following instructions for this case: (a) Download and install the “SALad Downloader” utility - The utility can be found here: http://www.embeddedautomation.com/IN...der-v1.0.2.exe - Install (Run) this utility (b) Copy the attached files to the following locations – it is assumed that you have previously installed the SaladDownloader (as per the previous step): - Download the following zip file which contains the necessary files to reset your controller: http://www.embeddedautomation.com/IN...et%20Files.zip - Copy the “plc3-2D.ump” file to the C:\Program Files\Common Files\Smarthome\DeviceManager\maps directory - Copy the “timercoreapp12.slb” file to the C:\Program Files\Smarthome\SALad Downloader directory (c) Start the SALad Downloader utility by pressing the Start button on your desktop, then select “All Programs …”, then the “Smarthome” folder, then the “SALad Dowloader folder” and finally selecting the “Smarthome SALad Downloader” utility. Two windows should open – select the Smarthome Device Manager window – because this will allow refined control of the download utility. The Smarthome Device Manager may also be accessed from your Windows system tray (bottom right of your screen). (d) With the Smarthome Device Manager window open, from anywhere within the “General Log” tab’s text window, type “DM” and this will open the command line for manual command entry. (e) Type the following: downloadCoreApp=timercoreapp12 – this will download the latest version of the CoreApp (v1.12). You will see it download the new memory information, several percent at a time - wait until it is complete. (f) Reset your PLC again - unplug the PLC for a minimum of 10 seconds, and then while holding down the Set button, plug in the PLC. Let go of the Set button 5 seconds after plugging it back in to complete the reset.3. Restart mControl Use the mControl Service Manager to restart mControl to reinitialize with the updated PLC adapter. Last edited by Ted Singh; 08-20-2010 at 09:08 PM. Reason: Grammar; Formatting; Fixed links |
|
#2
|
|||
|
|||
|
(b) Copy the attached files to the following locations – it is assumed that you have previously installed the SaladDownloader (as per the previous step):
- Copy the “plc3-2D.ump” file to the C:\Program Files\Common Files\Smarthome\DeviceManager\maps directory - Copy the “timercoreapp12.slb” file to the C:\Program Files\Smarthome\SALad Downloader directory Ted, How can I download these files? (These links do not work) Thanks! |
|
#3
|
||||
|
||||
|
Polfliet,
Fixed the links. Ted |
|
#4
|
|||
|
|||
|
Thanks Ted. This worked. I now have two-way communication and am able to see my paddle presses.
However, I am still experiencing a peculiar problem: I added one device, an Insteon 2476D within the mControl IE GUI. I could control it with mControl and the status would update on paddle presses. I recycled power to the switch (removed power for 12+ seconds). Now when I press On (paddle up) it takes 3 seconds for the level indicator to move to the 2nd position and it stays there. If I press Off (paddle down) it takes several seconds, then turns off. Fast On and Fast Off work fine. I did not change any of the default settings from within the Advanced tab (level/ramp rate, etc) when adding the device. Please advise. Thanks! Chuck |
|
#5
|
||||
|
||||
|
Polfliet,
I think it lost the link. I would relink it. Ted |
|
#6
|
|||
|
|||
|
Relinking didn't help. If I manually reset the ramp rate, this fixes it. It appears the ramp rate is being adjusted to max level whenever i add an insteon dimmer to mControl and later reset the power to that dimmer(s).
Is there a line of code in mControl to prevent any changing to the local ramp rate? |
|
#7
|
|||
|
|||
|
Can I provide a copy of the log or anything that would help?
Thanks Ted. Chuck |
|
#8
|
|||
|
|||
|
If, when I try the above procedure, I get an error message that the PLC is not attached or not responding, do I assume the unit has been damaged or is no longer able to be corrected?
|
|
#9
|
|||
|
|||
|
I did buy a Venstar thermostat T1800 and some access points. I couldn't figure out how to get connected to the thermostat thru a PLM 2412u PowerLinc Modem?
|
|
#10
|
|||
|
|||
|
i realiced all the steps, but the paddles in the insteon not work with the mcomtrol. Thanks
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|