Dear all,
I found some posts in the previous communities about the MK3-USB driver issue. Nevertheless the troubleshooting tips there do not solve my issue.
I installed the driver mention in the troubleshooting. Nevertheless I cannot access my MultiPluss II nor my MultiplusII GX.
I never had driver issues so far, though can anybody tell me what the issue may be?
Thanks a lot for your support!
First configuration?
Then, it is important to only power on one multiplus, and power on the others when asked to do so during the system setup.
Thank you. This is the way I tried. Just one is powered. Still no connection.
Try disconnecting all additional VE.bus connections until required.
So you only have one device connected to the mk3, without anything on it’s VE.bus out
I have only this connection:
Multiplus II VE.Bus to MK3-USB to PC (USB)
Nothing else.
Do you get an error or something like that? Can you make a screenshot?
Is the MK3 recognized and shown in the Windows device manager?
Sure. First of all the separate (!) configurations I try:
Configuration:
MultiPlus II --Interface MK3-USB (VE.Bus to USB Adapter) – PC
Connection with an RJ45 cable (same as I use for the CerboGX and which works there)
Configuration:
MultiPlus II GX – Interface MK3-USB (VE.Bus to USB Adapter) – PC
Connection with an RJ45 cable (same as I use for the CerboGX and which works there)
This is the screenshot of the Device-Manager prior to plugging in the MK3-USB to the Win11 PC:
And this is the Device-Manager after plugging in the MK3-USB to the Win11 PC:
When starting VE Configure 3 and plugging in the MultiPlus II (independant if the MultiPlus II or the MultiPlus II GX is plugged - important is the OR!), I first try
‘Port selection - Com Port - Auto detect’
It takes a while displaying dots and then I get this view:
Same result if I don’t select ‘auto detection’ but directly ‘Com 3 (USB serial port)’
Just to make sure, you did not insert any of the bus-end-connectors? (Docu says they are not needed, maybe having them present also blocks communication)
When connecting, check the Group “Ports (COM & LPT)” in Device Manager, make sure COM3 is the device that appears.
For my MK3 it’s COM10 by default, but that’s most likely random for every machine.
Thank you. I have no bus-end connectors.
The ports (COM & LPT) are as displayed in the screenshot:
Looks all good…
When you rightclick → properties on that device, you can change com-ports. You can try to pick another one.
Also make sure you have no other software running that utilizes com ports. I have one called solar-putty, that claims access to every connected device almost immediately.
Shut down any anti-virus software, they may block access as well.
Make sure to run VEConfigure as administrator (shift + right click in win 11 → run as administrator)
Then, i’m basically out of ideas.
Switched to COM7, not used so far. Started VEConfigure as admin → same result, no device found.
I also tried VEConnect as admin, same result.
Nevertheless thank you for your effort!
@manni27
There is a possibility that the dongle is not working correctly.
How can I check the dongle? Would be sad to buy a new one if I thebactual is not damaged but there may be an issue with the PC?
On case I get a new one I won’t be able to return it ifbitbis behaving the same way though I use it remote far from being able to return within 4-8 weeks.
Would a VEDirect to USB dongle 3nable thensame configuration, I saw I have one.
No, unfortunately it is the mk3 to program the inverter unless you do it over the internet with the vrm.
A simple test is to plug it into the GX ve bus (instructions here) with the patch cable. It should appear in the device list as in inverter.
I have a laptop that cannot be plugged into power at the same time as using it with an inverter. Just a weird side note can also be an issue.
The connection wirh the cerboGX does work without any issue.
So I did get a new MK3 to USB converter. Again same issue, no connection…
Today I saw I video to connect an Android phone vie the mk3 and a network cable. So this did work! It seems the issue is somehow with the USB driver.
