Brian H

Sounds OK. Was just double checking that none of the other signals where connected to anything. As two of them are the unused TTL In and Out signals.

OK. I thought it was a blank database. Not using the wiping it clean command in this case. Sounds like a good way to go. If you have not yet. Trying a UDI contact ticket. May get you a more definite answer. https://www.universal-devices.com/contact-us/ https://www.universal-devices.com/polisy/ Going to sound like a broken record here. The unused wires on the network side of the adapter are not touching anything or are cut off? I did not see any valid Insteon messages in the long string you posted. The two 02 entries did not have a valid message entry after the 02.

Thanks for the added information. V1.2B, firmware 9B is not a later 2413S. Date codes keep changing so 1252 may not be what I think is week 52 0f 2012. Since it is a new setup. You could try a 02 67 software reset and then see if 02 73 gives a different answer.

I have had a few power supplies on varied ISY controllers fail over time. Flashing power and other LED flashing was one of the symptoms. 5V to 30V is what the WIKI said. Last time I looked UDI was selling a 12V 1 Amp replacement.

Is their a white label on the back of the 2413S? With the hardware revision and date codes? 03 11 is a 2413S PLM. The firmware 9B is not the latest 9E. The only 9B I have in my stash is a hardware 1B.

The long string does not look too good and maybe confusing or over loading the. PLM The 02 60 is the Polisy checking for a PLM. Three times. The 02 73 get IM Configuration "[RX] 02 73 80 00 00 06". Unchanged PLM is 02 73 00 00 00 06. Indicates the 02 6B Set IM Configuration modified the way the PLM acts. The value of 80 indicates that linking with the Local Set Button on the PLM is disabled. Only the controller connected can do linking and probably is fine. For 02 60, I got: [TX] 02 60 [RX] 02 60 21 31 48 03 11 9B 06. Three digit module ID, 03 category, 11 subcategory, 9B firmware version, 06 ACK command processed and reported correctly.

OK Will see what you find out. I did a ring out of the cable in the box again. It matches what you posted for your cable.

If you want the BusyRats PLM test program let me know. It is extremely crude and you manually type in the commands and then send and receive messages from a PLM. Information is in the PLM Developers Guide that can be found in a few locations. The same basic commands used by the DockLight Scripting entries. I tried the DockLight program and it seemed to also run the program fine. So the scripting version may not be a requirement as it didn't complain. The X10 commands should just be sent and a 06 ACK on the message back. I have an X10 module I can test with to see if they also where being sent messages.

The script I used is for the DockLight Scripting. My file is PLM.ptp. I found a way to modify the one of the Smarthome versions. For my use. Running the programs should open DockLight Scripting to the evaluation page. Just click OK as you will be in the limited evaluation mode. If you are using COM1 you should be fine. If you have a different COM port. Tools Project settings and pick your COM port and then OK. Get Version 02 60 should get a reply back. With the 02 60 then the three digit module ID, the category, sub category ID's, firmware version, ending with a 06 ACK if processed properly. Get IM config 02 73 should return a 02 73 00 00 00 06. If the PLM has not been reconfigured. 02 69 First Link in database should return the first link in the PLM. If empty the reply is 02 69 15. Get next link 02 6A will return the next link or a 15 if empty. Look out for the Reset 02 67. It is the command to factory reset the PLM through software PLM.ptp

Did you turn off both units and then start the PLM first. So when the Polisy started up it found the PLM? A Factory Reset will set everything back to blank state with no links in the link database. I don't have a Polisy so I cant tell you how to back it up. There are two PLM test programs we in the Developers Group got but they need the PLM serial cable, a serial port on the computer. They used the basic HEX commands to do things like software Factory Reset, test for a response from the PLM and dump a link in the link database. If you have to use a USB to Serial Port adapter one only used the lower COM addresses.

One point that may or no apply. The PLM only used three connections. Common, RS232 Send and RS232 received. There are other connections on the PLM that should not be connected. RJ45 pin 3 and pin 6 are TTL. If connected to the wrong thing may effect the PLM operation. Are you only connecting the two RS232 signals and Common? Cable in the box. DB9S pin 2 to RJ45 Pin 1, DB9S pin 3 to RJ45 pin 8, DB9S pin 5 to RJ45 pin 7.

I have had a few wall warts fail. With my assortment of UDI products. ISY99i and ISY994i. One was so weak when I did a power on reboot. All that happened was the LEDs started to flash in a cycle. I ended up putting a LightDim stick on to reduce the Power LED brightness. I used the original 50% to 80% version.

One other possibility is the Starlink Power supply is making power line noise or is a signal sucker. Especially if the Insteon modules are the older power line only model. Is the Starlink supply connected on the same power feed as the ISY994i and PLM? A PLM link count may also show something. Though it can be wrong if their is any Insteon messages during the count.

Sounds like a big improvement. Both switches have to be an Insteon or Icon for both to work correctly. I used an Insteon switch module and a mechanical switch. In my case I wired both travelers to the Red output. So either mechanical setting still worked with the Insteon module and the switch did nothing. Glad it works OK for you.

If it is a 2477S Dual Band Module. Page 12 gives the Factory Reset sequence. Remebber if it is in a 3 way setup. All the setting are gone and it will function like a new switch with no links. http://cache.insteon.com/documentation/2477S-en.pdf

Yes

Depending on its age and model number. There was a period of time where the 2476S Relay style and 2476S dimmer style SwitchLinc. Had a bad run of tact switches. The paddle would activate the switch and it would click but not make internal contact. Some only the Off or On switch and sometimes both. Remote controlling was perfectly fine. Smarthome actually gave us a 7 year warranty on that series of models. Your description sounds like it maybe a tact switch. Sometimes fine, some times bad and some times wiggle the paddle it would work. I did see a how to on replacing them and I believe someone here has done it.

I still use the query all. As I have a intermittent 2456S3 Appliancelinc. That occasionally gets locked up. I believe by power line noise.

The PLM has a Link Database Memory in it. If it gets corrupt it can cause communications issues. Power cycling and resets can sometimes get a weak power supply going for a short while. A weak power supply may also effect the power line signal. I honestly can't see a rebuild changing the processor or RF control chip as both are programmed with firmware only Smarthome has access to. Unless salvaged from another PLM or they mistakenly didn't set the protection bit. So you could read the firmware back into a file. The PLM does have two 5 position programming connections. Main and Rf for the chips. The memory chip and RS232 chip probably could be exchanged. Long thread here on how we changed our caps and symptoms. https://forum.universal-devices.com/topic/13866-repair-of-2413s-plm-when-the-power-supply-fails/

The 2412U has the same ~2000 link database in it as the 2412S. It is probably like the 2412S and the ISY994i. The ram is slower and many had problems around 800 Links. If the PLM database was fresh abd all the devices had to be added. Every link is every device has to be updated with the new PLMs address. Along with the modules added to the new PLM. The 2413PLM is serial as pointed out. Just used a RJ45 network style cable. Some here have made a cable to go from the 2413S PLM to a DB9 serial type connection, if needed.

If the power bar had a surge and noise suppressor in it. The bar can also absorb power line signals as noise. I had one with a capacitor across the line and it killed the signals. Watch your power needs. The X10 XPPF is only a 5 amp filter or the XPF 20 amp one is quite large. The Smarthome FilterLinc was 10 amps but hard to find these days.

I took another look and the Licon brand was in my 4.? versions. If it is a 4.? with the cap parallel to the board. You should sill be able to use the original sized 470mfd/35V. I had one of the 30 volt Zener diodes short. Under the cap. I got lucky and replaced it and the cap for good measure. Since it is around a 30 volt supply. The 35 volt cap should be fine. Depending on size a 50 volt would also work with a larger voltage tolerance but probably a larger size. Longer or fatter depending on what you try to use.

I had a few go bad myself. One was On and started to pulse on and off at about a two second cycle. Mine was a green cased NOVER brand cap. It is not a high frequency supply. It is a half wave circuit. 30 cycles on the cap. Not like what was in the PLM and another few Insteon modules. I just got a good quality Panasonic 470mfd/35V designed for power supply use. Panasonic EEU-FC1V471 but any good brand should be OK. They where taller but still have room to close the top cover. This is the Icon version of the V1.4. The V4.? used the same capacitor just a 100% different design. I have used that capacitor in a V4 and my V1 modules. In the V4 it is sideways parallel to the board and has some component glue holding it. https://efundies.com/guides/insteon/hardware/paritial_schematic_of_insteon_icon_on-off_module/icon_on_off_schematic.png

You may have a power line issue. Any new devices like a cell phone charger or any other electronic devices? Some are known signal suckers or power line noise makers? Unplugging a device and seeing if things chance is one test. A deteriorating presently installed device could also be a factor.

Are you using the ISY Launcher program? It picks the correct information to access the ISY994i and no longer need a different start program with the proper data for each version.