2 jsy modules

[reguiny]

Is it possible to use a JSY-MK-333 to read the grid power and use a JSY-MK-194G to read routed power? If so how do I connect them?
Thank you.

[mathieucarbou]

Hello,

No this is not supported, but this is definitely possible to develop this feature.
Not now though because this implies a lot of code change and there is currently another possibility.

Currently, with a JSY-MK-333 used to measure the grid power, you can use a PZEM to measure the routed power.

PZEM devices are cheaper and they can be connected on the same serial, one for each output.

I will add an item to the board to track this work.

[mathieucarbou]

Hi @reguiny ,

I plan to release a new YaSolR version in a few days including a lot of new features (like cycle stealing) and also a revamp of how measuring devices are configured. With the new version we will be able to chose which measuring device to use for grid and routing power measurement and in both cases we can also chose between remote, serial1 or serial2. So you could in theory even have 1 remote jsy for the grid metrics, 1 jsy for output 1 and 1 jsy for output 2 if you wanted, or, like you want: have a JSY-333 on serial1 for example for the grid and one JSY-194 on serial 2 with channel 1 for output 1 and channel 2 for output 2.

=> would you like to help me test this setup before I release or no time ?

[reguiny]

Thank you for the update. I would be pleased to test your new version but the jsy-333 is on order and should arrive next week.
I will be using it with a jsy-194g, will the zx (zero cross) still work?

[mathieucarbou]

Thank you for the update. I would be pleased to test your new version but the jsy-333 is on order and should arrive next week.

I will be using it with a jsy-194g, will the zx (zero cross) still work?

That is perfect : it lets me time to test and update the website.

Yes, it is supported, although not the better ZCD since the event is bot based on hardware but on the calculations made with the Renergy cheap, on 20ms so the ZC point has to be inferred.

What will you use for dimming ? A random SSR or a normal synchronous SSR. I added support in main branch for cycle stealing so it will also be available and it works nicely. If you want to read about it you can have a look at the MycilaDimmer library ;-)

[reguiny]

I will keep you updated about the delivery..
I am using a pwm dimmer at the moment but I see a high thd in the thousands, would it be lower if I used a normal ssr? Are all ssrś suitable for cycle stealing?

[mathieucarbou]

I will keep you updated about the delivery..

I am using a pwm dimmer at the moment but I see a high thd in the thousands, would it be lower if I used a normal ssr? Are all ssrś suitable for cycle stealing?

The THDi is the sum of all harmonics so it is high yes and probably not the one to look at. I plan on removing this metric since it tends to make people think that harmonic levels are high when they are not always high. What is important to look at is the harmonic graphs and compare to the local regulation as explained in the website and YaSolR release page.

A normal SSR with cycle stealing does not produce harmonic levels like phase control does indeed but still produces some at a little higher frequencies but they have far less impact.

For cycle stealing look at the website. Either random SSR + ZCD, or just a normal one.

[mathieucarbou]

@reguiny : FYI I have pushed in the repository main branch the ability to use any device on any Serial / Remote for any kind of measurements. We can now chose for each (grid, output 1 and output 2) if we want to use MQTT, Victron, JSY, JSY Remote, PZEM, etc plus, also, when applicable, which channel and which Serial to use. I will update the website in the following days.

If you use / test with the OSS version, these can be configured at http://192.168.123.99/config

For Pro:

Dimmers:

[mathieucarbou]

@nicograne : I've just implemented the feature.
Since you are using the OSS version, you will be able to directly get the firmwares built by the build system from the last pushed change here: https://github.com/mathieucarbou/YaSolR/actions/runs/24688298864.
When the build is green, you have a list of zip files for all the boards. If your tests are successful I will release.

If you get the pro version you should see this dropdown for grid:

and outputs:

Same dropdowns are also in the /config page for oss version.

Let me know how it works please!

[nicograne]

I've just implemented the feature.

Thanks for the very quick response!
This is great news!
Sorry, but I just ordered the JSY MK-333 because I was waiting to see if it was possible to implement the option. I'll test it as soon as it arrives and post the results!
... I'm just getting started on GitHub, so I'm not entirely clear: I purchased the Pro version a few weeks ago. To use this modification with the Pro version, can I update via OTA with the files in the zip file at the link above? How does it work? I opened the compressed folder and saw that the files are all OSS.
Thanks in advance for your patience!

[mathieucarbou]

I've just implemented the feature.

Thanks for the very quick response! This is great news! Sorry, but I just ordered the JSY MK-333 because I was waiting to see if it was possible to implement the option. I'll test it as soon as it arrives and post the results! ... I'm just getting started on GitHub, so I'm not entirely clear: I purchased the Pro version a few weeks ago. To use this modification with the Pro version, can I update via OTA with the files in the zip file at the link above? How does it work? I opened the compressed folder and saw that the files are all OSS. Thanks in advance for your patience!

Hi,
I double-checked and indeed you donated to the project so you have access to the pro version.
I will release a new version today that you will be able to download at the usual place for the pro version (https://github.com/mathieucarbou/YaSolR-Pro/releases).
This will be version 1.2.0.

[nicograne]

Thank you so much! You're too kind!
As soon as I receive the JSY MK-333, I'll put it to use right away!

[mathieucarbou]

Thank you so much! You're too kind! As soon as I receive the JSY MK-333, I'll put it to use right away!

Thanks! Let me know how it works ;-)

[reguiny]

Thank you for the update,I will have to wait for you to publish the binaries as i cannot compile the file.
I get these errors when I try to compile:

cacerts.py: Certificate bundle already exists
embed.py: [embed.py] config.html up to date
embed.py: [embed.py] logo-icon.png up to date
embed.py: [embed.py] logo.png up to date
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Exception: No branch name found:
File "/home/mike/.platformio/penv/lib/python3.12/site-packages/platformio/builder/main.py", line 167:
env.SConscript(env.GetExtraScripts("pre"), exports="env")
File "/home/mike/.platformio/packages/tool-scons/scons-local-4.8.1/SCons/Script/SConscript.py", line 620:
return _SConscript(self.fs, *files, **subst_kw)
File "/home/mike/.platformio/packages/tool-scons/scons-local-4.8.1/SCons/Script/SConscript.py", line 280:
exec(compile(scriptdata, scriptname, 'exec'), call_stack[-1].globals)
File "/home/mike/Downloads/YaSolR-main/tools/version.py", line 79:
do_main()
File "/home/mike/Downloads/YaSolR-main/tools/version.py", line 33:
raise Exception("No branch name found")

I am not a programmer!

[mathieucarbou]

Ah!! Sorry this is my fault indeed... I think I can fix that. When building, I use git to lookup for the version but when you download the zip there is no git info...

[mathieucarbou]

@reguiny : I had this issue in several of my projects. Thanks for notifying. I fixed it.

[reguiny]

It compiles now. I have tested with my existing setup and everything seems fine, i will test with the 333 when it arrives.

What does the shared setting in the source config do?

[mathieucarbou]

shared is for users having just 1 JSY-MK-194: they have the channel 2 clamp measuring the grid and channel 1 clamp (or tore) used to surround the 2 wires of output 1 and 2. So output 2 power is shared with output 1. This is really not recommended since leads to wrong stats when dimming because of the different algorithms and phase angles.

[reguiny]

I have installed the JSY-333 and it appears to to working correctly.
There is a problem with the output sources selection, the 3 choices for the 194 are shown twice! I have tried both for my setup, the led on the 194 board flashes but I do not receive any readings.

[mathieucarbou]

I have installed the JSY-333 and it appears to to working correctly.

There is a problem with the output sources selection, the 3 choices for the 194 are shown twice! I have tried both for my setup, the led on the 194 board flashes but I do not receive any readings.

Can you please send a screenshot ?
For each JSY Channel, we have to select if this is on serial 1, 2, or a remote one (Mycila JSY App)

[reguiny]

I have selected the correct serial port, but I do not receive any readings when I activate the dimmer.

Another problem the 333 is only showing the power from 1 phase not the total of the 3 phases. I have compared with the linky.

[mathieucarbou]

I don't see any duplication in the list. Where is the issue ? You need to select the option matching your JSY:

• model
• channel 1 ou 2 is used (JSY 193 and 194 have 2 channels)
• serial1 or serial 2 (where is connected your jsy)

Then after that you can restart.

For the 333, the code is reading the aggregated metrics sent from JSY internals directly (https://github.com/mathieucarbou/YaSolR/blob/main/src/yasolr_jsy.cpp#L158-L171)

What you can do to counter verify that is setup Mycila JSY App on an ESP32 connected to your JSY-MK-333 in order to validate the metrics in the UI: you should see all 3 phases.

Then go to the REST API of Mycial JSY App: http://jsy-a62d44.local/api/jsy

You should see a Json with the complete JSY metrics. Mine looks like this:

{
"enabled": true,
"time": 2383486663,
"speed": 9600,
"address": 1,
"model": 355,
"model_name": "JSY-MK-163",
"frequency": 50.03,
"voltage": 238.13,
"current": 5.25,
"active_power": -260,
"reactive_power": 1228.834,
"apparent_power": 1256.039,
"power_factor": 0.207,
"active_energy": 4281790,
"active_energy_imported": 3851520,
"active_energy_returned": 430270,
"resistance": 9.433106,
"dimmed_voltage": 49.52381,
"nominal_power": 6011.37,
"thdi_0": 472.6284
}

But for yours with the 333, you should see all 3 phases plus a section for the aggregation.

If all that works, then it should work with YaSolR since this is exactly the same library. The only difference is the input voltage: Mycila JSY App is enough to power the JSY-333 but YaSolR with all other stuff might not. There is a jumper or different pin in the JSY 333 board to power it through 3.3V or 5V. Maybe power it with the same 5V used to power your ESP.

You can also try this: in Mycila JSY App connected to your JSY 333, activate UDP sending. And in YaSolR, select JSY 333 (Remote) for the grid source. This should read the aggregated metrics of the 333 from Mycila JSY App.

Let me know.

I do not have 3 phases at home and do not have access to so the only way I tested is by simulating that by putting 3 loads through the 333 clamps. I am pretty sure the JSY 333 setup works in YaSolR since I know at least a user using it, and it uses the MycilaJSY library used by several people also.

So this is either a config / wiring issue, or may be a bug in the new code in main I did to support multiple JSY.

That's why your testing will help a lot!

On my side I will do some more testing also this week-end. I did with JSY and PZEM but not with 2 JSY for now.

[mathieucarbou]

@reguiny : I did some testing and everything works fine.

• JSY-194 powered by +5V DC (my esp does not provide enough voltage for 3.3V)
• JSY-333 powered by +5V DC (my esp does not provide enough voltage for 3.3V)

My GPIO config:

My Hardware config:

Logs:

I am activating the 2 outputs:

Result : I have some power for grid (I put a wire in phase C) and outputs

Here is the output also of http://192.168.123.99/api/debug which shows the JSY data and its aggregated output plus the router and its outputs:

{
  "grid": {
    "online": true,
    "metrics": {
      "source": "JSY-MK-333 (Serial1)",
      "time": 714898,
      "apparent_power": 241,
      "current": 1.05,
      "energy": 120,
      "energy_returned": 0,
      "frequency": 49.97,
      "power": 110,
      "power_factor": 0.457,
      "voltage": 229.5238
    }
  },
  "jsy": {
    "serial1": {
      "enabled": true,
      "time": 714898,
      "speed": 19200,
      "address": 1,
      "model": 819,
      "model_name": "JSY-MK-333",
      "aggregate": {
        "frequency": 49.97,
        "voltage": 229.5238,
        "current": 1.05,
        "active_power": 110,
        "reactive_power": 130,
        "apparent_power": 241,
        "power_factor": 0.457,
        "active_energy": 120,
        "apparent_energy": 160,
        "active_energy_imported": 120,
        "reactive_energy": 40,
        "reactive_energy_imported": 40,
        "resistance": 99.77325,
        "dimmed_voltage": 104.7619,
        "nominal_power": 528.0091,
        "thdi_0": 194.6317
      },
      "phaseA": {
        "frequency": 49.97,
        "voltage": 0,
        "current": 0,
        "active_power": 0,
        "reactive_power": 0,
        "apparent_power": 0,
        "power_factor": 1,
        "active_energy": 60,
        "apparent_energy": 70,
        "active_energy_imported": 60,
        "reactive_energy": 10,
        "reactive_energy_imported": 10,
        "phase_angle_u": 0,
        "phase_angle_i": 0,
        "phase_angle_ui": 0,
        "thd_u": 0,
        "thd_i": 0,
        "thdi_0": 0
      },
      "phaseB": {
        "frequency": 49.97,
        "voltage": 0,
        "current": 0,
        "active_power": 0,
        "reactive_power": 0,
        "apparent_power": 0,
        "power_factor": 1,
        "apparent_energy": 80,
        "active_energy_imported": 50,
        "reactive_energy": 30,
        "reactive_energy_imported": 30,
        "phase_angle_u": 0,
        "phase_angle_i": 50.02,
        "phase_angle_ui": 0,
        "thd_u": 0,
        "thd_i": 0,
        "thdi_0": 0
      },
      "phaseC": {
        "frequency": 49.97,
        "voltage": 235.98,
        "current": 1.05,
        "active_power": 110,
        "reactive_power": 130,
        "apparent_power": 241,
        "power_factor": 0.457,
        "active_energy": 10,
        "apparent_energy": 10,
        "active_energy_imported": 10,
        "phase_angle_u": 0,
        "phase_angle_i": 50.02,
        "phase_angle_ui": 62.79,
        "thd_u": 2.09,
        "thd_i": 97.91,
        "resistance": 99.77325,
        "dimmed_voltage": 104.7619,
        "nominal_power": 558.1312,
        "thdi_0": 194.6317
      }
    },
    "serial2": {
      "enabled": true,
      "time": 714944,
      "speed": 38400,
      "address": 1,
      "model": 404,
      "model_name": "JSY-MK-194",
      "aggregate": {
        "frequency": 49.97,
        "voltage": 236.3958,
        "current": 2.8138,
        "active_power": -69.25929,
        "reactive_power": 662.1496,
        "apparent_power": 665.7619,
        "power_factor": 0.10403,
        "active_energy": 3127,
        "active_energy_imported": 1030,
        "active_energy_returned": 2097,
        "resistance": 8.747655,
        "dimmed_voltage": 24.61415,
        "nominal_power": 6388.338,
        "thdi_0": 956.0443
      },
      "channel1": {
        "frequency": 49.97,
        "voltage": 236.3958,
        "current": 1.7332,
        "active_power": -190.3639,
        "reactive_power": 363.429,
        "apparent_power": 410.267,
        "power_factor": 0.464,
        "active_energy": 3109,
        "active_energy_imported": 1012,
        "active_energy_returned": 2097,
        "resistance": 63.37051,
        "dimmed_voltage": 109.8338,
        "nominal_power": 881.845,
        "thdi_0": 190.9128
      },
      "channel2": {
        "frequency": 49.97,
        "voltage": 236.3958,
        "current": 1.0806,
        "active_power": 121.1046,
        "reactive_power": 224.9696,
        "apparent_power": 255.4949,
        "power_factor": 0.474,
        "active_energy": 18,
        "active_energy_imported": 18,
        "resistance": 103.7124,
        "dimmed_voltage": 112.0716,
        "nominal_power": 538.8263,
        "thdi_0": 185.7647
      }
    }
  },
  "network": {
    "ip_address": "192.168.123.99",
    "ip_address_ap": "0.0.0.0",
    "ip_address_eth_v4": "0.0.0.0",
    "ip_address_sta_v4": "192.168.123.99",
    "ip_address_eth_v6_local": "::",
    "ip_address_sta_v6_local": "fe80::b2b2:1cff:fe0a:1c48",
    "ip_address_eth_v6_global": "::",
    "ip_address_sta_v6_global": "::",
    "hostname": "yasolr",
    "mac_address": "B0:B2:1C:0A:1C:48",
    "mac_address_ap": "B0:B2:1C:0A:1C:49",
    "mac_address_eth": "",
    "mac_address_sta": "B0:B2:1C:0A:1C:48",
    "mode": "STA",
    "state": "NETWORK_CONNECTED",
    "wifi_bssid": "00:17:13:37:28:C0",
    "wifi_rssi": -31,
    "wifi_signal": 98,
    "wifi_ssid": "IoT"
  },
  "pid": {
    "config": {
      "enabled": true,
      "pMode": "input",
      "icMode": "clamp",
      "reverse": false,
      "time_sampling": false,
      "setpoint": 0,
      "kp": 0.1,
      "ki": 0.3,
      "kd": 0,
      "filter_alpha": 1,
      "output": {
        "min": -800,
        "max": 4000
      }
    },
    "runtime": {
      "start_time": 342571,
      "last_time": 714901,
      "elapsed": 372330,
      "last_input": 110,
      "last_output": -497.07,
      "last_error": -110,
      "pTerm": 302.93,
      "iTerm": -800,
      "dTerm": 0,
      "feed": 0
    },
    "stats": {
      "iae": 515560.8,
      "ise": 1551197000,
      "itae": 150581100,
      "rmse": 2041.125,
      "avg_err": 1384.688
    }
  },
  "pulse_analyzer": {
    "enabled": true,
    "online": true,
    "type": 1,
    "frequency": 100,
    "period": 9989,
    "period_min": 9927,
    "period_max": 10008,
    "shift": -150,
    "width": 1128,
    "width_min": 683,
    "width_max": 1209,
    "grid": {
      "frequency": 50,
      "period": 20000,
      "semi-period": 10000
    }
  },
  "relay1": {
    "enabled": true,
    "state": "off",
    "switch_count": 0
  },
  "relay2": {
    "enabled": true,
    "state": "off",
    "switch_count": 0
  },
  "router": {
    "metrics": [
      {
        "source": "Computed",
        "apparent_power": 305.367,
        "current": 1.330437,
        "energy": 0,
        "energy_returned": 0,
        "frequency": 0,
        "power": 157.8586,
        "power_factor": 0.516947,
        "voltage": 0
      },
      {
        "source": "Measured",
        "apparent_power": 665.7619,
        "current": 2.8138,
        "energy": 3127,
        "energy_returned": 0,
        "frequency": 49.97,
        "power": 311.4685,
        "power_factor": 0.467838,
        "voltage": 0
      }
    ],
    "output1": {
      "enabled": true,
      "state": "ROUTING",
      "bypass": "off",
      "bypass_elapsed": 0,
      "temperature": 22.3125,
      "metrics": [
        {
          "source": "Computed",
          "apparent_power": 97.69642,
          "current": 0.425648,
          "energy": 0,
          "energy_returned": 0,
          "frequency": 0,
          "power": 40.5293,
          "power_factor": 0.414849,
          "voltage": 95.21781
        },
        {
          "source": "JSY-MK-194 Channel 1 (Serial2)",
          "time": 714773,
          "apparent_power": 410.267,
          "current": 1.7332,
          "energy": 3109,
          "energy_returned": 0,
          "frequency": 49.97,
          "power": 190.3639,
          "power_factor": 0.464,
          "voltage": 236.3958
        }
      ],
      "dimmer": {
        "type": "thyristor",
        "enabled": true,
        "online": true,
        "state": "on",
        "semi_period": 10000,
        "duty_cycle": 0.1721,
        "duty_cycle_mapped": 0.1721,
        "duty_cycle_fire": 0.3172,
        "duty_cycle_limit": 1,
        "duty_cycle_min": 0,
        "duty_cycle_max": 1,
        "harmonics": {
          "H1": 100,
          "H3": 2.982687,
          "H5": 24.94661,
          "H7": 13.33471,
          "H9": 5.45063,
          "H11": 11.82983,
          "H13": 4.234973,
          "H15": 5.677062,
          "H17": 7.272423,
          "H19": 0.80278,
          "H21": 5.286677
        },
        "power_lut": true,
        "pin": 25,
        "firing_delay": 6828,
        "firing_angle": 122
      },
      "relay": {
        "enabled": true,
        "state": "off",
        "switch_count": 0
      },
      "ds18": {
        "enabled": true,
        "model": "DS18B20",
        "address": 7757842149514961000,
        "elapsed": 7268,
        "expired": false,
        "temp": 22.3125,
        "time": 707730,
        "valid": true
      }
    },
    "output2": {
      "enabled": true,
      "state": "ROUTING",
      "bypass": "off",
      "bypass_elapsed": 0,
      "metrics": [
        {
          "source": "Computed",
          "apparent_power": 207.6706,
          "current": 0.904789,
          "energy": 0,
          "energy_returned": 0,
          "frequency": 0,
          "power": 117.3293,
          "power_factor": 0.564978,
          "voltage": 129.6759
        },
        {
          "source": "JSY-MK-194 Channel 2 (Serial2)",
          "time": 714773,
          "apparent_power": 255.4949,
          "current": 1.0806,
          "energy": 18,
          "energy_returned": 0,
          "frequency": 49.97,
          "power": 121.1046,
          "power_factor": 0.474,
          "voltage": 236.3958
        }
      ],
      "dimmer": {
        "type": "dfrobot",
        "enabled": true,
        "online": true,
        "state": "on",
        "semi_period": 10000,
        "duty_cycle": 0.3192,
        "duty_cycle_mapped": 0.3192,
        "duty_cycle_fire": 0.4071,
        "duty_cycle_limit": 1,
        "duty_cycle_min": 0,
        "duty_cycle_max": 1,
        "harmonics": {
          "H1": 100,
          "H3": 29.02619,
          "H5": 3.843567,
          "H7": 6.554513,
          "H9": 10.36374,
          "H11": 9.884538,
          "H13": 6.750285,
          "H15": 2.508954,
          "H17": 1.461062,
          "H19": 4.152003,
          "H21": 5.076555
        },
        "power_lut": true,
        "sku": "DFR0971_GP8403",
        "output": "0-10V",
        "i2c_address": 92,
        "channel": 1,
        "resolution": 12
      }
    }
  }
}

[reguiny]

Thank you for the time you have spent on my problem, I have found the reason I was getting strange readings, after installing MycilaJSYApp I was able to see one phase was showing negative values! I turned the ct round and the problem was solved.
The ct had been assembled incorrectly, as they were all installed in the same direction.