Where can I find more information on that motion-activated beacon? That seems to be just the thing I need to make my droid alert me when the mail arrives.
here's the only other video i've done about it ruclips.net/video/1UvBvs6lMXs/видео.html maybe i should do another video? i think i didn't go further into it because it's not easy to setup. the whole thing is based on a module called "WT51822-S4AT" which you can connect to via serial (which means you need something like a USB to Serial adapter to talk to it). you can send commands to program the data that it'll transmit as a beacon. the gotcha is the actual beacon data has to be sent as it's raw value. meaning if you're using a text-based terminal to talk to it, you need to first find a way to create a binary file that consists of just the 8 bytes or so of data for the beacon, open that file into a text editor, copy the garbage on the screen, then paste that into the terminal you have connected to the module. it's not very intuitive or friendly. maybe i should modify the droid toolbox code to activate when some pin on the TTGO goes high. then I could hook up the motion sensor to the toolbox. but then the whole purpose of the original motion sensor beacon was very low power requirements, which the TTGO does not have, so... i don't know. well.. maybe now i remember why i didn't do much more with that particular project. ;)
It would be cool to add a "colder / warmer" function in the scanner section. Could refresh the resistance every few moments and ijt will tell you if the signal is getting colder or warmer.
Great video. I like the added functionality of the "Scanner" to connect to a selected droid and play group and track sounds. I took your previous version and added a display line when the Beacon is turned "ON" that shows what the "source" is (i.e. Dok-Ondar's). I was getting ready to switch the displayed location to Aurebesh with the "translated" location displaying after a few seconds.. I too recently purchased a Seeed XIAO and have been playing with it. For some reason, it doesn't seem to be holding the code in memory so I have to upload it each time. I'm assuming its something I'm doing wrong. I also had some conceptual idea of hopefully using the XIAOs for setting up multiple beacons in my Star Wars room so when a droid came close, it would trigger the beacon to send the signal to the droid. I look forward to seeing what you work out. Your help previously was great on the Droid Toolbox. I had been attempting to do the random beacon signals and the way you did it was great. I appreciate you sharing this information. I just started working with Arduino IDE last October, so I have much to learn. I'm heading to Batuu (West) next week and building a droid with my grandson. He really likes the one his sister built last year so we're all really geeking out over this. Thank you.
I had a minor setback adjusting my version (v0.52), to include the "source" for the Beacon (i.e. Dok-Ondar's). I made the changes and reuploaded the IDE, and had my screen disappear. Come to find out, I had updated the TFT_eSPI Arduino Library and when this was done the "User_Setup_Select.h" had been overwritten. Once I went back in and re-updated the "User_Setup_Select.h" to again use the TTGO T-Display, my Sketch worked again. I was afraid I had bricked my TTGO T-Display, but I hadn't. I just wanted to throw in this comment, in case someone else had encountered something similar. My version now displays the "source" for the Beacon. Thanks again Rutthsarian for the great IDE code.
I love that you have the BLE framework accessible. There are limitation with only 2 buttons and this TFT display. I'm looking to expand the non beacon control. It would be helpful to have a version without this specific TFT display. Even using just dumping output to a physical serial connection. A user could easily modify that code to use their particular display
Could this be used to make the red sequencer light on Moff Gideon's new beskar chest armor? Any suggestions for an IC that could be programmed to operate as seen on Mandalorian S3 Ep8 Chpt 24?
Help! Everything seems to work except when I try to connect to my droid after scanning the TTGO resets! Or at least the program restarts (I see the Droid Toolbox title screen again)
is your droid's remote off? are you using the ESP32 core from github.com/espressif/arduino-esp32 or could you be using a different core? do you have ArduinoBLE installed as a separate library? if so, remove it. before compiling and uploading the program, what board do you have selected? is it the ESP32 Dev Board? -- update -- the problem turned out to be an old version of the ESP32 core (1.0.6) was being used to compile the code. updating the core solved the problem.
Just programmed one of these bad boys and I'm wondering two things: - I have one of your personality chips and it shows CB-23 and Ruthsarian instead of Blue and Scoundrel. Did you cover how that was done in the personality chip videos? - Second do you have a video showing how you extracted the sounds from the purchased chip? I've tried making a rip of a red one I have but I am having trouble extracting the individual sounds Thank you for all the help you've given everyone and all the work you've done for this community!
it shows CB-23 because I created that personality chip before CB or any of the new personality chips existed, so I used an ID that, eventually, Disney used for their own stock personality chips. So the code is using the name for the stock Disney chip, not mine. The affiliation reads 'Ruthsarian' instead of 'Scoundrel', because I noticed Disney was not using a particular ID for affiliation, so I decided to use it for myself. I'm removing that 'Ruthsarian' affiliation in a later version of the code. The text 'ruthsarian' is not anywhere on the personality chip. All that is on the personality chip is a number. The code reads in that number, and says "If the number is X, then print "Ruthsarian"'. The text 'Ruthsarian' is in the droid toolbox code. It is not part of the personality chip. You can use this code to extract audio from chip dumps: github.com/ruthsarian/a3400pro-decode
Sounds like the humming sound from the sabers that loops Also, do you know if anything like this was ever done for those expensive little phone-controlled droids? I still have the BB-9E sitting around with nothing interesting to do.
Any plans to extend this to allow motor control? Was thinking of building a remote that could drive the droid as well as control the sounds. Seems like some of the motor control messaging may have been worked out.
The motor control commands have been worked out. It's possible to add motor control to the toolbox. The question is how would you design the interface when you only have two buttons? That's something I'll have to play with and figure out what 'feels' right. I'm also a little wary of adding motor control. If something goes wrong and a stop command is missed then the droid's motors will keep running, potentially at full speed, until you cycle the power on it. That could turn the droid into a little bundle of mayhem and destruction. I'd want some sort of safeguard, like a command that includes both a start and a stop. I have a couple ideas on how I'd do that, but I'm not sure how usable that sort of safety-based control will work. It's an idea that's rattling around my head, but it's not a high priority item for me at the moment. But if anyone else wanted to give it a shot they certainly could. I recently updated the droid controller tab on the research spreadsheet (docs.google.com/spreadsheets/d/13P_GE6tNYpGvoVUTEQvA3SQzMqpZ-SoiWaTNoJoTV9Q/edit#gid=941538687) to be a bit more informative on how the commands (including motor controls) work. With that information and the droid toolbox code to connect to and send commands to a droid, it wouldn't be too hard to mod the droid toolbox to include movement.
@@Ruthsarian Thanks for the quick reply! If I was going to build a remote with a motor controller capability, I think I would add some additional push buttons on a bit of proto board connected to some of the gpio pins.
@@Ruthsarian Is there any way to attach the toolbox to the existing controller and use the controller Bluetooth connection to send the audio commands from the toolbox.
@@Cougar2ei4 nope. An entirely new remote would have to be constructed, designed to replicate the stock controller behavior along with the toolbox behavior. Possible? Yes. But it would require a lot of work to reverse engineer the original remote's programming. And that sort of work is outside my capabilities.
The sound you describe as a possible "motor" sound, sounds a bit like Data sent from a Modem (old school stuff🙂). Have you tried looking at it with an Oscilloscope or Data Analyser to see if it's some sort of Telemetry or hidden Easter Egg?
interesting idea. i hadn't tried that. here's an image of the track, extracted from a personality chip, in Audacity with both a spectrograph and a spectrum analyzer: imgur.com/a/ImZ7oCG unfortunately i don't think there's any data there. but of course now i want to double-check some other personality chip tracks to see if they have anything interesting...
@@Ruthsarian It was a familiar sounding "sound" from many many years ago. It would be interesting if it was Data? and what it meant if it could be "read" 🙂
I want to get some videos online showing assembly and installation so people have a chance to understand what's involved before buying one. That's where I'm at with the blade controller. I've got maybe 40 of them assembled and programmed. I just need to get the videos showing how to install it online.
i don't have a specific battery I can recommend. what follows is educated guess work. the battery will depend on the available space inside the case you bought. assuming it's the same case I have, which is the 'official' one from LilyGo, you have room of about 7x25x60mm for the battery. it needs to be a rechargeable lipo battery with a JST connector that has a 1.25mm spacing between the pins of the connector. given that, i believe one of these should work: www.amazon.com/dp/B09J25PKN7/ www.amazon.com/dp/B0D47LK8QL/ probably the first one, because the delivery times on the second are ... out there. you might also find 1.25mm to 2.0mm connector adapters, like this one www.amazon.com/dp/B08C7GBG45/, which would then allow you to buy lipos with a 2.0mm connector. just pay attention to the battery sizes. battery size and connector will get you if you're not paying attention.
@@Ruthsarian I found one I think will work. 550mah 502248, and it says it has a 1.25 plug. Expensive, though. dp/B0CW9R7N89/ (cut because it seems comments with links get deleted)
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
Where can I find more information on that motion-activated beacon? That seems to be just the thing I need to make my droid alert me when the mail arrives.
here's the only other video i've done about it
ruclips.net/video/1UvBvs6lMXs/видео.html
maybe i should do another video? i think i didn't go further into it because it's not easy to setup. the whole thing is based on a module called "WT51822-S4AT" which you can connect to via serial (which means you need something like a USB to Serial adapter to talk to it). you can send commands to program the data that it'll transmit as a beacon. the gotcha is the actual beacon data has to be sent as it's raw value. meaning if you're using a text-based terminal to talk to it, you need to first find a way to create a binary file that consists of just the 8 bytes or so of data for the beacon, open that file into a text editor, copy the garbage on the screen, then paste that into the terminal you have connected to the module.
it's not very intuitive or friendly.
maybe i should modify the droid toolbox code to activate when some pin on the TTGO goes high. then I could hook up the motion sensor to the toolbox.
but then the whole purpose of the original motion sensor beacon was very low power requirements, which the TTGO does not have, so... i don't know.
well.. maybe now i remember why i didn't do much more with that particular project. ;)
oh man now you made me go down the rabbit hole ... lol!! thanks
Need more videos! You are amazing.
It would be cool to add a "colder / warmer" function in the scanner section. Could refresh the resistance every few moments and ijt will tell you if the signal is getting colder or warmer.
Great video. I like the added functionality of the "Scanner" to connect to a selected droid and play group and track sounds. I took your previous version and added a display line when the Beacon is turned "ON" that shows what the "source" is (i.e. Dok-Ondar's). I was getting ready to switch the displayed location to Aurebesh with the "translated" location displaying after a few seconds.. I too recently purchased a Seeed XIAO and have been playing with it. For some reason, it doesn't seem to be holding the code in memory so I have to upload it each time. I'm assuming its something I'm doing wrong. I also had some conceptual idea of hopefully using the XIAOs for setting up multiple beacons in my Star Wars room so when a droid came close, it would trigger the beacon to send the signal to the droid. I look forward to seeing what you work out. Your help previously was great on the Droid Toolbox. I had been attempting to do the random beacon signals and the way you did it was great. I appreciate you sharing this information. I just started working with Arduino IDE last October, so I have much to learn. I'm heading to Batuu (West) next week and building a droid with my grandson. He really likes the one his sister built last year so we're all really geeking out over this. Thank you.
I had a minor setback adjusting my version (v0.52), to include the "source" for the Beacon (i.e. Dok-Ondar's). I made the changes and reuploaded the IDE, and had my screen disappear. Come to find out, I had updated the TFT_eSPI Arduino Library and when this was done the "User_Setup_Select.h" had been overwritten. Once I went back in and re-updated the "User_Setup_Select.h" to again use the TTGO T-Display, my Sketch worked again. I was afraid I had bricked my TTGO T-Display, but I hadn't. I just wanted to throw in this comment, in case someone else had encountered something similar. My version now displays the "source" for the Beacon. Thanks again Rutthsarian for the great IDE code.
I love that you have the BLE framework accessible. There are limitation with only 2 buttons and this TFT display. I'm looking to expand the non beacon control. It would be helpful to have a version without this specific TFT display. Even using just dumping output to a physical serial connection. A user could easily modify that code to use their particular display
I think that humming sound might be a disney parks lightsaber sound?
Could this be used to make the red sequencer light on Moff Gideon's new beskar chest armor? Any suggestions for an IC that could be programmed to operate as seen on Mandalorian S3 Ep8 Chpt 24?
Help! Everything seems to work except when I try to connect to my droid after scanning the TTGO resets! Or at least the program restarts (I see the Droid Toolbox title screen again)
is your droid's remote off? are you using the ESP32 core from github.com/espressif/arduino-esp32 or could you be using a different core? do you have ArduinoBLE installed as a separate library? if so, remove it. before compiling and uploading the program, what board do you have selected? is it the ESP32 Dev Board?
-- update --
the problem turned out to be an old version of the ESP32 core (1.0.6) was being used to compile the code. updating the core solved the problem.
Just programmed one of these bad boys and I'm wondering two things:
- I have one of your personality chips and it shows CB-23 and Ruthsarian instead of Blue and Scoundrel. Did you cover how that was done in the personality chip videos?
- Second do you have a video showing how you extracted the sounds from the purchased chip? I've tried making a rip of a red one I have but I am having trouble extracting the individual sounds
Thank you for all the help you've given everyone and all the work you've done for this community!
it shows CB-23 because I created that personality chip before CB or any of the new personality chips existed, so I used an ID that, eventually, Disney used for their own stock personality chips. So the code is using the name for the stock Disney chip, not mine.
The affiliation reads 'Ruthsarian' instead of 'Scoundrel', because I noticed Disney was not using a particular ID for affiliation, so I decided to use it for myself. I'm removing that 'Ruthsarian' affiliation in a later version of the code.
The text 'ruthsarian' is not anywhere on the personality chip. All that is on the personality chip is a number. The code reads in that number, and says "If the number is X, then print "Ruthsarian"'. The text 'Ruthsarian' is in the droid toolbox code. It is not part of the personality chip.
You can use this code to extract audio from chip dumps: github.com/ruthsarian/a3400pro-decode
@@Ruthsarian Thank you so much for taking the time to respond. I did find the code in the Ardunio code and started messing around with it.
Sounds like the humming sound from the sabers that loops
Also, do you know if anything like this was ever done for those expensive little phone-controlled droids? I still have the BB-9E sitting around with nothing interesting to do.
There is a different TTGO board using RP2040 (which appears to be cheaper). Will this work the same, or does it have to be the ESP32 version board?
The rp2040 does not appear to support Bluetooth, so it wouldn't work.
Any plans to extend this to allow motor control? Was thinking of building a remote that could drive the droid as well as control the sounds. Seems like some of the motor control messaging may have been worked out.
The motor control commands have been worked out. It's possible to add motor control to the toolbox. The question is how would you design the interface when you only have two buttons? That's something I'll have to play with and figure out what 'feels' right.
I'm also a little wary of adding motor control. If something goes wrong and a stop command is missed then the droid's motors will keep running, potentially at full speed, until you cycle the power on it. That could turn the droid into a little bundle of mayhem and destruction. I'd want some sort of safeguard, like a command that includes both a start and a stop. I have a couple ideas on how I'd do that, but I'm not sure how usable that sort of safety-based control will work.
It's an idea that's rattling around my head, but it's not a high priority item for me at the moment. But if anyone else wanted to give it a shot they certainly could. I recently updated the droid controller tab on the research spreadsheet (docs.google.com/spreadsheets/d/13P_GE6tNYpGvoVUTEQvA3SQzMqpZ-SoiWaTNoJoTV9Q/edit#gid=941538687) to be a bit more informative on how the commands (including motor controls) work. With that information and the droid toolbox code to connect to and send commands to a droid, it wouldn't be too hard to mod the droid toolbox to include movement.
@@Ruthsarian Thanks for the quick reply! If I was going to build a remote with a motor controller capability, I think I would add some additional push buttons on a bit of proto board connected to some of the gpio pins.
@@Ruthsarian Is there any way to attach the toolbox to the existing controller and use the controller Bluetooth connection to send the audio commands from the toolbox.
@@Cougar2ei4 nope.
An entirely new remote would have to be constructed, designed to replicate the stock controller behavior along with the toolbox behavior.
Possible? Yes. But it would require a lot of work to reverse engineer the original remote's programming. And that sort of work is outside my capabilities.
The sound you describe as a possible "motor" sound, sounds a bit like Data sent from a Modem (old school stuff🙂). Have you tried looking at it with an Oscilloscope or Data Analyser to see if it's some sort of Telemetry or hidden Easter Egg?
interesting idea. i hadn't tried that. here's an image of the track, extracted from a personality chip, in Audacity with both a spectrograph and a spectrum analyzer: imgur.com/a/ImZ7oCG
unfortunately i don't think there's any data there. but of course now i want to double-check some other personality chip tracks to see if they have anything interesting...
@@Ruthsarian It was a familiar sounding "sound" from many many years ago. It would be interesting if it was Data? and what it meant if it could be "read" 🙂
Do you have any updates on the blade controller? I would love to buy one!
I want to get some videos online showing assembly and installation so people have a chance to understand what's involved before buying one. That's where I'm at with the blade controller. I've got maybe 40 of them assembled and programmed. I just need to get the videos showing how to install it online.
I'm just about to build one of these using an S3 with a case off Amazon. Do you know offhand what battery will fit?
i don't have a specific battery I can recommend. what follows is educated guess work.
the battery will depend on the available space inside the case you bought. assuming it's the same case I have, which is the 'official' one from LilyGo, you have room of about 7x25x60mm for the battery. it needs to be a rechargeable lipo battery with a JST connector that has a 1.25mm spacing between the pins of the connector.
given that, i believe one of these should work:
www.amazon.com/dp/B09J25PKN7/
www.amazon.com/dp/B0D47LK8QL/
probably the first one, because the delivery times on the second are ... out there.
you might also find 1.25mm to 2.0mm connector adapters, like this one www.amazon.com/dp/B08C7GBG45/, which would then allow you to buy lipos with a 2.0mm connector. just pay attention to the battery sizes.
battery size and connector will get you if you're not paying attention.
@@Ruthsarian I found one I think will work. 550mah 502248, and it says it has a 1.25 plug. Expensive, though. dp/B0CW9R7N89/ (cut because it seems comments with links get deleted)
sick cheers
I think it's C1-10P, not CH1-10P
You are correct. I will update the Droid Toolbox code to fix that. thanks!
Nice video. Show off the droids in the video with the toolbox next time. Alot more views i'm sure.