I'm glad that we were on the same page with repurposing J2 for the ESC telemetry! Using a PWM at 100% or 0% is a great idea to avoid reconfiguring the pins.
@Alex-Kushleyev said in VOXL 2 IO - 8 PWM channels & Futaba (SBUS) Rx:
Please give me a few days to check a few things, mainly to make sure that we can do 5 dshot and 3x pwm (1 pwm used as gpio)
Have you confirmed the status of mixing dshot & pwm as well as the possibility of 5 dshot channels?
Alex
Thank you for the resource! We certainly had some confusion regarding dshot, bi-directional dshot, and esc telemetry interfaces.
In the long term, we will need to obtain all of the available telemetry via the UART telemetry interface. The telemetry interface is something we will have to account for in a later hardware revision in a month or two.
We are developing a quick & dirty Rev 1 platform right now, so we will forgo the ESC telemetry & dshot for the time being.
On Rev 2 of our hardware, I will be looking to incorporate dshot control (5 channels) and the serial telemetry (5 channels). From the telemetry, we want RPM, voltage, current, temp - all the bells & whistles.
So, the topic of discussion now is less about telemetry (as I will have to create a design in Rev 2 to accomodate our telemetry needs) and more about the capabilities of the M0065 moving forward.
M0065 needs on J1 include
I may also look into potentially repurposing J2
@Alex-Kushleyev , I appreciate your effort to understand our needs.
I'm only vaguely familiar with dshot. To my knowledge, bi-directional dshot makes use of 1 wire for control & telemetry with 16-bit data packets for control (idk how big the telemetry packets are).
I am not sure of the difference between bi-directional dshot & uart-based telemetry aside from the fact that the uart telemetry uses a separate telemetry wire.
As of right now, we would need:
I haven't dealt with the various ESC control & telemetry protocols yet. If you have any information to add to or correct my understanding, I would be happy to learn more.
Alex
@Alex-Kushleyev , we did consider using ModalAI's ESCs, but our configuration is now a lift-cruise (5 motors) and we will be using the APD 40F3.
@Alex-Kushleyev , we like the ability to have controls and telemetry on 1-wire and, most importantly, it simplifies ESC calibration. We don't want our customers to deal with ESC calibration in the field.
@Alex-Kushleyev , Are there any plans for the VOXL 2 IO Module to support DShot?
That's great! Thank you @Alex-Kushleyev
I want to drive 5 motors and 2 servos from the VOXL 2 IO module.
I saw that the latest firmware only supports 4 PWM channels for now and am curious if the firmware development for this module is a high priority, or, rather, is the ModalAI team expecting to push out a new firmware to support 8 PWM channels soon? Soon being within April.
This is a necessary function for my platform.
Additionally, I want to connect a Futaba receiver to the RC SBUS port on the VOXL 2 IO module at J3; however, the Futaba is a 5V system (power & signal) and its SBUS is inverted from the FrSky SBUS.
Is it currently necessary for me to step down and invert the signal before connecting the Futaba Rx to J3 of the VOXL 2 IO module?