Am I headed in the right direction?
Posted: Jan 5th, 2013, 7:19 pm
Here it is, my first post.
I've been trolling for a while now, mentally assembling my ROV. I've created a checklist of major components and wanted to see if (what are about to be) my first steps are steps in the right direction.
Background: I've been playing with RC planes, boats, and cars all my life, though they were most often assembled by my dad. I think I'm savvy enough to build an ROV, although programming will be a whole new world. I'm a marine biologist by trade, so it seems to be a logical next step. I'm in the US, if that helps you get a sense of parts availability/costs. I'm considering this first built as a learning step to an ultimate (future) goal (of a second or third build) of something I can launch in the Gulf of Mexico and descend to 75-100m. My goal with this build is to make it complex enough to force myself to learn the skills necessary, while keeping it inexpensive and easy enough to make it a task I can accomplish without being driven off in frustration. For instance, I'd rather be forced to do some programming than to simply utilize an off-the-shelf RC controller.
I plan to completely set up the operational components on the workbench before ever beginning to build the frame.
Here is what I'm thinking right now, with a few questions interspersed:
For my questions keep this in mind: 1) Easy, but complex enough to teach skills I can build upon 2) Relatively inexpensive compared to reasonable alternatives
Control:
I don't mind using a laptop computer as part of the control of the ROV. I have one running windows 7 that I can utilize for this purpose. I'd like the input to utilize some type of game controller/joysticks. I've read about people utilizing PlayStation controllers. It seems that the Ardunio platform has the most extensive support base for this type of applications.
1) Is it easier, or harder to utilize a laptop computer as part of the control?
2) If I'm utilizing the computer, what would be the best input controls to investigate. I think I've seen PS2 controllers mentioned a few times
3) From what I'm reading on here, it seems that if you're NOT using a computer, you'd need two Arduino's. I guess that is so one can receive and interpret the signal from the controller, then transmit it while only having to utilize three wires in the tether, then the other would decode the transmission and send the signals to the operational components on the ROV? Perhaps you could use only one on the ROV, but it would require more wires from the controller all the way to the ROV? Or is signal drop over the tether distance an issue? If I'm using the laptop computer, does this eliminate the need for the top-side Arduino?
Tether:
I'm thinking Cat5. Does this make sense? Do I need more wires than that? 2 Cat5 cables?
1) Can I go USB to Cat5 from the computer?
2) If I did go USB to Cat5, could I go back to USB in the ROV and use it like a hub to connect other components (cameras, control board, other sensors)?
3) If I'm utilizing the laptop, and on-board batteries on the ROV, do I need to send 12v power to the ROV? To power other components like lights, cameras, etc?
Batteries:
Thinking LiPo batteries on board to avoid the voltage drop issues I'm reading a lot about and to keep the tether size down.
1) What are most people running with on-board batteries? Everything? Just thrusters?
Thrusters:
I'm thinking brushless motors with brushless ESCs. I know there is a lot of debate about the use of brushless in water and especially in salt water. I have deep skepticism about these operating in salt water for long periods of time. The "test" I've seen have either been just setting a non-running motor in salt water, or by testing for a short period of time. I have a sinking suspicion that running current through these is going to do things in salt water that we haven't seen in test so far. Regardless, this is the first crack, and going brushless seems like the best way to save money and conserve on-board power. I can change direction on the second build if we find salt water tears these things apart.
I'm thinking three thrusters for this build. Two for forward and turning, and one for descending/ascending. I'm hoping that a good frame build will keep proper attitude, and I can live without having the ability to adjust attitude (in order to keep this build reasonably simple and inexpensive).
1) Anything I'm overlooking on thrusters?
Cameras:
I'd like 2 cameras. 1 looking forward, and one looking down. I'd like to be able to view a video feed from both cameras while operating the ROV. I'd like to be able to record the video. I'd use hacked LEDs for lighting.
1) If using the laptop, what considerations do I need to make? What should I be investigating? This seemed to be the best reason for using the laptop, as it would have the ability to manage the video feed and record. Is this misguided?
Other:
I think I'd like to know depth and heading. I'd like these displayed (on the laptop if I'm using it based on your guidance).
1) How much complexity should I expect this to add?
Thank you so much for your guidance. I'm looking forward to being a part of this community and learning from you!
Mel
I've been trolling for a while now, mentally assembling my ROV. I've created a checklist of major components and wanted to see if (what are about to be) my first steps are steps in the right direction.
Background: I've been playing with RC planes, boats, and cars all my life, though they were most often assembled by my dad. I think I'm savvy enough to build an ROV, although programming will be a whole new world. I'm a marine biologist by trade, so it seems to be a logical next step. I'm in the US, if that helps you get a sense of parts availability/costs. I'm considering this first built as a learning step to an ultimate (future) goal (of a second or third build) of something I can launch in the Gulf of Mexico and descend to 75-100m. My goal with this build is to make it complex enough to force myself to learn the skills necessary, while keeping it inexpensive and easy enough to make it a task I can accomplish without being driven off in frustration. For instance, I'd rather be forced to do some programming than to simply utilize an off-the-shelf RC controller.
I plan to completely set up the operational components on the workbench before ever beginning to build the frame.
Here is what I'm thinking right now, with a few questions interspersed:
For my questions keep this in mind: 1) Easy, but complex enough to teach skills I can build upon 2) Relatively inexpensive compared to reasonable alternatives
Control:
I don't mind using a laptop computer as part of the control of the ROV. I have one running windows 7 that I can utilize for this purpose. I'd like the input to utilize some type of game controller/joysticks. I've read about people utilizing PlayStation controllers. It seems that the Ardunio platform has the most extensive support base for this type of applications.
1) Is it easier, or harder to utilize a laptop computer as part of the control?
2) If I'm utilizing the computer, what would be the best input controls to investigate. I think I've seen PS2 controllers mentioned a few times
3) From what I'm reading on here, it seems that if you're NOT using a computer, you'd need two Arduino's. I guess that is so one can receive and interpret the signal from the controller, then transmit it while only having to utilize three wires in the tether, then the other would decode the transmission and send the signals to the operational components on the ROV? Perhaps you could use only one on the ROV, but it would require more wires from the controller all the way to the ROV? Or is signal drop over the tether distance an issue? If I'm using the laptop computer, does this eliminate the need for the top-side Arduino?
Tether:
I'm thinking Cat5. Does this make sense? Do I need more wires than that? 2 Cat5 cables?
1) Can I go USB to Cat5 from the computer?
2) If I did go USB to Cat5, could I go back to USB in the ROV and use it like a hub to connect other components (cameras, control board, other sensors)?
3) If I'm utilizing the laptop, and on-board batteries on the ROV, do I need to send 12v power to the ROV? To power other components like lights, cameras, etc?
Batteries:
Thinking LiPo batteries on board to avoid the voltage drop issues I'm reading a lot about and to keep the tether size down.
1) What are most people running with on-board batteries? Everything? Just thrusters?
Thrusters:
I'm thinking brushless motors with brushless ESCs. I know there is a lot of debate about the use of brushless in water and especially in salt water. I have deep skepticism about these operating in salt water for long periods of time. The "test" I've seen have either been just setting a non-running motor in salt water, or by testing for a short period of time. I have a sinking suspicion that running current through these is going to do things in salt water that we haven't seen in test so far. Regardless, this is the first crack, and going brushless seems like the best way to save money and conserve on-board power. I can change direction on the second build if we find salt water tears these things apart.
I'm thinking three thrusters for this build. Two for forward and turning, and one for descending/ascending. I'm hoping that a good frame build will keep proper attitude, and I can live without having the ability to adjust attitude (in order to keep this build reasonably simple and inexpensive).
1) Anything I'm overlooking on thrusters?
Cameras:
I'd like 2 cameras. 1 looking forward, and one looking down. I'd like to be able to view a video feed from both cameras while operating the ROV. I'd like to be able to record the video. I'd use hacked LEDs for lighting.
1) If using the laptop, what considerations do I need to make? What should I be investigating? This seemed to be the best reason for using the laptop, as it would have the ability to manage the video feed and record. Is this misguided?
Other:
I think I'd like to know depth and heading. I'd like these displayed (on the laptop if I'm using it based on your guidance).
1) How much complexity should I expect this to add?
Thank you so much for your guidance. I'm looking forward to being a part of this community and learning from you!
Mel