Just came back from Batuu West with a new BD1 droid. It was exciting to see it pop-up on the "SCANNING" option. With your handy Droid Toolbox I was able to listen to all the sounds this new little droid makes. It also responded well to the various BEACONS. Thank you!
I'm still enjoying your Droid Toolbox. I recently got the D-O Droid and A-LT Droids at the Droid Depot. It was nice to see the D-O Droid pop up with the "Scanning" option. I noticed the A-LT Droid did display as "Undefined" but I really liked that I was able to go through all of the "Sounds" and hear what the the new A-LT droid sounds were like. Thanks for this great "Droid Toolbox".
what version of droid toolbox are you on? the most recent version (0.73) should know it's an A-LT. If you're on 0.73 and it doesn't, let me know. I don't have an A-LT, but maybe we can troubleshoot it and get it working.
Thanks again. Very cool with the various fonts. I really like the "PWR: 9.99V" display. I know my batteries have a tendency to go down faster than I expect. I really appreciate the detailed instructions and how easy you make it look. I'm playing now with trying to get this to work with a LILYGO T-HMI. I'm not sure if this will work out. It looks like everything is setup in the TFT_eSPI library but I'm not seeing anything yet. I'll keep poking along. Several months ago I had asked you about setting up random beacons and now you've added that and so many cool features. Its been a real blast seeing all of these neat enhancements.
Such great work! Thank you for adding this to the community. Since the LilyGo has pin headers to accommodate cameras and other sensors, could this be extended to allow some sort of roam mode or other autonomy?
do you mean roam as in controlling a droid? it'd be possible. the processing power may limit the kind of image processing you could do with a camera feed, but you could at least do something with it.
A New id9 seeker droid was released in the parks, had me thinking about swapping boards in from an R or C unit to give it open bluetooth and personality chip functionality (though I imagine it would lose all remote and mobility functionality in doing so) Could you imagine any way to combine the boards from both that would work with the LEDs? I'd have to guess the juice just wouldn't be worth the squeeze but I love when I'm wrong!
Awesome update! But I do have one issue, downloaded the Mando AF Classic Font from Aurek Fonts, but can't seem to get the code right for the size? any suggestions?
"right for the size"? as in file size or display size? MandoAF comes as OTF files. You need to convert them to TTF. Once they're TTF they'll be 16kb and 10kb in size (not sure which one, classic or regular, you're using). Those are good file sizes. Convert the TTF files to .h files and then include them in the source code and add them to the dtb_fonts[] array. I've done that and got the fonts to load, although there are a couple issues. the font needs to be adjusted down slightly when being drawn. that can be done by setting the y_offset value of the font's entry in dtb_fonts[]. the font height is multiplied by y_offset and the y (vertical) position of the font will be adjusted by the resulting value. negative values move the font up, positive values move the font down. i've found that a value of 0.14 seems to work best for MandoAF. now if the problem is display size, there's not much that can be done about that. this is a tall, narrow font. for droid toolbox, fonts that have similar width and heights work best. here's my attempt at incorporating MandoAF: github.com/ruthsarian/Droid-Toolbox/tree/v0.66a---Mando-AF This is not something I plan to retain in the main Droid Toolbox branch. It's just an example.
@@Ruthsarian I was able to get them loaded with no issues (great tutorial BTW), It's the display size, I was playing with the numbers at the end of the entry: { MandoAFClassic, sizeof(MandoAFClassic), 2.0, 0 }, but wasn't sure what the numbers represented (size, ratio, etc), I also saw the workaround arguments above that look to modify the scale of the font just wasn't sure how to add them to the entry for that font: uint32_t size; float y_scale; // a workaround for font rendering issues; the font will be scaled by this value when rendered
@moonknight75 i take the font height of the default (pixelated) font and use that as a maximum height for any of the custom fonts. but some custom fonts, when their heights get calculated, come out taller than this maximum height. this is where y_scale comes into play. it's purpose is to shrink fonts down slightly that normally render larger than they should for the space they're given. i suppose you could increase this value beyond 1.0, but the fonts will likely start to overlap eachother. and some custom fonts, when rendered, appear higher or lower than they should be (i think this has to do with how the baseline value is set in the truetype font). thus the font height gets multiplied by y_offset and that value is added to the y position where the font would be rendered. it's probably a very terrible way to handle this problem and i'm probably using OpenFontRender in a way it was not foreseen to be used, but after working on this for a couple weeks i stopped caring about if it was the "wrong" way and only whether or not it did what i wanted it to do. i wouldn't be surprised if I rewrite a bunch of that code in the future. once i have time to get a better handle on things.
Is there a way to set up a random beacon broadcast as a type of set it and forget it device? My family and I came back with 5 droids, and it would be nice to cycle random beacon chirps with the new robotic hoard
Just came back from Batuu West with a new BD1 droid. It was exciting to see it pop-up on the "SCANNING" option. With your handy Droid Toolbox I was able to listen to all the sounds this new little droid makes. It also responded well to the various BEACONS. Thank you!
I'm still enjoying your Droid Toolbox. I recently got the D-O Droid and A-LT Droids at the Droid Depot. It was nice to see the D-O Droid pop up with the "Scanning" option. I noticed the A-LT Droid did display as "Undefined" but I really liked that I was able to go through all of the "Sounds" and hear what the the new A-LT droid sounds were like. Thanks for this great "Droid Toolbox".
what version of droid toolbox are you on? the most recent version (0.73) should know it's an A-LT. If you're on 0.73 and it doesn't, let me know. I don't have an A-LT, but maybe we can troubleshoot it and get it working.
Thanks again. Very cool with the various fonts. I really like the "PWR: 9.99V" display. I know my batteries have a tendency to go down faster than I expect. I really appreciate the detailed instructions and how easy you make it look. I'm playing now with trying to get this to work with a LILYGO T-HMI. I'm not sure if this will work out. It looks like everything is setup in the TFT_eSPI library but I'm not seeing anything yet. I'll keep poking along. Several months ago I had asked you about setting up random beacons and now you've added that and so many cool features. Its been a real blast seeing all of these neat enhancements.
Such great work! Thank you for adding this to the community. Since the LilyGo has pin headers to accommodate cameras and other sensors, could this be extended to allow some sort of roam mode or other autonomy?
do you mean roam as in controlling a droid? it'd be possible. the processing power may limit the kind of image processing you could do with a camera feed, but you could at least do something with it.
Where di i find the beacons at? would love to set one up
A New id9 seeker droid was released in the parks, had me thinking about swapping boards in from an R or C unit to give it open bluetooth and personality chip functionality (though I imagine it would lose all remote and mobility functionality in doing so) Could you imagine any way to combine the boards from both that would work with the LEDs? I'd have to guess the juice just wouldn't be worth the squeeze but I love when I'm wrong!
Hello....I commented out the custom fonts but I can't seem to get past the bug around line 1025
No arduino experience , any help would be appreciated
Did you comment out line 176:
#define USE_OFR_FONTS
Thank you for responding.
that did the trick
thankyou so much!@@Ruthsarian
Awesome update! But I do have one issue, downloaded the Mando AF Classic Font from Aurek Fonts, but can't seem to get the code right for the size? any suggestions?
"right for the size"? as in file size or display size?
MandoAF comes as OTF files. You need to convert them to TTF. Once they're TTF they'll be 16kb and 10kb in size (not sure which one, classic or regular, you're using). Those are good file sizes. Convert the TTF files to .h files and then include them in the source code and add them to the dtb_fonts[] array.
I've done that and got the fonts to load, although there are a couple issues. the font needs to be adjusted down slightly when being drawn. that can be done by setting the y_offset value of the font's entry in dtb_fonts[]. the font height is multiplied by y_offset and the y (vertical) position of the font will be adjusted by the resulting value. negative values move the font up, positive values move the font down. i've found that a value of 0.14 seems to work best for MandoAF.
now if the problem is display size, there's not much that can be done about that. this is a tall, narrow font. for droid toolbox, fonts that have similar width and heights work best.
here's my attempt at incorporating MandoAF:
github.com/ruthsarian/Droid-Toolbox/tree/v0.66a---Mando-AF
This is not something I plan to retain in the main Droid Toolbox branch. It's just an example.
@@Ruthsarian I was able to get them loaded with no issues (great tutorial BTW), It's the display size, I was playing with the numbers at the end of the entry:
{ MandoAFClassic, sizeof(MandoAFClassic), 2.0, 0 },
but wasn't sure what the numbers represented (size, ratio, etc), I also saw the workaround arguments above that look to modify the scale of the font just wasn't sure how to add them to the entry for that font:
uint32_t size;
float y_scale; // a workaround for font rendering issues; the font will be scaled by this value when rendered
@moonknight75 i take the font height of the default (pixelated) font and use that as a maximum height for any of the custom fonts.
but some custom fonts, when their heights get calculated, come out taller than this maximum height. this is where y_scale comes into play. it's purpose is to shrink fonts down slightly that normally render larger than they should for the space they're given. i suppose you could increase this value beyond 1.0, but the fonts will likely start to overlap eachother.
and some custom fonts, when rendered, appear higher or lower than they should be (i think this has to do with how the baseline value is set in the truetype font). thus the font height gets multiplied by y_offset and that value is added to the y position where the font would be rendered.
it's probably a very terrible way to handle this problem and i'm probably using OpenFontRender in a way it was not foreseen to be used, but after working on this for a couple weeks i stopped caring about if it was the "wrong" way and only whether or not it did what i wanted it to do.
i wouldn't be surprised if I rewrite a bunch of that code in the future. once i have time to get a better handle on things.
Great video
Thanks You!: )
Is there a way to set up a random beacon broadcast as a type of set it and forget it device? My family and I came back with 5 droids, and it would be nice to cycle random beacon chirps with the new robotic hoard
the latest version of droid toolbox includes a randomized beacon option. I think that will do what you're looking for.