ELKM1 / UPB / Upstart Implementation

[mseicshn]

Hey Guys. I've installed the PIM to the ELKM1 panel. Registered the device. Installed 2 light SA light switches. Downloaded and installed Upstart. Used Upstart to configure the 2 switches. Upstart has also found the PIM.

OK. I can control the switches with upstart but not through the elk panel. the elk pim's lights seem to be indicating the proper signals. When I send a on/off signal through ELK software I can hear the Pim buzz and see the indicator turn red... but the light does not turn on or off. any ideas?

 

[standon]

Hey Guys. I've installed the PIM to the ELKM1 panel. Registered the device. Installed 2 light SA light switches. Downloaded and installed Upstart. Used Upstart to configure the 2 switches. Upstart has also found the PIM.

OK. I can control the switches with upstart but not through the elk panel. the elk pim's lights seem to be indicating the proper signals. When I send a on/off signal through ELK software I can hear the Pim buzz and see the indicator turn red... but the light does not turn on or off. any ideas?

Did you add the switches in Elk RP2? It's under lighting.

 

[tmbrown97]

And did you set the network address information under the globals?

Also - you don't have to manually configure each light in the M1 - you can do an export in upstart and import that into Elk RP - IIRC, you right-click on Lighting and you'll see the import option.

And - sometimes you have to reset the PIM - you press the reset button 5 times, then 10, then 1 times to reset it - sometimes that's required when you move it around.

 

[mseicshn]

Yes, I added switches under lighting. Using the same device number as set up in upstart. I also set the global "UPB lighting network address" to be the address for the PIM in upstart. Correct?

 

[tmbrown97]

I think you might be mixing up the device id - you don't point it to the PIM - you point it to the network ID. In UpStart, go to Network > Properties. Get that network ID and put it in the Elk globals. I did an overlay of the two windows here for example:

 

[mseicshn]

I think you might be mixing up the device id - you don't point it to the PIM - you point it to the network ID. In UpStart, go to Network > Properties. Get that network ID and put it in the Elk globals. I did an overlay of the two windows here for example:

Thats definitely got somthing to do with it! (hopefully). I'll check it out when I get home. What about the device id of the switches? The device # in ELKRP should just match the upstart device# right?

 

[tmbrown97]

Thats definitely got somthing to do with it! (hopefully). I'll check it out when I get home. What about the device id of the switches? The device # in ELKRP should just match the upstart device# right?

Kinda - up to deviceId 192. The Elk can't talk to lights from 193-256 because it brings in the first 64 Links (the M1 only has 256 lighting addresses, whereas UPB has 256 lighting addresses and 256 link addresses; so it gives you a comprimise). I have a large install (60+) and it's not a concern - I just design around it... links that the M1 will never need to see are above 64; ones I want it to use are below.

I've attached a snipped of the lighting map out of the XSP's installation manual - it's a good reference to understand.

That said, it's way easier to go into Export and do File > Export and save a .UPE file that you can then import into the M1 - then when you look at or make rules they're easier to follow because it shows the actual names of your lights in ElkRP.

 

[mseicshn]

Kinda - up to deviceId 192. The Elk can't talk to lights from 193-256 because it brings in the first 64 Links (the M1 only has 256 lighting addresses, whereas UPB has 256 lighting addresses and 256 link addresses; so it gives you a comprimise). I have a large install (60+) and it's not a concern - I just design around it... links that the M1 will never need to see are above 64; ones I want it to use are below.

I've attached a snipped of the lighting map out of the XSP's installation manual - it's a good reference to understand.

That said, it's way easier to go into Export and do File > Export and save a .UPE file that you can then import into the M1 - then when you look at or make rules they're easier to follow because it shows the actual names of your lights in ElkRP.

Work2Play,
You are the best. Thank you for sharing your wealth of knowledge! So the PIM should be configured to use and address under 192 as well... right? I thought I was being smart and put it at 250 to get it out of the way if my switches! haha. I'm a dummy!

 

[tmbrown97]

Honestly I don't *believe* the M1 cares about the ID of the PIM. I read once what that's for but don't recall... It's most likely that network address that's tripping you up.

 

[mseicshn]

Honestly I don't *believe* the M1 cares about the ID of the PIM. I read once what that's for but don't recall... It's most likely that network address that's tripping you up.

Once again, thanks for putting me back on track. Thats all it was... the network address from upstart was what I needed in the global... Now I can resume installing switches... wish me luck!

 

[tmbrown97]

Awesome! Keep plugging switching away! I've installed a lot of them... nothin' to it!

 

[drvnbysound]

I was on the ELK site the other day and saw that they seem to have endorsed the PCSPIM (ELK-M1PCSPCM). I wondered a couple of things... Is this any different than the HAI PIM? I think I will end up with HAI dimmers and switches... will this work for me?

If you haven't seen it, here is the link to it on the ELK site:
http://www.elkproducts.com/_webapp_3228100/ELK-M1PCSPIM__M1_UPB_Interface

 

[tmbrown97]

That should work as well as any other PIM out there... but there's a couple things to know.

1. This PIM will be dedicated to the M1 - you can't share it for programming so you need a separate one for programming. That said, I recommend that *always* because it's easier.
2. The reason this is simpler is because it replaces the need for an M1XSP and a separate PIM - it combines them in one unit... that's pretty handy.

It's upb - so you should be fine... i have yet to hear of problems with mixing manufacturers.