Schedule issues?

Hi,

Having some schedule problems - but I am new to CBUS and hopefully this question doesn't frustrate you all.

I have a Wiser unit and have configured a schedule in PICED. I have transferred the project to the Wiser but the schedule doesn't seem to take effect.

(The schedule is a very simple turn a lighting group on/off to test it).

I've used a Pulse group for 10 seconds to turn the light on/off again.

Some basic questions:
1. Do I need to leave PICED running on a computer to make the schedule take effect? (hopefully not, I presumed the Wiser would store the schedule. I've tried with and without PICED running).

2. All references in PICED refer to "Local network" rather than my network name. I can push projects to Wiser though for other controls like Widgets and they work fine.

Any and all ideas appreciated

 

Update - I can see the Schedule in the Wiser (including the correct time) but it doesnt' seem to execute. Just watched the time tick past the scheduled pulse time but nothing happens...

Update: I've created another schedule to pulse a hallway light every 1 minute but same result - schedule seems to get pushed to Wiser unit, but does not execute. Wiser can control other on/off loads though.

 

I would suggest sending your project to Tech Support to see if they can replicate the problem.

 

Keep in mind, that after pushing a project to a Wiser, it takes a few minutes before Logic/Scheduling start executing. Wiser needs to get C-Bus time and/or ntp time before it starts executing Logic and Scheduling.

 

thanks kjayakumar,

I set a test schedule a number of hours in advance - and still nothing

The time (according to the Wiser web interface) is correct...

 

Hello Tom
Perhaps you could run the schedule in piced.
Make sure you have connected to cbus and enabled schedules.
Just to test that you have created the schedule properly.
There is a timeout so it wont stay connected forever but it might help you work it out.

 

Hi,

The screenshot attached shows some of my PICED configuration.

I have selected "Connect to CBUS" in PICED but it doesn't seem to result in any change in the interface (the schedule still doesn't appear to work either).

In the project I see references to the "Local Network" rather than my network name "KEW". Could this be the issue? I can't see how I specify the CBUS network/CNI in PICED...

The network is "KEW" @ 192.168.2.2 (CNI in the WISER).

Hope this helps...

 

I cant see your screenshot.
How are you connecting to CBus?
Through the Wiser?
I've never done that so I am not sure exactly how.
But without reading the manual I imagine you use the wiser ip address and port 10001 and imagine you set this in the project details.
Which could be completely wrong.
When you connect to CBus through wiser it will take wiser off line from what I read but you need to have your CBus connection up and running to test out your schedules in Piced.
That's just me guessing that your schedule may have a problem.

 

Not having used wiser I'm clutching at straws really but it should connect the same way as you connect in toolkit.

 

I got your screenshot.
It shows that you are not connected to CBus.

 

I am working on the assumption that the Wiser CNI is just like the normal Ethernet CNI.

My Wiser CNI is 192.168.2.2 - when I open that in a browser I get the clipsal CNI summary screen which is attached.

How is the CNI referenced in the PICED project? Just trying to work out how I "point" PICED at the CNI.....putting WISER to the side for the moment

 

So you have a regular CNI?

 

Sorry
So that says connected.
What about Piced

 

Check your project settings for the CBus connection details.
It only shows up if you select the project as a wiser.

 

A couple of points.

Firstly, the screenshot of the Wiser's CNI (above) is the configuration page for the CNI itself. When using the Wiser/CNI to connect to C-Bus you need to use the IP Address of the Wiser, not the IP Address of the CNI. This is because the CNI can only have 1 connection to it at any given time and this is 100% occupied by the Wiser. When you connect with Toolkit/PICED/Homegate/S+ you connect to the Wiser and the wiser then hands the CNI connection over to Toolkit/Homegate/S+/PICED/etc. Once you disconnect from the Wiser, the Wiser will resume normal operation.

The second point is that PICED will only start executing it's schedules once it has fully synchronised to the network. Simply establishing the connection is not sufficient for it to start working. You need to wait until the status bar at the bottom of PICED turns green and shows the Network as open 100%.

 

I wondered about that too, but my assumption is the "disabled/enabled" refers to the current state.

For example, the schedule that turns the lights on at 8.45PM is "disabled" up until that time. Similarly the schedule that turns the lights off at 2.00AM is enabled other than when the lights are on.

 

Thanks. I used the Wiser instructions to get PICED going - so the project is a "wiser" project. It connects to the Wiser IP (192.168.2.1) and I can successfully transfer projects to the Wiser).

I haven't yet seen the "green" status in PICED yet. Am I right in assuming that PICED will interact directly with the CBUS network? (i.e. through the wiser/CNI) ?

Do you know if there is additional configuration required in the project to "link" it to the CBUS network?

I'll also give Clipsal a call later today

 

Sorry about the avalanche of posts...

I opened up the toolkit and can connect to the network through the Wiser CNI perfectly (see screenshot).

In PICED, when I select Project -> CBUS Networks, the only listing is the "Local Network".

Interestingly the type is listed as "Serial COM3" (see screenshot). I was previously using a USB PCI interface, but this is no longer connected. Is there a way to get the Wiser to list the CNI rather than Serial COM3?

I had a look through the configuration but couldn't find it anywhere

Tom

 

No. Schedules have an optional "enable group". If that group is set to the pre-selected level, then the Schedule is said to be "enabled". In other words, it will execute the event at the selected time.

The term "enabled" or "disabled" does not apply to the thing being controlled.

So if the Schedule is shown as "disabled" it will never do anything.

As Nick said, check that your enable groups are set the correct level.