M1 with Bridges

Hello Guy

I have a site that has 3 networks.

Everything works great CBUS wise, bridge applications OK
Switching between networks Ok

But when it come to the M1 Alarm, it works OK recieving the groups address locally but when pressed on the other networks it doesn't do what it suppose to.

Local network Application 56 - 250 OK
Network 253 Application 56 - 250 Nothing to M1 but ok to CBUS product that has the application

Could anyone enighten me to were I could find afix to work arround????

Setting up the CBUS interface Nothing about bridges

Thanks
Kev

 

So, what you're saying is that you have buttons on switches that control the M1, and these work fine when pressed on the switches that are on the same network as the M1, yet when the corresponding buttons on the switches on the other two networks are pressed the M1 does not respond?

Do the indicators on the switches on the different networks track each other correctly?

 

What I'm saying is that all works on CBUS side

Setup Switch with group address 250 on network 254, aplication 56(on another Network 252)

See lights come on, and t/s button 250 in Network 254 app 56 on

So it seems that the M1 is not accepting tunnelled commands or seeing command from bridge.


I have put the Diagnostic Utility on the 254 network and don'tt see any command come throw but the t/s turns on

Bridges have be set to All Apps, sent to adjacent Networks

Kev

 

It sounds like the M1 is ignoring messages that include the inter-network routing information in them.

 

What version of the M1 CBus module are you using? The V1 and V2 were very shacky. V3 is much better. I have found the most reliable way of using the M1 is to place it on it's own application then use cbus logic to do all the work. I have never tried communicating over networks but I'll give it a go in the next couple of days and see what happens here.

 

Hello

Yes Ashley, using new version 3, with I believe the lastest firmware applied.

How did you go with that test???

I have put a question on the Ness forum as well to see if anyone else has had this problem.

Kev

 

I can confirm that this is a problem with the M1.

I my case I am using a wireless gateway which functions like a bridge.

The M1 "sees" changes that come from a wired switch but does not "see" changes that come from a wireless switch.

From a vague memory of the Cbus protocol, there is an extra byte or two on a message that comes from across the bridge.

I think that this is an issue that Ness should attend to but when I mentioned it to them some time ago there was not much interest

 

Hi Htnut,

You can configure the wireless and wired side using the gateway as a bridge. I figured it out a while back. Thought I had posted here but could not easily find it, fortunately I also posted on the Ness M1 forum so I cut and pasted it out here.

Not sure it will assist exsolter's issue but will definitely sort your out. I use it every day to switch on/off a power subwoofer.

Regards,

Fleetz

=====The following is my post from the Ness M1 forum=======

How to M1 control C-Bus devices on the wireless side
by fleetz ? Wed Oct 01, 2008 9:53 am

Thought I would feed this back as I don't believe there has been a solution to being able to or more to the point letting M1 control anything on the wireless side of C-Bus. It can be done it more about getting the wireless and wired side of C-Bus to respond to application 56.

I have been able to achieve this using Toolkit. The trick is to get the wireless and wired side to be transparent to application 56. M1 then doesn't care it is switching application 56.

On the wireless side....

Create a valid "ghost" application in this case it was application 49 on the wireless side and assigned that as primary on the wireless relay. That enabled me to assign application 56 as secondary on the relay. I then created a GA in application 56 on the wireless side. I then set up the relay for secondary application which is now 56 and assigned the button assignment as normal.

On the wired side......

Created a mirror group address and name as that on the wired side under application 56. Then on the DLT button selected primary, then selected the GA and it works fine. With Ness M1 it only looks at controlling lighting application 56, therefore using any other application other 56 won't allow M1 control.

Make sure that you have "Send to adjacent network" selected on both the wired and wirless sides in Toolkit under the wireless network gateway.

M1........

Now set up your lighting in the M1 to mirror the GA set up in application 56 in C-Bus and there you have it.

We were struggling with this sometime back not sure if anyone had been able to sort it out hence the post. I have this working a treat on my system......M1 and or RTI can now switch the power on and off to the wireless relay which is connected to my subwoofer!

Regards,

Fleetz

 

Hi Fleetz

I think you are misunderstanding the problem. There is no issue with passing commands from the M1 to the wireless outputs. The problem is that any change in state of GAs on the wireless side not initiated by the M1, is not seen on the M1