The error 10 is common with restarts so I wouldn’t worry too much about that.
Is any additional data logged on the gx, anything that indicates a grid failure on one phase?
Did you review the information and recommendations here for error 17:
The error is a slave device reporting it can’t see it’s master, this can be comms related or a fault of some kind.
Thank you for your support. Yes, I have read the page about Ve.Bus errors. Error #10 is rather insignificant. Error #17 is causing me concern:
In some cases this error can be seen temporarily while using Remote VEConfigure to write a new configuration.
Solution: ignore the error; the system will recover by itself.
The most likely cause is a cable-related communication issue on the VE.Bus network:
Solution: First check the network cable sockets. If that doesn’t solve it, replace all network cables, including the cable to the GX Device. Make sure to also inspect the female RJ-45 sockets, instead of only the cabling: sometimes badly mounted RJ45 cable connectors prevent the spring-contacts in the female RJ45 connectors on the Multis to properly make contact. Make sure to machine-made cabling. Do not use self-crimped cables.
DC fuse blown. In this case, all units may appear to be functioning properly and work well as long as mains power is available. However, when AC power is no longer available at the input (mains failure or generator stopped), the non-powered units are disconnected from the system.
Solution: Check the fuse in all units; replace the broken one.
I have already checked points 1 and 2.
Regarding point 3: Where is the DC fuse in a Multiplus 48/5000/70-100?
Worst case: Perhaps the communication module is defective?