Jump to content

incagarcilaso

Members
  • Posts

    203
  • Joined

  • Last visited

Profile Information

  • Gender
    Male

Recent Profile Visitors

2,246 profile views

incagarcilaso's Achievements

  1. Is it this TTT? https://github.com/victronenergy/dbus-mqtt
  2. OK. I had seen it there I think but looks complicated. I'll take another look. I do like the stats on tonnes of CO2 saved and other stuff on PVOutput.
  3. Ah, well no, not really about bragging rights. I suppose I am more used to pvoutput.org and find it offers more stats from the data. I'll take a look at VRM World though, and suppose I'll perhaps see more stats as the months roll on in VRM (system has been posting there since March).
  4. I do use VRM, but pvoutput.org is much more complete in its statistics and works better for long-term analysis. I also like that it is an "open" system where sharing and comparisons can be made.. It's much easier to see at a glance total energy, month to month differences and year to year changes on pvoutput.org. I'd like to have the stats in Victron's VRM but also in pvoutput.org.
  5. Hi. I have a Quattro with MPPT 150/85s, CCGX and BMV702. When I was using other equipment (Voltronic Axperts) I fed all generation and usage statistics to pvoutput.org which is a great way to monitor installations year to year and long term. Is there an easy way to feed statistics from my Victron installation to pvoutput.org. If it is very technical I will need a detailed explanation of the steps. I can't programme. Wasn't sure whether to put this here or in "The Internet of Things".
  6. Thank you. Very clear. I have carried out a couple of experiments, which haven't worked unfortunately. I'm sure your solution will work but the relay on the BMV is currently used of another purpose so I am not able to wire a physical relay into the Quattro. Because I don't have a physical relay available I looked for an alternative. What I tried was to use 2 "programmable relay" assistants. The first one stipulated to turn the general flag off when battery voltage was lower than 48v. The second one stipulated to turn the general flag on when the battery voltage was above 52v. However, once this configuration was uploaded it made the passthru switch back and forth continually (based on the first "programmable relay" it seems). It dropped below 48v and switched to passthru. As soon as it switched to passthru the voltage rose slightly and so it then switched back to inverter mode and so on and so on. I don't know why it ignored the second programmable relay, which I made sure was authoritative by putting it last in the list. Any ideas on why this didn't work? It's a shame the "programmable relay" assistant doesn't work in the same way as the relays in the BMV or on the CCGX where you have both an activate and de-activate condition in the set up of the relay. This way it would work. I noticed there is also an assistant called the "relay locker" with fairly obvious use. But the options in there are not clear. You can choose to implement it acccording to "primary programmable relay", "secondary programmale relay K1" or "secondary programmable relay K2". I'm not sure whether these options refer to physical or software relays. If the "primary programmable relay" refers to the "programmable relay" assistant then I could lock that for a maximum of 5 hours (max. allowed 16300 seconds) but this isn't clear. I think for now, following your tips, I will disable the charger and then change the battery voltage threshold parameters in the "generator start and stop" assistant. That way I can get an instant passthru (battery voltage is already down to 47.6) but the mains will not charge the batteries (that can be done with the MPPTs when the sun comes back out). I'm attaching an image of the current "generator start and stop" assistant, used in combination with the "general flag user". I'll just change the relay condition to 48v instead of 47v and that should do it - right? I hope this works. Hopefully next week I can get the firmware update to 415 or above and implement ESS. You're right about my Quattro having the newer chipset and able to implement ESS. I also checked on this. Thanks for all your help.
  7. Thanks Plonkster for the quick reply. I say HUB1 because that is what is showing as the mode in the CCGX. I know this is makeshift and am annoyed with the installer because it seems he didn't know what he was doing. He has set up a workaround for PowerAssist so that when consumption goes over a certain point help kicks in from the grid. But of course this is "back to front" because Power Assist is about using battery power to assist shoreline power rather than the other way around and (as I understand it) he has used the general flag to ignore AC in because of this and because AC1 in is not a generator but the grid. I have a few questions. 1. If I deselect "Enable charger", will the PV input still charge the batteries? 2. Yes, this should be set up as ESS but the installer didn't update the firmware on the Quattro and so when I try to run the ESS assistant en VE Config it throws an error because of the firmware version. As soon as he comes to update the firmware I will configure this in ESS mode, which is much better for the whole installation. 3. I can do the first part easily enough (disable the charger) but I'm not clear on installing a switch or the analog input. Are you talking about a physical switch or a virtual one? 4. Exactly which assistants would I need to have and in what order? 5. I really don't follow the role of the virtual switch tab or the general flag assistant. 6. What if I just disable the charger and remove the two current assistants - will that work? I just need to get out of this fix I'm in for the next couple of days.
  8. Hi guys, My Quattro (8k, 48v) hasn't been set up properly by the installer yet and I need to know how I can configure it to passthrough from the grid to loads on AC1 out without it also charging the batteries, because at the moment I can't even switch it to passthru. I'm on a run of very cloudy days here and my batteries I discharging more than I want (750 amp hours already consumed) but when I try to put it on "Charger Only" it doesn't supply power to the loads on AC1 out. According to the manual when it is put on "Charger only" is should switch power through from AC1 in to AC1 out. What I absolutely don't want is for it to switch to the grid and start recharging the batteries at this point because it is going to consume huge amounts of power that I can recoup as soon as the sun comes out. I'm running out of time on this as the batteries are almost at their 47v cut-off point I think the problem might be that "Power Assist" is implemented and that has a condition somewhere that says "ignore AC1 input". Can anyone clarify whether the "Power Assist" is the culprit. If I disable "Power Assist" will switching the Quattro to charger only power the loads from the grid without charging the batteries? This is what I need. My set up: It is set up in HUB1 mode. AC1 in comes from the grid. No AC2 input. AC1 out powers the house. No AC2 output. No generator. Battery bank. Two MPPT conrollers on the PV side. For those of you that have VE Config 3, I'm attaching the current setup file of the Quattro so that you can see exactly how it is configured. Thanks. PS. After research it seems the best set up for this installation is ESS. This is what I need and I have all the components necessary for this. I'm waiting for the installer to come and upgrade the firmware on the Quattro because the current version (413) doesn't support ESS. The ESS option appears already in my CCGX but it is empty (presumably until I upgrade to 415 minimum on the Quattro) 883314f622a2_inst_ttyO1_Interfaces_Mk2_Tunnel.rvsc
  9. Sure, and getting these implemented is not easy - but some things just seem so obvious that you wonder why it needs a request. I think most users will have more than one alarm configured ... Yes, and I will end up using the BMV but wouldn't it be good to have two separate relays at your disposal on a system with CCGX installed witht the BMV doing SOC (pretty common hardware stack).
  10. This could be the solution except that I have several alarm rules set up in the CCGX so that I receive timely information on system state by e-mail and I don't want the relay to activate for all of these alarm rules, of course, just one. It's odd that the CCGX doesn't allow to selectively apply the alarm rules that you set up to the relay so that not all alarm conditions activate the relay but only the one(s) you want. In this application I just need the relay to activate when my batteries reach full charge and then deactivate again when they have started to discharge. Given this shortfall in the options for the alarm relay, it looks like the only way to use the relay on the CCGX would be as you describe by setting it to manual and including a software layer in the middle.
  11. Ahh, good idea, that way I could reverse the NO / NC states. The only problem is that the Axpert works the relay according to setting 12 (point back to utility), which in principle I never reach, except in unusual circumstances. For this reason I had to rule out using the Axpert's own dry contact. It would work for energizing the relay because that is based on setting 13, which I do reach on a daily basis but at the other end of the relay scale setting 12 doesn't work for this application. The relay changes the mode of operation on the appliance rather than just switching it on and off so I do need it to switch the relay both ways every day - first when the batteries reach 100% (this will change the appliance mode to immediately heat the water to a higher temperature, making use of excess production) and second it needs to de-energize the relay a few hours later when battery charge state reaches, say, 98% (even thought the heat pump probably won't still be running at that point because it will already have heated the water to the set temperature). I use the CCGX because it is very reliable for reading system state, locally and remotely - it is the most reliable system I have used for this. Of course, it does not read the Axpert values directly so while I cannot see exact net PV production and total household consumption in the CCGX I can see the difference between them and so know more or less what is going on. Because I have the BMV in the system this does give me all the essential information in the CCGX for the battery state (ultimately the most important data). With this I find that the CCGX works well enough with the Axpert. Furthermore, all the additional features and configuration possibilities are still there with the CCGX and can be applied with an Axpert, like logging directly into the CCGX screen on the local network (or even remotely if you want to risk it) and using all of the alarm types and features. Loggin in to the CCGX live screen remotely means that you can operate the CCGX from there as well as see all it's values. Here's an image of one of the screens of the CCGX attached to an Axpert, showing general system state and one of the BMV readings.
  12. Thanks TTT, that's what I thought might be safer. I'm not good at that either (not an electrician). I'll see if I can work out exactly what kind of secondary relay I need between the BMV and the appliance in order for this to work and also work out how it has to be wired. What I don't fully get is how the current isn't passed from one circuit to another (even with an intermidiary relay) when the relay is energised, because in that state of energised the circuit is made between the BMV and the appliance. The appliance's relay input is rated 230VAC and 2A max, so I don't get how an intermediary relay translated the signal from the BMV rated at 60VDC and 1A max to that of the appliance.
×
×
  • Create New...