Jump to content

Victron MPPT connected to ICC Software communication


Recommended Posts

Good day

I am running ICC on a Raspberry monitoring an Axpert Inverter, Victron SmartShunt via a VE Direct to USB cable. These monitoring works like clock work.

Yesterday evening, I have linked up a Victron Smart Solar MPPT 150/60 to my system and connected it up via a VE Direct to USB cable also to the Raspberry.

On ICC "Victron MPPT" is on, "Add Victron MPPT PV to Total PV" is On, "Use external Victron Battery Monitor" is On.

After restarting the Raspberry, ICC picked up the MPPT, showing the model, serial number, firmware version and battery voltage in the Victron MPPT tab. The battery data from the SmartShunt update correctly and around every second.

However it was dark and no PV data was shown.  After the panels started to produce power today, I noticed that the ICC PV info updated very slowly and does not correspond with info shown on VictronConnect. The ICC Battery Voltage and MPPT Voltage update around +/- every 60 seconds incorrectly and the other values update like once or twice in the hour.

First, I thought the VE USB cable was faulty, swop the cables around between the SmartShunt and the MPPT and still no luck with the data feed from the MPPT to ICC. The SmartShunt updates correctly with any of the two cables.

On the MPPT, the TX port is set for Normal Communication and the RX Port is set for Remote On/Off, Smart Networking is enable between the MPPT and the SmartShunt.

Have spoken to Manie at ICC and he said that they have other clients with a same setup and on their systems both the MPPT and Battery values update fast and correctly.

Can someone assist me to get the MPPT data feed correctly?

Thank you for a great forum.

Herman

 

Link to post
Share on other sites
6 hours ago, hjr said:

Have spoken to Manie at ICC and he said that they have other clients with a same setup and on their systems both the MPPT and Battery values update fast and correctly.

Can someone assist me to get the MPPT data feed correctly?

I am also running a Victron MPPT together with ICC. I am not having the issues that you are describing. I have never really timed the update frequency, but it is definitely more frequent than 60 seconds. Here is a screenshot of my PV watts graph

PV.thumb.JPG.382de3c5a594ae179af8fcd53e35386b.JPG

What version of ICC are you running? If I remember correctly, then the update frequency in the first version that supported Victron MPPTs was still a bit sluggish - but Manie fixed that shortly afterwards

6 hours ago, hjr said:

On the MPPT, the TX port is set for Normal Communication and the RX Port is set for Remote On/Off

Same settings on mine

6 hours ago, hjr said:

After restarting the Raspberry, ICC picked up the MPPT, showing the model, serial number, firmware version and battery voltage in the Victron MPPT tab.

Here is what my MPPT tab shows (it's dark outside, so obviously some values are at 0)

PV2.thumb.JPG.21822dcd40dc98c916328511614aca25.JPG

6 hours ago, hjr said:

First, I thought the VE USB cable was faulty, swop the cables around between the SmartShunt and the MPPT and still no luck with the data feed from the MPPT to ICC. The SmartShunt updates correctly with any of the two cables.

Have you tried different USB ports on the Pi? 

Link to post
Share on other sites
37 minutes ago, wolfandy said:

What version of ICC are you running?

Update done, MPPT screen is now the same as yours and now showing "MPPT Tread Running"

Thanks again. Never thought about a software update recently. ICC was running like clock work and my believe is not to fix something that isn't broken.

Link to post
Share on other sites
10 minutes ago, hjr said:

Thanks again. Never thought about a software update recently.

Cool - happy to hear that fixed the problem

17 minutes ago, hjr said:

ICC was running like clock work and my believe is not to fix something that isn't broken.

On the one hand I am with you on that. But at the same time, my experience with Manie and his updates has always been outstanding - so I typically run the updates as soon as they are available

Link to post
Share on other sites
On 2020/09/05 at 9:24 PM, wolfandy said:

On the one hand I am with you on that. But at the same time, my experience with Manie and his updates has always been outstanding - so I typically run the updates as soon as they are available

Since I've done the version upgrade ICC is freezing randomly anywhere after 25H runtime, something I've never experienced with V2.996. I've looked up my upgrade path and have done an upgrade from 2.996 to 2.999, and on 2.999 I've experienced random freezing problems and rolled back to V2.996

Wolfandy, are you having any freezing or hanging problem with V2.99996?

Link to post
Share on other sites
39 minutes ago, hjr said:

are you having any freezing or hanging problem with V2.99996?

No problems at all. My current runtime is at 156h

Are you using the USB cable that originally came with the Axpert? If yes, then I would recommend replacing it with a current one. The original cable (older USB standard) can cause comms problems between the Axpert and the Pi

And your Raspberry OS is also current/updated?

Have you restarted your Pi after the update (usually not necessary, but might sometimes help)?

Link to post
Share on other sites

Not the cable, using a shielded USB external hard drive cable, Pi (Pi 2B) is update to date with the latest updates and I have restarted every-time when ICC hangs to clear any possible static charges that may accumulate. I'm sitting with my hands in my hair, can I pm you?

Link to post
Share on other sites
50 minutes ago, hjr said:

using a shielded USB external hard drive cable

Is it a current or older one? I originally replaced the Axpert USB cable with another USB cable that I had lying around (had no idea how old). Eventually picked up a new one and since then the occasional hiccups that I had with ICC (e.g. dying on me when changing something via VNC from my iPad) have virtually disappeared

53 minutes ago, hjr said:

I'm sitting with my hands in my hair, can I pm you?

Of course

Have you asked Manie to look into your new freezing problem? Do you have VNC running and granted him access, so that he can dig around a bit? He's been able to help me like that in the past

Link to post
Share on other sites
  • 2 weeks later...

Status Update

At the end of a couple of weeks of testing various combinations of ICC versions on a Pi3 and a Pi2, with Debian Buster Operating system and with the Debian Stretch Operation system, I figured that the culprit was a SD Card with some sort of file corruption.

On creating a new SD Card from the latest Pi4 image (with the Buster OS) to test on a Pi3, ICC immediately started to run smooth without any freezing problems. When testing the same on a Pi2, the same result as with the Pi3, no freezing. However the Pi2 struggled with the screen refresh rates of ICC on Buster OS. Done the same with the new SD Card but with Stretch OS on the Pi2, also no freezing so far, but with better screen refresh rates of ICC.

As part of the tests, I replaced the power supply on the Pi2 with the power supply of the Pi3 (5.1V 3.0A), and then realize that the Pi2 was under powered. According the Raspberry Pi forums, an under powered Pi can cause SD Card corruption.  On a Pi2, the red LED must be constant On, this is showing that the Pi2 is receiving sufficient power. If it flickers or is Off then the Pi2 is under powered. This was the case with the Pi2 before changing the power supply.

My only conclusion, at the moment, is that there is file corruption on the old SD Card of the Pi2 which caused the newer versions of ICC to freeze. The file corruption was caused by an under powered Pi2.

So far, the current run time of ICC V2.9996 on a new SD Card with Stretch OS on a Pi2 with a Pi3 power supply is approaching 70:00 with out any freezing problems.

Link to post
Share on other sites
13 hours ago, hjr said:

So far, the current run time of ICC V2.9996 on a new SD Card with Stretch OS on a Pi2 with a Pi3 power supply is approaching 70:00 with out any freezing problems

Cool - happy to hear that you got it sorted

Power and SD card problems are apparently not uncommon with the Pi. But have to admit that I also did not think of that at the time...

I've got the 4GB version of the Pi and have moved directories with frequent writes into RAM to reduce the number of writes to the SD card (see here for details and other tips on extending the life of the SD card)

Link to post
Share on other sites
  • 3 months later...
On 2020/09/09 at 10:22 AM, hjr said:

Not the cable, using a shielded USB external hard drive cable, Pi (Pi 2B) is update to date with the latest updates and I have restarted every-time when ICC hangs to clear any possible static charges that may accumulate. I'm sitting with my hands in my hair, can I pm you?

This is actually a common issue with various PIs (2B, 3B+, 4, etc.):

 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...