C-Gate

Cool, send it to [email protected] remove the NOSPAM part.

 

Hi Brodsky,

Thanks for the email. The error certianly indicates that C-Gate isn't getting a response from the PCI. I had a reread of some earlier posts in this thread and the following stood out to me.

Mainly the issue that V2.7 of the Installation Software also failed to communication to the PCI. I was suspecting the PCI might have a problem, but then you said.

I have 2 other tests I would like you to do:

C-Bus Diagnostic Software
Try and connect to the PCI using the C-Bus Diagnostic Software http://www2.clipsal.com/cis/technical/downloads/software#Diag

A) Unzip the ZIP file from the web page above.
B) Run "CBus Diagnostic.exe"
C) Confirm the correct COM port is set by selecting "Options|Program Options" and checking the Serial com port in the selection combo box.
D) Select "C-Bus|Connect to C-Bus"

Let me know if it successfully finds the PCI. If it does it the pop-up dialog will tell you the version number of the PCI and the Unit Type. Please let me know those values.

C-Gate Log
Next it would be help to get what we call an "Event Level 9" log from C-Gate. This is a detailed log of everything C-Gate does.

A) Ensure that C-Gate is NOT running.
B) Open the file "C:\CLIPSAL\C-Gate2\config\C-GateConfig.txt" in a text editor like note pad.
C) Change the following three parameters (use search to find them) if they are not already set to these values.

Code:

event-filename=event.log
use-event-file=yes
global-event-level=9

D) Start C-Gate and try and open the network.
E) Close C-Gate (assuming the network open fails).
F) Change the paramters back to there default values.

Code:

event-filename=event.log
use-event-file=no
global-event-level=5

IMPORTANT: You must reset these values otherwise C-Gate will run slower and consume all remaining HDD space logging it's commands. The log file will become gigabytes in size.

Now send me the "C:\CLIPSAL\C-Gate2\event.log" file and can you also send me a copy of your project file. This will be a file called <project name>.XML located in the C:\CLIPSAL\C-Gate2\tag directory. Where <project name> is the name of you project.

 

Hi Richo,

On it's way

Thanks

 

Richo,

BTW I opened the diagnostic s/w, but was also unable to connect to PCI.

Thanks
Brodsky

 

Richo,

Any answers yet??

Thanks
Brodsky

 

Sorry for the delay. It was a public holiday Monday here in SA and I was ill on Tuesday. Just starting to catch up. I will try and get back to you later today.

 

Looking at the logs and the information supplied there is no obvious reason as to why it is not working. Each of the 3 main C-Bus programs you have tried (V2, C-Gate and Diagnostic Software) all use different source code and techniques to access the com port.

There is certainly something about your hardware or hardware configuration that is proving incompatible with how the PCI needs to talk to the computer.

Information on how your computer is configured may help identify something.

Collecting Hardware Configuration

A) click start menu and select run.

B) Enter "cmd" without the quotes if you run Windows 2000 or XP (if you run Windows 95/98/ME type "command" without the quotes instead) in the dialog box and press OK.

C) In the resulting command window type the following command and press enter:

Code:

start msinfo32 /report c:\clipsal\hardware.txt /categories +componentsproblemdevices+resources

TIP: You can paste into a command session by using the system menu (top left icon on window title bar).

Send me the created file c:\clipsal\hardware.txt

I am however suspecting that the com port of this laptop does not confirm to the EIA-232 standard and is most likely using a low power level. Without using hardware testing equipment it is not possible confirm this however.

If there is no obvious issues in the hardware.txt file I suspect you will need to look at using a Dontronics USB<->RS232 adapter. Recommend using a USB adapter over PCMCIA for use with Toolkit as we have experienced issues with PCMCIA RS232 cards and C-Gate in the past.

 

Just a recent record of problems with, not c-gate but CIRCA:


Laptop A, "Unknown brand A" USB-->RS232 adpator doesn't work. No com port on this laptop.

Laptop B, "Unknown brand A" USB-->RS232 adpator doesn't work. Use com port ok.

Laptop C, com port doesn't work at all. "Unknown brand B" USB-->RS232 adpator WORKS!

(Unknown means I don't know what brand they are, but all made in Taiwan, I think)

So, always use a recommanded USB-->RS232 adpator will be a good starting point.

Wish you guys solve the problem soon and I guess you will.

 

I have heard of it working in rare circumstances, but normally it is hideously slow and thus not viable.