HONEYWELL TPS DCS SYSTEM

Sir
In our plant honeywell tps system working well since 2003. In our LCN 7 gus stations, HM (Node no.50) and AM (61) redundancy NIM (31&32) available. Last 10 years history module hard drive (1.8 gb) gives problems frequently such as MAINT, WARN and FAIL status and normalized as per procedure noted by seniors but not support by honeywell till date due to obsolete of History module service . At present History module failed condition ( always POWERON STATUS PERSIST) due to SELF TEST / ERROR RED LED GLOWN always not disappeard in SPC Module . How to rectify it.
How to retrieve soe points in uniformance phd node( AM) and logs/ trends.
 
Sir
In our plant honeywell tps system working well since 2003. In our LCN 7 gus stations, HM (Node no.50) and AM (61) redundancy NIM (31&32) available. Last 10 years history module hard drive (1.8 gb) gives problems frequently such as MAINT, WARN and FAIL status and normalized as per procedure noted by seniors but not support by honeywell till date due to obsolete of History module service . At present History module failed condition ( always POWERON STATUS PERSIST) due to SELF TEST / ERROR RED LED GLOWN always not disappeard in SPC Module . How to rectify it.
How to retrieve soe points in uniformance phd node( AM) and logs/ trends.
Sir

Have a read on this OEM manual notes:

Journal Display and Maintenance
Journal maintenance is the act of clearing journal entries or saving journal files to a
backup media. The NT Event Viewer can be configured for the size of the journal file
and for the policy for keeping or discarding events when the log is full. In addition, the
log file can be archived and retrieved later for viewing using the Event Viewer. The
Administrator is responsible for these maintenance policies.
PHD collects TPN Events and journals them into relational database tables. To view
these journals, any tools that can view relational database tables (e.g., MS Access) can
be used. Since the event journals are stored in relational tables, queries can be made to
search for desired events. The Event Journal tables must be maintained through the
relational database maintenance tools.

I am sure it can higlight some points that you are looking for!

Log file can be archieved & retrieved as mentionned on the above lines...

Also do you have a read on OEM manuals ,,,And what did you learned/retained from them

ControlsGuy25.
 
'Thank u sir.
My doubt is how to see the sequential events(DISOE) without History module in our tps release R630. Because of history module failed condition. How to format new hard disk suitable for 1.8 gb memory which can be used for HM. How to load HM .' if u have any procedure to format a new scsl harddisk and loading HM files
 
'Thank u sir.
My doubt is how to see the sequential events(DISOE) without History module in our tps release R630. Because of history module failed condition. How to format new hard disk suitable for 1.8 gb memory which can be used for HM. How to load HM .' if u have any procedure to format a new scsl harddisk and loading HM files
Thanks for the feedback!

Sorry I do not have such procedure...
Lets see if somebody can support you...

ControlsGuy25.
 
Here some notes from OEM document:

Use the procedure in Table 5.13 to load the personality. If the HMI
personality software is available on the History Module, you can do a
personality change directly, by selecting the LOAD/DUMP target on the
History Module Status display. If this is the case, skip Step 1
(it is not necessary to shut down the node to do a personality change).
Table 5.13 History Module Personality Loading Procedure
Step Action
1 Perform a node shutdown of the History Module. See the text above.
2 Load the HMI personality into the History Module.
3 Attempt to save as much data as possible using the BACKUP
function. Keep detailed records of which volumes/files were
recovered and which must be reloaded from an alternate known good
source.
4 Attempt to save Continuous History files. Keep detailed records of
which volumes/files were recovered and which were lost.
5 Load HVTS and run the SCMD test using Subtest 19. This test can
be configured to do a complete surface “Read Check” and
automatically add any bad sectors it encounters to the existing defect
list (Bad Sector List). A short period (approximately 10 minutes) of
running Subtest 14 will certify the read/write capability of the drive.
Additional tests should be run if there is any doubt concerning the
drive’s functionality.
An alternate method of drive recovery would be to completely
reformat the drive using Subtest 21 of the SCMD test under HVTS.
This test must be configured to add bad sectors (HVTS refers to
these as defective blocks) to the existing defect list (Bad Sector List).
Never run this test configured to clear the Bad Sector List.
This HVTS testing could reveal that the drive is defective and must
 
5.3.9 Redundant Drive Data Error Recovery

This failure could be a drive’s electronic failure or it could be a sectorrelated
problem where the software is unable to identify the sector address.
In either case, an exact diagnosis is not possible without shutting down the
History Module and running the HVTS off-line tests. One attempt to
“synch” the drive should be made in case the error was transient in nature.
If this is successful, the problem is resolved. If not, HVTS is required or
the drive must be replaced. The drive can be replaced while the History
Module continues full operation using the redundant (backup) drive.
Replacing the defective drive while its redundant partner is in full
operation is accomplished using the procedure in Table 5.16. Use extreme
care to prevent the accidental shutdown of the working drive(s).
Table 5.16 Redundant Drive Data Error Recovery Procedure –
Sector Not Known
Step Action
1 Use utility command OFF to set the suspected drive off-line.
2 If the History Module has redundant dual drives (4 drives), use the
utility command OFF to set all volumes on both Disk drives in the
same Winchester Drive Tray off-line.
3 Remove power from the tray that contains the defective drive.
4 Replace the defective drive using the procedures provided in this
manual, Sections 4 and 5. Pay particular attention to the drive’s
jumper block selections and whether termination modules should be
installed (front drive only).
5 Reapply power to the tray containing the replaced drive.
6 Use the utility command SYNCH to data synchronize the drive(s) that
is presently in the off-line state. One SYNCH command
 
Top