NSX 630A MCCB with Micrologic 2.3 trip testing

[BrianW]

Hi,

What is the preferred method of performing the Automatic Trip Curve tests (secondary injection test) on NSX 630A MCCBs with Micrologic 2.3 trip units, as the Service Interface kit does not seem to support connectivity with the trip? 

I seem to remember in the very recent past that I was able to carry out the test prior to a firmware upgrade on the SIK.

Thanks for any assistance,

Brian Whelan

[Gopi.S]

Hi Brian,

The preferred method for  performing the Automatic Trip Curve tests (secondary injection test) on NSX 630A MCCBs with Micrologic 2.3 trip units,  is via Service interface kit.
User experience on SIK Connectivity issue may be due to below reason

1. LED's on Service interface may not blink due to Communication loss from Breaker cable to Service interface.
2. LED's on Service interface may not blink  due to Communication loss from USB cable to Computer through SIK(Service interface kit).
3. Front plug pins damaged  which provides connection  from Breaker to SIK, Due to Which Breakers will not get connected.
4. Kindly check USB ports of the Computer is not blocked due to Security Concern.

[BrianW]

Hi Gopi,

Thank you for the reply. Unfortunately, although the SIK works perfectly well with any Micrologic 5 and higher trip units, I simply cannot connect to the older Micrologic 2.3 type trips, which we are using on many NSX 630A MCCBs at the moment. 

The connection seems to be fine to the MCCBs when trying to discover them with EPC, the LED flashes on the trip as per normal, but running the Discover Serial devices page discovers the SIK itself no problem, eliminating an issue with the USB connectivity, but when I continue to try to Find Devices, I continually get No Device found. As a sanity check, I try connection with MCCBs with Micrologic 5 trip units and the connection is perfect, the Find Device function works immediately. 

Resorting back to the older USB Maintenance Module TRV00911 and the antiquated LTU software can connect to the MCCBs, but this is far from ideal as operation of this is sporadic in nature and the process quite lengthy to continue, especially with volumes of secondary injection testing required. 

I seem to remember that the SIK did actually work previously with the 2.3 trips, but not since upgrading the SIK firmware to version 001.001.040. 

I would appreciate any other suggestions and thank you in anticipation,

Regards,

Brian 

[Gopi.S]

Hi Brain,

Kindly share the application log file, i can trouble shoot from my end.

[BrianW · Accepted solution]

Hi Gopi,

Please see attached.

Regards,

Brian

[BrianW]

Hi Gopi,

I was wondering if there is any update to my query after submitting the logs as requested. We are now seeing quite an issue when trying to use the Service Interface Kit on site to carry out maintenance on MCCBs and our engineers are having to resort to using the older Maintenance Module kit which, albeit it dreadfully slow and tedious to use, does work, but its adding so much time to the procedures. 

Basically the older Micrologic trip units, such as 2.3, etc., are not working at all with the SIK, but Micrologic 5 and 6 trips work perfectly. 

We do need a solution as soon as possible. 

Regards,

Brian

[Manon_Chaboud]

Hello @Gopi.S , can you help @BrianW, please? Thank you in advance!

[Gopi.S · Accepted solution]

Hi Brian,

I checked in logs EPC is able to identify the device and you have performed ATCT test for Micrologic  5.3E MCCB. 4P 400A Breakers & Micrologic  5.2E MCCB. 4P 100A Breakers 

But for Micrologic 2.3 no information of discovery is identified in logs. This may be some connectivity issues to device.
Brain can confirm when the SIK cable is connected with the Trip unit of Micrologic 2.3 breaker LED is getting  on.

[BrianW]

Hi Gopi,

Thanks for this. Yes, I can confirm that the cable is properly connected to the 2.3 Trip unit as the very short video shows. Also, I have attached some screenshots showing while I can connect to the SIK as a serial connection, once I try to connect to the trip unit, the available COM5 ADD DEVICES is greyed out, not allowing me to connect, no matter what I try, reloading the EPC, powering the SIK off and on, reconnecting everything, even clearing the cache. I cannot progress any further than trying to ADD DEVICE as shown. Also attaching a log file.

Regards,

Brian

[S-W]

@Gopi.S and @EPC_Leader: Any further advice based on the images @BrianW shared?

[Gopi.S]

Hi Brian,

Based on screen & video along with log shared.

I doubt on the cable pins which might be damged, due to which device is not getting listed in EPC.

[BrianW]

Thank you Gopi,

I had been thinking the same, but as a sanity check, just in case I was having hardware issues, such as the cable pins you mention, I would check that all was well by testing a MCCB with a Micrologic 5.2 trip installed which never has an issue being detected by the EPC. This is a standard test backup that we constantly perform to ensure that we do not have issues.

So, based on this, I can say that there is no issue with the full SIK, cable performs perfectly well with Micrologic 5.2 and higher, but not with Micrologic 2.3.

[MuckerMcD]

we are having the same issues, it works on all trips except the 2.2 and 2.3 for some reason?

Any answer yet?

[MuckerMcD]

Hi Brian did you ever get a solution for this as I am having the same issues with 2.2 and 2.3 trips?

[MuckerMcD]

Why is this marked as a solution? am I missing something?

[BrianW]

Hi @MuckerMcD 

No, I have not yet received a solution from SE regarding this issue. It has left us resorting to the older method of having to use the Maintenance Module kit which is extremely tiresome. There is no solution offered as far as I am concerned, despite the literature stating that the SIK can indeed test the trips mentioned. I still feel that the root cause could very well be firmware related because I distinctly remember being able to test 2.3 trips earlier this year with the SIK but after a firmware upgrade on the SIK, that functionality for the "older" trips was lost.

So I am still no further on with this issue 😞