Remote network, CNI and PCI

I have CQC running at the moment and I want to issue a command to a group on a remote network.

On my network I have a CNI (for configuration of networks) at adderss 0, and a Din rail PCI at address 230 (E6).

The bridge is working fine and is set to pass all command to the adjacent network.

I cant get CQC to turn loads on on the remote network. I connected the diagnositc utility up and monitored the traffic (connected through the CNI) and this is what I got.

The first line is what the diagnostic utility is seeing as the command from CQC via the PCI. This does not turn the load on.
The next three lines are a local key input toggling the load - and that works fine.
lines 5 &6 are via CQC and the PCI again - and it does not work.
The last two are via the diagnostic utilty and it works.

I changed the config of CQC to now use the CNI instead of the PCI and (not making any other changes), clicked the same button on the screen and the load on the remote network came on.

So it would appear that the PCI is the casue of the problem.

It must be noted that the PCI does not show up in toolkit properly. It is a din rail PCI and not what is shown in the image. THis is what toolkit detects it as.

As you can see it is at address 230 (which is E6). Is it at fault as I suspect, or have I made a fundamental mistake somewhere.

Mick

 

The Folk that did the driver for CQC would have put it in that mode if he knew what that mode was

Is that the mode that the public release protocol will place the PCI in? I'm assuming so as it works accross the bridge with the CNI.

Would you think that the folk who wrote the CQC driver might be better off using the Windows DLL, assuming he can get it to work with the newly aquired and very economicly priced, Borland compiler?

Cheers

Rohan

 

Well this sucks big time. The CNI was purchased well before the PCI (six months) and I have been screwed over with an old model. Not happy about that at all. Remmber this is NOT a 5100PC as shown but a din rail model (5500PC).

So basically what you are saying is that the PCI is only good for local network stuff and if I ever wanted to use a wireless bridge or network bridge I need a new one :-(

 

Purchased it 3.5 years ago.

So this is what I dont get

My CNI shows firmware 3.5 and it works. I know that a CNI is pretty much just a PCI with a device server. This works fine so why not the other


And no I am not an integrator - thats why it hurts so much.

When is CIS going to introduce upgradable products. There have been a few upgrades in firmware that would have been ideal but due to the cost of harware it is not feasible to buy new gear just for the firmware.

Mick

 

OT - Upgradable products

No extra needs to be paid. CIS should be adding this as a serice to its customers. Once you install a C-Bus system you are kind of locked-in, unlike a conventional system where you can use anyone mechs and dimmers

As to who does it - anyoine who wants too. How many examples do you want of user upgradable (and cheap) consumner items. Every STB (sat for FTA) out there is a good example, routers are another. WHile most will never do an upgrade, it is possible for it to be done.

I am not sure of the direction you are trying to come from with your statement, you are selling a product that required a degree of technical knowledge about it, and hence the person or persons installing/configuring would be techinically capable of doing an upgrade. It may require a special tool buit that is for CIS to determine - as for foolproof, mistakes can happen and there a numerous examples of patching going wrong.

Mick