Tag is cooked

Literally and figuratively. The board is shorted between 3.3v an GND, but it powers on(??), heating up in little time. SO now i have to redo half of the code due tomorrow cause we need to present the project :D kill me

tutto si distrugge nulla si crea

We are currently in Zagabria. I’ve not logged a LOT of hours. The remote shorts randomly with no apparent motive. we are missing the candy dataset, the uwb apparently had a fight cause they won’t talk anymore for some reason?? I am losing touch with reality

Screen turns on!!

@gismondi_simone yesterday broke our spare… i guess we have to work with that.
There are still some problems about the data sending between base and tag, but i’ve come a long way from the start.

Dataset compiler works!

I’ve spent the last few days trying to figure out the problem of the compiler (that worked the last time i used it so i was kinda confused) and after 4 hours of debugging with a little help from gemini i’ve finally made it work. Now we just need to take the ne photos for the dataset.

Back on the torturing part

At least this time I don’t have to install anything for two days! :D JUST KIDDING wasted 2 days on trying to make my pc work for this bs, turns out it’s still faster on @gismondi_simone ‘s pc… but hey trial and error right Hopefully working on dataset tomorrow
P.S., we solved the motor problem, turns out the driver wasn’t wired right…

It was a long 10 hours; I moved back and forth between different parts of the project. I installed the self-locking nuts onto the motor shafts (a very long, arduous, and boring process). Afterward, I built the entire conveyor system, but while i was working on it- and during a test run of the rover by my teammate-the brushless motor drivers burned out. We managed to get almost everything working in time to shoot the presentation video for the WRO. I assembled the entire scanner, mounted all the internal boards, and did a great job with the wiring. In meantime, I received a Centaury Carbon 2 Combo, a gift from our sponsor, Crea 3D.

Code works. Hardware not so much.

All @gismondi_simone ‘s fault . We have to figure out why the cam motor and it’s driver are overheating and not moving the arm, but at least everything in the code seems to work alright. If we are able to we’ll record the new dataset tomorrow. I forgot to take a picture of the terminal so enjoy this pic of a kitty

how the code folder is looking.
I’m entering flow state, now is the lock in period when i have to re-read every code and combine everything to work together. Tbf it’s all going good for now, if not the fact that we cooked the two drivers for the wheels and we have to buy new ones. My part is going good, in a little we’ll be able to remake the dataset for the AI recognition model in the 2.0 version, can’t wait!

hello! it’s been a while

a lot has changed since the last log, i made some new programs to integrate the dijkstra in the map creation and a motor tryout code to see how the motors work and to calibrate the data on the other codes.

For now everything seems good, we’ll see once i actually try it with the robot. For now i hope i didn’t look over any VERY IMPORTANT detail that could set something on fire :D

Had to reflash the rpi cause of some fuckups i did

lowk don’t even wanna talk about it

I hate this
save me pls

Added and adapted also p5 and p0 code

I readded the code for the scanner boards, adding the bin’s stepper to be controlled by the p0.

ESP can now manage two different receivers

I made the send function better, adding logic to change the receivers and the message in order of what is needed, now i need to work on the raspberry side logic

Beginning adapting the old code to the new hardware

finally i would also add xd
for now only did the ESP code, that will manage the conveyor movement and the calculation of the fullness to send to the remote. Next I’ll probably work on the communication remote-raspberry and raspberry-esp.

Adding buttons and display control

for now it’s only theory, we don’t have the display yet, but i want to see how it can send and receive the button information without a added microcontroller.
This would solve the internet connection lack problem.

It can drive.

(better)

added a configuration mode before starting to drive. Since we have only two anchors avaliable, with no way to check if the remote is in front of the robot or in the back, i added a “configuration” that turns 45 degrees to check if the left measuration increases or decreases (clever i know (anything to avoid spending 30€ more))

oh and added an error for the turning code, so it doesn’t zigzag all the time

It can drive.

Joined a collab repo with @gismondi_simone (hope your pillow is warm both sides)

UWB WORKING!!!

im so happy. Now i need to setup the reading for the p4 and implement it for the map creating algorithm. (⊙_◎)