# UserAction

UserName: marios angelis
Description:
  MinimumSoC: 20, GridSetPoint: 0, CalibrationChargeState: RepetitivelyEvery, CalibrationChargeDate: 06/16/2024 10:00:21


UserName: InnovEnergy Master Admin
Description:
  MinimumSoC: 20, GridSetPoint: 0, CalibrationChargeState: RepetitivelyEvery, CalibrationChargeDate: 06/15/2024 10:00:24


UserName: InnovEnergy Master Admin
Description:
  MinimumSoC: 20, GridSetPoint: 0, CalibrationChargeState: RepetitivelyEvery, CalibrationChargeDate: 06/22/2024 10:00:13


UserName: Atef Sarraj
Description:
  MinimumSoC: 20, GridSetPoint: 0, CalibrationChargeState: ChargePermanently, CalibrationChargeDate: 04/10/2024 15:40:00


UserName: Atef Sarraj
Description:
  MinimumSoC: 20, GridSetPoint: 0, CalibrationChargeState: RepetitivelyEvery, CalibrationChargeDate: 06/29/2024 10:00:13


UserName: Max Ursin
Description:
  To do Freitag 28.06.2024
  * Inseltest
  * Widerstand zw. DC1 und DC- prüfen ob gut in der Klemme
  * Überspannungsschutz installieren
  * Dokumente ausdrucken, Ordner machen


UserName: Peter Spietz
Description:
  system ready for testing: all devices configured, Salimax SW installed, services started and enabled (salimax and battery), 24VDC power supplies adjusted, PV connected, AMPT ethernet connected, ext EMU connected (Hausanschluss, not simulated HAK, prototype connected to HAK-EMU, up and running in parallel), front end functional. System up and running. Kill switch successfully tested, restart from battery successfully tested (1x), restart from grid successfully tested (1x). 
  ==> Ready for testing.
  Ready, steady, go! :-), ps


UserName: Atef Sarraj
Description:
  After testing on Steakhouse installation, We update the new Dc Link Voltage window in Island Mode on config.json:
  AcDc:
            
  Max : 930
            Ref : 750
            Min : 670
  DcDc:
            Max : 800
            Ref : 750
            Min : 700
  This is applied in All installations. 


UserName: Atef Sarraj
Description:
  After testing on Steakhouse installation, We update the new Dc Link Voltage window in Island Mode on config.json:
  AcDc:

            Max : 930
            Ref : 750
            Min : 670
  DcDc:
            Max : 800
            Ref : 750
            Min : 700
  This is applied in All installations. 


UserName: Atef Sarraj
Description:
  After testing on Steakhouse installation, We update the new Dc Link Voltage window in Island Mode on config.json:
  AcDc:
            Max : 930
            Ref : 750
            Min : 670
  DcDc:
            Max : 800
            Ref : 750
            Min : 700
  This is applied in All installations. 


UserName: Atef Sarraj
Description:
  We update the new Dc Link Voltage window in Island Mode on config.json:
  AcDc:
            Max : 930
            Ref : 750
            Min : 670
  DcDc:
            Max : 800
            Ref : 750
            Min : 700
  This is applied in All installations. 


UserName: Peter Spietz
Description:
  Preparing system for test, modifications in config-file: applied new DCLink voltage window settings for island mode (grid tied unchanged):
  AC3025:  690 / 750 / 930V
  DC1010: 700 / 750 / 790V
  MaxBattCharingCurrent 210
  MaxBattDischaringCurrent 210

  Tested various scenarios: 
  no PV, 3kW motor (Heubelüftung) connected to AC_island: 
  a) switching motor on and off several times in island mode: passed.
  b) Transition from island to grid tied and back to island while motor is running: 3 sequences tested: passed.
  Interuption island=> grid ca 5 sec, interuption grid=>island 10...15sec.
  c) the same as b), but with PV: passed.
  d) replaced motor by DC-load on AC_island, PV on, tested several transitions island <=> grid at several levels of load distributed over the 3 phases, up to 44,7kW total: passed.
  e) same as d), but PV off: on low to moderate levels of load: passed. At 35kW load and island mode voltage and frequency on AC_island begin to drop (AC3025 acts as virtual synchronous machine!) Voltage as low as 209V, frequency down to 48Hz.
  General result: tests passed successfully.


UserName: Peter Spietz
Description:
  1) RCMA (FI) moved from AC_island branch to inverter branch. To this end introduced additional Weidmüller 120mm² terminal blocks as branching point for "Y"-shaped cabling: Powerbar <-> K2 <-> AC_island, all three connected at terminal blocks. RCMA(FI) on branch between Powerbar and terminal blocks ("inverter branch").
  2) added wiring for separate test button for RCMA(FI), mounted accessible at front, next to RCMA(FI) relais (106K4).
  3) prepared for mounting additional DC breaker for incoming PV
  4) added surge protection, connected to DC-Link Cu bars

  After these modifications performed a limited functional test with motor with and without PV. Several transitions from grid parallel to island and back. Passed.
  In island as well as grid tied mode: motor switched on and off several times. Passed.
  No problems with inrush currents.
  Measurement: in island, without PV, DC-Link voltage drops from 750V to 725V, when motor starts (inrush current).


UserName: Peter Spietz
Description:
  IBN/Commissioning at Enggistein, customer Thomas Tschirren:
  Peter, Nico, Atef (remote), Hans Moser (distrib. partner)

  190kW PV installed, 18 AMPTs, distributed over 3 GAKs. Planned concept: GAKs 1 and 2 meant to be passed through one KACO each. GAK3 to be connected to DC-Link Salimax.
  Presently 20kW export limit due to weak grid connection. BKW promised improved grid for September, postponed now to March 2025. Innov promised to provide curtailing via AC3025, enabling connection of all 3 GAKs to DC-Link to use full PV at weak insolation. At high insolation maintain export limit of 20kW. AC3025 should solve the curtailing for all 3 GAKs.
  Problem: Simple AC3025 "reprogramming" is not possible. 
  ==> More complicated solution is required. For now only a brute force work around could be implemented. Difficult, as AMPT characteristic curve is very steep due to the extremely high PV power installed.
  In GAKs fuses were missing. 15A were available. According to AMPT current is somewhere between 13 and 14A. Very close. After discussion between Hans, Nico and Peter decided to use the 15A, which were available and keep an eye on them. If necessary, replace them by 20A.
  ==> clarify with AMPT, what is their recommendation.

  IBN as such:
  1) Checked all installation work in Salimax, which had been done by Hans. All connections correct.
  2) Hans and Thomas T. made cut-outs left side panel of Control cabinet.
  3) polarity of PV cabling checked: correct. Connected GAKs 1 and 2 directly to DC-Link. Connected GAK 3 via DC-switch in Salimax (see modification before final test and shipment).
  4) Connected signal wires from aux contact NA-Schutz. Initially problem on customer's installation Corrected by Hans.
  5) connected external EMU, configured external EMU. Ratio 300:5. External EMU is powered from the customer's electrical cabinet. Not from Salimax.
  6) LAN connected to Salimax
  7) IPC powered with separate power supply from external wall plug (Salimax still off) ==> Atef could access the IPC even though Exsys switch was not powered. Atef updated software and config file.
  8) switched off IPC, reconnected to Salimax internal power supply.
  9) switched on NA-Schutz, switched on AC_grid, unlocked kill switch and used start button ==> Salimax started. After correcting signal cabling from NA-Schutz (see above) Salimax went properly into grid tied mode (before due to missing contact on signal line remained in island mode, K2 open) and began heating batteries.

  Identified problems:
  a) Loose contact on 24VDC supply of system control AC3025 ==> caused interruption in heating. Salimax did not recover. Needed restart of services to get back into heating.
  ==> identified SW problem, combination of errors. "Precharge condition not met" on DC1010. To be clarified between Atef and Peter. 
  checked this by provoking the same error, by deliberately disconnecting 24VDC at sysControl AC3025. confirmed.
  Checked the same with PV connected to DC-Link: no problem. PV maintaied DC-Link active,no error Problem occurs only, if no PV present.
  ==> keep in mind, when having an IBN at bad wheather (until SW is corrected)...
  b) Labeling of PoE injector needs clarification. Possibly wrongly connected Required retracing of cabling to get it right and working.
  c) further test: during heating opened NA-Schutz (PV on or off? ==> check in S3 data, most likely on, as system continued heating). System went properly in to island. But simultaneously to opening of K1 (NA-Schutz) there occurred a hard "bang". FI-LS 105F4 blown out. EMU since then electrically dead, even though power is present at the EMU's terminals (with FI-LS switched on gain). Reason for this damage unclear.

  software: Brute force workaround for export limitation appears to work. Tested this roughly by switching on AC-loads of roughly 8kW, while monitoring PV input and exported power. Atef trimmed setting of upper limit of DC-Link voltage window AC3025 such that export never exceeds 20kW. Very coarse, because of steep AMPT characteristic curve.


UserName: Atef Sarraj
Description:
  I am testing the curtailing algorithm. different limit of export.
  From 16:35 I put 5Kw maximum export with deadband of 2 kw. To monitor this. S3 data may be not available before 16:33. 


UserName: Atef Sarraj
Description:
  Deploying the new software version on the IPC, made some problem. The software was off for two minutes. Fixed now.


UserName: Atef Sarraj
Description:
  Test new curtailing algorithm with safety changes. Entrance point of algorithm should be an export bigger than export limit. Otherwise the algorithm will not kick off, A point to optimise .


UserName: Atef Sarraj
Description:
  I am testing a Build/deploy method. I am building/deploying with this  parameters
         -p:PublishTrimmed=false \
         -c Release \
         -r linux-x64 


UserName: Atef Sarraj
Description:
  After 12 hours monitoring: We have to adapt the step size to the difference between the export limit and the active export. to be faster. We will also add an AC load graph.


UserName: Peter Spietz
Description:
  Observation: at 12th of Aug. 10:33 communication with AMPT CU lost. since then no communication with AMPT CU. Shortly after that at ca 12:53 export of 50kW, even though limitation to 20kW should be implemented. Algorithm failed.


UserName: Peter Spietz
Description:
  On 13th of Aug. frequent oscillations in grid power between export at >50kW and import. journalctl shows that K1-NA-Schutz opens due to overvoltage on the grid caused by our excessive export, followed by reconnect followed by again excessive export and subsequent opening of NA-Schutz and so on. ==> export limitation does not work. ==> clarified with Hans Moser: He talks to Thomas Tschirren that GAKs 2 and 3 are to be disconnected to reduce installed PV. 498 panels in total installed. Exactly 1/3, i.e 166 panels per GAK. ==> installed power must be reduced in config file as soon as GAKs 2 and 3 are switched off.


UserName: Peter Spietz
Description:
  Thomas Tschirren disconnected GAKs 2 and 3. This reduces installed PV from 189kW to 63kW ==> I changed the entry in the config.json from 180 to 63 (note: entry was 180kW and not 189kW, as it should be). restarted salimax with ./restart.


UserName: Peter Spietz
Description:
  After short consultation with Atef: changed config file back to 180kW max installed power, even though only 63kW are connected. Maintained 20kW export limit. Check tomorrow for the effect.


UserName: Peter Spietz
Description:
  This afternoon reset the value for max installed PV-power to zero to deactivate curtailing. Reason: Curtailing was still active as test (by Atef), but DC-link voltage is pushed up by this. ==> creates problem with DCDC charging station, which is incompatibel with voltage >800V(tbc). INCONSISTENCY between components of our planned DC system kit! NEEDS TO BE RESOLVED!! Open issue.


UserName: Peter Spietz
Description:
  on site, switched off system around 8:30 this morning. Doing re-wiring for new position of RCM/FI, DC-switch for PV, test button for RCM/FI. Also Schraubenkontrolle Aeschimann. Restarted system around 16:00. System is presently heating  (ca. 1800). AMPT communicates unreliably. Around 17:45 system stopped heaqting, batteries went off again, then re-initialised. Batt-Bus voltage must have gone to zero for some seconds. No switching heared, no disconnection of relays, only heater sound of DC1010 reduced for some seconds and switching off/on of batteries was heared. Strange ==> software issue?


UserName: Yinyin
Description:
  update process stopped at import Pika and ssh failed since the connection is very slow, /dev/root 94% usage


UserName: Yinyin
Description:
  currently get stuck in updating with large image even with remote console; only have normal image without node red


UserName: InnovEnergy Master Admin
Description:
  Cannot establish VPN connection
  Problem with connectivity. 
  The installation can ping the VPN server but it cannot establish a TLS connection


UserName: Peter Spietz
Description:
  >>Symptoms<<: Batteries cold (Daniel: for more than a week), WAGO fuse 201F3.1 (upper DC1010) in battery cabinet blown, LED solid red. Permanent short on 24VDC, not possible to switch on. PV and AC3025 working nominally (verified by monitor.innov.energy).  Upper DC1010 LED off, lower DC1010 LED green. Syscontrol LED red.  ==> 48VDC went dead and batteries went cold.  >>Steps taken<<: Restarted Syscontrol (WAGO 205F4 off and on again) ==> syscoontrol recognised remaining (lower) DC1010 ==> syscontrol and DC1010 went to LED green, should be operating, but no reaction on 48VDC. web interface DC1010showed 3.xxVDC, fluctuating. Left system like that for the time being...


UserName: Peter Spietz
Description:
  >>strange behaviour<<: Salimax clearly tried to heat the batteries: charge limiting status alternated between "inactive" and "IChargeMax". Quite synchronous to that DC-link voltage always dropped from 755VDC down to ca. 720VDC for a moment and then recovered again. Indicates that each time, the DC1010 tried to start heating, IChargeMax status was activated, DC-link voltage dropped and then the operation failed again. >>suspicion<< there is a short on the 48VDC battery bus, possibly caused by the faulty DC1010 (upper). permanent switching cacles, bad for HW. ==> asked Toby to disconnect both zbenys for both DC1010. Left the system like that ... 


UserName: Peter Spietz
Description:
  >>strange behaviour<<: when checking the web interfaces again later that evening, Salimax was again in switching cycles, but this time trying to connect the DC1010 to the DClink ==> continued switching trying to precharge DC-link by DC1010 based on 24VDC, failed ==> error precharge condition not met ==> retry ...  not good.    ==> decided to stop Salimax service to keep system from endless switching cycles. Fan of DC1010 was at 1200 rpms, not going down (remained like that until at least next day). 


UserName: Peter Spietz
Description:
  Tobi and I (peter) brought system into safe state: switched off PV, switched off AC_in, waited for capacitors to discharge. Then Tobi disconnected faulty DC1010 from 48VDC battery bus by removing the melt fuse on +48VDC. WAGO 201F3.1 remained off. zbeny 201F3 switched off ==> faulty DC1010 isolated on all three sides. With 0V on DC-link the zbeny (201F6) for the nominal DC1010 (lower) could safely be switched on.   24VDC power supply in control cabinet connected to external power source (Frankensteinstecker).   >>restarted salimax<< by powering the 24VDC power supply. Salimax started nominally, no problems. Reconnected PV. Is now running with only one DC1010. No non-nominal behaviour.


UserName: Yinyin
Description:
  no permission to VRM but everything works, e.g. ssh, batteries, grid. No communication with monitor. No need to fix.


UserName: Yinyin
Description:
  this installation has renamed to Niederberger (oldSchwander), Reckholdern1 Baldegg/LU(2019-00043), still can't find battery


UserName: Yinyin
Description:
  everything works since it is back to fork version thus no communication with monitor. no need to work


UserName: Atef Sarraj
Description:
  Ntp server installed. This was missing and this was part of problem of the stuck data communicated. Problem not totally solved but improved.


UserName: Atef Sarraj
Description:
  After not reaching end of charge for 2/3 days. We found out one battery have a warning (TAM1) and this battery have EOC flag false even was 98.4 % for 2 days. Then, We had to remove this battery from the communication (from the config file). Then the EMS move automatically to Optimise self consumption. 


UserName: Peter Spietz
Description:
  Implemented ADAM6060 HW into prototype. Up to now only wiring for ADAM6060 had been prepared, but no ADAM6060 had been installed.


UserName: Peter Spietz
Description:
  Checked and corrected wiring for ADAM6060. Signal lines (S2 from WAGO) and control lines (S1 to WAGO) had been confused in the preinstalled Salimax wiring, unclear origin. Now corrected. 
  Settings for all WAGOs checked and corrected. Thresholds for current were all correct. but configuration for S2 needed o be corrected. Settings for S2 are now "tripped or manually switched off" (option 7). S2 will be on high, wenn WAGO is connected, and will be on low, when WAGO is open, no matter, whether tripped or manually switched off or switched off by S1-command.
  System is ready for SW testing.


