Uploading Pac Program Via CBUS

First of all i would like to say i know this has been raised numerous times but with all the problems going on with 4.5 i thought i would raise it again, and hopefully it wont just be UNDECIDED and closed again!!!!!
- First of all we managed well over 100 CBUS sites remotely
- The feature that is in PICED that allows you to upload the piced program to the PAC via the Cbus network DOES NOT WORK,
- We have tried it on numerous sites and it normally gets to around 11% and stops.
- Even when we have it in a closed network within our office it works but on with one of the older versions and a tiny program still takes over 1hour to upload.
- Why have this as a feature IF IT DOES NOT WORK?
- Why release a new version IF IT DOES NOT WORK?
To me for this system to be complete this feature needs to work and NEEDS TO BE FIXED ASAP.

Look forward to hearing everyone's responses!

 

Hi CJ Polo,

I gave it crack myself and I can't say I had any problems. Transfer of a project containing hundreds of lines of code took about half an hour. The transfer time is dependent on the amount of network traffic at the time. Too much traffic, network errors or network instability are likely causes of failure.

Just wondering what problems 'all' refers to? There has been a lot of discussion recently regarding the new Wiser product. As a new product this is good.

I can understand your frustrations when things don't work. Please let us know what problems there with any details you can provide and we will do our best to fix them.

Regards,

Matty

 

Thanks Matt for your resposne.
After looking into it a bit more and resetting up our test bench here without any other devices on the network we have managed to get the program to upload over the cbus network within the test environment still as you said it takes a good 30min if not longer which to me is too long. But when we try and do the same to our remote sites it does not work i think it may have something to do with the "Keep alive time" "Response time" of the PAC/CNI as it is through a internet connection into other sites. Even the sites where we have a direct VPN it still does not work reached about 11% and crashs sometime even shorter.

In reference to ALL the problems, just a few minor things (which dont matter) and one major.
Since upgrading to 4.5 we have experienced the following:
- The Piced software when uploading may become unresponsive even when using USB. Once it finishs it is fine.
- The other major one is as follows:
We have found a problem with the Cbus PICED software and the Pascal Automation Controller. When writing a simple once statement using the day of the week option the PAC seems to restart itself every 20 minutes.
This only happens once the program is uploaded to the pac and wont happen while just running the code in PICED. To log this you need to put a line of code in the initialization section of the software.

You have to upload the program to a pac on a network and log it though toolkit. And you will see everything stops every 20mins and restarts.

We have tried this on many different versions of your software
PICED 4.4.1
PICED 4.4.2
PICED 4.5.0
Toolkit 1.9.2
Toolkit 1.10.3


And on many different sites, from large Gyms to my small test bench with only a power supply, CNI and PAC, all brand new out of the box.

But still the same issue

This issue has also been taken up with CIS and they are looking into it.

 

Are you trying to update the PAC project via remote access? VPN or similar or just locally via the C-Bus network onsite?
Due to the large nature of data file and veeeerrry slow network protocol messaging speed will take some time....