Discover the Future of Battery Testing with Me and the MegaCell Charger PRO

Поделиться
HTML-код
  • Опубликовано: 14 янв 2025

Комментарии • 6

  • @MACAVENTURES
    @MACAVENTURES Год назад

    Bravo, très belle aboutissement 👍

  • @wings2004
    @wings2004 Год назад

    It feels like the website is not fully working at the moment. I can only see the Pro and Pro Hobby and can't access any of the other pages. Also can't get to the documentation page for the Pro Hobby (I'm having some issues setting it up).

    • @thecelldoctor8890
      @thecelldoctor8890  Год назад +1

      Hi Jason, I am still working on the new website. It will be ready in a few days. Please check the videos I made about setting up the megacell monitor and about using the device in standalone mode.
      Here is also a link to the documentation of MCC PRO: deepcyclepower.com/downloads/TheMasterOverviewMCCPro.pdf

    • @wings2004
      @wings2004 Год назад

      @@thecelldoctor8890 this helps a lot! I couldn't figure out what anormal charged meant. Also weird thing happening right now where during a workflow max voltage set to 4.2v but the it switched to 1,073,692.75v. when I stopped the storage voltage which was set to 3.7v changed to 1,073,690.25v. I stopped before anything got too high in voltage but it started to reach over 4.20v. also the minimum voltage dropped to .17V. feels like a bug somewhere, I can't find where to reset these.

    • @thecelldoctor8890
      @thecelldoctor8890  Год назад

      Hi, there was an issue in the firmware setting the chemistry from megacell monitor. Check the documentation page on the product: deepcyclepower.com/product/lithium-ion-cell-testing-device-megacell-charger-pro-hobby/ .
      Scroll down to get the firmware file and enable OTA from menu config on the device then go to chargerip:8080/firmware . Login with default admin/admin and update the firmware.
      You can also reset the device to factory from the menu before this step to recover from the bad chemistry. Sorry for this issue, just found about it 2 days ago and fixed yesterday.
      I will make a video on Monday with the firmware update process and post it.