On a SCADA Cimplicity 6.10 system I encounter the following problem:
When a Cimplicity project is restarted, all the data from the virtual points is erased and brought back to a last known situation. This last known setting does not correspond to the initialization value filled in in the point configuration in the workbench.
For example a date is stored in a virtual point to remember when the specified equipment was calibrated. The initialization value is filled in as 06/08/2006 (date when engeneering started). When the calibration is done, 12/01/2013 was filled in. After a restart of the project 12/02/2008 reappears. This value is consistent after a restart.
I traced the value back to SAVED_POINT.stg under the log folder. The file, as found in other threads is not clearly readable but in notepad the date is readable at the specified calibration point.
I tried changing the way points are stored under the project settings point. It seems that 'On point update' or 'On project shutdown' does not make a difference.
Does anyone know the problem or know where to look in the cimplicity configuration to find out the problem? Thanks in advance:
some (maybe related) problems in the status log:
When a Cimplicity project is restarted, all the data from the virtual points is erased and brought back to a last known situation. This last known setting does not correspond to the initialization value filled in in the point configuration in the workbench.
For example a date is stored in a virtual point to remember when the specified equipment was calibrated. The initialization value is filled in as 06/08/2006 (date when engeneering started). When the calibration is done, 12/01/2013 was filled in. After a restart of the project 12/02/2008 reappears. This value is consistent after a restart.
I traced the value back to SAVED_POINT.stg under the log folder. The file, as found in other threads is not clearly readable but in notepad the date is readable at the specified calibration point.
I tried changing the way points are stored under the project settings point. It seems that 'On point update' or 'On project shutdown' does not make a difference.
Does anyone know the problem or know where to look in the cimplicity configuration to find out the problem? Thanks in advance:
some (maybe related) problems in the status log:
Code:
11/01/2013 13:53:24 Failure 2568 MAC_AM am_alloc_gen_lis 0
Allocated process does not exist
Error of type: COR_AM_ERR, Code: 21
11/01/2013 13:43:59 Failure 3916 CVf4c PtmapLocalPointR 0
Failed to get updated system points.
Error of type: COR_LIB_ERR, Code: 0
10/01/2013 21:45:38 Failure 2824 MAC_DL DbExecute 10054
(01000) [DBNETLIB]ConnectionWrite (send()).
Error of type: COR_DBDL_ERR, Code: 100
10/01/2013 21:44:48 Failure 1396 MAC_PTDL DbExecute 10054
(01000) [DBNETLIB]ConnectionWrite (send()).
Error of type: COR_DBDL_ERR, Code: 100
1/01/2013 22:17:08 Failure 3932 CVf5c Line::GetConnect 0
The request for a database connection has timed out.
Error of type: COR_DBDL_ERR, Code: 175
1/01/2013 21:58:55 Failure 2588 MAC_PTM ptmrp_get_ap_msg 24
Application message queue overflow - RUB-01000FH8qoi
Error of type: COR_PTMRP_ERR, Code: 1
11/01/2013 10:00:54 Success 2568 MAC_AM am_allocq_send_r 8
Allocated process does not exist
Error of type: COR_AM_ERR, Code: 21
11/01/2013 10:00:18 Success 2568 MAC_AM am_allocq_send_r 8
Allocated process does not exist
Error of type: COR_AM_ERR, Code: 21