Repository navigation
Ragtech Driver: can't communicate with Easy Way 1500 GT #3755
Description
On Fedora 44, using standard RPM package nut 2.8.5 from OS repo and source compiled Ragtech 0.10 driver from latest master.
Device Information
- Manufacturer: Ragtech Sistemas de Energia
- Model: Easy Way 1500VA GT. not Pro.
- Firmware: bcdDevice 1.00
- USB VID/PID: 04d8:000a
- Manufacturer: Ragtech Sistemas de Energia
- Product: USB Serial Port
- Port: /dev/ttyACM0
I took a glance at #3500 , so I guess maybe this model uses a different mapping of the bytes, but I'm not a low level programmer, it's beyond my current knowledge.
I can take a few more info from Fedora 44 and Windows 11 communicating with this model, if it helps.
Activity
pedroaugustosmribeiro commentedon Oct 20, 2026
Example of hex monitoring at 4800 baud 8N1 using VS Code serial monitor in raw hex mode on Windows 11, with Supervise services off:
66 e6 66 e6 f8 e6 9e 80 fe 80 e6 f8 20 26 fe 18
f8
ce f8 e6 00 18 f8 1e 00 f8 1e fe 00 e0 00 00 60
1e
78 fe 3e fe 1e 06 00 1e fe fe c0 06 e0 20 f8 86
c0
38 fe 66 e6 66 e6 f8 e6 9e c0 fe c0 e6 f8 20 26
fe 18
f8
9e f8 e6 00 18 f8 1e 00 f8 1e 00 e0 00 00 60 1e
7e
fe 3e fe 1e f8 fe 00 20 3e 80 06 e0 66 f8 86 80
78
26 e6 26 e6 f8 e6 9e c0 fe c0 e6 f8 20 26 fe 18
f8 ce
f8
e6 00 18 f8 1e 00 f8 1e fe 00 e0 00 00 60 1e 78
3e
9e 1e 38 00 1e fe fe 06 e0 20 f8 86 c0 9e fe 66
e6 26 e6 f8 e6 9e c0 fe c0 e6 f8 20 26 3e e0 f8
ce f8
e6
00 18 f8 00 00 f8 06 fe e0 00 00 60 1e 78 fe 7e
fe
1e 18 00 60 7e 80 06 e0 26 f8 86 c0 3e fe
jimklimov commentedon Oct 21, 2026
CC @juslex : would you please have time to look at this?
juslex commentedon Oct 21, 2026
Hi @pedroaugustosmribeiro, thanks for the report and the dump.
A first reading: the
ragtechdriver currently speaks only the request/response protocol of the Easy Pro line ("family 10"): the UPS stays silent until the driver sends a 6-byte0xAA ...read command. Your dump looks different in two ways:66 e6 66 e6 f8 e6 9e ...comes back on every cycle).f8,fe,e6,1e,80,c0,e0). On the Easy Pro the PIC runs the CDC firmware itself and the baud rate is cosmetic, but on your Easy Way the PIC may be a USB-to-UART bridge in front of another MCU, in which case the line speed does matter.So the Easy Way is most likely a different protocol family, not just a missing model entry. To tell for sure, could you collect the following? Please do not set
allow_shutdownand do not send any command to the UPS while testing; passive listening is enough for now.On Linux
lsusb -v -d 04d8:000aups.confsection you used.On Windows (this is the most valuable part)
devices.xml(or similar XML) from its installation folder. For the Easy Pro, that file describes the register map and scaling, and it may tell us which family the Easy Way belongs to..pcapng. Please also note the readings shown on screen at the time of the capture (input/output voltage, load %, battery %), so we can match bytes to values. This is exactly what made the Easy Pro support possible in Ragtech driver: Easy Pro 3200VA GT CBU-TI — no reply to initial status poll #3500.With that we can see whether the Easy Way can be added to
ragtechas a second family or needs its own code path.pedroaugustosmribeiro commentedon Oct 23, 2026
Output of
lsubs -v -d 04d8:000a:Bus 001 Device 005: ID 04d8:000a Microchip Technology, Inc. CDC RS-232 Emulation Demo Negotiated speed: Full Speed (12Mbps) Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 2 Communications bDeviceSubClass 0 [unknown] bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x04d8 Microchip Technology, Inc. idProduct 0x000a CDC RS-232 Emulation Demo bcdDevice 1.00 iManufacturer 1 Ragtech Sistemas de Energia iProduct 2 USB Serial Port iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0043 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 2 Communications bInterfaceSubClass 2 Abstract (modem) bInterfaceProtocol 1 AT-commands (v.25ter) iInterface 0 CDC Header: bcdCDC 1.10 CDC ACM: bmCapabilities 0x02 line coding and serial state CDC Union: bMasterInterface 0 bSlaveInterface 1 CDC Call Management: bmCapabilities 0x00 bDataInterface 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 2 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 10 CDC Data bInterfaceSubClass 0 [unknown] bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Device Status: 0x0001 Self Poweredpedroaugustosmribeiro commentedon Oct 23, 2026
In attachment, files for baud rates 9600 and 19200, 2400 came empty.
Used stty for configuring baud rates
stty -F /dev/ttyACM0 RATE raw -echoCaptured with cat and translated with xxd, as sugested:
timeout 15 cat /dev/ttyACM0 | xxd > easyway-RATE.txtMy ups.conf on Fedora 44 KDE (kernel 7.2.11-200.fc44.x86_64) is:
[nobreak] driver = ragtech port = /dev/ttyACM0 desc = "Ragtech NEP 1200"Output of
ragtech -DDD -a nobreak 2>&1 | head -200:easyway-9600.txt
easyway-19200.txt
pedroaugustosmribeiro commentedon Oct 23, 2026
In attachment,
devices.xmlfrom Windows 11 Supervise 8.9.7 installation folder, downloaded from https://ragtech.com.br/downloads/softwares-supervise-beta/ and captures with Wireshark + usbpcap and Supervise logdevices.xml
supervise_log_easywat_1500gt.csv
easyway1500gt.pcapng
juslex commentedon Oct 23, 2026
Thanks a lot, @pedroaugustosmribeiro, this was exactly what was needed. Here is what the data shows.
Your unit is a different protocol family. In the Supervise
devices.xml, the Easy Way line is family 14 ("NEW/QUADRI"), with 21 models (EASY WAY-TI/M1/M2, 500 to 1600 VA). Theragtechdriver currently implements only family 10 (Easy Pro). Your unit reports model byte0x0F=EASY WAY-TI 1400, which is probably sold as the 1500 VA model.It pushes data on its own, at 2400 baud 8N1. In your USB capture, Supervise never sends a single byte to the UPS. The UPS sends a 32-byte frame by itself, about every 1.28 s:
CSis the 8-bit sum of the 31 preceding bytes, and it checks out on all 24 frames in the capture. The 27 data bytes match the family 14 register map in the XML. Decoding them with the XML formulas gives the same values as your Supervise CSV at the same timestamps: 122.3 V in, 106.0 V out, 59.6 Hz, 12 % load, 13.6 V battery, temperature 55. Your first dump at 4800 baud was this same frame read at twice the line speed; simulating that reproduces your bytes exactly. So on this model the line speed matters, unlike on the Easy Pro.This means the Easy Way can most likely be supported inside
ragtechas a second, read-only family. The XML defines no shutdown action for family 14 and the capture shows no command being sent, so shutdown support would stay off.Two more tests would close the remaining gaps. As before, please don't send anything to the UPS; listening is enough.
1. Listening at 2400 baud, configuring and reading the port in one go
Your 2400 capture came back empty, probably because
sttyandcateach opened the port separately, so the setting may not have stuck. This keeps the port open across both steps (stop any other program using the port first):If it works, we should see lines starting with
55 55 ae.2. A short power cut, to see the "on battery" flags
None of the on-battery, low-battery or fault bits changed in the capture, because the UPS was on mains the whole time. Could you record a short outage?
timeout 120, or USBPcap + Supervise logging on Windows as before.If your UPS beeps or shows anything during that time, a note on that helps too.
pedroaugustosmribeiro commentedon Oct 23, 2026
Here we go, when it was unplugged it beeped within several seconds interval.
Unplugged 15:26:10 (UTC -3)
Re-plugged 15:27:03
supervise_log_easy_way_1500_gt_online_offline_online_test.csv
easyway1500gt_online_offline_online_test.pcapng