PAC won't take time updates from C-gate

I have set up my C-gate config file so the C-gate server is the master primary clock. On PICED in the logs I can see that the PAC keeps changing the date to 2008, and always changes the time to am incorrect time too.

What could I be missing here?

Screenshots of logs attached.

Thanks very much.

 

Possibly faulty PAC crystal not holding the time and defaulting back to 2008, does this happen when you cycle the power on the PAC?

brand new or second hand unit?

 

Thanks for the reply. It's a second hand PAC. I have a server permanently connected to my setup over serial, so I followed Glen's very helpful post here, and C-gate is now broadcasting the time every 30 minutes on the network and all is well

Solution here:
https://www.cbusforums.com/threads/c-gate-not-operating-as-clock-master.11479/

 

a long time ago there were issues with CNI setting the time from the lantronix side of CNI you had to go into the Ethernet side with lantronix software and change the region in the time section sorry to be a bit vague but it was a while ago

 

This isn't a CNI, it's just a RS-232 PC interface, so hopefully it's not affected. Everything seems to work fine now, although I do have another issue you can maybe help with...

I can see that when my External PIR sensor detects movement, it sends a lot of messages out that I can see in the logs, several per second. Is there any way to have it send a single message? (e.g. Turn on a single GA for 30 seconds) It's on the older firmware version.

 

Screenshot of the issue attached:

 

From memory the devices that have timekeeping function,
homegate / scheduleplus - colour touch screens updates hourly,
BW touchscreens 90 minutes and pac every 2 hours

the fastest one becomes the master timekeeper. in another post you said you have an Edlt,
set the time to display on it and you can monitor the time, also you can set the time here as well if you leave the tool page accessible

 

It looks to me like the timeout in the sensor is set to 1 second. Either that or you are using the any movement function incorrectly.

 

I was using the Any Movement function but changed it to Day & Night Movement and the issue seems to have gone away. Although now I can't see anything in the logs at all so it's not ideal.

 

You should get one log when it triggers (at night) and another when it times out. If it's retriggered while you won't see anything.

 

Not getting anything unfortunately. The PIR triggers a dummy group using the logic you supplied. (I think it was you anyway)

All works fine, just no logs.

 

Sorry, it wasn't you that sent me the code, it was Oracle. Here it is:

{sunset logic}
once (Time = Sunset) then
begin
isDark := true;
SetLightingLevel("Garage", 30%, "4s");
end;

once (Time = Sunrise) then
begin
isDark := false;
SetLightingLevel("Garage", 0%, "4s");
end;

{ PIR Logic}
once (GetLightingState("garage pir?") = ON) and (isDark = true) then
begin
PulseCBusLevel("local", "Lighting", "Garage", 100%, "4s", "0:03:00", 30%);
end;

 

So are you running this inside PICED or the PAC? If you have PICED running the same time as the PAC with the same project you will have duplicate logic running. This will confuse things. Try closing PICED and run the diagnostic utility for the logs.

 

No, the logic is only ever running on the PAC. I just keep PICED open (with logic not running) to keey an eye on messages on the C-bus network.

Is there another better way of looking at network traffic and messages etc?

 

Once you have uploaded a project if find it's best to shutdown PICED and use the diagnostic utility. That way you can be sure there is no interference from it. That being said, PICED should log all the messages. Do you get any logs at all? Have you checked the PICED log filters?

 

Yes all options enabled and I do get lots of info, just nothing from the PIR since I changed it from Any Movement to Night Movement.

Everything works perfectly though.

Weird.