GC MAXUM ALARM MESSAGE(20140709)

[마음의 여유]

경보 #	메세지	종류	전투를 제안하였습니다
301	?? 외부 메세지 : 기능 정지를 주십시오	메세지는 그것 자신으로부터 받아졌습니다 또는 메세지의 공급원은 동일시 하게될 수 없습니다 또는 출입구는 너무 복잡합니다 또는 전달은 데이터 베이스와 메세지 손으로 만지는 사람 사이에 중단되었습니다	게이트 웨이 또는 Syscon을 고쳐 놓으십시오
302	?? 외부 메세지 : 봉사자는 패배하였습니다	일어나지 않습니다
303	외부 메세지 : 단위 %3로부터 B4 무가치한 통신	메세지는 홈들없이 이전에 방송하였던 ADH 단위로부터 받아졌습니다 또는 홈은 범위 넘음입니다.	ADH 단위를 재설정하십시오.
304	외부 메세지 : 고아 메세지는 %3로부터 받았습니다	외부 PANDSP는 어울린 PANKEY없이 받아들여졌습니다, 또는 부착합니다 어울린 제동기없이 받아들여졌습니다, 또는 내부 timeout는 존재하지 않은 메세지를 위하여 산출되었습니다.	Syscon을 무시하거나 고쳐 놓았습니다
305	?? 외부 메세지 : %3을 위해 무가치한 메세지 기간	결과, 인쇄, HAE, 또는 서비스 패널 메세지들은 길이를 가지고 있지 않는 데이터 베이스로부터 받았습니다.	수표 데이터 베이스는 이 메세지들을 위하여 공급하였습니다.
306	외부 메세지 : 단위 %3에 쓸모없는 전달을 주십시오	데이터 베이스로부터 메세지는 홈 (홈들의 쓸모없는 레인지)들을 가지고 있지 않는 ADH 단위까지 돌려집니다, 또는 어떤 UID도 이제까지 받아들여지지 않았습니다.	수표 ADH 단위 .
307	!! 외부 메세지 : 사본 anlz_id %3는 탐색하였습니다 ; 세팅	ZIP 메세지는 또 다른 ADH 단원으로부터 받아졌습니다, 또는 또 다른 Maxum는 같은 분석기 #와 방송하였습니다.	다른 수표 네트워크에 단위
308	!! 외부 메세지 : 사본 단위 %3는 탐색하였습니다 ; 세팅 루프 / 단위	SLEP 메세지는 받아졌습니다. 또 다른 ADH 단원은 같은 루프 / 단위로 방송하였습니다	다른 수표 ADH에 단위
309	?? 외부 메세지 : rud : 단원은 응답하지 않습니다 ; 루프 / 단위 %3	루프 / 단위가 RUD 메세지에 응답하지 않을 때 일어납니다 － 데이터 베이스에 I/O, 주인, 또는 인쇄기 테이블로부터 비롯합니다	존재하지 않은 단원까지 외부로부터인 참고를 돌이키십시오.  수표 ADH 연결 .
310	?? 외부 메세지 : %3으로 알려지지 않은 단위	메세지는 알려지지 않은 단위까지 보내기 위하여 데이터 베이스로부터 받아졌습니다.	단위는 ADH에 그것의 주둔을 방송하지 않았습니다.
311	?? 외부 메세지 : %에 EVT의 액티베이션을 위하여 잘못	나쁜 HAE 메세지는 데이터 베이스에 의하여 보내졌습니다	진행을 반격하십시오
312	?? 외부 메세지 : %3을 위한 오류를 보내십시오	UDP에 대한 기능 정지가 메세지 순서보다 멀리가도록 보내십시오	이것은 네트워크에 문제를 지적하는 종합적인 실패입니다.
313	?? 외부 메세지 : %3에게 쓸모없는 울퉁불퉁한 바위산 연속물	메세지를 보냅니다 보낼 결과가 있지 않을 때 외부 유닛으로부터 받아들여졌습니다	수표 결과는 바꿉니다(결과의 #).
314	?? 외부 메세지 : Anlz : %3 & Anlz : %4는 L/U을 투쟁으로 시킵니다	일어나지 않습니다
315	?? 외부 메세지 : Anlz 아이디는 ADH을 위한 지장 없는 한계를 초과합니다	FUNCT 여든 여덟 경보 메세지는 HCI-H로부터 받았습니다 － 또는 데이터 베이스는 analyzer_id와 방송을 시도하였습니다 > 255	수표 분석기 ID
316	?? 외부 메세지 : 주인 : Anlz 1에서 50 투쟁	FUNCT 여든 아홉 경보 메세지는 HCI-H로부터 받았습니다	점검 #는 결과로서 생깁니다 그리고 # 흐름
317	?? 외부 메세지 : 주인 : anlz 쉰 하나 ―254― > 1 흐름 또는 > 9개의 성분	FUNCT 아흔 경보 메세지는 HCI-H로부터 받았습니다	점검 #는 결과로서 생깁니다 그리고 # 흐름
319	?? 외부 메세지 : 주인 : 무가치한 데이타는 anlz로부터 받았습니다	어떤 결과도 변속기를 위해 표시되지 않습니다	결과 테이블에 점검 trtval
320	?? 외부 메세지 : %4을 위해 %3 Timeout	ADREQ, REXD, 결과, HAE, 인쇄, FUNCT을 위한 timeout을 보내십시오	syscon을 고쳐 놓으십시오
321	%3에 시작되는 외부 메세지 연결	고쳐놓기로부터 정상적인 메세지	아무것
322	?? 어떤 ADH 연결도 실패가 되는 %3을 발견하지 않았습니다	메세지 손으로 만지는 사람	고쳐놓기 Syscon 점검 부츠 선택 항목들
323	?? 외부 메세지 : 쓸모없는 루프 %3는 탐색하였습니다 ; 세팅 루프 / 단위	WRLP 메세지는 ADH로부터 받아졌습니다.	수표 루프
332	!! 공법을 달리게 하십시오 : 어떤 모듈도 detr을 위해 근거하지 않았습니다 : %3	압력 / 온도를 위한 sne 모듈의 위치를 정할 수 없습니다	app_tempctl (hrdwr_id을 위해 app_pressctl)을 검사하십시오
333	!! 공법을 달리게 하십시오 : 어떤 Detr도 근거하지 않았습니다 또는 방법을 위해 나쁜 상태 . 채널 : %3	쓸모없는 검파기에게 realtime chrom 시도, 또는 검파기에게 나쁜 상태	hrdwr_id (app_detector을 위해 모듈)을 검사하십시오
334	!! 공법을 달리게 하십시오 : 어떤 Channel도 방법을 위해 근거하지 않았습니다 : %3	어떤 채널들도 존재하거나 채널을 위한 검파기를 발견할 수 없지 않습니다	app_detector (EZChrom 방법)을 검사하십시오
336	!! SNE 연결은 %3 잘못에 닫았습니다 : %4	sne 연결은 timeout 또는 잘못 때문에 닫았습니다	수표 SNE
338	?? SNE %3 공법 %4는 Chrom을 저장할 수 없습니다	결과는 알려지지 않은 흐름을 위해 SNE로부터 받았습니다	점검 흐름 테이블
339	?? SNE %3 공법 %4 애플리케이션 %1는 근거하지 않았습니다	적용 또는 SNE와 대등하는 방법이 결과로서 생기는 것을 발견할 수 없습니다	아무것
340	!! 무가치한 공법인 SNE %3 공법 %4 적재	무가치한 방법은 SNE에 의해 탐색하였습니다	EZChrom로부터 방법을 다운로드하십시오
341	!! 활동하지 않은 SNE %3 공법 %4	SNE는 방법이 활동하지 않은 메세지를 보냈습니다	적용을 재출발시키십시오
342	!! SNE %3 공법 %4 적재 － Max 공법은 도를 넘었습니다	SNE는 최대치 순서가 초과되었던 메세지를 보냈습니다	방법 (고쳐놓기 Syscon)의 수를 줄이십시오
343	!! 무가치한 방법인 SNE %3 공법 %4 적재	쓸모없는 패스 / 집착은 SNE에 보냈습니다	다시 Sycon 또는 시험을 고쳐 놓으십시오
344	!! 알려지지 않은 잘못 %5인 SNE %3 공법 %4 상태	SNE methodstatus로부터 알려지지 않은 잘못	SNE/Syscon을 고쳐 놓으십시오
345	!! 흐름 밸브는 존재하지 않습니다	cycle_events에 DO을 위한 appdo 또는 sys_do이 두어지는 것을 발견할 수 없습니다	cycle_enents에 DO 아이디를 검사하십시오
346	!! SNE %3는 IO %4이 존재하지 않는 것을 기록합니다 %5	doen't는 데이터 베이스로부터 일어납니다
347	!! SNE %3는 IO %4이 존재하지 않는 것을 읽었습니다	읽었던 IO는 존재하지 않는 SNE에 보내졌습니다	SNE/Syscon을 고쳐 놓으십시오
348	!! SNE %3 RT chrom %4는 존재하지 않습니다	존재하지 않은 SNE에 realtime chrom 요구	SNE/Syscon을 고쳐 놓으십시오
349	349 !349 ! SNE %3 공법 %4 － 편지를 쓰십시오 활동적인 방법에 시도됩니다	사용하지 않았습니다
350	!! %4에게 SNE 모듈 입출력 오류 0x %3	고착된 SNE 모듈에 시도되는 운영은 실패하였습니다	잘못이 고객 원조에 %3와 모듈 %4을 세는 것을 보도하십시오
351	!! %4에게 SNE pSOS 잘못 0x %3	시스템 소프트웨어 기능 정지	고객 원조에 보고서 시스템 잘못 %3와 모듈 %4
352	!! %4에게 SNE pSOS 드라이버 잘못 0x %3	드라이버 소프트웨어 기능 정지	고객 원조에 보고서 드라이버 잘못 %3와 모듈 %4
353	!! %4에게 SNE AAi 드라이버 잘못 0x %3	AAI 관습 드라이버 기능 정지	고객 원조에 보고서 드라이버 잘못 %3와 모듈 %4
354	?? %3에게 SNE TFTP 장전 잘못 : %4	tftpload 기능 정지	TFTP 봉사자가 달리고 있고 IP 주소와 파일 장소를 위한 옳은 정보가 옳은 것을 아는 수표 .  그러면, 다시 노력하십시오
355	?? %3에게 SNE 플래시 드라이버 잘못 : %4	기억 실패를 급히 알리십시오	고집하다다면 SNE을 대체합니다
356	!! SNE %3 흐름 / 방법 %4/%5는 존재하지 않습니다	SNE로부터 받아지는 결과는 흐름 / 방법의 위치를 정할 수 없습니다	점검 순서
360	! %3 %4	SNE 결함을 장군으로서 지휘하십시오	일어나지 않을 것입니다, 고객 원조에 보고서
361	? %3 %4	SNE 경고를 장군으로서 지휘하십시오	일어나지 않을 것입니다, 고객 원조에 보고서
362	+ %3 %4	SNE 정보를 장군으로서 지휘하십시오	일어나지 않을 것입니다, 고객 원조에 보고서
363	!! SYSCON로부터 쓸모없는 기능 요구 %3	SYSCON는 부정한 메세지들 또는 SNE/SYSCON 메세지들을 보내며 동조에서 있습니다	시스템을 재시동 하십시오
364	?? 어떤 realtime 완충기도 DPM %4에게 검파기를 위해 존재하지 않습니다	적당히 할 수 있게 되지 않았던 검파기를 위해 모아지는 검파기 데이타 .	만약 장전 순서 동안에 받아들여지면, 그것은 일시 휴업 순서의 가공품입니다.  다른 방법으로, 고객 원조에 occurance와 %4 그리고 보고서를 기록하십시오
365	!! 채널 %3에게 불완전한 분석	EZChrom 분석은 채널에 완료되지 않았습니다	방법에 통합 사건을 수정하는 것을 시도하십시오.  고객 원조에 불쾌한 방법을 보내십시오
366	!! 데이타 부패 잘못	SNE에게 데이터 오염을 전공하십시오.	SNE (보고서 잘못)을 고쳐 놓으십시오
367	!! 파일 %4 선 %5에 시스템 잘못 %3	시스템 소프트웨어 기능 정지	%3의 가치들과 사건과 보고서 잘못에 이르게 하는 기록한 문서 순서, 고객 원조에 %4와 %5
368	!! 할 수 없다 %3이 %4을 세는 것을 발견하기 위하여	하드웨어는 공법이 분석기에 없다라는 점에서 명시하였습니다	수표 방법
369	!! 받쳐지지 않은 채널 형 %3	하드웨어 채널 운영은 병약한 채널 형을 위해 요구하였습니다	SNE의 현재 버전을 위해 소프트웨어를 검사하십시오.  리로드를 요구할지도 모르거나 타락한 SysCon의 데이터 베이스를 재건할지도 모릅니다
370	?? realtime을 위해 DPM %4에게 어떤 채널 %3도 전시하지 않습니다	현실의 시간 디스플레이는 존재하지 않는 검파기 채널을 위한 그를 요청하였습니다	이것은 매수된 데이터 베이스로부터 가능하지 않을 것입니다.
371	!! 무가치한 채널 취득은 %3에 부분적으로 중복됩니다	같은 하드웨어 검파기를 참조사항을 붙이는 2 채널은 얻다 동시에 예정입니다.	만약 당신이 같은 하드웨어 검파기에게 다중 응용 검파기 도랑들이 할당하도록 하면, 그들의 시간들을 만드십시오 부분적으로 중복되지 마십시오
372	!! %4 # %5 채널 %6을 자세히 조사하는 일정 계획 잘못 %3	할 수 없다 모든 사건과 투표 틀에 박힌 듯한 방식들의 표를 만들기 위하여 .	기억 또는 하드웨어 고장 문제일 것입니다.  만약 방법이 사건의 엄청난 수뿐만 아니라 모든 18명의 검파기를 예정하면, 몇몇의 사건 또는 제거를 돌이키는 것을 시도하십시오 몇몇 검파기들의 그리고 SNE을 고쳐 놓으며 .
373	!! %4 # %5 채널 %6에게 모듈 입출력 오류 %3	모듈 %4 국제 알파벳 번호 5는 채널 여섯을 다루는 운영에 오류를 가지고 있었습니다	이 오류는 최신식인 분석기들에 떠오르지 않을 것입니다.  그들은 SysCon에 의하여 지금 해석됩니다.
374	!! 내부 전달 잘못 %3	SNE 이내에 소프트웨어 모듈들은 통신하는 것을 실패하고 있습니다.  대체로 SysCon timeout에서 기인하는 기억 상태에서 일어납니다	SysCon을 보증하는 동작을 하는은 과도한 처리 요구 조건들과 교착상태에 빠지게 되지 마십시오
375	!! 주기 말은 실패하였습니다 ; 멈추고 있는 순환	메세지 SNE 일의 주위에 방법의 목적이 잃게 되었던 그 좌표	SNE 운영은 타협되고 고쳐지어야 합니다.  수표 그리고 SNE 자세의 복잡함을 격하시키거나 SNE을 대체할 어떠한 길도 있는 지를 아십시오
376	+ Adjusting cycle clock master	Not valid for recent versions
377	! Error %3 scheduling cycle clock master adjustment	Resource for scheduling adjustment of event clock cannot be found	SNE may be overloaded.  Try reducing complexity of tasks for SNE.  SNE will need to be reset before event clock overflow.
378	+ %3 samples adjusted on chrom from channel %4	An inordinate number of samples had to be adjusted on Chrom	This should only occur in conjunction with some DPM alarms.  Replace affected DPM.
379	! Error %3 preparing analysis for channel %4	EZChrom processing error	Check integration events, try to modify any potentially problem events.
380	! Error %3 finding chrom peaks for channel %4	EZChrom processing error	Check integration events and peak table and modify any potential problem areas
381	! Error %3 generating results for channel %4	EZChrom processing error	Check method for any problems that could affect results
382	! EZchrom server failed	Resource problem on SNE	Attempt to reduce SNE workload or replace SNE
383	? Software Watchdog Timeout	SNE is running out of processing throughput	See if SNE workload can be reduced
384	! Method Modification Failed	An attempt to modify a running method failed	Most probably was fed invalid data.  Please check that modification was valid.
385	? Event Occured before modification request	Before a modification of a running method was completed, the event occurred
386	! Invalid Cycle Length %3	A cycle length larger than the maximum size was specified in a method	Most likely a corrupt method, since the maximum cycle length is approximately 2 days.
387	! Invalid Sample Rate %3 on channel %4	Invalid sample rate value chosen for channel in method
388	! Acquisition time greater than cycle length on channel %3	Start and stop acquisition times for a detector exceeded the method cycle length	Decrease acquisition time or increase cycle method time
389	! Invalid Event Type %3 for event %4	Invalid event downloaded with method	Check for proper SNE version or rebuild method
390	! Invalid Start Time %3 for event %4	Event time specified that is not within the cycle start and stop times
391	? %3 messages not sent to Syscon from SNE	Some messages that the SNE attempted to send to SysCon were lost.  Results may be unpredictable
392	? %3 Detector underflows detected on channel %4 of module %5	Detector is reading a raw value of 0.  It is potentially clipping the signal at the low value
393	? %3 Detector opens detected on channel %4 of module %5	Detector channel is not connected
394	? %3 Unexpected Calibration points on channel %4 of module %5	Detector channel went unexpectedly into calibration mode	Replace DPM if persistent
395	? %3 Detector overflows on channel %4 of module %5	Detector is reading above its maximum value and the signal is being clipped
396	! SNE out of memory at %3 line %4		Try to alleviate SNE workload.  Please report %3 and %4 values to Customer Support
397	! Invalid Trace from channel %3	No longer used
398	! Invalid Number of Temperature Program Segments	The number of temperature program setpoints was different from the number sent	Try to rebuild temperature program for method
399	+ Results not calculated for Channel %3	No longer used
400	! Sync Bus Failure %3	Sync Bus Test failed	Replace SNE
402	+ SNE reset requested	SysCon requested a reset from the SNE.	Usually means that the communications between the SNE and SysCon timed out.  This is can happen when SysCon is overloaded
403	! Configured Detector %3 Balance Failure	Balance Failure from an Advance+ detector	Check detector elements
404	? All Methods must be in Hold before Configuring Detectors	All methods must be in hold while describing any configured detectors
511	! Program Failed event # %3 %4	error running MaxBasic program called from an external source	check message and program
512	? Program execution cancelled: event # %3	doesn't occur
513	! Program Failed: Run requested on running event # %3	doesn't occur
514	! Program Invalid frequency; disabling event # %3	invalid program frequency	check freq_unit
561	+ Ezchrom download	doesn't occur
562	+ Ezchrom upload for app %1 method %3	doesn't occur
671	! Database: Failure: %3	1. can't find method; 2.can't find MaxBasic program 3. Invalid stream for program 4. Bad status on external result	1. check methods, sequences 2. Check program table 3. Check program streamcontext 4. Verify extresult table entries
672	! Database: Remote Service lost on %3	doesn't occur
673	! Database:value > limit: %3	limit exceeded	defined in limit and alarmhandler tables
674	! Database value < limit: %3	limit exceeded	defined in limit and alarmhandler tables
675	! Database: No Stream at cycle start on applicaton %1	can't locate stream to start	check sequence; make sure that the entries are enabled
676	! Database: delay limit exceeded on stream %3	temperature or pressure wait has been exceeded	check temp or press controller
677	! Next Stream Error	can't locate next stream in sequence	check sequence
678	! End of Cycle occured before events complete	entry in program execution table at the end of cycle	probably bogus - removed in Version 3.1
679	! Application is out of service	attempt was made to move results for an out of service application	put application in service
680	? print job failed: %3 for Printer: %4	print failure	print again
681	! Application is disabled	attempt was made to set disabled application to run	enable application
682	! Database: i/o failure: %3	bad status on AO, DO write	check I/o channels
683	! Database: no normal sequence for application: %3	no active sequence	check sequences
684	! Database: no enabled entries in sequence	can't find enabled entry in sequence	check sequence
685	? Printer: TCP connection or queue failed	Printer connection failed	check address in printer table
686	? Printer: TCP Print failed	communication failure with TCP printer	try again
687	! Results for cycle %3 lost due to SNE reset		automatically repaired - no action necessary
688	! method is corrupt: %3 reload from EZChrom	method is corrupt	download method from EZChrom
691	? Database: Warning: %3	doesn't occur
692	! Database: Divide by zero in %3	peak measured value is zero	check method
693	? Database: i/o warning: %3	doesn't occur
694	? Database:value > limit: %3	limit exceeded
695	? Database value < limit: %3	limit exceeded
696	? DB: Screen access denied	doesn't occur
697	! DB: Run requested on disabled program: %3	doesn't occur
698	? MODBUS: NAU %3 not available to receive results	1. No analyzer reference in host table for Maxum Modbus   2. Can't open remote analyzer for Maxum Modbus	1. Check host table anlzref 2. Check network+D15
699	? MODBUS: result is not in address map  %3	can' t find address in map for result or analyzerstatus that came from an analyzer	check modbus_addmap
700	? MODBUS: Analyzer %3 not available to receive host commands	analyzer can't be opened from NAU	check network, reset Syscon
701	? MODBUS: scale factor or euhi absent for %3	doesn't occur
702	? MODBUS: host command for %3 invalid; undefined database location	doesn't occur
703	? MODBUS: host command for undefined address: %3	host message received that is for an unknown address	check modbus_addmap
704	? MODBUS: host can't write to this address: %3	The address is not defined with a value_type that the host can send messages to	check value_type of address im modbus_addmap
705	? MODBUS: host command can't be processed: %3	1. Invalid host command was sent to an optichrom 2. EUHI, calibrate, stream select, skip stream, run/hold, doset set from host that can't be located in analyzer table	1. Can't clear alarms on optichrom 2. Check analyzer
706	? MODBUS: can't locate euhi %3	can't find euhi for result	check euhi address in modbus_addmap_result table
707	? Calibration rejected: margin exceeded for %3	peak margins exceeded on auto calibration	check peak margins in EZChrom
708	? MODBUS: Data type failure for address: %3	data_type mismatch with value_type	check modbus_addmap.  This is usually self-correcting, but changes should be checked.
711	+ Database: %3	doesn't occur
712	! System Startup Ver: %3 - %4 on %5	Syscon has been reset	normal
713	+ System backed up	doen't occur
714	+ All alarms cleared	doesn't occur
900-996	custom alarms from alarmhandler table	text as in alarmhandler table
715	+ Database Build	doesn't occur
997	3%	general alarm - may originate from MaxBasic	nothing
998	? %3	general alarm - may originate from MaxBasic or be a general DB runtime error	runtime errors should be reported immediately to SAAI customer support - please make careful note of the alarm message.
999	! %3	general fault alarm - may originate from MaxBasic, or may be software problem	runtime errors should be reported immediately to SAAI customer support - please make careful note of the alarm message.
1002	Id Key Not Connected on %4	All PICs: The module location id connector is disconnected or set to 0.  This is an abnormal condition and the module is not guaranteed to be operational	Verify that the location id connector is in good condition and connected properly.
1003	Id Key Change on %4	All PICs: The module location id value was changed while the module was operating.  This is a transient error.  When it happens, the module automatically resets and can then be addressed at the new location id. The module is operational at the new address.	Verify that the location id connector is in good condition and tightly connected.  Check for intermittent connection.
1004	EEPROM Bad Checksum on %4	All PICs: A checksum error was detected in the module EEPROM.   The firmware will still use all the information that it can read from the EEPROM, however the module may not operate normally.	Cycle power and if it happens again replace the module
1005	Temp Diag Error on %4	All PICs: The on-board temperature sensor (LM-75) diagnostic failed.  The alarm generation in case of a module overheat (alarm #1044) may not happen.  This alarm is in no way related to and should not be confused with the Overtemp Shutdown on a temperature controller.  This alarm is known to happen occasionally, on fully functional board, following a board reset,.	Nothing should be done unless it happens systematically.  If it does, replace the module
1007	Firmware Fault on %4	All PICs: A “run-time” error was detected in the PIC firmware.  For example, a timer is turned off at a point where the firmware expects it to be on.  The firmware will attempt to recover.  Usually an additional specific flag will be set to provide more information about the cause of the fault	Report to AAI for further investigation
1008	EEPROM Bad Value on %4	All PICs: A value read from EEPROM is out-of-range or invalid.  This may happen if a board’s EEPROM was incorrectly initialized during manufacturing.   It may also happen if the EEPROM was not at all initialized and is then set together with the EEPROM_BAD_CHECKSUM flag	Cycle power and if it happens again replace the module
1009	Local I2C error on %4	All PICs: A fatal error was detected while accessing the internal, on-board I2C bus.  The communication with the EEPROM or the LM75 (on board temperature sensor) may be impossible.	Cycle power and if it happens again replace the module
1010	Fatal error on %4	All PICs: An error or an invalid operational condition was detected by the PIC firmware.  The board is shutdown to a failsafe mode.	Report to AAI for further investigation
1041	AO Out Of Range on %4	All PICs: An AO was set to a value outside of the allowed range.  The value was clipped to the allowed range.                                              For example an EPC has a 0 to 100 psi nominal range for the pressure setpoint.  An attempt to set the setpoint to 150 psi results in an “AO out of range” and the setpoint is clipped to remain within the allowed range (100 psi).	Locate the problematic AO and change the AO value to a value within the proper range.
1042	Invalid Group Channel on %4	All PICs: The hardware I/O channel(s) requested does not exist on the module.	Check the “Sys Hardware” table for invalid entries.  Check that only detector channels are specified in the detector I/O table. Check that only EPC are defined in the pressure controller table. Check that only temperature controllers are defined in the temperature controller table.
1043	Invalid EEPROM Address on %4	All PICs: The on-board EEPROM addresses requested do not exist or cannot be accessed within a single command. Should happen only during board manufacturing.	Report to AAI for further investigation
1044	Board over-heating on %4	All PICs: The module temperature is greater than the defined maximum operating temperature (default 65 DegC) and there is now a possibility that the module life expectancy will be reduced because of overheating.  This alarm is in no way related to and should not be confused with the Overtemp Shutdown on a temperature controller.  An over-heating condition can cause permanent damages to the analyzer electronic and should be dealt with as soon as possible.                                                     Note:  This alarm can show together with an alarm 1005 (Temp Diag Error) in which case the board may not be really overheating.	If the overheating condition is real, determine and fix the cause of high operating temperature.  Look for:     · Ambient temperature higher than specification                                                · Inoperative fan in the EC (restricted air flow inside the EC
1045	Output Locked on %4	All PICs: The state of the DO or the value of the AO are locked and cannot be changed.  The AO or DO command was ignored. Some DO and AO are locked during a board self-test.	When performing a board self-test, all other operation affecting the board should be suspended.
1081	Data Not Ready on %4	All PICs: The data requested is not available.  Should happen only during board manufacturing.	Report to AAI for further investigation
1082	Reset Detect on %4 %5	All PICs: A reset was detected.  Normal indication that the PIC was reset	Ignore
1083	Power Up on %4 %5	All PICs: A power-up cycle was detected. Normal indication that the PIC was just powered-up	Ignore
1084	I2C Timeout on %4	All PICs: An I2C communication timeout timer has expired. The timer is reset after each successful character processed.  Only an addressed module may get a timeout.  The timeout is checked on character going in as well as character going out	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
1085	I2C Read Past End on %4	All PICs: The I2C communication master did not stop reading after the complete response had been sent.	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
1086	I2C Buffer Overflow on %4	All PICs: The combination of the transmit and receive I2C message was too big causing a buffer overflow.               (With kernel rev 1: SSP_READ_UNEXPECTED_STOP,  a stop condition occurred before the end of the response)	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
1087	I2C Write Past End on %4	All PICs: In an I2C message, more than the number of bytes specified by the length was written. The extra bytes are ignored.	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
1088	I2C Resync Error on %4	All PICs: Severe I2C error, causing the current message to be dropped.  It will re-synchronize after the next START or STOP condition.  Most of the time this is associated with an alarm 1092.	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
1089	I2C Write Unexpected Stop on %4	All PICs: A new I2C message was received in the middle of a write.  The old message was discarded and the new message is served (this message may be out of sequence and therefore cause other flags to be set).     (With kernel rev 1: SSP_WRITE_UNEXPECTED_STOP, During a slave write, a stop condition occurred before the message was completed.  The message is ignored )	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
1090	I2C Write Unexpected Strt on %4	All PICs: A new I2C message was received in the middle of a read.  The old message was discarded and the new message is served (this message may be out of sequence and therefore cause other flags to be set).     (With kernel rev 1: SSP_WRITE_UNEXPECTED_START, During a slave write a Start or Repeat Start (RS) condition was detected before the entire message was received (according to the length field).  The message is ignored and processing resumes following the Start or Repeat Start )	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
1091	I2C Write Before Read on %4	All PICs: An attempt was made to write an I2C message before reading the response from a previous message.  This means that an attempt was made to do a  Slave Write - RepeatStart - Slave Write combination	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
1092	I2C Read Unexpected on %4	All PICs: An I2C read from the peripheral was attempted before a slave write loaded a command	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
1093	I2C Invalid Checksum on %4	All PICs: An I2C message with an invalid checksum was received.  The message was ignored	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
1094	Data not available on %4	All PICs: Some data was lost and is no longer available.  For a detector channel it means that a “Detector Read” command was received with an invalid index.  This can happen when a request to retransmit detector data came too late when the data was already gone from the buffer. This situation may also happen while accessing the I/O related to the LM75 (BOARD_TEMPERATURE and OVERTEMP_SETPOINT).  It indicates that the local I2C bus was not available to perform the desired action.	Cycle power and if it happens again replace the module or the SNECON
1095	Invalid Message on %4	All PICs: An I2C message with a valid checksum was not recognized or had an invalid op-code	Cycle power and if it happens again replace the module and/or the SNECON
1121	Firmware Math error on %4	All PICs: An unexpected math operation error was detected by the PIC.  It can be an un-handled overflow, underflow, etc…  This flag is always associated with a FIRMWARE_FAULT flag.	Cycle power and if it happens again replace the module
1122	Firmware Mem error on %4	All PICs: A jump or a call was made to an invalid PIC memory location causing the PIC to be reset.  This flag is always associated with a FIRMWARE_FAULT flag.	Cycle power and if it happens again replace the module
1123	Firmware Table error on %4	All PICs: An error was detected when addressing an internal PIC firmware table.  The index in the table is likely to be invalid.  This flag is always associated with a FIRMWARE_FAULT flag.	Cycle power and if it happens again replace the module
1124	Firmware Watchdog on %4	All PICs: The PIC watch dog timer has expired causing a module reset.  This flag is always associated with a FIRMWARE_FAULT flag. It can be an indication that the I2C clock or data line was held low for more than the timeout duration (nominally 30 ms).	Cycle power and if it happens again replace the module
1125	Firmware System Monitor on %4	All PICs: The background system monitoring task has discovered a problem causing the PIC to be reset.  It can be that the interrupt or timer were disabled when they should have been enabled, and the like.  This flag is always associated with a FIRMWARE_FAULT flag.	Cycle power and if it happens again replace the module
1126	Firmware Application on %4	All PICs: A general PIC firmware error was encountered causing a board reset.	Cycle power and if it happens again replace the module
1317	Valve Switch Error on %4	SVCM PIC: The SVCM firmware has detected an invalid condition in the circuit driving the solenoid valves.  One or more valve is likely to be malfunctioning	Replace the module
1318	J10 Disconnected on %4	SVCM PIC: The SVCM J10 connector is not properly connected and the corresponding bank of solenoid may not work	Check the corresponding connection
1319	J11 Disconnected on %4	SVCM PIC: The SVCM J11 connector is not properly connected and the corresponding bank of solenoid may not work	Check the corresponding connection
1617	LWH1 Output Fault on %4	PECM PIC: On-board diagnostic indicating that LWH1 is not working correctly.  This diagnostic is active only when a SSR output is configured for PECM self control, when the loop-back connector is present.  The diagnostic is not active when the control is from a temperature controller.	If associated with an “Invalid configuration alarm” (1659), then check the corresponding connection on J3 on PECM.  Otherwise, replace the PECM
1618	Lwh2 Output Fault on %4	PECM PIC: On-board diagnostic indicating that LWH2 is not working correctly.  See 1617 for more details	Check J4 on PECM …  See 1617
1619	Lwh3 Output Fault on %4	PECM PIC: On-board diagnostic indicating that LWH3 is not working correctly.  See 1617 for more details	Check J5 on PECM …  See 1617
1620	Lwh4 Output Fault on %4	PECM PIC: On-board diagnostic indicating that LWH4 is not working correctly.  See 1617 for more details	Check J6 on PECM …  See 1617
1621	Lwh5a Output Fault on %4	Not implemented…
1622	Lwh5b Output Fault on %4	PECM PIC: On-board diagnostic indicating that LWH5B is not working correctly.  See 1617 for more details	Check J7 on PECM …  See 1617
1623	Lwh6a Output Fault on %4	Not implemented…
1624	Lwh6b Output Fault on %4	PECM PIC: On-board diagnostic indicating that LWH6B is not working correctly.  See 1617 for more details	Check J8 on PECM …  See 1617
1625	ABH1 Output Fault on %4	PECM PIC: On-board diagnostic indicating that ABH1 is not working correctly.  See 1617 for more details	Check J91 on PECM …  See 1617
1626	ABH2 Output Fault on %4	PECM PIC: On-board diagnostic indicating that ABH2 is not working correctly.  See 1617 for more details	Check J92 on PECM …  See 1617
1627	ABH Ctrl Plug Missing  on %4	PECM PIC: The air bath heater control cable is missing in J9 and at least one of the air-bath heaters is non-disabled.  If the cable is missing, the NO_AIR_ABH_x flag will also be set on the non-disabled air-bath heater channels	If the air bath heater is not used, then disconnect J91 and J92 on PECM in order to eliminate the alarm.  Otherwise check J9.
1628	ABH Air Plug Missing on %4	PECM PIC: The air-bath heater air-sensor connector is missing and at least one of the air bath heaters is non-disabled.	Check J10 on PECM.
1629	Purge Indicator not available on %4	PECM PIC: Neither the SYSCON nor the MMI level 1 LED panel is connected.  It indicates that there is no purge indicator connected, the PECM has nowhere to report the purge information.	Check J1302 and J101 on PECM.  Verify the cable connected into J1302.
1657	ABH1 No Air on %4	PECM PIC: The air bath heater #1 is turned off, as the air pressure is too low for a safe operation of the heater. This flag is set only if the corresponding air bath heater is in-use.  The PECM considers the air bath heater in-use if a loop-back connector or a cable from a temperature controller is connected.	· If the channel is not in-use, disconnect the loop-back connector or temperature controller cable.        · Check the air pressure on the corresponding air bath heater.  Make sure that it is 10 psi or above.      · Electrically disconnect the pressure switch and verify that it operates normally by measuring the contact resistance with a multimeter at 0 and 10 psi.  Verify that with the multimeter that there is no continuity to ground.  Verify the harness with the multimeter.           · Replace the PECM
1658	ABH2 No Air on %4	PECM PIC: The air bath heater #2 is turned off, as the air pressure is too low for a safe operation of the heater. This flag is set only if the corresponding air bath heater is in-use.  The PECM considers the air bath heater in-use if a loop-back connector or a cable from a temperature controller is connected.	· If the channel is not in-use, disconnect the loop-back connector or temperature controller cable.        · Check the air pressure on the corresponding air bath heater.  Make sure that it is 10 psi or above.     · Electrically disconnect the pressure switch and verify that it operates normally by measuring the contact resistance with a multimeter at 0 and 10 psi.  Verify that with the multimeter that there is no continuity to ground.  Verify the harness with the multimeter.           · Replace the PECM
1659	Invalid Configuration on %4	PECM PIC: An attempt is made to control a heater output with a DO command and the corresponding loop-back cable is not installed	Install or verify the corresponding PECM loopback plug
1697	Purge Loss on %4	Purge failure in the EC enclosure. The pressure differential between the interior and exterior of the EC is not high enough.	Depending of the environment classification where the analyzer is used, this may be an alarm that requires immediate action to correct the situation or an alarm that can be totally ignored
1917	Balance Hardware Failure TCD L %5 on %4	Not implemented…	Not implemented…
1918	Balance Hardware Failure TCD U %5 on %4	Not implemented…	Not implemented…
1919	A/D Failure TCD L %5 on %4	TCD DPM Detector PIC: Set when the corresponding Analog to Digital Converter hardware does not work properly.  The flag will be set if the A/D internal calibration cycle is not completed within a pre-determined period of time or the A/D does not report any valid data within a pre-defined timeout period.     Note:  A firmware problem affecting the version 1.000 of the TCD detector PIC may cause an A/D failure flag to show-up occasionally following a PIC reset.  This is not a sign of a defective A/D converter.	Cycle power and if it happens again consistently then replace the module
1920	A/D Failure TCD U %5 on %4	TCD DPM Detector PIC: Set when the corresponding Analog to Digital Converter hardware does not work properly.  The flag will be set if the A/D internal calibration cycle is not completed within a pre-determined period of time or the A/D does not report any valid data within a pre-defined timeout period.      Note:  A firmware problem affecting the version 1.000 of the TCD detector PIC may cause an A/D failure flag to show-up occasionally following a PIC reset.  This is not a sign of a defective A/D converter.	Cycle power and if it happens again consistently then replace the module
1921	PIC Timeout on %4	Not implemented…	Not implemented…
1922	Incompatible Hardware on %4	TCD DPM Detector PIC: The PIC firmware is not compatible with the DPM board	Replace the module
1957	Balance Failure TCD L %5 on %4	TCD DPM Detector PIC:                                 Rev 1 TCD DPM:                                                                 A detector balance sequence failed because of a hardware failure or because of an improper configuration or sequence of events.  Some possible causes are:                         1) The detector beads are too unbalanced to be “balance-able”.     2) The detector signal is not stable enough and proper balance could not be obtained before the maximum number of iterations was reached.   3) The A/D or D/A do not work properly.      4) The detector is not configured for acquisition or turned off.     5) SIMULATE_TCD_x  is set to ‘1’, the balance cannot be done in detector simulation mode.   6) The balance is disabled (DISABLE_BALANCE_TCD_x is set to ‘1’).     7) The sampling period was changed during the balance sequence.      Rev 2 TCD DPM:    Not implemented …	Refer to "Detector Balance Troubleshooting.doc"
1958	Balance Failure TCD U %5 on %4	TCD DPM Detector PIC:     Same as alarm 1957 for upper channel	Refer to "Detector Balance Troubleshooting.doc"
1959	Balance Out Of Limit TCD L %5 on %4	TCD DPM Detector PIC:                             Rev 1 TCD DPM:  A detector balance value is above the normal limits.  The balance may still work as this is an early warning.            Rev 2 TCD DPM:      Not implemented	If associated with a balance failure (alarm 1957), then the source of the balance failure must be corrected.    If not associated with a balance failure and the balance limits are normal (>9 Volts or 90%) then maintenance should be scheduled to replace the detector beads.
1960	Balance Out Of Limit TCD U %5 on %4	TCD DPM Detector PIC:                             Rev 1 TCD DPM:     A detector balance value is above the normal limits.  The balance may still work as this is an early warning.                       Rev 2 TCD DPM:        Not implemented	If associated with a balance failure (alarm 1958), then the source of the balance failure must be corrected.     If not associated with a balance failure and the balance limits are normal (>9 Volts or 90%) then maintenance should be scheduled to replace the detector beads.
1997	Buffer Overflow TCD L %5 on %4	TCD DPM Detector PIC: The PIC detector data buffer filled-up before an I2C command was received to retrieve the data.  Some data was lost. The SNECON was not fast enough to come to retrieve the points or that the SNECON stopped polling without turning off the corresponding detector channel. This may happen with a combination of a very high speed detector with a large burst of I/O commands	· Staggering the balance events and valve switching events by maybe 10-20 ms will distribute the load on the I2c bus and may fix the problem.                                        · Disconnect the SNECON debug cable (if connected) and reset.            · Reload SNE-OS and APP software.D155
1998	Buffer Overflow TCD U %5 on %4	TCD DPM Detector PIC: Same as alarm 1997 but for the upper channel	Same as alarm 1997 but for the upper channel
1999	Detector Disabled on %4	TCD DPM Detector PIC: An attempt was made to read detector information from a disabled detector.	Cycle power and if it happens again replace the module
2217	Balance Hardware Failure FID on %4	Not implemented…	Not implemented…
2218	Balance Hardware Failure TCD on %4	Not implemented…	Not implemented…
2219	A/D Failure FID %5 on %4	FID DPM Detector PIC: Set when the corresponding Analog to Digital Converter hardware does not work properly.  The flag will be set if the A/D internal calibration cycle is not completed within a pre-determined period of time or the A/D does not report any valid data within a pre-defined timeout period.	Cycle power and if it happens again consistently then replace the module
2220	A/D Failure TCD %5 on %4	FID DPM Detector PIC: Set when the corresponding Analog to Digital Converter hardware does not work properly.  The flag will be set if the A/D internal calibration cycle is not completed within a pre-determined period of time or the A/D does not report any valid data within a pre-defined timeout period.	Cycle power and if it happens again consistently then replace the module
2221	PIC Timeout on %4	Not implemented…	Not implemented…
2225	Glow Plug Bad on %4	FID DPM Detector PIC: The glow plug is not working correctly.  The diagnostic is performed when the board is reset or when an attempt is made to light the flame.  The hardware diagnostic verifies that a minimum current and voltage is present, checking for a short and open glow plug.	Confirm‎ that the glow plug cable is securely inserted in J5.  Replace the glow plug.  Replace the DPM
2257	Balance Failure FID on %4	FID DPM Detector PIC:   A detector balance sequence failed because of a hardware failure or because of an improper configuration or sequence of events.  Some possible causes are: 1) The detector signal is not stable enough and proper balance could not be obtained before the maximum number of iterations was reached.                                                            2) The A/D or D/A do not work properly.          3) The detector is not configured for acquisition or turned off.                                    4) SIMULATE_FID  is set to ‘1’, the balance cannot be done in detector simulation mode.     5) The balance is disabled (DISABLE_BALANCE_FID is set to ‘1’).          6) The sampling period was changed during the balance sequence.	Refer to "Detector Balance Troubleshooting.doc"
2258	Balance Failure TCD on %4	FID DPM Detector PIC:    A detector balance sequence failed because of a hardware failure or because of an improper configuration or sequence of events.  Some possible causes are:                                                           1) The detector beads are too unbalanced to be balanced corrected.                                     2) The detector signal is not stable enough and proper balance could not be obtained before the maximum number of iterations was reached.                                                    3) The A/D or D/A do not work properly.          4) The detector is not configured for acquisition or turned off.                                                5) SIMULATE_TCD  is set to ‘1’, the balance cannot be done in detector simulation mode.     6) The balance is disabled (DISABLE_BALANCE_TCD is set to ‘1’).     7) The sampling period was changed during the balance sequence.	Refer to "Detector Balance Troubleshooting.doc".
2259	Balance Out Of Limit FID on %4	FID DPM Detector PIC: A detector balance value is above the normal limits.  The balance may still work as this is an early warning	If associated with a balance failure (alarm 2257), then the source of the balance failure must be corrected.      If not associated with a balance failure and the balance limits are normal (>9 Volts or 90%) then maintenance should be scheduled to clean or replace the FID detector.
2260	Balance Out Of Limit TCD on %4	FID DPM Detector PIC: A detector balance value is above the normal limits.  The balance may still work as this is an early warning	If associated with a balance failure (alarm 2258), then the source of the balance failure must be corrected.     If not associated with a balance failure and the balance limits are normal (>9 Volts or 90%) then maintenance should be scheduled to replace the detector beads.
2265	Flame Ignition Failure on %4	FID DPM Detector PIC: The FID flame could not be lit within a 25 sec delay.  No other attempt will be made to automatically light the flame until the MANUAL IGNITION DO is activated.	· If associated with an alarm 2225 (Glow plug failure), then diagnose and fix this other alarm first.               · If a BASIC program is used to control the electronic pressure controller (EPC) to adjust the gas mixture for proper ignition, confirm‎ that the poll rate of the “IGNITE” DI is set to 2 sec.                               · Check that the gas supply pressure is adequate.                     · Verify the proper operation of the EPC.
2297	Buffer Overflow FID on %4	FID DPM Detector PIC: The PIC detector data buffer filled-up before an I2C command was received to retrieve the data.  Some data was lost. The SNECON was not fast enough to come to retrieve the points or that the SNECON stopped polling without turning off the corresponding detector channel. This may happen with a combination of a very high speed detector with a large burst of I/O commands	· Staggering the balance events and valve switching events by maybe 10-20 ms will distribute the load on the I2c bus and may fix the problem.                                        · Disconnect the SNECON debug cable (if connected) and reset.          · Reload SNE-OS and APP software.
2298	Buffer Overflow TCD on %4	FID DPM Detector PIC: Same as 1997 but for the TCD channel	Same as 1997 but for the TCD channel
2299	Detector Disabled on %4	FID DPM Detector PIC: An attempt was made to read detector information from a disabled detector.	Cycle power and if it happens again replace the module
2305	Flame Out on %4	FID DPM Detector PIC: The flame is out, the data generated on FID channel is probably not valid.	Check that the flame gas supply is adequate.     Verify the operation of any associated  EPC.
2306	FID Bias Off on %4	FID DPM Detector PIC: The detector is used while the 300 Volts bias is disabled.  The data validity is unknown.	Set the “disable bias” DO to ‘0’
2500	I2C Premature Stop on %4	SNECON I2C driver:  A stop condition was detected in the middle of a transfer (SNECON hardware rev 2.x)	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
2501	I2C No Acknowledge (Module Disconnected?) on %4	SNECON I2C driver: No module responding to the I2C address.  A module was disconnected or is no longer responding	Reset the analyzer
2502	I2C NS486 Timeout Overflow on %4	SNECON I2C driver: An  I2C communication timeout condition was detected (SNECON hardware rev 2.x)	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
2503	I2C Address is Odd on %4	SNECON I2C driver:  Illegal I2C address	Reset the analyzer.  Reload SNE OS
2505	I2C Driver Not Initialized	SNECON I2C driver:  An attempt was made to communicate to the I2C driver before it’s initialized	Reset the analyzer.  Reload SNE OS and APP
2508	I2C Improper Acknowledge on %4	SNECON I2C driver: No module responding to the I2C address.  A module was disconnected or is no longer responding (SNECON hardware rev 2.x)	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
2509	I2C Invalid Message Checksum Received on %4	SNECON I2C driver:  A message was received with an invalid checksum	(SNECON hardware rev 2.x): I2C communication error, refer to "I2C Communications Troubleshooting.doc".  Verify that the application does not use an hardware address that does not exist.
2510	I2C Module Not Found: %4	SNECON I2C driver:  No module of this “module type” and “location id” is listed in the address table	Reset the analyzer.     Verify that the application does not use an hardware address that does not exist.
2511	I2C Invalid Opcode Received from %4	SNECON I2C driver:  The message received corresponds to an unrecognized opcode	Reset the analyzer.  Reload SNE OS and APP.  Replace the SNECON
2512	I2C Error Reading ISR Queue	SNECON I2C driver:  An error was detected reading a communication queue (SNECON hardware rev 2.x)	Reset the analyzer.
2513	I2C Message Too Big on %4	SNECON I2C driver:  The I2C message received is too big and is not valid	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
2515	I2C Address Table Full	SNECON I2C driver: No free addresses on the I2C bus.  There is a limit of 120 addresses per bus, each PIC is taking up one address	Reset the analyzer.
2516	I2C Invalid Bus on %4	SNECON I2C driver:  Invalid I2C bus identification number	Reset the analyzer.
2518	I2C Unknown Address Received on %4	SNECON I2C driver:  SNECON firmware internal error	Reset the analyzer.
2519	I2C Invalid Data Type on %4	SNECON I2C driver:  SNECON firmware internal error	Reset the analyzer.
2520	I2C Invalid Number of I/O Channels on %4	SNECON I2C driver:  SNECON firmware internal error	Reset the analyzer.
2521	I2C Bus Conflict; Lost Arbitration on %4	SNECON I2C driver:  An I2C communication error was detected (SNECON hardware rev 2.x)	Confirm‎ that only 1 SNECON is present on the bus as a rev 2 SNECON cannot share the I2C bus.  Refer to the I2C communication troubleshooting.
2522	I2C Using a Free Message Buffer on %4	SNECON I2C driver:  SNECON firmware internal error	Reset the analyzer.
2523	I2C NS486SXF-C0 Patch Timeout on %4	SNECON I2C driver:  SNECON firmware internal error	Reset the analyzer.  Replace the SNECON
2525	I2C Invalid Driver Control Command on %4	SNECON I2C driver:  SNECON firmware internal error	Reset the analyzer.  Reload the OS and APP. Replace the SNECON
2526	I2C Capability Information Too Big on %4	SNECON I2C driver:  SNECON firmware internal error	Reset the analyzer.
2527	I2C Message Lost in a Controller Reset: %4	SNECON I2C driver: A pending I2C message could not be sent and was lost as a result of a reset of the I2C interface.  The cause of the reset is usually a re-occurring communication error	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
2529	I2C Invalid Capability Version; Incompatible Firmware on %4	SNECON I2C driver: An I2C module has provided an invalid device capability information message.  The associated “Sys_Hardware” table may be invalid	Replace the module.  Reload a newer SNE OS and APP
2530	I2C Internal Error; Invalid Daemon Function on %4	Not implemented…	Not implemented…
2531	I2C Internal Error; Invalid Info on %4	SNECON I2C driver:  SNECON firmware internal error	Reset the analyzer.
2532	I2C Invalid Device ID Version; Incompatible Firmware on %4	SNECON I2C driver: An I2C module has provided an invalid device id information message.  The module type and location id information may be invalid	Replace the module.  Reload a newer SNE OS and APP
2534	I2C Internal Error; Bus Manager Invalid Command on %4	Not implemented…	Not implemented…
2537	I2C Address Table not initialized on %4	SNECON I2C driver:  SNECON firmware internal error	Reset the analyzer.
2538	I2C ISR Lockup	SNECON I2C driver:  The SNECON message receive indicator is stuck  (SNECON rev 3.0 hardware only)	Reset the analyzer.  Replace the SNECON
2539	I2C Invalid Message Status Size on %4	SNECON I2C driver:  SNECON firmware internal error	Reset the analyzer.  Replace the SNECON
2540	I2C Message Too Short on %4	SNECON I2C driver:  An I2C message received by the SNECON in too short to be valid	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
2541	I2C FPGA Queue Full on %4	SNECON I2C driver:  SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer.  Replace the SNECON
2542	I2C FPGA Write Before End on %4	SNECON I2C driver:  SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer.  Replace the SNECON
2543	I2C FPGA Write After End on %4	SNECON I2C driver:  SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer.  Replace the SNECON
2544	I2C FPGA Message Too Short on %4	SNECON I2C driver:  SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer.  Replace the SNECON
2545	I2C FPGA Invalid Checksum on %4	SNECON I2C driver: SNECON on-board communication error.  Is known to happen very infrequently with SNECON I2C FPGA rev 23 or lower (SNECON rev 3.0 hardware only)	Ignore the alarm.  If happening too frequently, replace the SNECON
2546	I2C FPGA Invalid Size on %4	SNECON I2C driver: SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software.  Replace the SNECON
2547	I2C Heartbeat Timeout Expired; Resetting Controller	SNECON I2C driver: A SNECON PIC was not responding and was reset (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software.  Replace the SNECON
2549	I2C Heartbeat Counter Mismatch on %4	SNECON I2C driver: One or more messages were lost on the on-board communication (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software.  Replace the SNECON
2550	I2C Invalid Message Status on %4	SNECON I2C driver: SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software.  Replace the SNECON
2551	I2C Internal Error; Invalid Block Structure ID on %4	SNECON I2C driver: SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software
2552	I2C Internal Error; Invalid Block Offset on %4	SNECON I2C driver: SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software
2553	I2C Internal Error; Invalid Block ID on %4	SNECON I2C driver: SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software
2554	I2C Internal Error; New Block Offset Non-Zero on %4	SNECON I2C driver: SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software
2555	I2C Internal Error; Block Table full	SNECON I2C driver: SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software
2556	I2C Not Enough Memory	SNECON I2C driver: SNECON firmware internal error	Reset the analyzer. Reload the SNECON OS software
2557	I2C Internal Error; Block Too Big on %4	SNECON I2C driver: SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software
2558	I2C Internal Error; Block Not Found on %4	SNECON I2C driver: SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software
2559	I2C Internal Error; Invalid Block Size on %4	SNECON I2C driver: SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software
2560	I2C Driver OS and Application version mismatch	SNECON I2C driver: The version number of the SNECON OS is incompatible with the SNECON APP version	Reload the OS and APP
2562	I2C Internal Error; Bad state on %4	SNECON I2C driver:  SNECON firmware internal error	Reset the analyzer. Reload the SNECON OS software
2563	I2C FPGA bad version	SNECON I2C driver:  The SNECON I2C FPGA is incompatible or broken	Reload the OS with the newest version.  Replace the SNECON
2564	I2C Temperature Block Version Invalid	SNECON I2C driver:  The temperature controller PID parameter data block supplied by the SYSCON is incompatible	Reload the SNECON OS and APP to the corresponding SYSCON version
2565	I2C Opcode not expected in current state on %4	SNECON I2C driver:  Unexpected I2C message opcode received by the SNECON from a module	I2C communication error, refer to "I2C Communications Troubleshooting.doc"
2566	I2C Modules were reset following multiple errors	SNECON I2C driver:  A fatal error or multiple consecutive retries have forced the I2C controller to reset	Usually indicates a severe I2C communication error, refer to "I2C Communications Troubleshooting.doc"
2567	I2C Header Index Mismatch; Message Lost	Not implemented	Not implemented…
2568	I2C Internal Error; Invalid Block Index on %4	SNECON I2C driver:  SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software
2569	I2C FPGA Queue Full on %4	SNECON I2C driver:  The SNECON I2C FPGA queue is full, the PIC is no longer processing I2C message	Reset the analyzer.  Replace the SNECON
2570	I2C FPGA Packet Too Big on %4	SNECON I2C driver:  SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software.  Replace the SNECON
2571	I2C FPGA Recovery Failed on %4	SNECON I2C driver:  SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software.  Replace the SNECON
2572	I2C FPGA Read in progress not set after header on %4	SNECON I2C driver: SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software.  Replace the SNECON
2573	I2C Not enough memory in ISR on %4	SNECON I2C driver:  SNECON firmware internal error (SNECON rev 3.0 hardware only)	Reset the analyzer. Reload the SNECON OS software.  Replace the SNECON
2574	I2C Pic Reset Detected on %4	SNECON I2C driver:  A problem was detected by a SNECON PIC and it went through a reset	If happening frequently, replace the SNECON.  Can also be caused by an I2C communication error.
2575	I2C General AO error	SNECON I2C driver: A channel specific error was detected while an AO command was processed (Example AO out of range) .  A more specific alarm will be reported by the module on the next poll.	Provides the channel information for an alarm reported on the same module.
2576	I2C General DO error	SNECON I2C driver: A channel specific error was detected while a DO command was processed (Example DO locked).  A more specific alarm will be reported by the module on the next poll.	Provides the channel information for an alarm reported on the same module.
2817	12V Error on %4	Temperature controller PIC: The 12 volts supply is not working normally.	Disconnect the RTDs and feedthrough connector.  If the error does not go away then replace the DPM.  If the error goes away, confirm‎ that there is no continuity between any RTD lead and ground
2818	Setpoint Board Missing on %4	Temperature controller PIC: The OTS and temperature limit configuration board (t-rating configurator) is not detected on J10.  The temperature controller is non-functional	Install or replace the TLIM-OTS T-rating configuration board
2819	RTD Failure 1 on %4	Temperature controller PIC: An attempt was made use a temperature channel that has an invalid RTD signal.  The RTD is shorted or open circuit.  The temperature controller cannot function.	Verify the 4-wires temperature sense RTD on channel #1.  The RTD resistance must be between 81 and 269 ohms.  Confirm‎ that none of the lead has any continuity with ground.
2820	Rtd Failure 2 on %4	Temperature controller PIC: Same as alarm 2819 but on channel #2	Same as alarm 2819 but on channel #2
2823	SSR Cable 1 Missing on %4	Not implemented…	Not implemented…
2824	SSR Cable 2 Missing on %4	Not implemented…	Not implemented…
2825	A/D Failure on %4	Temperature controller PIC: An Analog to Digital Converter chip does not work properly.  The flag will be set if the A/D internal calibration cycle is not completed within a pre-determined period of time or the A/D does not report any valid data within a pre-defined timeout period.                  Note:  A firmware problem affecting the version 1.002 of the Temperature controller PIC may cause an A/D failure flag to show-up occasionally following a PIC reset.  This is not a sign of a defective A/D converter.	Cycle power and if it happens consistently then replace the module
2899	Over Temp Shutdown 1 on %4	Temperature controller PIC: The Over-Temp Shutdown function is active on channel #1, the heater cannot be turned-on.	The overtemp shutdown condition indicates that the temperature reached the absolute limit.  The cause can be:                                 · A disconnected TLIM-OTS configuration board.                      · A temperature setpoint too high for the allowed T-rating.                    · A defective OTS or T-limit temperature probe.                         · A defective DPM                       · A defective (shorted) SSR.
2900	Over Temp Shutdown 2 on %4	Temperature controller PIC: The Over-Temp Shutdown function is active on channel #2, the heater cannot be turned-on.	See alarm 2899
2901	Deviation 1 Exceeded on %4	Temperature controller PIC: The measured temperature deviation (TEMP_DEVIATION) has exceeded the corresponding MAX_DEVIATION value.  The PID control was not successful to control the heater with the desired precision on channel #1.	A large deviation is normal on power-up and immediately following a change in the temperature setpoint.          The cause for temperature instability can be:                                                 · Improper controller type “temptype” selected in the “App_tempctl” table in Advance System Manager.  The PID parameters are not optimal.               · Fast variation in the ambient temperature, airflow or line voltage.          · Insufficient air flow.  For an air bath heater with 1/8” spargers, 3 cfm is adequate for up to 100 DegC and then 4 cfm should be used.                            · A temperature setpoint too high for the allowed T-rating.                                            · An Air pressure switch that works intermittently.                                              · A defective DPM.                          · A defective PECM.                                               · A defective Solid State relay.
2902	Deviation 2 Exceeded on %4	Temperature controller PIC: Same as alarm 2901 on channel #2	Same as alarm 2901 on channel #2
2903	Ramp has no origin 1 on %4	Temperature controller PIC: A ramp rate was set without a prior temperature setpoint on channel #1.  A ramp must have an initial temperature defined by the previous setpoint value	Set the power-up default ramp value to 0.
2904	Ramp has no origin 2 on %4	Temperature controller PIC: A ramp rate was set without a prior temperature setpoint on channel #2.  A ramp must have an initial temperature defined by the previous setpoint value	Set the power-up default ramp value to 0.
3117	Pressure 1 Out-Of-Control on %4	EPC (Electronic Pressure Controller) PIC: The measured pressure, on channel #1, has exceeded the absolute maximum allowed pressure and the corresponding channel was shutdown.  The pressure controller is no longer working.	· Confirm‎ that the flow is greater that the minimum specification.                             · Replace the EPC.
3118	Pressure 2 Out-Of-Control on %4	EPC (Electronic Pressure Controller) PIC: Same as 3117 for channel #2	· Confirm‎ that the flow is greater that the minimum specification.                             · Replace the EPC.
3119	A/D 1 Failure on %4	EPC (Electronic Pressure Controller) PIC: The Analog to Digital Converter chip does not work properly.  The flag will be set if the A/D internal calibration cycle is not completed within a pre-determined period of time or the A/D does not report any valid data within a pre-defined timeout period.                                Note:  A firmware problem affecting the version 0.250 of the EPC PIC may cause an A/D failure flag to show-up occasionally following a PIC reset.  This is not a sign of a defective A/D converter.	Cycle power and if it happens consistently then replace the module
3120	A/D 2 Failure on %4	EPC (Electronic Pressure Controller) PIC: The Analog to Digital Converter chip does not work properly.  The flag will be set if the A/D internal calibration cycle is not completed within a pre-determined period of time or the A/D does not report any valid data within a pre-defined timeout period.                                      Note:  A firmware problem affecting the version 0.250 of the EPC PIC may cause an A/D failure flag to show-up occasionally following a PIC reset.  This is not a sign of a defective A/D converter.	Cycle power and if it happens consistently then replace the module
3157	Low Supply Pressure 1 on %4	EPC (Electronic Pressure Controller) PIC: Set when the contact on the optional supply pressure sensor on J5 is closed indicating that the supply pressure is getting low and that the bottle will have to be changed soon.	Replace the corresponding bottle
3158	Low Supply Pressure 2 on %4	EPC (Electronic Pressure Controller) PIC: Set when the contact on the optional supply pressure sensor on J6 is closed indicating that the supply pressure is getting low and that the bottle will have to be changed soon.	Replace the corresponding bottle
3159	Deviation 1 Exceeded on %4	EPC (Electronic Pressure Controller) PIC: The measured pressure deviation has exceeded the corresponding MAX_DEVIATION value.  The PID control was not successful to control the pressure with the desired precision on channel #1.	· MAX_DEVIATION_x that is too small.                                                 · An improper setting of TIME_LIMIT_DEVIATION_UP_x or TIME_LIMIT_DEVIATION_DN_x.                       · Insufficient supply pressure.                                   · Flow too small or too large.                · Defective EPC.
3160	Deviation 2 Exceeded on %4	EPC (Electronic Pressure Controller) PIC: Same as alarm 3159 on channel #2	Same as alarm 3159 on channel #2
3161	Setpoint1 changed following a change in Max Pressure	EPC (Electronic Pressure Controller) PIC: The SETPOINT_1 AO value was modified internally as a result of the SETPOINT_MAX_1 AO value set to a value lower than the SETPOINT_1 value.	Make sure to set the SETPOINT_MAX_1 value first and then set the setpoint
3162	Setpoint2 changed following a change in Max Pressure	EPC (Electronic Pressure Controller) PIC: Same as alarm 3161 on channel #2	Same as alarm 3161 on channel #2
3401	TFTP Protocol Error	Protocol error detected, such as receipt of a non-DATA packet or lack of an expected message acknowledgment	Most likely the gateway settings on the SNE are wrong.  It will be necessary to power up the SNE connected to a serial terminal and change the settings in the startup dialog.
3402	TFTP Timeout	The TFTP client didn't receive any response from the server.	Either the TFTP server is not running on the host computer or the host computer is not connected to the SNE through the network.
3403	TFTP Server out of Sync	The data packets requested by the TFTP client to not match those sent by the TFTP server.	Either the TFTP client or TFTP server is in la-la land.  First try reseting the SNE, if that does not help try restarting the TFTP server on the host computer.
3404	TFTP Server out of Sockets	TFTP server can't create a portal from which to communicate	SNE or host computer is low on resources.
3405	TFTP Max Channels is exceeded	Too many TFTP load requests have been commanded.	Only request one TFTP load at a time.
3406	TFTP Driver not initialized	TFTP driver was not successfully initialized.	Usually a problem of resource.  Ensure that the SNE has 16Mb of memory or isn't otherwise deficient.  Try a reset.
3500	TFTP Client out of memory	Client ran out of memory loading file.	Ensure SNE has 16Mb SIMM.  Try reset.
3501	TFTP Client Checksum Error	File loaded had invalid checksum	Check to ensure loadfile is correct and uncorrupted.
3502	TFTP Client Missing End of File	Attempt to load truncated file	Loadfile may be corrupt.
3503	TFTP Client Invalid OS File	Attempt to load OS with invalid address range.	Loadfile may be Application file or corrupt
3504	TFTP Client Invalid App File	Attempt to load App with invalid address range	Loadfile may be OS file or corrupt
3501	Advance Adapter Initialization Failure	Adapter Detected, but responding improperly	Repair or replace adapter
3502	Invalid Channel for Advance Adapter %4	Reference to invalid channel on Advance Adapter	Fix improper database.
3503	Advance Adapter Backplane Timeout on %4	I/O %4 on backplane board did not respond	Try to reseat or replace board corresponding to hardware ID.
3504	Advance Adapter Backplane Error on %4	I/O %4 on backplane responded improperly	Try to reseat or replace board corresponding to hardware ID.
3505	Resource for %4 not available on Advance Adapter	Memory or operating system object not available for hardware access	Ensure SNE has 16Mb SIMM.  Try reset.
3516	No Advance Adapter detected	Unused alarm
3517	Advance Adapter Driver Out of Memory	Driver initialization failure due to lack of memory	Ensure SNE has 16Mb SIMM.  Try reset.
3518	Invalid Advance Adapter Driver Command	application requested invalid command from Adapter Driver	Most likely a mismatch between the SNE OS and application.  Reload SNE software.
3718	FPGA Error Full on %4	SNECON PICs: The FPGA queue to the NS486 was full and a packet could not be sent. A best attempt is made to continue but one or more packets were lost	Reset the SNECON -or- Replace the SNECON.
3719	FPGA error reset_W on %4	SNECON PICs: A FPGA reset was detected during a packet write from the PIC.  The packet and any packet still in the FPGA queues were lost.	Reset the SNECON -or- Replace the SNECON.
3720	FPGA error reset_R on %4	SNECON PICs: A FPGA reset was detected during a packet read by the PIC. The packet and any packet still in the FPGA queues were lost.	Reset the SNECON -or- Replace the SNECON.
3721	FPGA error_W on %4	SNECON PICs: An error was detected while writing the packet header or data to the FPGA.  A best attempt is made to continue but one or more packets may be lost.	Reset the SNECON -or- Replace the SNECON.
3722	FPGA error_R on %4	SNECON PICs: An error was detected when reading the packet header or data from the FPGA.  A best attempt is made to continue but one or more packets may be lost.	Reset the SNECON -or- Replace the SNECON.
3725	Error SCL on %4	SNECON PICs: An abnormal situation was detected on the I2C “Serial Clock” line.	This is an indication that the WDB is broken, a cable harness is broken or one board connected to the I2C bus is malfunctioning, pulling the I2C clock signal to a logical low.  Refer to the I2C communication troubleshooting guide
3726	Error SDA on %4	SNECON PICs: An abnormal situation was detected on the I2C “Serial Data” line.	This is an indication that the WDB is broken, a cable harness is broken or one board connected to the I2C bus is malfunctioning, pulling the I2C data signal to a logical low Refer to the I2C communication troubleshooting guide
3727	I2C won't align on %4	SNECON PICs:  I2C communication error	Refer to the I2C communication troubleshooting guide
3728	I2C msg not allowed on %4	SNECON PICs: A packet containing an I2C message was received by the PIC (from the NS486 through the FPGA) at a time when it is not allowed but after a valid configuration message was received. The message was discarded.	Reset the SNECON -or- Reload the OS  -or- Replace the SNECON.
3757	NACK address on %4	SNECON PICs: An I2C message transaction failed after the required number of retries.  A cause of this failure was a non-acknowledged destination address byte (first byte in the message).  This may happen if a module was disconnected from the bus after its address has been re-assigned	Reset the analyzer
3758	NACK Byte on %4	SNECON PICs: An I2C message transaction failed after the required number of retries.  A cause of this failure was a non-acknowledged byte that is not the first byte in the message (any byte other than the destination address was not acknowledged).  This may happen if a module is seriously confused or the I2C signal integrity is a problem (noise, etc…)	I2C communication error, refer to "I2C Communications Troubleshooting.doc".
3759	NACK Message on %4	SNECON PICs: An I2C message transaction failed after the required number of retries.  A cause of this failure was a NACK message with a non-zero flag.  This may happen if the firmware of the peripheral module is not responding properly.	Reset the analyzer  -or- Replace the module being addressed.
3760	Invalid Checksum on %4	SNECON PICs: An I2C message transaction failed after the required number of retries.  A cause of this failure was an invalid checksum in the reply message.  This may happen if the firmware of the peripheral module is not working properly or the electrical properties of the I2C signals are marginal.	I2C communication error, refer to "I2C Communications Troubleshooting.doc".
3761	Invalid Opcode on %4	SNECON PICs: An invalid private opcode was received from the NS486.  The message was ignored.  This may happen if the PIC firmware is out-of-date relative to the SNE software	Reload the OS and APP software -or- Replace the SNECON.
3762	Invalid Message on %4	SNECON PICs: An I2C message transaction failed after the required number of retries and a cause of this failure was a reply message that had a valid checksum, valid opcode but was invalid in any other way.  This may happen if the firmware of the peripheral module is not working properly of the SNECON software is too old.	Reload the OS and APP software -or- Replace the module being addressed –or- Replace the SNECON.
3763	Arbitration Loss on %4	SNECON PICs: An I2C message transaction failed after the required number of retries and a cause of this failure was that the PIC could not successfully arbitrate its way to the bus.  Other bus master capable devices are using all the I2C bus bandwidth	I2C communication error, refer to "I2C Communications Troubleshooting.doc".
3764	Timeout SCL on %4	SNECON PICs: An I2C message transaction failed because the I2C clock was stretched beyond the allowed timeout period specified in the configuration.  A module may be malfunctioning.	I2C communication error, refer to "I2C Communications Troubleshooting.doc".
3765	Timeout SDA on %4	SNECON PICs: An I2C message transaction failed because the I2C data line was held beyond the allowed timeout period specified in the configuration.  A module may be malfunctioning	I2C communication error, refer to "I2C Communications Troubleshooting.doc".
3766	Bus Not Sync on %4	SNECON PICs: The master mode operation generated a start condition that was not detected by the FPGA.	Reset the SNECON -or- Replace the SNECON.
3767	Timeout Buffer on %4	SNECON PICs: A master mode message has not been processed within a timeout period.  This is a catch-all alarm, the PIC will discard the message and attempt to recover	I2C communication error, refer to "I2C Communications Troubleshooting.doc".
3768	Invalid Handle on %4	SNECON PICs: The header handle received was not sequential, one or more I2C message was lost.	Reset the SNECON -or- Replace the SNECON.
3797	Invalid Checksum Slave on %4	SNECON PICs: An unsolicited I2C message was received with a bad checksum.  The message was discarded and it is expected that the master will retry the message.  This is a communication error that can be ignored if not too frequent	Reset the SNECON -or- Replace the SNECON.
3798	Invalid Message Slave on %4	SNECON PICs: An unsolicited I2C message was received with an invalid message size, invalid opcode or invalid data.  The message was discarded. There may be a firmware version conflict	Reload the OS and APP software to all SNECONs
3799	Invalid Status Summary on %4	SNECON PICs: A packet was received by the PIC from the NS486 and the packet had an undefined bit set in the Status_summary field of the packet.  The packet was processed normally.	Reload the OS and APP software -or- Replace the SNECON.
3800	Module Not Ready on %4	SNECON PICs: An I2C message transaction failed after the required number of retries and the cause of the failure was a series of consecutive message NACK all with a 0 flag.  This may happen if the firmware of the peripheral module is not responding properly.	Reload the OS and APP software -or- Replace the module being addressed –or- Replace the SNECON.
3801	Invalid Status Data on %4	SNECON PICs: The content of the status buffer “Status_data” was invalid and not recognized by the PIC.  This may happen if the PIC firmware is out of date relative to the NS486 software	Reload the OS and APP software -or- Replace the SNECON.
3802	Invalid Status Type on %4	SNECON PICs: The value of the status_type was invalid and not recognized by the PIC.  This may happen if the PIC firmware is out of date relative to the NS486 software	Reload the OS and APP software -or- Replace the SNECON.
3803	Invalid Msg Size on %4	SNECON PICs: A packet was received with an invalid I2C message size or no I2C message at all.  The packet was discarded	Reload the OS and APP software to all SNECONs
3804	Arbitration Loss Slave on %4	SNECON PICs: The PIC lost a slave read arbitration.  It indicates that at least another module responded to the same message request	No action to be taken.     If happening too frequently, reset the analyzer.
4001	TFTP cannot load with active method %3	Method currentlly running when software load was commanded	put method on hold and wait for it to complete before loading SNE software.
4022	I/O Channel not found on %4	Hardware resource requested not present	reload and or repair SysCon database
4024	Slope Check failure on Channel %4	Slope check commanded with invalid parameters	Check method for slope check events and review data.
4025	Detector channel underflow occurred on %4	A/D converter for detector reading lowest possible value	Check A/D inputs, potentially replace referenced DPM
4026	Detector channel open occurred on %4	Open connection detected on A/D detector input	Most detectors can't detect this, probably represents some sort of DPM problem.
4027	Detector channel overflow occurred on %4	A/D converter for detector reading maximum value possible	Check A/D inputs, potentially replace referenced DPM
4028	Detector channel unknown error occurred on %4	undeterminable error occurred on detector channel circuit	reset, if repeatable replace DPM.
4029	Zero Correction failure on lower channel of %4"	a) If the DPM is a rev 1 TCD or a rev 2 FID: Following the balance correction (done by hardware of the DPM), the detector voltage was still not between +/- 2 Volts (It should be at -1 Volts following the balance correction and the zero correction brings it to 0 volts).   In this case, the zero correction failure should be associated with a balance failure  b) If the DPM is a rev 2 TCD: The zero correction value exceeded the max allowed value for that particular board.  This is a balance failure situation	Eliminate the cause of the balance failure: a) On TCD detector, replace the detector bead or filament b) On FID detector, clean or replace the FID
4030	Zero Correction failure on lower channel of %4"	Same as 4029	Same as 4029
4525	AD Failure on %4	Advance Adapter Temperature controller PIC: The Advance adapter temperature A/D converter is not generating data point within the prescribed time interval.	Reset the analyzer.  Replace the advance adapter
4526	Overtemp Shutdown supply failure	Advance Adapter Temperature controller PIC: The power supply used for overtemp shutdown is not working properly	Replace the advance adapter
4557	Setpoint changed internally	Advance Adapter Temperature controller PIC: The SETPOINT AO value was modified internally as a result of the SETPOINT_MAX AO value set to a value lower than the SETPOINT value.	Make sure to set the SETPOINT_MAX value first and then set the setpoint value
4599	Over Temp Shutdown	Advance Adapter Temperature controller PIC: The Over-Temp Shutdown function is active, the heater cannot be turned-on.	The overtemp shutdown condition indicates that the temperature reached the absolute limit.  The cause can be:     · A temperature setpoint too high for the allowed T-rating.                               · A defective temperature probe.                              · A defective Advance adapter.                      · A defective (shorted) SSR.
4601	Temperature Deviation Exceeded	Advance Adapter Temperature controller PIC: The measured temperature deviation (TEMP_DEVIATION) has exceeded the corresponding MAX_DEVIATION value.  The PID control was not successful to control the heater with the desired precision.	A large deviation is normal on power-up and immediately following a change in the temperature setpoint.     The cause for temperature instability can be:                             · Fast variation in the ambient temperature, airflow or line voltage.                                     · Insufficient air flow.                        · A temperature setpoint too high for the allowed T-rating.                                · A defective DPM.                            · A defective Solid State relay.