Schedule issues?

"Serial COM 3" is the interface used by C-Gate to connect to the network. It has nothing to do with how Wiser connects to the network. Wiser has its own connection (CNI).

 

Thanks for the replies.

I've updated the schedule (screenshot attached) so the test schedule is enabled "always" (I set the enabled-by application to = Enable Control).

....But still no schedule execution

 

It looks like you should set the time for the test schedule at repeat 20 seconds instead of 6.00pm

 

Make sure in your event settings that the final level is zero.

 

It's still not going to turn your hall lights on and off until you are connected to CBus.

 

I think that is what I'm struggling with.

The Wiser is connected to CBUS - I can control on/off widgets successfully to various groups.

I can also view the Schedules in the iphone/Web Wiser interface (but they don't seem to take effect), so the schedules are definitely being transferred to the Wiser.

I'm just puzzled about how to get the PICED software to show a successful CBUS connection. The open project is configured to use the Wiser.

 

Have tried both 0% and Off

(and ON/100% for the starting level)

 

Sorry same thing.

 

Do you have an indicator in Piced for the hall lights.
It should be flashing now even if you are not connected to CBus

 

Where abouts in PICED are you referring to?

I turned on logging and found the following...

I can see the messages being transmitted to the Bus (it is pulsing the Hallway light for 16 seconds every 30 seconds).....however the light doesn't pulse.

There seems to be the odd message received from the bus - with the correct network name "KEW".

Still also seeing "Local Network" so not sure if that's an issue...


12/15/2011 10:35:01 PM C-Bus Tx : Set Hallway On (Schedule "Test ON")
12/15/2011 10:35:17 PM C-Bus Tx : Set Hallway Off (Timer Expired)
12/15/2011 10:35:31 PM C-Bus Tx : Set Hallway On (Schedule "Test ON")
12/15/2011 10:35:47 PM C-Bus Tx : Set Hallway Off (Timer Expired)
12/15/2011 10:36:01 PM C-Bus Tx : Set Hallway On (Schedule "Test ON")
12/15/2011 10:36:03 PM Debug : Free Memory: 312.0 MB
12/15/2011 10:36:03 PM Debug : CPU Usage : 0.0 % to 100.0 %
12/15/2011 10:36:03 PM Debug : Screen Draw: 0ms to 0ms (0 redraws)
12/15/2011 10:36:12 PM C-Gate : Tx "[255]get 254 state"
12/15/2011 10:36:12 PM C-Gate : Rx "[255] 300 //KEW/254: state=new"
12/15/2011 10:36:17 PM C-Bus Tx : Set Hallway Off (Timer Expired)
12/15/2011 10:36:17 PM Info : Network 254 (Local Network) is off-line, command has been queued
12/15/2011 10:36:31 PM Info : Schedule "Test ON"
12/15/2011 10:36:31 PM C-Bus Tx : Set Hallway On (Schedule "Test ON")
12/15/2011 10:36:31 PM Info : Network 254 (Local Network) is off-line, command has been queued
12/15/2011 10:36:47 PM C-Bus Tx : Set Hallway Off (Timer Expired)
12/15/2011 10:36:47 PM Info : Network 254 (Local Network) is off-line, command has been queued
12/15/2011 10:36:48 PM Debug : Save PFR File
<snip>
12/15/2011 10:39:12 PM C-Gate : Rx "#c# //KEW/254 #InterfaceState=opening #OID=70564a20-0914-102f-8d66-e8ccf65e0e0b"
12/15/2011 10:39:12 PM C-Gate : Rx "#c# //KEW/254 #InterfaceState=closing #OID=70564a20-0914-102f-8d66-e8ccf65e0e0b"
12/15/2011 10:39:12 PM C-Gate : Rx "#c# //KEW/254 #State=sync #OID=70564a20-0914-102f-8d66-e8ccf65e0e0b"
12/15/2011 10:39:12 PM C-Gate : Rx "#e# 20111215-223912 754 //KEW/254 70564a20-0914-102f-8d66-e8ccf65e0e0b State=sync Previous=new Reason=closing network"
12/15/2011 10:39:12 PM C-Gate : Network 254 (Local Network) changed state to sync - (closing network)
12/15/2011 10:39:12 PM C-Gate : Rx "#c# //KEW/254 #InterfaceState=streamsclosed #OID=70564a20-0914-102f-8d66-e8ccf65e0e0b"
12/15/2011 10:39:12 PM C-Gate : Rx "#c# //KEW/254 #InterfaceState=closed #OID=70564a20-0914-102f-8d66-e8ccf65e0e0b"
12/15/2011 10:39:12 PM C-Gate : Rx "#c# //KEW/254 #State=new #OID=70564a20-0914-102f-8d66-e8ccf65e0e0b"
12/15/2011 10:39:12 PM C-Gate : Rx "#e# 20111215-223912 754 //KEW/254 70564a20-0914-102f-8d66-e8ccf65e0e0b State=new Previous=sync Reason=Interface Closed"
12/15/2011 10:39:12 PM C-Gate : Network 254 (Local Network) changed state to new - (Interface Closed)
12/15/2011 10:39:12 PM C-Gate : Rx "[259] 120-initializing"
12/15/2011 10:39:12 PM C-Gate : Rx "[259] 120-opening port"
12/15/2011 10:39:12 PM C-Gate : Rx "[259] 120-stopping threads"
12/15/2011 10:39:12 PM C-Gate : Rx "[259] 120-threads stopped"
12/15/2011 10:39:12 PM C-Gate : Rx "[259] 120-closing streams"
12/15/2011 10:39:12 PM C-Gate : Rx "[259] 408 Operation failed: //KEW/254: Open failed: no such port"
12/15/2011 10:39:12 PM C-Gate : Rx "[260] 200 OK: //KEW/254"
12/15/2011 10:39:17 PM C-Bus Tx : Set Hallway Off (Timer Expired)
12/15/2011 10:39:17 PM Info : Network 254 (Local Network) is off-line, command has been queued
12/15/2011 10:39:31 PM Info : Schedule "Test ON"
12/15/2011 10:39:31 PM C-Bus Tx : Set Hallway On (Schedule "Test ON")
12/15/2011 10:39:31 PM Info : Network 254 (Local Network) is off-line, command has been queued
12/15/2011 10:39:47 PM C-Bus Tx : Set Hallway Off (Timer Expired)
12/15/2011 10:39:47 PM Info : Network 254 (Local Network) is off-line, command has been queued
12/15/2011 10:40:01 PM Info : Schedule "Test ON"
12/15/2011 10:40:01 PM C-Bus Tx : Set Hallway On (Schedule "Test ON")
12/15/2011 10:40:01 PM Info : Network 254 (Local Network) is off-line, command has been queued

 

Hello Tom
Since I dont have a Wiser you will need to get some help from someone else with the connection to CBus.
It seems that your schedules werent right initially so perhaps you are part way there.

 

Thanks for your help so far. I will give the clipsal tech support line a try tomorrow when I get a free moment

Thank you again

 

It seems that PICED is not connected to C-Bus. There isn't enough of the log to see exactly what is happening.

PICED will show whether C-Bus is connected or not. There is a coloured bar at the bottom of the window showing the network connection state. There is also the Project Networks form which shows the state of the networks.

Once you are connected to C-Bus, you can place a component on a page to test that the light can be controlled manually.

Then check to see if the Schedule controls this light.

 

Hi,

I accidentally solved this issue today.

I was having problems accessing the Wiser from the Internet (have a separated embedded 3G device for external access) and stumbled upon a post in the forum that mentioned "User Wiser as a LAN device" (see attachment).

I set this up (as the Wiser has no WAN connection, just LAN with port forwarding on my external router).

Suddenly the test schedules started to work.....

Had a play with a few others and they all seem to work now.

Many thanks to all who posted in reply

Tom