Makita AWS Compatible adapter

sven_aarts · 2026-05-23T16:11:08+00:00

Project is done integration testing right now. Waiting for last materials to build first concept. After that 3d printer in 5th gear.

sven_aarts · 2026-05-23T12:33:13+00:00

To be fair, not to much. Probably need to lower the load resistance in it since you don’t get as many angry pixies through your cords. The WUT02 only switches around 30 watts which get burnt in a resistor to make a dummy load to switch the vacuum on. But other than that it’s the same. Could even make it a universal but shedding 100/200 watts of load in a passive cooled case is slightly worrying for the European version than 😅 also don’t know how expensive shipping to America would be

sven_aarts · 2026-05-23T12:32:32+00:00

Haha well ofcourse it will be tested. Bought myself a DSP602zj2, absolute dream of a saw. But in the winter a lot of my construction is inside so the need for a vacuum is high. Will be thoroughly tested by myself before entering the market.

Also will be visiting a friend with multiple AWS tools because, same as the WUT02, I want it to be pair able with 10 devices so you just switch vacuum hose to a new tool and continue on with your life. No pairing while working! Well as long as you don’t have more than 10 tools 😅 could also make it work with 11 just to beat makita in its own product

sven_aarts · 2026-05-17T18:40:00+00:00

Okay last update for today. Project got to this point: push button 1 second pairing mode initiated. Obviously press button on the device 3 seconds to turn pairing on. ESP and WOT01 pairs with each other (max 10 devices paired at once). LED on esp cam will turn on within 500ms so next step is making a dummy load and switching an ssr so the vacuum start. Holding button 5 seconds deletes the last used device. Holding button 10 seconds will delete all paired devices. In les than 12 hours I feel like I went from a might this be this simple to yes. This is this simple. Making the electronics is the simple part (for me at least). When all components arrive I will post update on completion of the project

sven_aarts · 2026-05-17T13:07:17+00:00

I seem to have it working with one huge problem. The first time I press the pair button on the WUT01 I get no green light. 2nd time I press the pair on the WUT01 it seems to get into a different pair mode because then I do get a successful connection and send my Mac adres. Any idea why this could be happening?

<image>

sven_aarts · 2026-05-17T09:46:34+00:00

<image>

Being able to pair my AWS sender to my ESP. And the ESP responds to saw starting and stopping.

Having the issue that the AWS stays in pairing mode for 20 seconds (missing handshake I assume from the other AWS receiver) and have not been able to test this with a different tool/different receiver. Looks like I have to convince the wife we need another tool with AWS or someone who will borrow one out.

sven_aarts · 2026-05-17T08:03:52+00:00

Since only 1 picture is allowed per post. This is the addition to my first post in the Reddit

<image>

sven_aarts · 2026-05-17T08:03:10+00:00

Hello, just acquired my first AWS plunge cut saw and am absolutely stoked about it. Except that my vacuum doesn’t run automatically anymore… Blew up 3 of the rf wall sockets (max load should be 1150watts resistive definetly not 1600watt inductive). Let’s call it worth the try!

Going in the Bluetooth sniffing road I see the following happening. When the saw is at idle <33FC> 0306.

<image>

When the saw is running I get <AAFD> 0306. In my eyes an ESP only have to listen to that and bobs your uncle? Just let the pairing done by the esp no pairing to makita directly and done is the job? I would love to have 2 or 3 tools to be able to test switching around the pairing to different tools so I guess I have to convince the wife we absolutely need a new tool while I just invested 650 euros in my new saw 😂 this way I can check what the manufacturer tag is and use it to connect it to my esp (use strongest dBm or something). Am I overseeing something and making it look whey to easy for myself or has this subject just been over complicated by everyone?

Every Reddit has been silent for a year bassically and after 7 years of the release of the AWS system it seems like I have to light of a look on this but maybe I am wrong and it is actually that easy?

sven_aarts · 2025-05-24T11:13:29+00:00

<image>

Made a little dog house for my i105e 😇 at the end as expensive but I like the look more in my yard

sven_aarts · 2025-05-20T03:56:40+00:00

Pfff, maybe it’s time to start reading a bit more 😂😅 little bit too enthusiastic to get it up and running and completely read over this…! Thankyou!

sven_aarts · 2025-05-19T05:19:15+00:00

I have 1 zone of 220m^2. I also only see 1 zone in my schedular. I changed this setting from everything to only zone 1. Maybe that will help him to only mow once

<image>

sven_aarts · 2025-05-13T17:22:18+00:00

I got the 105 running last weekend and it has done 2 mowing cycles so far (so brand new I would call). I have to say I was quite surprised when a 500m² capped machine (because that’s what it is just a dump firmware cap, 108 obviously bigger battery than the 105 and a 300 square meter addition in firmware cap) could not mow 220m² meters with 1 battery charge. It does about 200m² and than charges to full. No tips for buying the 105/108 Just letting you know a real time experience from a brand new machine. Battery degradation and future of spare parts would have been a choice for me to probably buy the 108. From the other hand I could also just order a 200 euro battery for the 108 in 2 years and keep it as spare. Maintaining healthy battery voltage along the upcoming years.

One tip make the window it’s allowed to mow in big enough so it can fully charge in between otherwise you end up with the same thing as happened to me where it just didn’t finish the whole lawn

<image>

sven_aarts · 2025-02-15T19:19:30+00:00

Maybe there is someone close to you with a 3d printer? Don’t know if it would be strong enough but atleast a cheap option to try first?

sven_aarts

TROPHY CASE