After 20 years doing Victron finally got stuck.Cannot get Victron Connect to talk a Multiplus II GX through MK3.
A bit of backgroung:updated from 556 to 558 firmware without a problem and the unit is working just fine.After a few days got called for a minor issue.Tried to talk to the unit through MK3 and VEBus and no luck.Again tried VEDirect to USB adapter and still no luck.Tried VEConfig via MK# and VEBus and it works.Checked the drivers for the FTDI chips inside the adaptors and they’re fine(strangely 2 USB/RS485 adaptors of mine stopped working recently and it brought reminders of 2014 1nd 16 when FTDI bricked thousands of FTDI counterfeit chips ).But because VEConfig works through MK3 and VEBus proves that the drivers are fine.
Also what makes it hard is that Victron Connect just upgraded to V6.24.So I don’t know if there’s bugs with it or firmware 558.That’s why I decided to ask if anyone is having the same issues before going gangbusters and start rolling back to firmware 556 and so and so.
Still not able to talk to the Multiplus II GX over VE Direct.Yesterday tried to go back to Victron Connect V6.23.Went to the Changelog and sure it was still there.Clicked on the Windows 10 version and to my amazement,after installed,realized it was V6.24???.Victron can you please fix that!.
Couldn’t find a copy anywhere else so had to download a Android version of the V6.23.Then with a Android Emulator for Pc managed to run it.Anyway after all these troubles still could not talk to the Multiplus.Could talk with the VEConfig but not with Victron Connect.
That proves the problem is not with Victron Connect but probably with firmware 558.Well,have to roll back to 556,and see what happens.
A MultiPlus doesn’t have VE.direct, so you don’t need to try that.
(I guess you have a MultiPlus GX, in that case the VE.direct port is from the GX module, not from the MultiPlus)
You need to use the VE.bus MK3 interface.
Do you get an error or isn’t the MultiPlus shown in VictronConnect?
I use VictronConnect 6.24 with MK3 and last FW without problems.
But I also prefer to use VE.config instead of VictronConnect.
I’ve done that.There’s not an issue with VEConfig.The thing is there’s things you can’t do on VeConfig like turn on the WiFi on the Multiplus etc.That’s why I need the Victron Connect.
Thanks Matthias for the link issue.Anyway,today rolled back to 556,but the problem is still there.
Guess next step is running V6.23 with 556 and see what happens.If does not work don’t know what to try next.Any idea where I can find V6.23 for Windows 10?.
Going back to Victron Connect,I’ve also tried Linux,and does not work.Next tried on a Android phone with a OTG adapter and it works.
I think Victron is going full on with Android and Ios and leaving Windows behind.Everyone’s doing that.
Even the new look VRM is unworkable on a Windows laptop.Try to go Installation-Advanced and try to change your widgets.The pop up windows leave no space left to see the data.Terrible.It works great on a phone screen(portrait)but not on a laptop screen(landscape).
They left VEConfig for Windows because you need it to change grid codes and the assistants.Victron Connect does not support such changes as yet.Why does(at least on my end)VeConfig work and Victron Connect doesn’t?.Still don’t have an answer.
Could you find any solution? I have had similar problemes twice. I’m using venusOS in serveral victron installations and the MK3 interface to connect the MP2. There seems to be a slight chance that the MK3 dies on a reboot of the system. I had it once while installing an venusOS update and once after performing a reboot. The MP2 won’t reconnect after the restart to the venusOS and won’t show up using VictronConnect via MK3 but still could be configured via the same MK3 interface and the configure program. There is nothing smelly or burned in the MK3 interface and everything works fine with the MP2 and venusOS when using a new MK3.