Network shutdowns randomly.....full version

Hi,

How come my full version of Homegate keeps randomly closing the network?
The original version has been upgrade to 3.9.0.0


Thanks,
Mark

 

How come you didn't post a log?

 

Mark,

What Richo should have said is -

Mark, if you would kindly post some log information we may be able to assist you further.

P.S. Richo, lOse the attitude!

 

ok..........here it is hope this helps?

 

The network appears to be going in and out of error state. This is normally due to comms issues.

What version of C-Gate are you running (C-Bus Toolkit about box will tell you).

 

Hey Petey,

http://ashleigh.id.au/?p=822

Cheers, Dunc.

 

Hey Dunc, I can't see the prOblem...

 

Hi,

it's c-gate v2.6.1 (build 2242).

"C-Gate : Rx "#e# 20080323-103914 754 //NEWHOME/254 eb3862a0-01e0-1029-a599-98a63958a1d0 State=error Previous=ok Reason=no response (CAL)"

What's the above mean?

Thanks,
Mark.

 

C-Gate didn't get a response from a command that it expected to get.. as Richo said, probably a comms errors..

C-Bus Diagnostic Software is your friend.

 

Guys,

I can definately tell you that there is a problem somewhere between C-Gate v2.6.1, Homegate 3.9.0+ (inc version 4) and Java Runtime 1.5_06+.

Here is the issue:
We have many sites that have been operating without a problem with a dedicated PC running homegate for months/years without the PC unexpectedly dropping of the CBus network. Upgrade Toolkit to version 1.7+ and the problem arises. I can replicate it on my laptop everytime... open a network in toolkit and scan. can leave it for hours and the network won't go into error. Open a Homegate/Piced project and choose 'Connect to CBus' and within 5 mins, the local network will go into error. The response from cgate is always the same, Cbus send error #, then you get state=error, previous=ok, reason = no response.

Reverting toolkit/cgate to 2.6 and reverting any installations of java back to original seem to fix. This is happening consistently with networks that have been 100% for a long time.

No explanation as yet other than "must be a comms issue".

 

If you can replicate the fault reliabily in one configuration and not in another then there is a good chance we can track this down.

If you could run a event level 9 log in c-gate using both configurations (do the same thing in both one producing the error and one not).

The send that to tech support with a note to forward to Darren.

heres a post on how to do logging http://www.cbusforums.com/forums/showpost.php?p=16987&postcount=3

 

Its important to note that when Toolkit is idle there's almost nothing happening between C-Gate and the C-Bus Network.. if you manage to get Toolkit/CGate to scan a Network thats a little dodgy then once the scan is complete the Network is highly unlikely to go into error because there's hardly any commands being sent to the Network that C-Gate needs a response to.

This is completely different from Homegate which when running, even if idle, will result in quite a steady stream of traffic to the C-Bus Network from C-Gate.. so you're MUCH MORE likely to notice Networks going into error from Homegate than Toolkit.

Not saying its a comms issue, just pointing out that you've got a flaw in your diagnosis.

 

The way I was reading his summary is that the OLD HomeGate works fine, the NEW HomeGate shows the network errors. Hence the hope that an event level 9 log can show some sort of problem.