I feel like the absence of an assistant, should not create the scenario you are facing.
if you have access to the currently running configuration, you should be able to read from that cfg to find out what the default communication setting is and perhaps temporarily configure your device to communicate like that.
Again, without having read the thread…
Did you disconnect everything from the VE.bus and only connected the MK3.
If you don’t get it back to life again you should try to contact a Victron installer to get some help.
waht do you mean by “default communication setting”? Is there a way to specify details on communication protocol? Or which information should I get from there and how can this information help me to get the inverter up and running again?
If @M_Lange has pointed you to an installer, it would imply that my understanding or depiction of the situation is effectively false and I defer to his statement and impeccable record for and as the best help available in this forum.
woop woop => saved my weekend, everything is up and running again!
so what did the trick?
well, I simply connected behind the VE.Bus:
my chain: Quattro → RJ45 → Mains Detect → RJ45 → VE.Bus → RJ45 → Victron Display
my connecting point: Quattro → RJ45 → Mains Detect → RJ45 → VE.Bus → RJ45 → MK3
So I unplugged the RJ45 from the display and connected it to the MK3 and tadaaaa….was able to connect to the Quattro again and re-enable the VE.Bus.
Did not dare to touch anything else now…so will leave iot as is and maybe another time try to start an update through that chain.
Also attaching images of my setup, the quattro is not visible there it is sitting a little bit more at the left.
Also attaching an image of the Main Detect: I figured out it is not even connected with the second wire so it is kind of a simple pass through…
thx every1 for your excellent help, highly appreciated, you are a great community!
thx,
Florian
Great success!!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
