Easy UPS 3S RS-485 port issues

[jaimegut]

Hello community !

Need some support in getting an Easy UPS 3S talking via the Modbus RS-485 port.  Here is the FW version

Rectifier: V55.008.002

Inverter: V55.008.002

I've tried both with a Panel Server PAS600 and PAS800 with similar results when trying to use ModScan to read register values.

ModBus Set values:
Address: 001
Com Mode: ASCII (have tried RTU as well with exact same results)

Baud Rate: 9600

Com set: Normal

There's a tutorial video on YouTube that shows exactly how some colleagues in Schneider Electric Spain did this and I've replicated the steps with no luck.

https://www.youtube.com/watch?v=XdSHnuA9-i0

In the video, the narrator even shows the exact function code they are reading and the registers, no success when I try the same.

At some point I even tried flipping the + and - wires on the back of the UPS to try and rule out that as a possible issue.

Looking for some additional ideas, maybe a FW issue or something else.

Any ideas are welcome.

I've read similar previous posts below:

https://community.se.com/t5/EcoStruxure-Building-Operation/Modbus-integration-of-a-3S-UPS-on-EBO/m-p...

[jaimegut]

I should have mentioned that I already had the ModBus register map and tried different register reads. 

Any other suggestions?

[tjlaw]

HI, 

Just wondering if you tried connect directly via USB to RS485 to the UPS and scanned using ModScan? Or maybe you can share the error you have while using ModScan through Panel Server? 

BR, 

TJ

[jaimegut]

I completely missed that there was activity on this thread, my bad.

Actually I have tried USB directly to the RS-485 port as well and scanned using ModScan, nothing seems to be talking out of the RS-485 terminals.

Using the PanelServer is the same (either via the embedded webpage of the panel server or using ModScan going through the panel server), there's nothing but "no comms" status being returned.

I've been careful to follow all the settings listed in the ModBus manual (stop bits, parity, default baud rate, etc.).  I even went as far as flipping the + / -  on the back of the Easy UPS to try and see if that would present any different results (both when using the panel server or communicating directly).  Nothing shows any signs of that port actually doing anything unfortunately.

The registers that I'm trying to read from are a few easy points to verify that communication is even possible.

For example,

Input Voltage on each phase, address 10012, 10013, 10014 using read function 0x03

Input Frequency on each phase, address 10018, 10019, 10020 using read function 0x03

I'm pretty sure that the unit I have is not communicating via the RS-485 port.

[Dominique38]

Hi,

Be sure that menu "Communication Set " is set to Normal.

Take care about modbus address sent to the UPS, depends of tool used

With Modscan, you must add one to register address

Exemple, for address 2710 hexa format requested, you have to set either 10001 decimal format or 2711 haxa format

After that, Easy 3S is working fine with modbus requests

[jaimegut]

Thank you for the response @Dominique38 ,,, I did verify this already see attached document.

And yes, I have considered the offset based on the Modbus protocol to make sure that I wasn't polling an incorrect register.

[Dominique38]

See my Modscan request:

is there an answer form the Easy ??

[jaimegut]

@Dominique38 

Let me ask something, so I can replicate exactly what you are doing.  

1. Are you using panel server in between the Easy UPS and Modscan ?  ( That's the setup I have and have also tried going direct via a USB to RS-485 converter)   I am asking so I can replicate the method you are doing.

2. In the Easy UPS, under "ModBus Set", what setting are you using (RTU / ASCII) ?  

[Dominique38]

I use a small USB/RS485 converter 2 wires form Aliexpress, like this one:

https://fr.aliexpress.com/item/1005003032516569.html

Then i use RTU mode and 9600bd (works bettter than 19200), 8 bits/no parity/no flow control/one stop

[Shaun]

Hi @Dominique38 

That looks reasonable to me -the next bytes look like a modbus exception so it looks like communication is good (eg, both ends are speaking to each other, they just don't like the answer)

Could you try requesting less than 125 registers?  The modbus map is non-contiguous (there's "reserved blocks" eg at 10056-70).  How that's handled varies between devices - some only complain if you start the request in empty space, some won't allow you to address empty space at all.

I haven't been able to test this myself yet, but this is the only difference I can see between your examples and the spanish video, so it may be worth trying.

Regards,

  Shaun

[Dominique38]

Hi Shaun,

i did not see the video

Here is the answer of the 125 register: the Easy is able to reply the 125 registers contiguous even if some of them are reserved

[tjlaw]

Hi, 

Do you mind sharing the UPS firmware version you communicating with? Compared with the firmware version encountered by @jaimegut 

BR, 

TJ

[jaimegut]

Just replicated everything you've suggested,

 

MODBUS Message TIME-OUT is the response being sent back to ModScan (Pictures shows both 125 registers and 10 registers attempted to be read)

I'm striking out with this particular unit left and right

[Shaun]

@Dominique38 , sorry, I got you and the customer confused.

That does seem to rule out that idea though, thanks for that.

[Dominique38]

I can not check UPS firmware now, i'll do it next Monday.

Check your USB/RS485 converter...??

[jaimegut]

I'm using:

https://www.gearmo.com/shop/usb-to-rs485-rs422-converter-with-ftdi-chip/

Hasn't been a problem on other devices 😀

[Dominique38]

Hi,

Here is UPS firmware version:

[jaimegut]

I'm sourcing another USB to RS485 converter, will have it in a day or two. 

I'll provide an update to see if that changes anything, however I doubt this is the problem since the results have been the same using an EcoStruxure Panel (PAS600) server to try reach its registers through TCP-IP and the panel server as well was not able to establish communications with the UPS unit.

[jaimegut]

@Dominique38 

Sorry, it took me a week to source the component to be similar to the one you are using.

Just tried it out, no difference in the results.  

Changed Baud Rate, flipped the +/- wires, changed from RTU to ASCII (both on the UPS and on ModScan), did several things to make sure it wasn't a bad item on the physical wiring or a setting oversight.

I'm back to thinking that this particular unit I have is not able to communicate over the RS-485 port in the back.

[afecomt]

updating firmware sometimes solve the problem

tenemos muchos problemas con este ups. 

schenider support requested us logs with Tuner software. lets see