@Rithish

Dev Log #20:
Pulled out my old AtomRC Dolphin from the school project and stripped everything off it. Starting fresh with my own sensors. No coding today, just figuring out where to place everything and making sure the wiring is clean and airflow is good. Got the RF receiver mounted too. Next few dev logs are gonna be all about this physical build.

Dev Log #19:
Read the feedback about the PCB issue today and started learning how to design one properly. I also uploaded the current schematic to the repository and updated the README with the hardware plan. Since the sensor set is still being tested, I need to validate the sensors first before finalising the PCB, so I don’t design it around components that may change later. Tomorrow, I’m going to continue adding and testing more sensors with the Arduino UNO R4. Small steps, but the system is coming together!

Dev Log #18:
Got the M10 GPS chip and a FPV receiver with a screen today, let’s go! Finally some new hardware to play with. Tried soldering some stuff and honestly quit midway lol. But I did manage to solder a few other things and it was kinda fun ngl. Burned my fingerprint in the process but I’m fine. Gonna test both soon and get them integrated with the rest of the system.

Dev Log #17:
Tested the PMS5003 and it works. Plan is to add sensors one by one so troubleshooting is easier. Mapped out wiring for SCD40 (I2C bus) and MQ-135 (A0, 5V). Wrote test code that reads CO2, temp, humidity from SCD40 and raw gas readings from MQ-135. MQ-135 will be used as a relative gas-trend sensor unless calibrated later. Next up is combining everything with RF telemetry, SD logging, and OLED.

Dev Log #16:
Today I finished designing the full RF telemetry packet for the NRF24L01. Got all sensors packed into 55 bytes - MPU6050, BN-880 GPS, SCD40, BME680, PMS5003, MQ135, and MS4525DO. All neatly packed and ready to send to the ground station. The full integration code is written with SD logging, web server, and everything. Will test it all tomorrow on the bench and upload to GitHub once it’s working.

Dev Log #15:
Wrote and uploaded the full MPU + SBUS + PID code to GitHub. Got roll and pitch data from MPU, sticks from RadioLink, and PID corrections calculated. Tomorrow I’ll test it properly with just the ailerons to check if the self-correcting actually works. Also did some research on the MB102 power supply and the Uno to see if it helps with bench testing. Just research for now, nothing tested yet. But good progress overall. More testing tomorrow.

Dev Log #14:
Traveling rn soo no hardware, had to work with my phone but yeah i used the time to plan out my own fc os mercury and also how safefail priority is a main thing. just planned out and took notes but the plans and the direction is solid….

Dev Log #13:
After reading the Stardance feedback, I completely shifted my project direction. Instead of building an airframe, I am now focusing entirely on the flight controller itself. I updated everything - BOM, README, journal, schematic, code. Just resubmitted the funding request for $147.50 USD. This funding will help me build a proper Teensy 4.1 flight controller with IMU, airspeed, barometer, telemetry and FPV. I really hope this gets approved. Fingers crossed.

Dev Log #12:
Busy day today! Got the final BOM ready with all components, links, and prices in both AED and USD. Total comes to ~$147.50 USD including shipping and import tax. Finally locked in the sensor list: MPU-9250 for orientation, BMP280 and MS5611 for altitude, MS4525DO for airspeed, and the SLONWAKE 1W VTX for long-range FPV. Also got the logic level converter from Noon to safely connect everything to the Teensy. Tomorrow is the big day - gotta upload everything to GitHub for the Stardance submission. Need to add the BOM CSV, the README, the journal, and the demo videos. Still need to figure out the CAD/STEP file situation and the wiring diagram. Feeling good about where the project is at. One more push and it’s done!

Dev Log #11:
Finally got the RadioLink receiver working with the Arduino! Connected the SBUS signal to pin 3 and got all 6 channels showing up in the Serial Monitor. Aileron, Elevator, Throttle, Rudder, and switches all reading properly. Took forever to figure out the wiring and the right library but it’s done now. Next step is merging the MPU data with the radio input so the flight controller can correct my sticks and keep the plane stable. Both systems work separately, now just gotta combine them. Feels good to finally have a real transmitter

Dev Log #10:
Just submitted the Stardance funding request for $260 USD. This is it man. If it gets approved, the dream build becomes real. Xfly X1300 airframe, 4S battery, motor, ESC, servos….everything I need. Teensy 4.1 and ICM-20948 are already borrowed from my tutor. The Apprentice is wrecked anyway so the X1300 will be the real deal. Been working on this for weeks. Soldering, coding, troubleshooting, failing, fixing, learning. This is the moment it all comes together. Fingers crossed.

Dev Log #9:  
Finally got the GitHub README fully updated, cleaned it up, removed the old dev logs, added the BOM as a future funding plan for Stardance, mentioned the Apprentice is broken and just a test body now, and put in notes about schematics and code coming soon. Also finalized the BOM list with all components and links in both AED and USD. Tomorrow I’m filming the Stardance demo video showing the bench setup with the MPU-6050 data streaming and servos moving. Feeling pretty good about where this project is heading. Just need to film that video and then we can focus on the Teensy 4.1 integration and getting everything on the actual airframe

Dev Log #8:
Back home finally! Got back to work on the TFCS-1. Coded the Uno to work with rudder and ailerons together - both control surfaces responding to MPU data now. Still need to test them all together on the actual airframe but the code logic is solid. Also updated the README on GitHub with all the project details, hardware specs, dev logs, and the whole story behind this build. Feels good to have proper documentation now. Next step is testing everything together on the bench and then moving to the Teensy 4.1 integration

Dev Log #7:
Traveling right now so no hardware today 😭. But honestly still made progress. Planned out the whole power system - ESC BEC will power the servos and UBEC will power the Teensy. Both from the same battery with all grounds tied together. Got the code ready to test once I’m back home. Everything is planned out, just need to actually build it when I return. Really really want that plane man. Let’s see….

Dev Log #6:
Kinda felt off tdyy so i didnt work on it much but i did some research on the airframe which i wanna actually test my systems on…TAAAADAA X1300 looks cool ryt ?

Dev Log #5:
WE DID IT! 😭🙌 The flight controller is officially WORKING! MPU-6050 is reading roll data and both wing servos move exactly how they should. Tilt left and left wing goes UP, right wing goes DOWN. Tilt right and left wing goes DOWN, right wing goes UP. It’s beautiful watching them fight to keep the board level. Finally figured out the servo pin thing - pins 9 and 10 are the way to go, pin 8 was dead for some reason. Both servos get the same signal but since they’re physically mirrored on the plane, one goes up and the other goes down. That’s actually genius lol. Spent way too long on this……but it’s finally done.

Dev Log #4:
Pulled out the wings from my old RC plane that’s been sitting in the garage forever. Took the servos off them and tested both sides - left and right wings working smooth on pins 9 and 10. 90° neutral, 40° up, 140° down. No binding or breaking. Tomorrow we’re adding the MPU to make them actually respond to the plane tilting. Old plane parts getting a new brain.

Dev Log #3:
I GOT DATA! MPU-6050 is streaming roll and pitch like crazy on the Serial Monitor. No servos yet but the numbers are moving when I tilt the board so that’s a huge W. Next step is gonna be connecting this thing to the actual plane and seeing if the Uno can handle powering the servos without burning itself out lol .But for now we got data and that’s what matters.

Dev Log #2:
Came back today, tried the ICM again, still doesn’t work without resistors. Spent like 15 minutes on it, ran the scanner, sensor shows up at 0x68 but still hangs when I try to read data. Same problem as yesterday. Need those 4.7kΩ pull-up resistors. Gonna order them and try again later. At least the Teensy still works lol…..

Dev Log #1:
So today was the first real day of the TFCS-1 project and honestly it was a mix of hype and headache lol. I finally got my hands on a Teensy 4.1 from an old tutor of mine who lent it to me for a few weeks which is insane because this is literally the microcontroller I’ve been dreaming about for months. Plugged it in, got the orange LED blinking, uploaded a test sketch, and saw my messages pop up in the Serial Monitor so I know the board is alive and working which felt amazing. Then I tried wiring up the ICM-20948 IMU that he also lent me and uh yeah that didn’t go so well. The I2C scanner couldn’t find anything no matter what address I tried or how many times I rewired it. Tried it on an Arduino Uno first to avoid frying the Teensy and still nothing. Might be dead, might need a logic level converter, might just be my bad wiring I don’t even know anymore lol. But you know what the Teensy works and that’s what matters right now. Gonna take a break, sleep on it, and figure out the sensor stuff tomorrow.