Critical errors

Hello,



I just upgraded to piced version 4.And I am having problems with critical error report 309.

That is because I am using application 208, that application is great because I can stimulate minderpros keypad On colour touch screens.

How do I get around this problem using version 4 and still having this great future.

Any help would be greatly appreciated.

 

Application 208 (Security App) can be controlled using in-built system IO variables. It is no longer necessary to use the "hack" where lighting messages were used to emulate Security App messages.

 

Thanks for your reply.
Is there any where I can get notes, on using in built
system IO variables.

Cheers,

Nigel.

 

Darren,

I use logic in a PAC to determine the alarm state, which worked well before V4, my understanding is that System IO variables are not available on a PAC. How do I go fix this?

 

In-Built System IO

Hi Josh,

In-built System IO is supported in the PAC. Check out what values are available in the help file

To get the Alarm State use:
GetBoolIBSystemIO("Security Alarm")

Cheers,
Mark.

 

It is carefully hidden in the help file under the topic "In-built System IO"

 

Great, the system IO works well.

Now I am having the problem of deleting application 208 from
toolkit, so that I can upload piced with out the critical error report.

How can get around this with out starting a new toolkit project.

Cheers,

 

You could (with Toolkit closed) use the C-gate console window and execute console commands. (backup project first). The documentation is available on the Clipsal website.

 

Thanks Mark, will try that and see. I have coded it in, but could not test in the middle of the night, I do not think my neighbours would have been happy.