ElkRP and other software from AO?
- Thread starter dbinaz
- Start date
Steve
Senior Member
mustangcoupe
Senior Member
oh, so your the voice behind those videos 
.... more complex rules using virtual outputs might be good... (unless we are getting more features in the rules soon?)
.... more complex rules using virtual outputs might be good... (unless we are getting more features in the rules soon?)Hi Spanky,Spanky said:
I consider the Elk installation manual to be excellent. Even so there are some things that just aren't apparent. An example is the use of [insert condition] in voice descriptions. How do you use this option, or [say number], [say up/down]?
A review of some of the questions on this group will indicate where installers are having problems. For me the basic installation was simple, it's those little things that don't come easy at my age (63). For me the concept of Tasks escaped me until I tinkered with them a bit. I equate them to macros that can be conveniently called from a keypad or another rule.
A training video might include some installation planning tips, like keeping often used tasks assigned to lower numbered positions so they show up first when keypad control is used.
A tip like using an output/timer on startup to inhibit/skip some rules until the system stabilizes would be handy for beginners.
Many beginners may not be used to ladder logic programming and a primer on this would save them some time.
Incidentally, I never got a response concerning a previous question about rules firing when various "areas" are armed. In my case, all violated zones (in any area) trip a rule when area 2 is armed. So, if I have a rule that says when zone x becomes unsecure do y, y gets done when area 2 is armed, even though y was done once when zone x was initially violated. Hope that makes sense
An explanation of how the M1 handles text messages to be displayed on the LCD would help. Depending on display option settings it can be hit or miss if your text message will actually display at all.
Looking forward to the video
John
acdcelectric
Member
Hi Spanky,
I agree with most of carry15+1's ideas and here are a couple of my own.
How about some installation tips for all of the peripheral Elk boards, hubs, sensors, with some prgramming tips on how to get them up and running.
Some programming tips on use of external data, (ie: temps and analog inputs) for better whole house integration.
I know this is off the subject, but the biggest (or smallest) problem that I have is that the Elk can is too small. How about an optional can that is 50-100% larger. With the M1, a battery and and 1 input expander board, I can barely fit the zone wiring around to the terminals. As soon as I have to add an elk relay board, hub or serial interface I am out of luck.
There is almost no installation that I don't have to put external boards into the structured wiring can and run power and data wiring between them. They cannot always be co-located.
I agree with most of carry15+1's ideas and here are a couple of my own.
How about some installation tips for all of the peripheral Elk boards, hubs, sensors, with some prgramming tips on how to get them up and running.
Some programming tips on use of external data, (ie: temps and analog inputs) for better whole house integration.
I know this is off the subject, but the biggest (or smallest) problem that I have is that the Elk can is too small. How about an optional can that is 50-100% larger. With the M1, a battery and and 1 input expander board, I can barely fit the zone wiring around to the terminals. As soon as I have to add an elk relay board, hub or serial interface I am out of luck.
There is almost no installation that I don't have to put external boards into the structured wiring can and run power and data wiring between them. They cannot always be co-located.