Such an awesome project from you guys. I just started a new project and currently ordering parts. Got a few questions. What is the smallest board usable without image throughput?
Would a pi zero work? Otherwise a USB stick board like Intel Compute Stick CS125, that even has USB 3.
Really good to see the support and detailed awnsers given here. I am ok with Python and Linux but completely new to drones and ardupilot. If the pi zero doesn’t work I’ll try the cs125 route.
I have a very small form factor and would love to use the pi zero caus of the power consumptiom.
Very cool, building my parts list and going with the Banana first.
My use case is indoor, basically I want to fly a drone a route manual and ‘record’ the path, an afterwards let the drone follow the exact path in a (slow) given speed. I would think that with the T295 a lot of waypoints could be created. Is there groundcontrol software that would make it easy to manage this? I don’t need a full explanation but just a pointer so I don’t have to try out all of them. Any other bottlenecks you already see?
Are there plans to enhance the great work from last year using the T265 and possibly the RPi4? One thing I am not clear about - is ROS required? I just got a T265 and have built the libraries on RPi4 but, ROS is proving to be a little more challenging…
Please Help!!!
Whenever I try to take off my drone it is going straightway up very fast and finally out of control. Can not even land. I lost one drone like that outdoor. Finally, I am now testing with ropes diagonally connected to my drone but still offboard takeoff is so fast. Due to fast movement, I get “SLAM Error Speed” at the ROS node and no luck for weeks. Please guide me.
as @amilcarlucas mentioned, it’s better to create a new thread if the problem is not directly related to this thread.
however, in this case it is not necessary: the error “SLAM Error Speed” means that the Realsense T265’s tracking function has failed and the data that it is providing is no longer valid. Hence, the main issue is that the T265 could not provide satisfactory performance in your use case.
this typically happens in situations such as quick motion from static position, or if the device temporarily looks at a blank wall, or that the device moved more rapidly than expected for typical handheld motion.
@amilcarlucas and @LuckyBird thank you so much for your prompt response. I found that I was doing a silly mistake in the threshold curve. I am using QAV250 frame along with 2300kv motors + 5 inch props. After I adjust the max threshold to 70% from Flysky F6 TX and took off in AltHold and in Loiter mode the problem resolved.
The main reason I was experiencing it, due to sudden motion, which incurred Slam speed error and the co-ordinate values got some garbage values. So, due to no co-ordinate info and the copter become crazy.
If further issues occur I will open a new thread.
Thank you so much @LuckyBird for your such nice and lucid tutorial.
Susanta Sharma
PhD. scholar, NYCU (formally known as NCTU), Taiwan