But this topic is something i was looking for and wanted to know “How to run t200 thruster using a generic esc”.
I agree that the following parameters need to match:
Cell rating (2-7s)
Current rating (30A max)
Firmware (BLHeli_S)
Direction (Bi-directional 1100-1900 [1500 stop])
Protocol (PWM)
Is there anything else that needs to be kept in consideration, if yes can yiu please let me know?
Also in the document of basic esc, it is noted that it supports OneShot 125 protocol, but the navigator probably operates it with PWM protocol (given the pwm values ranging from 1100-1900).
So, does any oneshot125 compatible esc can be directly used instead of basic esc? *Apart from configuration of bidirectional setup.
Hi @Jarvis1310, I’ve moved your post to its own thread because it was unrelated to the original topic.
None of those are requirements for running a T200 Thruster.
You need an ESC that is capable of running a brushless DC motor, and it must be capable of supplying power within the 7-20 V range the thruster is specified to.
Bidirectional output support is necessary if you want to be able to drive the thruster both forwards and backwards (which is usually the case, but not for all applications).
The input protocol(s) supported by your ESC are only relevant to how you want to send commands to it. PWM is one-directional communication, and is reliant on analog timing of electrical pulses, but there are many different sources that can provide a servo-style PWM signal, so it’s a good versatile option if you don’t need extremely precise motor control.
If you have full control over what hardware you use to send signals to your ESCs then you have several alternative options, with different tradeoffs that may or may not be important to you.
Underwater thrusters often spin a fair amount slower than the motors used for aerial propellers (for drones and planes and the like), so you may need to configure your ESC to run well for low kV motors.
That requires some non-negligible startup power, and in the case of the Basic ESC we also:
as well as having “Brake on Stop” turned off, since water tends to slow the propellers down quite quickly anyway, and (as I understand it), it’s preferable to avoid spikes of back-EMF from trying to brake faster.
I am controlling the t200 thruster using a Blue robotics Navigator. According to what i have read about linux based autopilot boards, they dont support ESC protocols such as OneShot ans DShot. Even in the BlueOS vehicle setup page, the option/parameter named “MOT_PWM_TYPE” when set to the above protocols shows “This PWM type is not supported by BlueOS”.
Therefore i am asking, what’s the requirements in esc software/firmware/protocol aspect to run a T200 thrusters using blue robotics Navigator?
For a Navigator it is recommended to use ESCs that are controllable by servo-style PWM signals. We use 1100-1900 µs pulse durations by default for our ESCs, but other ranges are also possible (1000-2000 is common as I understand it), and can be made compatible with the autopilot using the MOT_PWM_MIN/MAX parameters.
If you’re using ArduSub or skid-steering in ArduRover the expectation is for the ESCs to be programmed as bidirectional.
The Navigator’s servo channels are controlled by a PCA9685 LED PWM driver, so for precise timing it only supports PWM outputs. It does also support on/off relay functionality, but not at rates or with timing precision that would be suitable for a serial protocol, and it has no means of accepting inputs on those pins.
As far as I’m aware only PWM will work, and that’s all we’ve tested, but you are welcome to try other output-only protocols and see what happens on an oscilloscope if you’re so inclined