You can get out all electrical and if the easYgen is connected to the engine electronic controller you can usually get oil pressure, water temperature etc. You can also get out all sorts of alarms. I always prefer to use the RP3000 annunciator as well.
With respect to the Schneider-Modbus issue I often use their MCCB bodies and a 5E protection unit so I can extract electrical data. The protection unit even stores maximum and minimum values for all electrical data - great when you are hooked up to gas generators sometimes and can prove that they have run the voltage and frequency too high and locked up your control gear, caused burn outs or whatever. Then there is a small communications unit that plugs into the MCCB for the extraction of data. This is then connected to an interface unit that provides Modbus RTU to my PLC. The interface unit 'reads' the Modbus request from the PLC and auto sets to how you set up your protocol - 19.2, 8, 2, none for example - no programming - great little device. This device will not operate 8, 1, none at all and sits there flashing. Same goes for the interface to the ACBs - same interface.
I was recently working on a job where Citect (now Schneider) were doing the SCADA system. Our interface was serial and they put in another interface module to go from Modbus RTU serial to Modbus TCP. When the guy was setting up the interface with the Schneider software the software did not give the option of changing the number of stop bits at all - only speed and parity. He could not 'read' us at all. I changed my setup in the serial card to 8, 2, none and he read us straight away. Funny thing was he did not understand what I was talking about - fortunately I was aware of the situation from the MCCBs and cottoned on to his problem straight away or we would still be there. Up and running in 2 minutes.
With respect to the Schneider-Modbus issue I often use their MCCB bodies and a 5E protection unit so I can extract electrical data. The protection unit even stores maximum and minimum values for all electrical data - great when you are hooked up to gas generators sometimes and can prove that they have run the voltage and frequency too high and locked up your control gear, caused burn outs or whatever. Then there is a small communications unit that plugs into the MCCB for the extraction of data. This is then connected to an interface unit that provides Modbus RTU to my PLC. The interface unit 'reads' the Modbus request from the PLC and auto sets to how you set up your protocol - 19.2, 8, 2, none for example - no programming - great little device. This device will not operate 8, 1, none at all and sits there flashing. Same goes for the interface to the ACBs - same interface.
I was recently working on a job where Citect (now Schneider) were doing the SCADA system. Our interface was serial and they put in another interface module to go from Modbus RTU serial to Modbus TCP. When the guy was setting up the interface with the Schneider software the software did not give the option of changing the number of stop bits at all - only speed and parity. He could not 'read' us at all. I changed my setup in the serial card to 8, 2, none and he read us straight away. Funny thing was he did not understand what I was talking about - fortunately I was aware of the situation from the MCCBs and cottoned on to his problem straight away or we would still be there. Up and running in 2 minutes.
