Skip to content
View in the app

A better way to browse. Learn more.

Power Forum - Renewable Energy Discussion

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

PurePower

Members
  • Joined

  • Last visited

Everything posted by PurePower

  1. Some chargers have a built in RCD, if this is the case would you still need an upgraded RCD on your main board?
  2. They are the low voltage ones, max DC input voltage is 145v. See pic below. I tend to agree, haven't given me any issues, I purchased spare units thinking my current 2 would fail but they are still solid and going. I'm looking to upgrade as my PHEV needs charging and want to put install a decent charger.
  3. Price drop: R11k for all 4 Picture of the 2 currently in use.
  4. Hey all, I recently had a warranty replacement of a US3000C and received the US3000D module. Unfortunately the ICM software which was still working for me for years is now struggling to gather BMS data for my stack from the US3000D which is my new master unit. I was just wondering if anyone has an updated firmware for this unit? I have noticed the firmware console commands does not include all commands from previous generations. It does have the new charging voltages, etc as per the last firmware update for the US3000C. I also noticed it has board NF4.E3 which is different to some of my US3000C modules with board NF4.E2 I executed some familiar commands from the console. Some commands did not work, so it seems the firmware has not implemented previous commands. BatteryView v3.0.24/28/37 does not show scaned data even on its UI, only command line interaction worked to some degree. Not sure if there is a later version of BatteryView that caters for this US3000D. pylon_debug>info info @ Manufacturer : Pylon Device name : US3000D Board version : Board : NF4.E3 Main Soft version : B1.4.0.0 Soft version : V1.1 Boot version : V0.02 Comm version : V2.0 Release Date : 25-11-13 Barcode : (I removed my barcode for obvious reasons) Specification : 48V/74AH Cell Number : 15 Max Dischg Curr : -70000mA Max Charge Curr : 70000mA EPONPort rate : 1200 Console Port rate : 115200 Command completed successfully $$ pylon_debug>pwrsys pwrsys @ Recommend chg voltage : 52800 mV Recommend dsg voltage : 45000 mV Recommend chg current : 15000 mA Recommend dsg current : -37000 mA Command completed successfully $$ pylon_debug>pwr pwr @ ---------------------------- Power Voltage : 49823 mV B+B-.Volt : 49771 mV Current : -814 mA Temperature : 23500 mC Coulomb : 85 % Total Coulomb : 74000 mAH Max Voltage : 57600 mV Charge Times : 0 Basic Status : Dischg Discharge Sec. : 0 s Volt Status : Normal Current Status : Normal Tmpr. Status : Normal Coul. Status : Normal Soh. Status : Normal Heater Status : OFF Protect ENA : BOV BHV BLV BUV POV PHV PLV PUV CBOT CBHT CBLT CBUT DBOT DBHT DBLT DBUT POT PHT PLT PUT COC COC2 COCA DOCA DOC DOC2 SC Bat Volt Status : 0x4 BVNOR Bat Tmpr Status : 0x8 BTNOR Pwr Volt Status : 0x4 PVNOR Pwr Tmpr Status : 0x8 PTNOR Pwr Curr Status : 0x20 CNOR Pwr Base Status : 0x8 DSG Pwr Coul Status : 0x2 COULNOR Mos Tmpr Status : 0x1 MOSNOR Env Tmpr Status : 0x4 ENVNOR System Fault : 0x0 Cascade Status : 0x1 CascadeNOR ---------------------------- Command completed successfully $$ pylon_debug>bat bat @ Battery Volt Curr Tempr Base State Volt. State Curr. State DTemp. State CTemp. State SOC Coulomb BAL 0 3322 -1075 21300 Dischg Normal Normal Normal Normal 85% 63300 mAH N 1 3322 -1075 21300 Dischg Normal Normal Normal Normal 85% 63300 mAH N 2 3322 -1075 21300 Dischg Normal Normal Normal Normal 85% 63300 mAH N 3 3320 -1075 21300 Dischg Normal Normal Normal Normal 85% 63300 mAH N 4 3322 -1075 21300 Dischg Normal Normal Normal Normal 85% 63300 mAH N 5 3322 -1075 20500 Dischg Normal Normal Normal Normal 85% 63300 mAH N 6 3321 -1075 20500 Dischg Normal Normal Normal Normal 85% 63300 mAH N 7 3320 -1075 20500 Dischg Normal Normal Normal Normal 85% 63300 mAH N 8 3321 -1075 20500 Dischg Normal Normal Normal Normal 85% 63300 mAH N 9 3321 -1095 20500 Dischg Normal Normal Normal Normal 85% 63300 mAH N 10 3321 -1095 20800 Dischg Normal Normal Normal Normal 85% 63300 mAH N 11 3322 -1095 20800 Dischg Normal Normal Normal Normal 85% 63300 mAH N 12 3320 -1095 20800 Dischg Normal Normal Normal Normal 85% 63300 mAH N 13 3321 -1095 20800 Dischg Normal Normal Normal Normal 85% 63300 mAH N 14 3321 -1095 20800 Dischg Normal Normal Normal Normal 85% 63300 mAH N Command completed successfully $$ pylon_debug>soh soh @ Unknown command $$ pylon_debug>socd socd @ Unknown command $$ pylon_debug>getpwr getpwr @ getpwr $$ If anyone has more info on this US3000D module, latest firmware and the latest compatible BatteryView, please share. It will be highly appreciated by the community here.
  5. I do exactly the same. It would be really nice to have a way to query what your outstanding fees are and also just settle that amount every month. I dont need the 62.5 units per month, its accumulating now as I'm over 300 units and growing... lol
  6. Is there a way to determine your outstanding service fee?
  7. Certainly not. My Pylons US2000B, US2000C & US3000C's are hooked up on my old Axpert 5KVA inverters without any comms cables.
  8. Here you are... the latest I managed to find for both old and new chip. From the bin file for the new chip(v2.2), it just seems they refactored some code, so no major changes from v2.1. I noticed there is also support for UP5000 as well on these versions. US_C_stV2.9_NTV2.2Crc.zip
  9. There are 3 commands that you can try: socclr clear bq34z100 data flash and reload default value - socclr statc Clear statistic - statc datac Clear data - datac [event/history] The easiest would be to re-flash the firmware even if its the same version but ensure that the "Clear EEPROM" box is checked before clicking "Program"
  10. Hi all, Just purchased a new US3000C to add to my bank and it has the newer chipset with v2.2 firmware on it. Does anyone have this firmware file as I see the effekta link below only has v2.1 https://www.effekta.com/download/firmwareupdate-for-us2000c-3000c/
  11. i would recommend the FTDI chipset for those cables. Don't use a cheap cable, they are not reliable.
  12. I'm interested to know the difference as well. Any update here?
  13. Item: Axpert 4kw/5kva x 4(Various brands but all compatible, they are NOT the clones/knock offs) Age: from 2018 onwards, I did not purchase them all at the same time. Price: R22k for all 4 Payment Method Accepted: EFT, funds to be cleared before goods handed over. Condition: Good, all in working order Location: Jhb Reason: Upgrade Shipping: At the buyers cost and risk. Collection: Yes Warranty: None I have 4 x Axpert 4kw/5kva inverters. I currently only use 2 of them in parallel and 2 are backups. All are fully functional with the latest firmware from the Australian forum. They all have parallel cards in them and i have all the relevant cables required too. The 2 in use are paired up with my 10 x Pylontech battery bank. Looking to upgrade to a Sunsynk inverter. Any takers? Willing to accept R22000 for all 4. Please PM me.
  14. Thanks! Looks like v2.1 is for the 2000C/3000C using the newer chipset. Would be nice if Pylontech issued release notes...
  15. Identify the cells which are unbalanced with BatteryView then manually charge those cells(2 pouches make a cell) using a 3.7v charger with 1.5A max then add it back in. Assemble the battery again and test.
  16. Thank you @Tinbum, your guidance has worked.
  17. Batteries 8, 9 & 10 are the US2000B models and are at end of the pack...but after reading the manual again... you may be onto something. The below is from a US3000C manual: @Tinbum, you reckon if I shift the US2000B's into position 6, 7, & 8 then i should be good to go? Basically invert the order of batteries in the left cabinet and make the US3000C battery 9 and the US2000C battery 10... This actually makes sense now as the US2000B's only ever accommodated 8 in a single group... Lemme try this. PS: Note to self, don't commission new batteries into a pack at midnight!
  18. This looks like the correct thread to add my issue to. I too also have mixed Pylontech's in a single group but having issues when I recently added 2 more batteries to my existing pack of 8. I may have stumbled across a new issue. I had eight(batteries 3 - 10) in the pack but recently I have added two more batteries to my bank, totaling 10 modules now. Battery 1 and 2 are the latest additions. Below is a pic of them. Numbered from newest to oldest. Batteries 1 - 5 are the US3000C running the newer chipset and all have v1.8 firmware loaded. Battery 6 is a US3000C running the older chipset with v2.8 firmware. Battery 7 is a US2000C running v2.8 firmware. Batteries 8-10 are the US2000B's running v3.4 firmware. The manual always says that your newest battery should be the master which is how I have configured it but when you start the master(1) battery up(SW), it starts up each battery but when battery 9 is reached, it seems the BMS is not capable of dealing with more than 8 batteries in a single group even though the manual says that the C model battery can handle 16 batteries in a single group. All LED's on Battery 1 - 9 flashes and it attempts to restart each battery again. Battery 10 does not even start up. Unfortunately the battery pack does not start up and I can't even connect using BatteryView. I attempted to use Battery 6 as the master as it's using the older chipset, slaves starting then from 1 - 5 and continuing with 7 - 10. The same issue when reaching battery 9 as my previous point. I also then tried using Battery 6 again as the master but the order of the slaves are starting from 7 - 10 and continuing with 1 - 5. This seemed to have worked but can't connect to BatteryView for some reason still. Also this goes against having the newest battery higher up in the pack. At the moment I have disconnected Battery 1 and 2 like I had before so that I can continue to use my pack. This seems to be a firmware issue as I have double checked cabling and all is in order there. I even tried running Batteries 1 - 8 and there were no issues starting them up. This makes me believe that the firmware on the newer chipsets of the US3000C does not accommodate more than 8 batteries in a single group. I have emailed Pylontech and awaiting their response. Has anyone else experienced a similar issue?
  19. BatteryView HV 3.9 BatteryView 3.9.0 B1.2.zip
  20. Yeah, he needs to check whether he has the old or new chipset on the US3000C If OLD chip, then v2.8 is the latest firmware if NEW chip, then v1.8 is the latest firmware NT1.8+ST2.8.zip
  21. Yeah, you can upgrade straight to v1.8
  22. Board: NF4.E2 is the newer chipset and v1.8 is the latest available firmware for it. Use the tool and the zip file.
  23. New firmware for the C model range. Its an update to v1.8 for the new chip C models. NT1.8+ST2.8.zip
  24. You meant to say v1.8 is for the newer chipset Has anyone loaded v1.8? What has changed from v1.7?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.