C-bus integrated Security- Elk M1? Anything else new?

Ness M1 C-Bus Interface

The Ness M1 C-Bus Interface has now been signed off by Clipsal as a C-Bus enabled product.

It connects directly into the main RS232 port on the M1 panel. If the Ness Ethernet module occupies this, an optional serial expander (up to 7 can be connected) can be purchased to connect the interface into the M1.

Over 20 pre-release interfaces have already been supplied to some lucky customers all with no reported problems, so they may have taken a while to get here but all the testing seems to have proved well worth the wait.

Ness are waiting for Clipsal to supply the SIM module to complete production of the Interface, so the C-Bus can connect directly to the Ness module. These are expected to be supplied by Clipsal to Ness early March 2006, so Ness expects supply of a full production run approx Mid March.

The Ness part number is 101-225 and at a reasonable price.

GCK

 

D16 with C-Bus Interface

I bought the panel and works perfect. It's amazing how this guys from Ness can produce such a good product for only $400!!

here are some of the good things I found with this panel:
1. Very easy to configure using the keypad
2. Good price. It has 16 digital inputs (i.e. the sensors) than can trigger 16 independent C-Bus events. For AU$400, I would prefer using this panel over 4x 4-Channel bus adapter.
3. Excellent support from Ness over the phone and emails.

Some bad things:
1. It is not possible to see motion/reed sensor status from the C-Bus side. You can trigger a C-Bus event using the motion/reed sensors, such as pulse a group address, ramp, etc, when the sensor changes from ON to OFF, but not vice-versa.
2. Alarm can be fully armed from C-Bus (Zones 1 and/or 2), but C-Bus cannot arm the monitoring (or "night") mode.

Not present but desired things:
1. Distinguish between User #1 and User #2 (or even more users), when using the remote control unit.
2. Disarm monitoring mode.

CS.

 

Thanks Ashleigh, I'm sure that will happen soon. As I said, it is an excellent product and I'm very happy with it.
CS.

 

But it only talks one way, right?

In my view it needs to be able to react to C-Bus messages to take advantage of the logic.

But then again perhaps I'm just spoilt by my Thinkboxx

Cheers

Rohan

 

It is two way:

From C-Bus to D16x
- Arm Area 1
- Arm Area 2
- Arm Area 1 and 2

From D16x to C-Bus
It sends the following commands:
- On/Off, Ramp or Pulse lighting application groups
- Trigger max/min "Trigger Control" groups
- Set network variables in "Enable Control"
These commands can be initialized by any of these D16x events:
- Unsealed zones
- End of exit delay
- Alarm goes off
- Panel disarmed
- Panel armed

CS.

 

Sorry, it seems some of this thread is relating to the M1 and some to the D16.

I got confused

I was referring to the M1

Cheers

Rohan