home.social

#openems — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #openems, aggregated by home.social.

  1. Seit ich gestern unser #Fenecon System auf die Softwareversion 2026.4.1 aktualisiert habe, wird die Speicherentladung falsch geregelt. Es bleibt immer ein Netzbezug von 300 W übrig auch wenn der Speicher noch voll ist.
    Weiß jemand Abhilfe?
    #openEMS #fems #Photovoltaik #pvbuddies

  2. Seit ich gestern unser #Fenecon System auf die Softwareversion 2026.4.1 aktualisiert habe, wird die Speicherentladung falsch geregelt. Es bleibt immer ein Netzbezug von 300 W übrig auch wenn der Speicher noch voll ist.
    Weiß jemand Abhilfe?
    #openEMS #fems #Photovoltaik #pvbuddies

  3. Seit ich gestern unser #Fenecon System auf die Softwareversion 2026.4.1 aktualisiert habe, wird die Speicherentladung falsch geregelt. Es bleibt immer ein Netzbezug von 300 W übrig auch wenn der Speicher noch voll ist.
    Weiß jemand Abhilfe?
    #openEMS #fems #Photovoltaik #pvbuddies

  4. Seit ich gestern unser #Fenecon System auf die Softwareversion 2026.4.1 aktualisiert habe, wird die Speicherentladung falsch geregelt. Es bleibt immer ein Netzbezug von 300 W übrig auch wenn der Speicher noch voll ist.
    Weiß jemand Abhilfe?
    #openEMS #fems #Photovoltaik #pvbuddies

  5. More on #openEMS Windows porting: the legacy port is also a success, AppCSXCAD now runs on Windows 7 SP1 with Qt 6 and Mesa 25.3.3 software rendering.

  6. Implemented "Pull-Request Ganging" and "Branch Ganging" in in the #openEMS GitHub Actions CI. If you open pull requests against multiple repos, and all your open PRs use the same source branch name, they're tested together. If you push to a branch in one repo, and another dependent repo also has the same branch name, they're also tested together. In both cases warning messages are generated.

  7. More #openEMS Windows documentation. The importance of documenting everything. Yet another trap for young players. ​:woozy_baa:​

  8. More #openEMS Windows documentation. The importance of documenting everything. This time, it's a counterintuitive Visual Studio "feature" that nobody expected: deselecting vcpkg means also deselecting Ninja.

  9. More #openEMS Windows documentation. I doubt most developers can solve this Back To The Future problem, even if they know the root cause! The importance to document everything!

  10. More #openEMS Windows documentation. Qt 6 is truly a great stress test for Windows.

  11. More #openEMS Windows documentation. You know it's C++ when this happens.

  12. Back to #openEMS Windows development. The importance of documenting everything... ​:woozy_baa:​

  13. More on the #openEMS Win32 porting effort: Microsoft has download links for Visual Studio 2022 at aka.ms/vs/17, but no link for Visual Studio 2026. You only get aka.ms/vs/stable, if you use this in your documentation, all links are going to break 4 years later. ​:woozy_baa:​ Someone already reported it to Microsoft, but I'm not sure how many escalations it takes before Microsoft adds a link. https://developercommunity.visualstudio.com/t/Short-links-akams-for-VS-2026-install/11008785

  14. Success! I just (re-)ported the latest #openEMS git branch to Windows and MSVC in two days ​:woozy_windows:​, without any Windows knowledge, using only SSH without launching the Visual Studio IDE even once. Maintaining a MSVC port of a free software project is definitely much easier now in comparison to Steve Ballmer's days, thanks to community toolchain (CMake, Ninja), and Microsoft not being an obstructionist.

  15. Back to #openEMS build system maintenance: now working on creating a CI/CD pipeline for Windows after spending two hours installing Windows 11 and Visual Studio. ​:woozy_windows:​ At least Windows 11 now comes with an optional OpenSSH Server so I can use cmake, ninja and clang via PowerShell.

  16. Ich gehöre ja zu den priviligierten Menschen, die sich überlegen können, eine #Photovoltaik-Anlage auf das Dach zu stellen.

    Seit Kurzem beschäftige ich mich nun mit dem Thema und bin froh, dass ich auf #OpenEMS gestoßen bin, ein #FOSS Energie-Managementsystem. Das scheint meine Erwartungen mehr als zu erfüllen, so dass ich mal einen Dankesbeitrag im OpenEMS-Forum gelassen habe: community.openems.io/t/danke-o

  17. More full-wave SMA/3.5mm coax connector simulations... The previous simulation result reported a capacitance too low, until I realized the reference plane of an SMA socket is at the center pin, while an SMA plug's reference plane is at the coax body, behind the center pin. Both setups are not exchangeable, otherwise you'll miss a ~1 light-millimeter of time delay. #electronics #openEMS

  18. Simulating a coax cable in cylindrical coordinates has a funny problem. The mesh cell becomes progressively smaller in area or volume at you move closer to the singular origin, which is the region where the center conductor is located. So you spend an absolutely ridiculous amount of CPU cycles to calculate nothingness - there's no electric field inside a conductor ​:blobcatfacepalm:​ openEMS has a special "multigrid" mode to solve this problem. When it's enabled, it skips every other radial mesh line within the specified radius, and can be applied recursively too. #electronics #openEMS

  19. Finally got my new #openEMS simulation running after debugging it for days. #electronics

  20. /me Trying to understand how to run #openEMS full-wave simulations in cylindrical coordinates instead. #electronics

  21. Do you understand how #RF and #magnetics work? Any time I check out Sam Aldhaher's visualizations, I do just a bit better. We spoke on The Amp Hour this week about how to get started in #blender and build out visualizations using tools like #openems and #elmer_fem.

    theamphour.com/695-making-the-

    This episode was similar to the one I recorded with Katerina Galitskaya last year, who also does amazing visualizations. It's just SO useful to have people explaining RF with math and 3D models!

  22. #openEMS simulation of 0402 AC-coupling capacitor parasitics. On a 4-layer board, with 0.2 mm from signal layer to plane. Interestingly, the parasitic capacitance of the mounting pads and the parasitic inductance of the capacitor forms an accidental matching network and compensated each other in this stackup, making it usable even at 20 GHz! You can see similar results without a full-wave solver in lumped circuit simulators, by modeling the mounting pads as two short microstrips, and inserting an 0.1 - 0.2 nH ESL in series. But I won't trust this result unless I can borrow a 20 GHz VNA somewhere, since it's extremely sensitive to parasitic modeling. Also, the magical effect disappears for a better 0.1 mm dielectric, often preferred for lower loop area and lower crosstalks. #electronics

  23. Should you remove ground planes below SMD mounting pads to compensate for parasitics? Quick answer: on 4-layer boards (0.1 mm to plane), just use 0402 parts for sensitive signals. Even if you do nothing, my #openEMS simulation found the performance is great up to ~2 GHz (20 dB RL) and usable to ~8 GHz (10 dB RL). I'm going to improve the simulation and publish all details as a tutorial. #electronics

  24. I'm doing full-wave simulation of circuit parasitics around a 100 nF surface-mount AC coupling capacitor in #openEMS. The lumped capacitance itself is modeled as a 2D plane, so its parasitic inductance is obviously almost solely controlled by its mounting height - which I had trouble determining. I had to make an educated guess that a small 100 nF capacitor requires only a few layers, so its capacitance is concentrated at the center of the Z plane. It seemed to work, but I still wanted confirmations. I remembered @[email protected]'s book Open Circuits, and I found exactly what I needed. #electronics

  25. New toy day!!!

    My new GMKtec K8 plus arrived today 😁 It's small, but powerful. It's got 64GB DDR5-5600MHz ram, and a Ryzen 7 8845hs processor.

    Once I get a decent sized SSD in the thing, I'm planning on installing proxmox, and using it as a containerised development machine. Hopefully it'll run #openEMS simulations a bit faster than the 10 year old Dell Latitude in the corner of the room.

    #gmktec #nuc #ryzen

  26. Wrote more #openEMS documentation, now playing the role of the project historian. The little-known history on the endless attempts to make simulation easier, each time with the creation, abandoning, and recreation of third-party tools. #electronics

  27. Wrote more documentation for #openEMS. Lumped elements pitfalls. #electronics

  28. Still tweaking the #openEMS documentation. Physicists and engineers run out of variables be like... #electronics

  29. More #openEMS documentation. Spent two days trying to figure out why these formulas don't match textbooks, so you don't have to. ​:cirno_hi:​ #electronics

  30. More #openEMS documentation work: I was trying to derive the equation in the project wiki using the source code, but the SageMath output doesn't make any sense... The units in the original wiki page were completely mixed up. ​:blobcatfacepalm:​ Some f in the equations are ordinary frequencies, some are angular frequencies... ​:woozy_baa:​