Using a PLK-DMS with Netlinx?
gravityhammer
Posts: 65
I recently picked up a PLK-DMS to tool around with at home. I connected it to my NI-3100 with ICSNet, and it comes up. I see it in my online tree at device #13. If I try to load a test file, though, to 13:1:0, it fails. I've seen references to setting the PLK stuff to 6001+ device numbers - if I changed the device address to 6001, sending the kpd file to 6001:1:0 also fails.
What does it look like I'm doing wrong?
What does it look like I'm doing wrong?
0
Comments
You then need to declare the real device of each dms and one virtual per dms in your program, declare two variables for name of kpd file (that you have uploaded through ftp in the master) in that way: Be very careful about name of file !
and then add declaration of module:
Vincèn
The KPD file has to be loaded into master, not into DMS !
Vincèn
Are there different steps to do to load the .kpd file into the master? Currently, I'm going to the "file transfer" dialog and loading everything from there.
Not sure it still works that way with latest release of NSX ! If you do it with NSX, you should setup to load the file at 0:1:0 as it's supposed to be stored in master and not in DMS ! If it doesn't work, just use an FTP client (server: ip of your master, login: NetLinx, pass: password, be careful to respect the case) and then transfer your(s) kpd file !
Vincèn
The way I deal with addresses is I hook them up one by one, look at the device tree (waiting for them to show up. It can take a minute or so) then right-click on whatever device they show up as and change it to what I want it to be. It doesn't matter 'technically' what device number they are set to as long as they are not in the virtual device range (over 32000 or so). I tend to follow AMX's recommendation and use 600X. But have a couple systems where they are 601~620 and even 11000. It was one of those cases that it was just easier to change the program...
Feedback is a bit of an issue in that they just don't seem to like to be told what to do too much.
Clients seem to want to too much on them and quickly end up with crazy interfaces that can be many levels deep due to the relative lack of buttons. I always try to keep expectations pretty low on them and when successful, the clients like having them around.
One more piece of advice, put the power supply on a good power conditioner/UPS. They are fairly finicky with noisy power.
E