PLK-DMS
Prodigal
Posts: 90
I've never worked with these before and had to update an old system that wasn't created by me.
The system was running some very old Panja controllers with a PLB-AS8 Audio Switch from Landmark. The house has 5 PLK-DMS keypads, they are all connected to each other.
Basically 1 cable went out of the controller to the PLB-AS8 and from here to the 1st Keypad, from the 1st to the 2nd and so on.
All till a RF device that works under ICSnet aswell, wich has a conector on the end, to finalize the network
Problem is that it doens't have any ICSnet HUB.
As I've read on some topics, everyone uses HUB's to connect the Keypads, altho this system wasn't connected that way.
I've installed a new NI3100 using the same concept as it was before, and I'm constantly having problems.
A lot of connection losses. And then they simply stop working. After some time (30min or 1h) they restart working, till they loose connection again.
Is the HUB totally necessary or is there another reason for this to happen?
The system was running some very old Panja controllers with a PLB-AS8 Audio Switch from Landmark. The house has 5 PLK-DMS keypads, they are all connected to each other.
Basically 1 cable went out of the controller to the PLB-AS8 and from here to the 1st Keypad, from the 1st to the 2nd and so on.
All till a RF device that works under ICSnet aswell, wich has a conector on the end, to finalize the network
Problem is that it doens't have any ICSnet HUB.
As I've read on some topics, everyone uses HUB's to connect the Keypads, altho this system wasn't connected that way.
I've installed a new NI3100 using the same concept as it was before, and I'm constantly having problems.
A lot of connection losses. And then they simply stop working. After some time (30min or 1h) they restart working, till they loose connection again.
Is the HUB totally necessary or is there another reason for this to happen?
0
Comments
Assuming you have everything connected properly (have you checked your wiring?) you must have a failing device. If you have a DMS diagnostic keypad then run the tests. Otherwise try starting at the beginning of the chain and remove all devices except for the first one. Put the terminator in this device. Continue adding one device at a time until you find the problem piece while moving the terminator to the last device each time you add.
My guess would be that this system always had this problem, and the Landmark "handled" the dropouts. I wired a few of my early Landmark jobs that way, and they worked well enough to be functional, but we found very quickly that re-wiring them made the system far more responsive and reliable.
I agree that if you can wire them in home run config, that would be best.
Also - check the voltage that is driving them - we had an issue with the KPs being powered by the Mic Hub and voltage seemed to be low and was killing keypads. I believe voltage should be 12V, as I recall although someone else noted 10V - I stand to be corrected. I WAS told by tech support that minor fluxuations of voltage can mess them up.
Enjoy 'em if you can get 'em working! They are still my favourite - for features and value for $$$
Cheers!
So If I understood this well (my english can be a little sloppy some times.. ok, maybe a lot) the best way is to rewire every single DMS to a hub and terminate them all.
If that is the option.. god, I can't even see this being possible since the person who installed it passed the cables in the most imaginative ways.
That would be the preference, but if you can't, you can't. Re-check all the connectors, make sure they are CAT 5 compliant; make sure each DMS that doesn't have a loop coming out is terminated; make sure all your voltages are good.
In the case that it's totally impossible to run new cables, I'll try to update the Keypads for some new MIO that use AX-Link, since the Daisy Chain is already created.