question

Michael Gane avatar image
Michael Gane asked

Epever MPPT on DBUS not displayed on GUI

I Have a Tracer 40A MPPT that uses Modbus protocol and am running Venus on a raspberry pi.

I've managed to run a dbus service as com.victronenergy.solarcharger.epever_ttyUSB2 and then in a separate script can publish values to it by writing on the system bus.

I can set the /State and the Pv / battery info fine and it displays in the "Device List" in the Venus remote console panel and the values update just fine.


I never get a solar item in the overview screen and it doesn't display on the VRM portal. Is there some values that I need to publish somewhere else other than the `com.victronenergy.solarcharger.epever_ttyUSB2` dbus item to get the solar input to display?

MPPT ControllersVRMVenus OSCCGX Color Control
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

3 Answers
Kevin Windrem avatar image
Kevin Windrem answered ·

You may need to create and populate additional parameters in order to get the system to recognize your dBus service as a valid solar controller. If you have other solar charge controllers, you can look at it in dbus-spy to see what else you might need to create.

For starters, the /Mgmt/... parameters and /Connected and possibly /DeviceInstance.

There is some information about dBus services here:

https://github.com/victronenergy/venus/wiki/dbus-api

and more here:

https://github.com/victronenergy/venus/wiki/dbus

note the section on generic paths which may be required to make a dBus service recognizable.

also some specifics for solar charge controllers here:

https://github.com/victronenergy/venus/wiki/dbus#solar-chargers

Hope that helps

1 comment
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

I have most of the information now showing in the venus remote console.

One thing I can't seem to figure out, is what I should be setting for the following values?

/ProductId
/DeviceInstance


I assume the productId will affect if the overview screen displays the data as solar input?

I can't seem to find any examples anywhere of productIds and the various GitHub dbus pages only let me know it should probably be a hex value?

0 Likes 0 ·
Kevin Windrem avatar image
Kevin Windrem answered ·

/ProductId can be any number you'd like. I just used 0

/DeviceInstance can be any number as long as it is unique across all services with the same service name. There's a brief discussion here:

https://github.com/victronenergy/venus/wiki/dbus-api.

1 comment
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Thanks!

Turns out I wasn't passing some of the values correctly to dbus which was causing the system to crash or not register correctly.


dbus --system com.victronenergy.solarcharger.sample /State SetValue %3

// Note the % after SetValue, /State wasn't working without this


0 Likes 0 ·
Nikolay Nedeltchev avatar image
Nikolay Nedeltchev answered ·

Hello, @michael-gane.

What you did sounds great! Can you please share? I use the same MPPT controller. Thank you in advance.

2 comments
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Hey, the scripts I use to publish on DBUS are here: https://github.com/ganey/victron-json-mppt

After many weeks of trying, I couldn't poll the Epever for readings frequently enough to keep it stable in Venus, it kept dropping out from the GUI and then the epever would freeze for a few minutes and not provide any readings.

I currently have a raspberry pi reading once a minute from the Epever and writing the values to a json file.

The github scripts read the json file over my local network and publish the values on DBUS.


You could probably read the values once a minute from a raspberry pi running Venus and just publish them frequently on dbus. I tried this but my epever still wasn't happy doing the readings, it might be because it uses the +ve as the common rather than the -ve, newer models (with blue buttons?) use -ve as common instead.

0 Likes 0 ·

Thank you for your reply.

I red someware info that this MPPT controller is very sensitive on 'grounding' and this can cause the problems of interupting the data.

0 Likes 0 ·