Retractable Saber from Japan

[olivierflying747-8]

I don’t know if this is helpful to you @Magus1340 but @herotech has already made an extendable/retractable saber. Here are some of his threads:

Proffieboard V3.9 powering extendable/retractable blade design?

Hey everyone, my team and I are working on a saber with an extendable/retractable blade using the Proffieboard V3.9. We’ve done our best to read up the documentation but it seems like what we are doing is a bit of a special case. We had two main questions: We are using a motor and a driver to power the extension/retraction. Would editing the Arduino code that gets flashed to the Proffie to recognize button input and send a signal to the motor driver to turn on/off the motor accordingly be enough, or would we have to go in and change something with the config files as well? The LED strip we are using for the blade is a COB LED strip that is not addressable and just has two wires for positive and negative. Looking through the blade config generator, would using the config for the segmented string blade and hooking up the negative wire to the negative pad for LED1 be enough for the LED strip to turn on as planned? (Effectively acting as a single segment of the blade) Any help would be greatly appreciated and thank you for taking the time to read this!

Extendable and Retractable Spinning Lightsaber Proffie Control

Hi again, thank you so much for your help with the previous retractable lightsaber! I am working on the next version of the lightsaber and I had a few questions. How the new lightsaber works is: 1 linear micro servo serves as a mechanical clutch, upon activation it releases the blade (blade extends with magician’s cane propulsion) 2 motors reel in 2 LED strip spools to retract the blade 1 additional motor rotates the magician’s cane while retracting for a smoother retraction The entire inner hilt chassis is rotated with an external motor (not controlled with Proffie) So the components we need to control with Proffie are: 2 non-addressable LED strips 2 N20 retraction motors 1 cane rotation motor 1 linear micro servo motor For turning on the saber, I was thinking that once the Proffie senses that it is spinning, it activates. And to turn off the saber, I was thinking that once the Proffie senses that it is spinning slower, it retracts and turns off. (I can externally control the rotation speed) So this is the order of operations that I’m thinking: Detect when hilt chassis is spinning = turn on saber, shift linear micro servo motor right 5mm, then after 500 milliseconds shift micro linear servo motor back left 5mm while turning on both retraction motors with PWM (SABER ON STATE) Detect when hilt chassis spinning is slowed = turn on cane rotation motor, full PWM power to both retraction motors, after 2000 milliseconds turn off saber, current sense when stall is reached and stop retraction, OR stop retraction after _____ milliseconds (SABER OFF STATE) A few questions I had were: Would the above order of operations work with Proffie? When the saber is on and spinning, I need to have the retraction motors powered a little bit, but not so much that it retracts the blade. This is because if there is no retracting force when the blade is spinning, the LED strips will look like a globe instead of a tight line. Can I do this with PWM by having the motors linked to LED pins? Are the LED pins current sensing? To stop the retraction, is it possible to detect when it reaches the stall current of the motor and then shut it off? Would the wait ____ milliseconds be a problem with Proffie? If I’m understanding correctly, Proffie can’t wait for things exactly, it has to do things in small quick increments. To turn off swing, clash, and smoothswing sounds, is it just changing the CLASH_THRESHHOLD_G and others to a really high value?

ProffieOS Button Code for Three-State Lightsaber Control

Hi again, I’m trying to code a custom prop file that uses the power button input to cycle between 3 states: off, on, and retracting. I want to override the normal power button inputs so that the sound and lights trigger only as I define it in my custom prop file - would the implementation below in my custom prop file under the loop() section be the right way to do it? Alternatively, if I don’t want my button presses to activate the saber when I don’t want it to activate, could I just redefine the button in my config file to something like aux2? bool Event2(enum BUTTON button, EVENT event, uint32_t modifiers) override { if (EVENTID(BUTTON_POWER, EVENT_CLICK_LONG, MODE_OFF) || EVENTID(BUTTON_POWER, EVENT_CLICK_LONG, MODE_ON)) { // State machine for saber control switch (power_state_) { case OFF: if (((EVENTID(BUTTON_POWER, EVENT_CLICK_LONG, MODE_OFF) || EVENTID(BUTTON_POWER, EVENT_CLICK_LONG, MODE_ON)) && !is_on_ && millis() > activation_buffer_) { ActivateSaber(); power_state_ = ON; activation_buffer_ = millis() + 8000; } break; case ON: if (((EVENTID(BUTTON_POWER, EVENT_CLICK_LONG, MODE_OFF) || EVENTID(BUTTON_POWER, EVENT_CLICK_LONG, MODE_ON)) && millis() > activation_buffer_) { BeginRetraction(); power_state_ = RETRACTING; activation_buffer_ = millis() + 2000; } break; case RETRACTING: if (((EVENTID(BUTTON_POWER, EVENT_CLICK_LONG, MODE_OFF) || EVENTID(BUTTON_POWER, EVENT_CLICK_LONG, MODE_ON)) && millis() > activation_buffer_) { DeactivateSaber(); power_state_ = OFF; activation_buffer_ = millis() + 20000; } break; } } }