|
1502
|
tachyoo - a (fast) minecraft server by @hq2000 | S tachyoo - a (fast) minecraft server by @hq2000 | Stardance...
|
hq2000
|
0
|
49.27
|
0
|
[]
|
[{"post_id": 41396, "ts": "202 [{"post_id": 41396, "ts": "2026-08-05T16:14:16Z", "hours": 14.1728, "text": "I though I already made a devlog, but well… I needed to read my past commits to write this, so basically, I added more packets, created a packet viewer (wip, doesn’t really work) , a wasm plugin crate and tried to get it to communicate with the client. As of now, the login nearly works, I only need to reply to the cleint using the correct player profile info and session id. But, after looking at the logic, I (again) realize thinking about the architecture should be the top priority especially if you want to write a highly concurrent (and hopefully fast) minecraft server. This means I’m going to remove the old code and make a readable, maintainable and fun to work with protocol implementation (= config, status and login stages of the protocol). below is the stderr output of the server (yes, that’s my uuid)"}, {"post_id": 11789, "ts": "2026-06-19T05:51:58Z", "hours": 13.4533, "text": "“making it work”: I added a tokio (async runtime) task that gets spawned for each incoming connection and more parsing infrastructure, though I know have the fun to either write a “few” trait impls or mess with pseudo-variadics. below is a screenshot of the server output after receiving a handshake from the client"}, {"post_id": 8122, "ts": "2026-06-13T15:46:17Z", "hours": 10.2433, "text": "can’t believe it’s 10h again, I needed to look through my past commits to recount what I did, which turns out to be a quite mixed bag. I added a few types for server -> client transmission. trying to write them to a buffer first (because packets can be compressed), I realized I need to make the Transmission trait (/interface) sync and then write the packet to the tcp stream asynchronously…a dumb mistake, but rewriting existing code was easy using the search+replace functionality. I tried to get it to work (which json is pretty useful for), but didn’t finish it. thanks serde_json! aside from that, I added a server wip implementation using tokio, I think the design will for now just be having an asynchronous task for each connection which parses the packets and sends them as messages to the (ecs) minecraft world and the simulation send some messages back to the same task (or a separate one?). my next priority will be to have my server be recognized by the client (and making more frequent devlogs maybe). below a screenshot of some code (maybe next time something else?)"}, {"post_id": 2350, "ts": "2026-06-04T20:01:01Z", "hours": 10.0253, "text": "I’m still implementing the Data Types for server -> client transmission as well as the traits necessary (I changed them like 4 times, and some changes meant a reimplementation of existing impls). Now there is just a Transfer trait for types that are ready to transmit (≙ types that can easily write their transmission data to, e. g., a tcp stream or a buffer around one). The implementation now is supposed to be correct, but not necessarily the fastest / most memory efficient one, I will come back to do that later. I already implemented a majority of the data types, prominently lacking NBT (efficient binary data format), some JSON stuff (I guess) and a few small other things, I won’t do the debug data types until I need them. Below is a screenshot of the trait the code I wrote is centered around."}, {"post_id": 419, "ts": "2026-06-01T20:24:08Z", "hours": 1.3764, "text": "I’m currently trying to implement the Java Edition Server protocol, starting with the data types (like Boolean, VarInt, BitSet, Slot) and transfering them via tcp packets. I’m trying to make it type-safe via a Transferable trait (as seen below) that a few newtypes (respectively called VarInt, Boolean etc) which can be sent over will implement, so I can later just put some of these together for actually implementing the protocol without having to worry about the low-level details (= I can just do sth like send(stream, [VarInt(45), Byte]) ). I hope this accelerates the implementation."}]...
|
Title: tachyoo - a (fast) minecraft server by @hq2 Title: tachyoo - a (fast) minecraft server by @hq2000 | Stardance
Devlogs:
I’m currently trying to implement the Java Edition Server protocol, starting with the data types (like Boolean, VarInt, BitSet, Slot) and transfering them via tcp packets. I’m trying to make it type-safe via a Transferable trait (as seen below) that a few newtypes (respectively called VarInt, Boolean etc) which can be sent over will implement, so I can later just put some of these together for actually implementing the protocol without having to worry about the low-level details (= I can just do sth like send(stream, [VarInt(45), Byte]) ). I hope this accelerates the implementation.
I’m still implementing the Data Types for server -> client transmission as well as the traits necessary (I changed them like 4 times, and some changes meant a reimplementation of existing impls). Now there is just a Transfer trait for types that are ready to transmit (≙ types that can easily write their transmission data to, e. g., a tcp stream or a buffer around one). The implementation now is supposed to be correct, but not necessarily the fastest / most memory efficient one, I will come back to do that later. I already implemented a majority of the data types, prominently lacking NBT (efficient binary data format), some JSON stuff (I guess) and a few small other things, I won’t do the debug data types until I need them. Below is a screenshot of the trait the code I wrote is centered around.
can’t believe it’s 10h again, I needed to look through my past commits to recount what I did, which turns out to be a quite mixed bag. I added a few types for server -> client transmission. trying to write them to a buffer first (because packets can be compressed), I realized I need to make the Transmission trait (/interface) sync and then write the packet to the tcp stream asynchronously…a dumb mistake, but rewriting existing code was easy using the search+replace functionality. I tried to get it to work (which json is pretty useful for), but didn’t finish it. thanks serde_json! aside from that, I added a server wip implementation using tokio, I think the design will for now just be having an asynchronous task for each connection which parses the packets and sends them as messages to the (ecs) minecraft world and the simulation send some messages back to the same task (or a separate one?). my next priority will be to have my server be recognized by the client (and making more frequent devlogs maybe). below a screenshot of some code (maybe next time something else?)
“making it work”: I added a tokio (async runtime) task that gets spawned for each incoming connection and more parsing infrastructure, though I know have the fun to either write a “few” trait impls or mess with pseudo-variadics. below is a screenshot of the server output after receiving a handshake from the client
I though I already made a devlog, but well… I needed to read my past commits to write this, so basically, I added more packets, created a packet viewer (wip, doesn’t really work) , a wasm plugin crate and tried to get it to communicate with the client. As of now, the login nearly works, I only need to reply to the cleint using the correct player profile info and session id. But, after looking at the logic, I (again) realize thinking about the architecture should be the top priority especially if you want to write a highly concurrent (and hopefully fast) minecraft server. This means I’m going to remove the old code and make a readable, maintainable and fun to work with protocol implementation (= config, status and login stages of the protocol). below is the stderr output of the server (yes, that’s my uuid)...
|
1792727628.5528948
|
1793332428.5528948
|
|
1507
|
Sub 100 Wh portable power station by @win7 | Stard Sub 100 Wh portable power station by @win7 | Stardance...
|
win7
|
0
|
232.03
|
0
|
[]
|
[{"post_id": 81818, "ts": "202 [{"post_id": 81818, "ts": "2026-10-22T16:59:23Z", "hours": 0.6336, "text": "Finally replaced the MDP1933 MOSFETs with beefier IRFB4110 MOSFETs, but boy was it expensive! Whenever we replace blown MOSFETs, its a good practice to replace the entire array even if one MOSFET is blown and the others work perfectly fine since you never know if the voltage spike or whatever calamity had partially destroyed it (it would fail to close properly, dropping a lot of voltage) Atleast the inverter’s been fixed now (or is it..?) and outputs a clean 230 V RMS. Tested with a 20 W lamp and it works well. Need to replace the 35 A automotive fuse on it as well since it was also blown due to the direct short that occurred, I’m using a piece of solder wire as a temporary substitute (not recommended btw) Need to test with bigger loads to ensure that its back at business and nothing else was damaged due to the overload. Also worked on the Instructable for the past two days while waiting to get the MOSFETs."}, {"post_id": 81032, "ts": "2026-10-19T16:53:58Z", "hours": 0.4167, "text": "Switching to daily devlogs from now on.. Worked on the broken inverter. Tried replacing the MOSFETS with a different ones. The original ones were MDP1933, with a drain to source resistance of less than 5 milliohms, while the ones I replaced with were IRFZ44N and featured a drain to source resistance of 15 milliohms. I need to find a stronger MOSFET than the original MDP1933 used in the build and also upgrade my table’s sticker to gray :D"}, {"post_id": 80699, "ts": "2026-10-18T15:31:28Z", "hours": 9.7653, "text": "After a full 2-week fever, I’m back into business :D. Things aren’t great to start off. To sum it up, the inverter died after I connected a chineese steamer apparently rated for “120 W”, when in reality, it drew around 500 W from my wall. My inverter tried to maintain its voltage and ended up killing its MOSFETS. I really hope the MOSFETS are the only ones damaged."}, {"post_id": 73669, "ts": "2026-09-25T17:07:41Z", "hours": 7.9381, "text": "Had to tear the unit down, do plastic welding since the screw mounting slots broke. Probably I would rate this as a 0/10 in the reparability scale by myself -_-. Also, bypassed the 10 V regulator on the charger boost converter module and now it can work from 9V. Planned to add another separate boost converter for the inverter to prevent inverter’s low voltage protection from kicking in. Bypassed the regulator here as well. I feel kinda lazy and tired, probably will log more time from tomorrow,,"}, {"post_id": 71826, "ts": "2026-09-21T16:47:09Z", "hours": 9.3172, "text": "Had to harvest a boost converter from my old bench power supply, fix it (it was dead shorted due to an internally shorted capacitor) Planning on adding a pre-boost converter for the inverter and the charger functions. They refuse to work below 10.2 V, disregarding 20~30% of battery capacity. Recorded the voltage, current, milliamp hours, power drawn along with time stamps. Gosh, my hands are numb now -_-."}, {"post_id": 71159, "ts": "2026-09-20T11:30:16Z", "hours": 9.6525, "text": "Welp, killed another boost converter. This one failed by having its output voltage always equal to the input voltage no matter what, unlike previously where the boost converter failed as a direct short. Other than this, I spent a lot of time troubleshooting the charging MPPT function, which seemed to not have proper limit and tripped whatever charger I had connected it to. Had to change the values quite a bit but nothing helped. In the end I noticed that the initial_in_voltage variable was set to the absolute minimum trigger point whenever the charger was connected, therefore the condition where the (initial_in_voltage - in_voltage variable <= 0.2) inequation is always held true and therefore the Arduino ramped up the PWM no matter what, it took a ton of time to figure out -_- In addition to this, I had also spent a around 2h in testing the power station regarding its thermals and max. power capability.."}, {"post_id": 70210, "ts": "2026-09-18T18:28:05Z", "hours": 3.8333, "text": "Successfully completed the soft started board in order to prevent the inrush current drawn by the XL4016 module from tripping certain chargers. It felt endless, I had to use 2 NPN transistors in an inverter configuration in order to not use a PNP transistor since I did not have one lol. Also 3D printed and replaced the old battery case for a newer one which has ventilation holes, helping in keeping the battery temperatures low.."}, {"post_id": 70113, "ts": "2026-09-18T14:21:50Z", "hours": 7.6569, "text": "In the process of making the soft starter circuit for the XL4016 module, since the inrush current trips some chargers, I’m set on using a 555 timer chip in order to turn on a relay 2s after powering on the relay. Anyways, tested the bare-bones version of the power station at around 100 W and/or 10A of current and it worked beautifully, though I was scared to my core when doing so, not wanting this setup to blow up like last time which killed the boost converter and both the charger modules."}, {"post_id": 69616, "ts": "2026-09-17T12:56:32Z", "hours": 9.4322, "text": "Printed the left side panel, tried to print the bottom panel but failed, also the BOM list final is ready!! Well, seems like the assembly process is going to be hard due to a ton of wires and obstacles :( Had to trim the direct source connector panel twice for it to fit in the right side panel Boost converter module is held under really high amount of tension probably due to 10mm bolt and nuts. Made orientation and placement mistakes while installing the chargers panel -_-"}, {"post_id": 69073, "ts": "2026-09-16T10:15:00Z", "hours": 9.6933, "text": "Looked through the designs and measurements, edited them when necessary, tested the charging circuit, not sure why but it trips my MacBook’s PD 30 W charger but not my Samsung PD power bank, probably due to inrush currents. After a long conflict, finally printed the right side panel, need to proceed with the left, top, bottom and back panel as well. I don’t know, I’m scared to waste ~100g of filament and ~10h of time over a failed print just because of a dimensional mistake or inaccuracy, I’m just looking through the final model in Fusion 360 countless times,!"}, {"post_id": 68037, "ts": "2026-09-14T12:41:01Z", "hours": 9.7931, "text": "Birthday devlog today🎉! Did a ton more of CAD work, including modification of slots and sketches, and boy was it painful!. I had to re-draw each sketch on top and repeat this once again since I need one for negative extrusion and one for filling the already existing slots. All caused by my poor judgement of the dimensions of the other parts But here I am! Also, had tweaked the code a little, did some power wire replacements and stuff"}, {"post_id": 66828, "ts": "2026-09-12T18:50:31Z", "hours": 7.2039, "text": "Working on the mainboard mount. The mainboard is planned to be mounted on top of the battery pack. Not sure how I’m gonna figure out how to make mounting holes on the bottom panel. Its 12:20 AM rn, need to go to bed,,,"}, {"post_id": 66084, "ts": "2026-09-11T17:35:16Z", "hours": 8.3944, "text": "Probably a really messy workbench right now. Anyways, once again, did quite a bit of working, especially in CAD and 3D printing. Finally, I’ve hit 100% of the program storage space in my Arduino Nano when uploading my code. Need to optimize the code. Had to snap off the screw mounts and the bottom section of the button mount cover for it to fit, fixed it in the later version though. Also, spent 5 full minutes troubleshooting, opening the mainboard out of its case only to find out that nothing was connected (power button, navigation buttons, etc.). Probably, late night fatigue kicking in,,"}, {"post_id": 65290, "ts": "2026-09-10T10:13:56Z", "hours": 9.3603, "text": "Printed out the front panel, got a ton of work to do on the other panels. Thinking of whether or not to add a fuse in series to the direct source connector.. I feel like fitting all of these components into their designated space might be a very tedious task. Its just a pain to measure and ensure everything is in its own designated region and every part seats in properly, and also, found a mini bug, which is to be fixed in the code,,"}, {"post_id": 64192, "ts": "2026-09-08T12:47:58Z", "hours": 7.145, "text": "Printed and assembled the chargers part And also, I’m in the middle of designing the right side panel, gonna take up a ton of time as I’m using hit and trial method"}, {"post_id": 63471, "ts": "2026-09-07T10:49:09Z", "hours": 8.2628, "text": "Completed the modelling part of the inverter case, charger panel and probably also the front panel. Did some minor bug tweaks in the code Also finished cutting the copper sheet for the inverter module"}, {"post_id": 62681, "ts": "2026-09-06T05:13:52Z", "hours": 9.9372, "text": "TERRIBLE NEWS: I lost 3D models of the main front panel, the inverter case AND the chargers panel to a power outage. I know I should’ve saved it but I either complete it and save it or just have them lying in my RAM overnight till it finishes and that power outages are rare for me, but here I am! Completed the bench power supply part, printed the front side in orange and screwed it on the gray bench power supply mount since I’m planning to use orange on gray as opposed to gray on orange. Also added an extra master XT60 connector for direct battery access connections."}, {"post_id": 62043, "ts": "2026-09-05T08:16:17Z", "hours": 5.7331, "text": "Officially over the 100h mark! 🎉 Designed the front plate of the chargers, designed a stencil to drill through the copper sheet that acts as a small ‘heatsoak’, soldered some cables and much more"}, {"post_id": 61095, "ts": "2026-09-03T20:18:00Z", "hours": 9.33, "text": "Did quite a bit of various work today, but the one that made me glad is the successfull printing of the bench power supply part after 5 devastating failed attempts. Designed the case in Fusion 360 Worked on the header connections Worked on the bench power supply part"}, {"post_id": 60231, "ts": "2026-09-02T13:52:59Z", "hours": 8.4903, "text": "Completed the case for the inverter part, switched to digital operation of the fan instead of analog due to never ending problems."}, {"post_id": 58861, "ts": "2026-08-31T13:16:28Z", "hours": 7.7978, "text": "Completed the addition fan and LED interface to the mainboard. I had to add a separate boost converter to the setup. Still the addition of fan causes fluctuation in time to empty readings, need to fix them in code,,"}, {"post_id": 57981, "ts": "2026-08-30T09:57:15Z", "hours": 9.0681, "text": "Finally completed the haptics part, there are still some areas that do not work like intended, but I cannot really do much about it. Designed as well as printed cases for the main board and batteries for enhanced safety. My streak has not extended for today despite 3h of work today.,"}, {"post_id": 56720, "ts": "2026-08-28T16:15:26Z", "hours": 8.8742, "text": "Worked on the haptics for quite a while, still need to add haptic feedback/notification for other messages displayed on the screen, though it is SOO BUGGY! I had to work on it for 3 full days, yet I still feel like the haptic patterns were inconsistent, gotta do more fixing tomorrow, or probably I might focus into something else for a while."}, {"post_id": 54409, "ts": "2026-08-25T12:36:45Z", "hours": 5.1358, "text": "Messed up and messed around using millis(), need more time to debug and fix it (I’m not an expert when it comes to dealing with millis(), open to suggestions), I don’t want to use delay() since it interferes with my mAh measurement in the code. Did a weird contraption of a capacitor, polarity protector diode on a perf board in order to act as a power distribution board since the boost converter had only 1 screw terminal.."}, {"post_id": 53145, "ts": "2026-08-23T16:06:15Z", "hours": 4.215, "text": "I have planned to integrate haptics to the power station too, though traditional ERMs felt too cheap and unreliable, therefore I made something called the “Haptic block”, an LRA (Linear Resonance Actuator)-based haptic actuator, similar to the ones found in flagship smartphones (I’m looking at you, iPhone 6S!). Used a 12V, 6N solenoid along with a MOSFET, resistor and a flyback diode for switching the solenoid with the Arduino board. It works great, started with the coding process, the timings have to be perfect, else, it feels like metal and plastic colliding (though that’s exactly what’s happening XD). With perfect timing though, it enhances the user experience by a lot!"}, {"post_id": 52310, "ts": "2026-08-22T12:55:48Z", "hours": 5.5439, "text": "Took quite a while to try various methods, debug, fix, etc. the MPPT charging. Finally, a transistor pulling the floating 100mV to ground along with an RC filter seems to work, works for now, though not the best way of doing this. (Literally screamed in joy when it finally worked lol :D)"}, {"post_id": 51662, "ts": "2026-08-21T13:48:01Z", "hours": 9.6022, "text": "A week’s worth of devlog, probably I’m gonna switch over to weekly devlogs cuz I’m a bit lazy. Anyways, once again, a ton of changes: First and foremost, replaced the charger modules and the boost converter (Boy was it expensive for me). Added ADS1115 ADC as I needed an extra analog pin for measuring input charging voltage, switched voltage, current and temperature measurement to there as well. Planning on adding 2 more temperature sensors, 1 for the battery and 1 for the charger modules. Working on charging part for now, gonna use MPPT. A mystery addition that I bet nobody can guess (its in the image btw), open to your guesses btw."}, {"post_id": 49024, "ts": "2026-08-17T16:46:02Z", "hours": 4.0364, "text": "A lot of changes and events. Spent almost an hour modifying/testing the charging lightning icon on top of the battery. Fixed the mAh counter Fixed the time to empty counter Edited the power value such that only positive values are shown Killed the boost converter and charger modules, still unsure what caused it but I suspect the boost converter overheating and then finally, a voltage spike killed the charger modules too. Any ideas/opinions are very helpful.."}, {"post_id": 46946, "ts": "2026-08-14T14:53:17Z", "hours": 2.3461, "text": "After 800 lines of code, I finally hit the 2kB RAM ceiling. Did some optimization work on the code. Had to take a backup of the flawless code, try new stuff, in split screen mode between 2 IDE screens"}, {"post_id": 46396, "ts": "2026-08-13T16:02:49Z", "hours": 2.4861, "text": "Completed the chargers part (mainly fixed the power measurement bugs). In addition to that, did the temperature controlled fan part for today, so far works perfectly."}, {"post_id": 45868, "ts": "2026-08-12T16:29:10Z", "hours": 4.4317, "text": "Finally completed the soft-latching power control part in the circuit. 2 Arduino nano(s) were k1lled during the process :*(. Used an N channel MOSFET at first in order to control power going to the Arduino, failed at it, switched to a relay (big mistake), driven by a transistor, finally got out, bought a P channel MOSFET, still driven by an NPN transistor, and in the end, it works flawlessly, gave me immense happiness watching it work flawlessly :D"}, {"post_id": 44056, "ts": "2026-08-09T16:02:34Z", "hours": 3.285, "text": "Did more soldering work, not the prettiest, has a ton of improvements to be made both on the hardware as well as the software side. So far, the charger and the inverter switching part works, need to add a transistor in between the system and the battery in order to turn it off completely when not in use.. Open to suggestions and improvements.."}, {"post_id": 42800, "ts": "2026-08-07T18:17:35Z", "hours": 3.3397, "text": "Burnt some midnight oil to disassemble the breadboard prototype and start with the actual circuitry, soldered a few components so far, yet there’s a lot more to do so, probably gonna take a month to complete -_-."}, {"post_id": 41956, "ts": "2026-08-06T14:15:24Z", "hours": 1.9422, "text": "Worked on the settings screen for a while. Added maximum power limit as well as basic RGB LED colour setting along with EEPROM memory to store the parameters"}, {"post_id": 40710, "ts": "2026-08-04T12:30:27Z", "hours": 1.1986, "text": "Completed drawing the sketch of the portable power station (sorry for the messy work, its the first sketch). Please let me know of any suggestions/improvements.."}, {"post_id": 38209, "ts": "2026-07-31T14:39:56Z", "hours": 1.9614, "text": "Did a lot of tidying and reposition work as well as addition of various controls toggles on and offs."}, {"post_id": 36412, "ts": "2026-07-28T14:57:38Z", "hours": 0.5439, "text": "Added 2 pages: Controls and Info, settings page is still pending.."}, {"post_id": 35897, "ts": "2026-07-27T16:59:50Z", "hours": 0.5722, "text": "Replaced the 20 A BMS with a 40 A one, in order to achieve the full 27 A capability"}, {"post_id": 21533, "ts": "2026-07-03T15:39:47Z", "hours": 0.7169, "text": "Started with the framework of the icons for turning the outputs on or off."}, {"post_id": 20828, "ts": "2026-07-02T15:07:41Z", "hours": 0.3336, "text": "Re-positioned the screen page indicator, fixed a bug that that was present since the start (fun fact: I thought that it was not possible to fix that till yesterday till I remembered “break” statement exists thanks to a dream I had last night using break statement to fix the same)"}, {"post_id": 20105, "ts": "2026-07-01T16:59:16Z", "hours": 0.3414, "text": "Added some adjustments, possibly also a framework of multiple screens."}, {"post_id": 19142, "ts": "2026-06-30T11:57:17Z", "hours": 1.2953, "text": "Completed the temperature reading, temperature warning, as well as temperature controlled fan pwm signal. Bugs: Temperature and PWM value fluctuate greatly when connecting an LED as a test for PWM regulation"}, {"post_id": 18287, "ts": "2026-06-29T12:00:09Z", "hours": 0.9761, "text": "Bare-bone version of the code is ready, works without any major bugs.. Next step: Continue coding of the remaining features and functions (Tested and verified on my trusty breadboard setup)"}]...
|
Title: Sub 100 Wh portable power station by @win7 Title: Sub 100 Wh portable power station by @win7 | Stardance
Devlogs:
Bare-bone version of the code is ready, works without any major bugs.. Next step: Continue coding of the remaining features and functions (Tested and verified on my trusty breadboard setup)
Completed the temperature reading, temperature warning, as well as temperature controlled fan pwm signal. Bugs: Temperature and PWM value fluctuate greatly when connecting an LED as a test for PWM regulation
Added some adjustments, possibly also a framework of multiple screens.
Re-positioned the screen page indicator, fixed a bug that that was present since the start (fun fact: I thought that it was not possible to fix that till yesterday till I remembered “break” statement exists thanks to a dream I had last night using break statement to fix the same)
Started with the framework of the icons for turning the outputs on or off.
Replaced the 20 A BMS with a 40 A one, in order to achieve the full 27 A capability
Added 2 pages: Controls and Info, settings page is still pending..
Did a lot of tidying and reposition work as well as addition of various controls toggles on and offs.
Completed drawing the sketch of the portable power station (sorry for the messy work, its the first sketch). Please let me know of any suggestions/improvements..
Worked on the settings screen for a while. Added maximum power limit as well as basic RGB LED colour setting along with EEPROM memory to store the parameters
Burnt some midnight oil to disassemble the breadboard prototype and start with the actual circuitry, soldered a few components so far, yet there’s a lot more to do so, probably gonna take a month to complete -_-.
Did more soldering work, not the prettiest, has a ton of improvements to be made both on the hardware as well as the software side. So far, the charger and the inverter switching part works, need to add a transistor in between the system and the battery in order to turn it off completely when not in use.. Open to suggestions and improvements..
Finally completed the soft-latching power control part in the circuit. 2 Arduino nano(s) were k1lled during the process :*(. Used an N channel MOSFET at first in order to control power going to the Arduino, failed at it, switched to a relay (big mistake), driven by a transistor, finally got out, bought a P channel MOSFET, still driven by an NPN transistor, and in the end, it works flawlessly, gave me immense happiness watching it work flawlessly :D
Completed the chargers part (mainly fixed the power measurement bugs). In addition to that, did the temperature controlled fan part for today, so far works perfectly.
After 800 lines of code, I finally hit the 2kB RAM ceiling. Did some optimization work on the code. Had to take a backup of the flawless code, try new stuff, in split screen mode between 2 IDE screens
A lot of changes and events. Spent almost an hour modifying/testing the charging lightning icon on top of the battery. Fixed the mAh counter Fixed the time to empty counter Edited the power value such that only positive values are shown Killed the boost converter and charger modules, still unsure what caused it but I suspect the boost converter overheating and then finally, a voltage spike killed the charger modules too. Any ideas/opinions are very helpful..
A week’s worth of devlog, probably I’m gonna switch over to weekly devlogs cuz I’m a bit lazy. Anyways, once again, a ton of changes: First and foremost, replaced the charger modules and the boost converter (Boy was it expensive for me). Added ADS1115 ADC as I needed an extra analog pin for measuring input charging voltage, switched voltage, current and temperature measurement to there as well. Planning on adding 2 more temperature sensors, 1 for the battery and 1 for the charger modules. Working on charging part for now, gonna use MPPT. A mystery addition that I bet nobody can guess (its in the image btw), open to your guesses btw.
Took quite a while to try various methods, debug, fix, etc. the MPPT charging. Finally, a transistor pulling the floating 100mV to ground along with an RC filter seems to work, works for now, though not the best way of doing this. (Literally screamed in joy when it finally worked lol :D)
I have planned to integrate haptics to the power station too, though traditional ERMs felt too cheap and unreliable, therefore I made something called the “Haptic block”, an LRA (Linear Resonance Actuator)-based haptic actuator, similar to the ones found in flagship smartphones (I’m looking at you, iPhone 6S!). Used a 12V, 6N solenoid along with a MOSFET, resistor and a flyback diode for switching the solenoid with the Arduino board. It works great, started with the coding process, the timings have to be perfect, else, it feels like metal and plastic colliding (though that’s exactly what’s happening XD). With perfect timing though, it enhances the user experience by a lot!
Messed up and messed around using millis(), need more time to debug and fix it (I’m not an expert when it comes to dealing with millis(), open to suggestions), I don’t want to use delay() since it interferes with my mAh measurement in the code. Did a weird contraption of a capacitor, polarity protector diode on a perf board in order to act as a power distribution board since the boost converter had only 1 screw terminal..
Worked on the haptics for quite a while, still need to add haptic feedback/notification for other messages displayed on the screen, though it is SOO BUGGY! I had to work on it for 3 full days, yet I still feel like the haptic patterns were inconsistent, gotta do more fixing tomorrow, or probably I might focus into something else for a while.
Finally completed the haptics part, there are still some areas that do not work like intended, but I cannot really do much about it. Designed as well as printed cases for the main board and batteries for enhanced safety. My streak has not extended for today despite 3h of work today.,
Completed the addition fan and LED interface to the mainboard. I had to add a separate boost converter to the setup. Still the addition of fan causes fluctuation in time to empty readings, need to fix them in code,,
Completed the case for the inverter part, switched to digital operation of the fan instead of analog due to never ending problems.
Did quite a bit of various work today, but the one that made me glad is the successfull printing of the bench power supply part after 5 devastating failed attempts. Designed the case in Fusion 360 Worked on the header connections Worked on the bench power supply part
Officially over the 100h mark! 🎉 Designed the front plate of the chargers, designed a stencil to drill through the copper sheet that acts as a small ‘heatsoak’, soldered some cables and much more
TERRIBLE NEWS: I lost 3D models of the main front panel, the inverter case AND the chargers panel to a power outage. I know I should’ve saved it but I either complete it and save it or just have them lying in my RAM overnight till it finishes and that power outages are rare for me, but here I am! Completed the bench power supply part, printed the front side in orange and screwed it on the gray bench power supply mount since I’m planning to use orange on gray as opposed to gray on orange. Also added an extra master XT60 connector for direct battery access connections.
Completed the modelling part of the inverter case, charger panel and probably also the front panel. Did some minor bug tweaks in the code Also finished cutting the copper sheet for the inverter module
Printed and assembled the chargers part And also, I’m in the middle of designing the right side panel, gonna take up a ton of time as I’m using hit and trial method
Printed out the front panel, got a ton of work to do on the other panels. Thinking of whether or not to add a fuse in series to the direct source connector.. I feel like fitting all of these components into their designated space might be a very tedious task. Its just a pain to measure and ensure everything is in its own designated region and every part seats in properly, and also, found a mini bug, which is to be fixed in the code,,
Probably a really messy workbench right now. Anyways, once again, did quite a bit of working, especially in CAD and 3D printing. Finally, I’ve hit 100% of the program storage space in my Arduino Nano when uploading my code. Need to optimize the code. Had to snap off the screw mounts and the bottom section of the button mount cover for it to fit, fixed it in the later version though. Also, spent 5 full minutes troubleshooting, opening the mainboard out of its case only to find out that nothing was connected (power button, navigation buttons, etc.). Probably, late night fatigue kicking in,,
Working on the mainboard mount. The mainboard is planned to be mounted on top of the battery pack. Not sure how I’m gonna figure out how to make mounting holes on the bottom panel. Its 12:20 AM rn, need to go to bed,,,
Birthday devlog today🎉! Did a ton more of CAD work, including modification of slots and sketches, and boy was it painful!. I had to re-draw each sketch on top and repeat this once again since I need one for negative extrusion and one for filling the already existing slots. All caused by my poor judgement of the dimensions of the other parts But here I am! Also, had tweaked the code a little, did some power wire replacements and stuff
Looked through the designs and measurements, edited them when necessary, tested the charging circuit, not sure why but it trips my MacBook’s PD 30 W charger but not my Samsung PD power bank, probably due to inrush currents. After a long conflict, finally printed the right side panel, need to proceed with the left, top, bottom and back panel as well. I don’t know, I’m scared to waste ~100g of filament and ~10h of time over a failed print just because of a dimensional mistake or inaccuracy, I’m just looking through the final model in Fusion 360 countless times,!
Printed the left side panel, tried to print the bottom panel but failed, also the BOM list final is ready!! Well, seems like the assembly process is going to be hard due to a ton of wires and obstacles :( Had to trim the direct source connector panel twice for it to fit in the right side panel Boost converter module is held under really high amount of tension probably due to 10mm bolt and nuts. Made orientation and placement mistakes while installing the chargers panel -_-
In the process of making the soft starter circuit for the XL4016 module, since the inrush current trips some chargers, I’m set on using a 555 timer chip in order to turn on a relay 2s after powering on the relay. Anyways, tested the bare-bones version of the power station at around 100 W and/or 10A of current and it worked beautifully, though I was scared to my core when doing so, not wanting this setup to blow up like last time which killed the boost converter and both the charger modules.
Successfully completed the soft started board in order to prevent the inrush current drawn by the XL4016 module from tripping certain chargers. It felt endless, I had to use 2 NPN transistors in an inverter configuration in order to not use a PNP transistor since I did not have one lol. Also 3D printed and replaced the old battery case for a newer one which has ventilation holes, helping in keeping the battery temperatures low..
Welp, killed another boost converter. This one failed by having its output voltage always equal to the input voltage no matter what, unlike previously where the boost converter failed as a direct short. Other than this, I spent a lot of time troubleshooting the charging MPPT function, which seemed to not have proper limit and tripped whatever charger I had connected it to. Had to change the values quite a bit but nothing helped. In the end I noticed that the initial_in_voltage variable was set to the absolute minimum trigger point whenever the charger was connected, therefore the condition where the (initial_in_voltage - in_voltage variable <= 0.2) inequation is always held true and therefore the Arduino ramped up the PWM no matter what, it took a ton of time to figure out -_- In addition to this, I had also spent a around 2h in testing the power station regarding its thermals and max. power capability..
Had to harvest a boost converter from my old bench power supply, fix it (it was dead shorted due to an internally shorted capacitor) Planning on adding a pre-boost converter for the inverter and the charger functions. They refuse to work below 10.2 V, disregarding 20~30% of battery capacity. Recorded the voltage, current, milliamp hours, power drawn along with time stamps. Gosh, my hands are numb now -_-.
Had to tear the unit down, do plastic welding since the screw mounting slots broke. Probably I would rate this as a 0/10 in the reparability scale by myself -_-. Also, bypassed the 10 V regulator on the charger boost converter module and now it can work from 9V. Planned to add another separate boost converter for the inverter to prevent inverter’s low voltage protection from kicking in. Bypassed the regulator here as well. I feel kinda lazy and tired, probably will log more time from tomorrow,,
After a full 2-week fever, I’m back into business :D. Things aren’t great to start off. To sum it up, the inverter died after I connected a chineese steamer apparently rated for “120 W”, when in reality, it drew around 500 W from my wall. My inverter tried to maintain its voltage and ended up killing its MOSFETS. I really hope the MOSFETS are the only ones damaged.
Switching to daily devlogs from now on.. Worked on the broken inverter. Tried replacing the MOSFETS with a different ones. The original ones were MDP1933, with a drain to source resistance of less than 5 milliohms, while the ones I replaced with were IRFZ44N and featured a drain to source resistance of 15 milliohms. I need to find a stronger MOSFET than the original MDP1933 used in the build and also upgrade my table’s sticker to gray :D
Finally replaced the MDP1933 MOSFETs with beefier IRFB4110 MOSFETs, but boy was it expensive! Whenever we replace blown MOSFETs, its a good practice to replace the entire array even if one MOSFET is blown and the others work perfectly fine since you never know if the voltage spike or whatever calamity had partially destroyed it (it would fail to close properly, dropping a lot of voltage) Atleast the inverter’s been fixed now (or is it..?) and outputs a clean 230 V RMS. Tested with a 20 W lamp and it works well. Need to replace the 35 A automotive fuse on it as well since it was also blown due to the direct short that occurred, I’m using a piece of solder wire as a temporary substitute (not recommended btw) Need to test with bigger loads to ensure that its back at business and nothing else was damaged due to the overload. Also worked on the Instructable for the past two days while waiting to get the MOSFETs....
|
1792702058.5845563
|
1793306858.5845563
|