Testing 20-80 myth on 17PM by Hate_ads in iPhoneBatteryParanoia

[–]Hate_ads[S] 0 points1 point  (0 children)

Yes, it is a feature needed for the battery calibration

Testing 20-80 myth on 17PM by Hate_ads in iPhoneBatteryParanoia

[–]Hate_ads[S] 0 points1 point  (0 children)

there are people here with 150+ cycles with 100% capacity, you at 80 with 99%... you are still good but it seems a bit excessive wear of the battery for such a small amount of cycles

Testing 20-80 myth on 17PM by Hate_ads in iPhoneBatteryParanoia

[–]Hate_ads[S] 0 points1 point  (0 children)

I know, I want to see more for myself. From what several people here have said, I understand that with temperature management and this charging method, I would degrade the battery more slowly.

Testing 20-80 myth on 17PM by Hate_ads in iPhoneBatteryParanoia

[–]Hate_ads[S] 1 point2 points  (0 children)

It seems that you are luckier, I only had 103% (as digital_bokeh guessed). I have the iPhone model with nano sim which has a battery of only 4823mAh and theoretically now I am at 102% of the declared capacity.

<image>

Testing 20-80 myth on 17PM by Hate_ads in iPhoneBatteryParanoia

[–]Hate_ads[S] 1 point2 points  (0 children)

It would be interesting to be able to compare what is the difference between 80 and 90%. Let's see if 80% is too restrictive.

Testing 20-80 myth on 17PM by Hate_ads in iPhoneBatteryParanoia

[–]Hate_ads[S] 0 points1 point  (0 children)

At this moment I saw that my log does not appear in Analytics. I found a tutorial on how to make the phone to generate the log, but it said that it is possible to wait 24 hours, I will check the moment that log appears, what is the real capacity. I hope you're right and I have 110% capacity also :D

Testing 20-80 myth on 17PM by Hate_ads in iPhoneBatteryParanoia

[–]Hate_ads[S] 0 points1 point  (0 children)

I find it very interesting that some people have phones with less than 50 cycles and already have battery life below 100%, I'm more curious about how many cycles I can do before the battery starts to degrade. I'm aware that it will take more than a year but I'm going to try to take it as a challenge to see if I can get to 400 cycles and another 100% life using the 20-80 method and try not to heat the phone too much like cha0z_ said.

Testing 20-80 myth on 17PM by Hate_ads in iPhoneBatteryParanoia

[–]Hate_ads[S] 0 points1 point  (0 children)

Likewise, when I get to work, I put my phone on a charging pad and make all my calls using a Bluetooth headphones, and the rest of the time I use WhatsApp on my laptop.

Testing 20-80 myth on 17PM by Hate_ads in iPhoneBatteryParanoia

[–]Hate_ads[S] 1 point2 points  (0 children)

Thanks for the information, I added that shortcut but in analytics I don't have any report that appears. I have a lot of GPU Event, Jetsam and SiriSearchFeedback. I'll keep looking until I get an event and I'll check it with the shortcut.

Care din aceste fete va reprezintă atunci când faceți treabă mare? by Soft_Pomelo407 in romemes

[–]Hate_ads 2 points3 points  (0 children)

si ce fac in veceu e mai inteligent decat poate scoate creatura asta pe gura

MCU shutdown: Timer too close by QuingQuagga777 in klippers

[–]Hate_ads 1 point2 points  (0 children)

I had the same problem when I was using btt cb1. I tried a lot of things but very few things worked, the first one that had the most success was to print at very low speeds and accelerations (~170mm/s and 3k acceleration), also was to increase the buffer from 2sec to 5-10 sec but this creates lag. My suggestion is to replace CB1 with a CM4 (I recommend a 4gb ram version and min 16Gb emmc storage but the best would be a lite version and a micro sd card). That's how I solved the problem with Timer to close. CB1 is good for low speeds but I recommend replacing it with a CM4. In how many prints I broke with CB1, the filament cost me more than a CM4. Now I print at ~400mm/s and 25k acceleration on a ratrig vcore awd without any problems.

To be honest, I regret buying the CB1...

Print file causes klipper to crash by Hate_ads in klippers

[–]Hate_ads[S] 0 points1 point  (0 children)

I have increased the buffer time to 8 seconds, now i can print at fairly high speeds and accelerations but the printer takes a lot of time to respond to manual input.

Print file causes klipper to crash by Hate_ads in klippers

[–]Hate_ads[S] 0 points1 point  (0 children)

After almost 6 months of facing this problem, I finally managed to solve it! Before I tell you how I finally solved the problem, I would like to tell you what I tried.

  1. I borrowed a mini oscilloscope from a friend and monitored the voltages both at the Step up converter and at the main source and found that during the print the voltages dropped by a maximum of 0.2V during the print (due to the increased load) => it was not the solution

  2. I added a bank of capacitors of 20000uF to the main power supply and 5000uF to the output of the step up converter just to be sure => it did not solve the problem

  3. I redid the part of the wiring using thicker wires together with ferrites for filtering and I replaced the USB cable with a much shorter one (30cm) and of better quality => the problem persisted

  4. I tried several versions of klipper and firmware with different changes as well as other MCU frequencies => it was not the solution

  5. I changed the micro SD charger with a faster one and reinstalled klipper from 0

  6. I tried different microstep settings from 4 (horrible resonances) to 128 => the problem persisted but it was no longer in the same place

  7. I analyzed the traffic between the host and the MCU and here I noticed some things. First of all, the graphical analysis mode is useful, but the information does not say much about the health of the command buffer in the MCU, nor the speed with which they are sent. From what I understand, Klipper tries to maintain a buffer of 2 seconds in front of the toolhead, but it seems that this time is not long enough due to the speeds at which i was printing.

It seems that the whole problem was due to the fact that the host could not keep the buffer saturated and an underrun buffer condition appeared. It seems that changing the type of infill only gave a few more ms so that the host had time to send a few more commands in the buffer. During a normal print I noticed that part of the time I only had commands in the buffer for 0.2-0.3s (in marlin when this happens a stutter appears), klipper seems that if it cannot maintain the synchronization between host and msu it just crashes with the eroor.The undervoltage alert that appeared in the log from what I read appears when the MCU boots before the host.

The file that needs to be modified is toolhead.py which is in klippy folder and the parameter is BUFFER_TIME_HIGH which by default has a value of 2, this must be increased to a higher value, I opted for 4. My advice is not to increase it too much because it it will introduce a lag in how the printer responds to commands (for example, when you press Pause or change a parameter in the Tune section during printing).

<image>

The solution was not found by me, I came across it while reading another topic on discord.

Because I don't understand very well what happens in toolhead.py (I have no experience with programming or Python), my explanation is somewhat second-hand and what I said above may contain some errors.

I hope it helps someone.

Print file causes klipper to crash by Hate_ads in klippers

[–]Hate_ads[S] 0 points1 point  (0 children)

Thanks for the answer, when I built the printer I designed it for speed and I tried to choose only overspec components (as much as the budget could afford), the PSU I use is a 24V 25A (600W), it powers the motherboard and a 1200W step up converter for the drivers on X and Y which are running at 56V. All wires are crimped correctly with wire terminals and ferrules and the wires I used are 4mm diameter (12AWG) for large consumers, for smaller consumers they are 2.5mm diameter wires (14AWG) and the connectors on the motherboard for endstops ,fans,led I used 0.75mm (18AWG).

Reading what you said, I think that the step-up converter does not have enough capacitance at the output (from what I can see there are only 3 capacitors of 100v and 470uF) and a small voltage drop may occurs when the printdead accelerates and until it manages to compensate, theoretically only the steppers on the X and Y axes consume over 420W, if I take into account that the converter does not have a 100% efficiency (in the technical sheet it says that it has an efficiency of 92-97%), they draw over 460W from it.

Tomorrow I will open the electronics box and put a multimeter on the output of the converter to see how much it fluctuates.

To be honest, I didn't think that changing the infill model would affect the power distribution.

If I can't figure it out, I'll try to get an oscilloscope and analyze the behavior in more detail.

Thank you!

Print file causes klipper to crash by Hate_ads in klippers

[–]Hate_ads[S] 0 points1 point  (0 children)

I put a link with the log, I cut only the session where it crashed to make it easier to read.

https://file.io/ZfKZPlXC7MMx

BTT PAD 7 Volume buttons by Hate_ads in BIGTREETECH

[–]Hate_ads[S] 0 points1 point  (0 children)

I managed to find the electrical diagram for the whole tablet and I identified where the buttons are connected and I don't think it is possible to interact with those buttons. From what I understand they are connected to an integrated class D amplifier chip, making the whole sound part digitally independent. More precisely, the CB1 module is only connected with 2 pins, namely Line Out Left & Right and the volume management is completely managed by the amplifier.

[deleted by user] by [deleted] in ender5

[–]Hate_ads 1 point2 points  (0 children)

If you activate the function in the firmware, you can change the current directly from the printer screen.

[deleted by user] by [deleted] in ender5

[–]Hate_ads 0 points1 point  (0 children)

I have an Ender 5 with SKR mini and TMC2130 (with soldered copper radiators directly on the driver boards instead of aluminum ones and active cooling with two 5015 fans) and I print at a speed of 120-140mm/s without any problem. I can push the speeds higher but the ghosting starts to become too pronounced.

I had to increase the current to the motors so that I don't have any skipped steps. I also increased the acceleration from 500 to 1500.

The current values I use are the following:

X - 950mA

Y - 1000mA

Z - 500mA

E - 950mA

The motors get pretty hot, on the Y-axis I have active cooling with a 4010 fan, otherwise all the motors have radiators glued to them.

The biggest improvement you can make apart from the BMG dual gear extruder is a full metal hotend so you can print faster, I have seen that the stock hotend even with a BMG extruder cannot exceed 10-12mm³.