C-Bus v2 -> "No Response" issues

Hello,
I was hoping someone could help us with our new C-Bus...

We were wondering if anyone has come across the issue of C-Bus V2.7.9 not being able to connect to the C-Bus2 PC Interface box.

It is giving me the error of "No Response" when looking for the network...

To rule out possible COM port issues, and Windows compatability issue I have tried to connect from various laptops (differing Win OS's) and using different COM connections (USB, pure COM).

I haven't been able to find any information on the various forums/website relating to C-Bus v2 error messages...

We have also tried to connect to it over HyperTerminal using the settings listed in the troubleshooting .pdf from Clipsal.. also no dice... it rejects any inputs...

I have no real knowledge of the C-Bus system, I was hoping to learn by getting in the deep end and trying to figure it out.. the lights on the C-Bus signal that it is linking and so forth, and the electrician has checked the basics of it, but he has no programming knowledge of the system either....

It looks rather straight-forward in the quick-start .pdf, so I am thinking the actual interface unit itself is cactus....

if anyone has any other suggestions as to what I could try, please let us know.

Thanks
Daniel

 

I managed to get the C-Bus v2 software to connect, and roughly do its thing. I guess the major issue now is that the PC Interface (v4) seems to be
stuck on id 255... the problem is when other units are added it wont automatically assign them a different id. I can see in the C-Bus diagnostic software that there are conflicts between one of the 8-dimmer rails and the pci unit.....

Is there a way to factory reset the C-Bus equipment back to empty settings in an effort to start fresh?
The diagnostic can see the equipment, but wont really allow me to change any of the settings....

I was also curious as to what order you are meant to wire in the switches? We have had differing opinions as to wether they need to be programmed individually beforehand, then wired/set onto the wall.... or they can all be wired up and then setup later on.. ???

Again, any suggestions are greatly appreciated!

 

Hi Daniel
With only the pc interface connected go to Network in the menu and click on local network..the pc interface should be listed ,with it highlighted click on change unit address and change then repeat this for each device..
HTH
Frank

 

You should only add one new (unprogrammed) unit to the network at a time, program it, then add the next new unit. There is no required order as far as unit types, do it as willy-nilly as you please. As a matter of good practice I generally do all the output units (relays,dimmers) first, but it's certainly not necessary. You definitely should start with the PC Interface though.

When I do a new installation, I program the entire thing (connecting one unit at a time of course) on my desk, then pack the lot back in its boxes and it goes out to site. Then the whole network can be installed and connected, and it's up and running straight away, ready for fine tuning. I'm guessing most installers do it this way.

Perhaps it's worth you treating this as a new installation - disconnect all the units, then reconnect & reprogram them one by one? Bit of a hassle, but you'll at least be able to see what the network is doing with each step, and will give you confidence in the fact that you're in charge, not the network! You don't have to go the whole hog and program every detail, but at least assign a Unit Address and Part Name to each unit before you connect the next new one. Set up a numbering system for Unit Addresses, eg allocate switches the addresses 020 to 029, dimmers get 030 to 039, etc. It makes things nice and neat on the screen.

As for your problems with the PC Interface, one thing you should get in the habit of doing is opening the C-Bus Communications Server (I think it's called that) which is the other program on the taskbar when the C-Bus Software is open. Click the "Refresh" button, and it will scan for available Com ports. Then select the one you're connected to and hit Ok. This can save a lot of mysterious headaches! Hopefully the need to do this will be done away with in V3.

Good luck, and most importantly, have fun!

 

Thanks for the suggestions,

The cabling guys from work had some spare time and they went and wired all the sockets to the walls... before we started to work on anything C-Bus related.... my prediction is we will be unwiring 30+ switches

Im going to attempt the following steps:

ill try by reprogramming the pc-interface box on its own first (reassign it to 000) as suggested in one of the .pdfs - that should hopefully resolve any major conflicts with the units....

next ill patch the 8-dimmer rail into the pci and attempt to program that, then unplug it and plug in the next rail.. and so forth...
the final patch layout suggested by the electrician i have attached as
cbus.jpg... does that look correct? there are 2 pink leads coming out from behind the cbus panel, i assume they are to the rest of the switch network...

and as far as programming all the sockets/switches...
would I program them by cutting a patch lead, and wiring the socket, then patching it directly into the pci and adding swtich via C-Bus v2 program ?
i havent found much information on the sockets themselves...
or is it possible to program them while they are still on the wall...?

does this sound like the correct course of action??
once i get past the initial learning curve, cbus looks like fun

 

I've updated my post above, there might be some more help there.

Your proposed method for programming looks right. You don't have to disconnect each programmed unit before you do the next one though, in fact I'd recommend you leave the programmed units connected while continuing to add new ones - and watch the network come together on the screen as you go. Obviously the network scan time will increase slightly with each new unit, but it's worth being able to see a complete picture of what you've done at all times.

Unfortunately the 30-odd switches will need to be disconnected. Don't completely remove them though, just disconnect the negative terminal on each one and leave the switch in position. Then you can reconnect the negative wire on each switch as you are ready to program it. When you do this, make sure there is still continuity on the negative side of the bus, ie if you disconnect a negative and there are two wires in the terminal, make sure they're twisted together so the units downstream don't lose their negative.

The same will go for any other field devices, ie Motion Detectors etc.

Once you've programmed all the units in the actual C-Bus panel, and disconnected all the field devices (ensuring that there is still continuity on the network), plug in the two pink leads that go off into the ether (as you guessed, they connect all the field devices to the network), then rescan the network. This is where you'll see if there's any new units you've forgotten to disconnect. From this point, just make sure you've got only one new unit connected at a time and program away!

As for the sockets, do you mean that you have RJ45 (data sockets) to give you access to the C-Bus network in different rooms? If this is the case, don't worry about disconnecting them, as long as they're wired properly they won't get in the way. If anything is plugged into them though (ie any C-Bus units that have been adapted to be portable) you'll have to unplug it, then add it again when you're ready to program it.

 

Peter,

Now might be a good time to mention clocks and burdens and their default settings.

Rohan

 

I seem to be having the biggest problem scanning the network to see what is actually on it. Im running C-Bus v2.7.9... and as simply as I could setup, just the PCI unit and a 8-dimmer...

If i run C-Bus diagnostics, it will report the PCLOCAL4 on 255 - i run an identify and it will also list a DIMDN8 on 001.... aparently they pick up ok.

now the strange part is when i attempt the same basic network scan in C-Bus v2... i get the following error... (i tried both enable/disable auto conflict resolve)

Could not get the project name
Reason: Unknown Error (0)

pow! that is causing me grief as I cant figure out how to change the address of the PCI to anything other than 255.

I am currently downloading v2.7.7 in the chance that something is cactus in this version with my config/cbus....

has anyone else seen this error before?

ive seen clocks and netowrk burden mention in some of the pdf's... but none of the cbus stuff i have has a jumper for burden as mentioned in the pdfs...

thanks for everyones help and input on this somewhat troubling sytem

 

Hi Daniel,

V2.7.7 should behave the same as the current version. Did you receive my email last night?