It's just hard due to the way serial ports are handled. Serial needs to be serviced relatively fast at higher baud rates, and may or may not get offended by buffering delays in both directions. Ethernet is easily fast enough to carry the traffic, but scan dependent latency can completely wreck protocols. Rather than put out solutions that are spotty and work or fail intermittently, we choose not to go there.
I'm generally a fan of sticking a small controller like a BRX out on the drive(s) and talk to it via Ethernet. While localizing the drive comms, that also allows you to put some additional logic at the drive, which can be useful in the event of a network failure.
Currently you can have 2 RS485 ports (which can talk to multiple drives each), but we are also developing a SERIO for BRX.