Download Control Microsystems SCADAPack2 C/C++ Tools

Transcript
The argument used for application type in existing calls to create_task must be
replaced with the global variable applicationGroup. The operating system assigns a
unique value to applicationGroup when it is defined in appStart.cpp.
Please see the documentation for create_task in the Function Specifications section
for more details.
Controller I/O Functions
The following functions are no longer supported. The replacement function is indicated
for each. Each function is documented in the Function Specifications section.
Function
interruptInput
interruptCounter
readCounter
readCounterInput
ioReadDin5232
ioReadCounter5232
ioRead5601Inputs
ioRead5601Outputs
ioWrite5601Outputs
Replaced with
no replacement function
no replacement function
ioReadCounterSP2
no replacement function
no replacement function
ioReadCounterSP2
ioReadSP2Inputs
ioReadSP2Outputs
ioWriteSP2Outputs
Exit Handler Function
The argument used to specify the exit handler function in existing calls to
installExitHandler must be cast to the type (FUNCPTR). Please see the
documentation for installExitHandler in the Function Specifications section for
more details.
Program Status Functions
The functions getProgramStatus and setProgramStatus have changed syntax. To
support multiple C++ applications, these functions now have an argument to specify the
application. The new syntax for these functions is documented in the Function
Specifications section.
Freeing Dynamic Memory
When a C++ Application is ended (e.g. by using the STOP button from the C/C++
Program Loader), memory allocated by using the malloc function is not freed
automatically. An exit handler must be installed to free allocated memory. Please see the
documentation for installExitHandler in the Function Specifications section for
more details.
Non-Volatile Data Sections
The SCADAPack2 has a different method for declaring static non-volatile memory. There
is still 8 kB of memory available but it must now be shared with all user-loaded C++
applications. Non-volatile variable declarations and their pragma statements must be
removed from each source file and declared globally in the one file nvMemory.h. Include
nvMemory.h in each source file that uses non-volatile variables.
Please see the section Non-Volatile Memory for more details on editing nvMemory.h
and on using these variables in your source files.
2
SCADAPack C++ Tools User Manual
527