F
Hello
We have a problem about I/O in C core. IO status don't reach A7, it stopped in A5 level. This failure didn't affect the turbine running but other problems begin to appear like a command execution and visualisation (ie the inputs(feedback...) allocated in CD didn't validate in R, S, T, D and the HMI's connected through D couldn't get the real status of this signals,the opposite case through C.
We tried to resolve IO status problem in the first place, so we log in DCC monitor with the LCC keypad, IO C cards status function was checked, only these random characters were diplayed <16> **** -- 1F when i scrolling through this function. What mean that ? and can the IO cards status affect the communication between C and R, S, T, D , how a can use the hexadecimal bit encoding in denet diagnostic data with diagnostic counters tool because this bits changed frequently in tow states.
Thank you for your answers.
We have a problem about I/O in C core. IO status don't reach A7, it stopped in A5 level. This failure didn't affect the turbine running but other problems begin to appear like a command execution and visualisation (ie the inputs(feedback...) allocated in CD didn't validate in R, S, T, D and the HMI's connected through D couldn't get the real status of this signals,the opposite case through C.
We tried to resolve IO status problem in the first place, so we log in DCC monitor with the LCC keypad, IO C cards status function was checked, only these random characters were diplayed <16> **** -- 1F when i scrolling through this function. What mean that ? and can the IO cards status affect the communication between C and R, S, T, D , how a can use the hexadecimal bit encoding in denet diagnostic data with diagnostic counters tool because this bits changed frequently in tow states.
Thank you for your answers.