Skip to content

ESCs, Sensors and Accessories

413 Topics 2.4k Posts

ESCs, image sensors, ToF and tracking cameras, Microhard and cellular modems, power modules, GPS and other add-on boards.

  • Issues with Microhard connection and VOXL 2

    microhard
    28
    0 Votes
    28 Posts
    8k Views
    Jeremy FrederickJ
    @AP123 What was the resolution to this issue? My team is experiencing a similar problem. Were you able to access the microhard web portal through the VOXL 2?
  • IMX 678 Camera Color Problem

    Unsolved image-sensor
    4
    1
    1 Votes
    4 Posts
    1k Views
    E
    @mkriesel I wonder if that is the reason why IMX678 product on modalai show as out-of-stock at the moment. I contacted FRAMOS and they told me that they did not develop the driver for the sensor but modalai probably did it themselves.
  • Eight MSU-M0113 Connections

    Unsolved image-sensor
    2
    0 Votes
    2 Posts
    577 Views
    ModeratorM
    @RykerBarthold To connect 8 concurrently would require a significant amount of kernel and driver level modifications
  • ESC cuts out on high RPM

    Unsolved esc
    12
    0 Votes
    12 Posts
    2k Views
    Alex KushleyevA
    OK, quick update.. I did a quick test.. ramp from 0 to 100% power runs fine on ID3, see image below. optical encoder test was good, i did 3 measurements : ESC: 8040, 11800, 1850rpm, tachometer 8035, 11810, 18500. (rounded to closest 100rpm). The optical tachometer was very very close to reported rpm of the ESC. I used the following command to do a quick ramp test: ./voxl-esc-spin.py --id 3 --power 100 --ramp-time 4.0 --timeout 5.0 --enable-plot 1 (btw, i just updated voxl-esc on dev branch to plot the total current, since M0129 does not have individual current measurement, but if you test one motor at a time, you will get current for one motor) got to about 33000 rpm at 100% power, 14.8V, about 5.8A current.. More details will follow as I tune for RPM control. [image: 1696005724291-0867e8c5-fa0a-4c21-9d2a-58edb1adcb2a-image.png]
  • ESC Mini 4 in 1 - params crc

    Unsolved esc
    6
    2
    0 Votes
    6 Posts
    1k Views
    Alex KushleyevA
    @0x45, Great to hear! Sorry again about the bug and thank you for reporting it. Alex
  • Microhard Settings

    Unsolved microhard
    1
    0 Votes
    1 Posts
    616 Views
    No one has replied
  • Quectel 5G modem firmware version compatibility

    Unsolved quectel 5g modem cellular
    1
    0 Votes
    1 Posts
    883 Views
    No one has replied
  • This topic is deleted!

    16
    0 Votes
    16 Posts
    46 Views
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    7 Views
    No one has replied
  • Microhard pmddl2450 long range testing

    Unsolved microhard
    9
    0 Votes
    9 Posts
    6k Views
    tomT
    @Mastermind This is great info! Thanks for sharing!
  • IMX 678 IMX 412 LED Meaning

    Unsolved image-sensor
    2
    0 Votes
    2 Posts
    690 Views
    VinnyV
    Hi @sspiller This LED, D6, is an indicator that all power supplies for the board are ON (and GOOD) and the image sensor is OUT OF Reset. [image: 1692925189378-e5f4c9b6-8d8a-4346-a0ce-833bf912f621-image.png] When you see it toggling OFF, it implies the VOXL/VOXL 2 is holding the image sensor in reset.
  • 0 Votes
    10 Posts
    3k Views
    Eric KatzfeyE
    @Mastermind In our next release (SDK 1.0.1) we will have the ability to use a UART on the DSP (assuming px4 isn't running on VOXL2) from the applications processor specifically for the use case of running an external flight controller through it.
  • Image quality difference between Voxl and Voxl2

    Unsolved image-sensor
    3
    4
    0 Votes
    3 Posts
    931 Views
    Gerhold Ten VoordeG
    @modaltb, Is there any news regarding this issue? Are you able to reproduce this phenomenon?
  • M0113 Image fipped

    Unsolved image-sensor
    1
    0 Votes
    1 Posts
    475 Views
    No one has replied
  • ESC Calibration

    Unsolved esc
    11
    0 Votes
    11 Posts
    4k Views
    Alex KushleyevA
    @dlee , sorry for the delay. Just to clarify, it is possible that your CW and CCW propellers are not exactly the same, therefore the CW and CCW motors are showing slightly different response to calibration. In this case we can calculate an average for this calibration and use that for all 4 motors. I modified the script to calculate the quadratic fit for all four calibration results together. import numpy as np import plotly.graph_objects as go rpms = np.arange(0,13000) #rpm range for the quadratic fit cals = [] fits = [] all_fits = [] #enter the calibration results from each motor cals.append([7.53669159958e-06, 0.336081465707, 112.878194918]) cals.append([2.9479165331e-06, 0.37353561309, 35.6265065345]) cals.append([8.8413818561e-06, 0.3256003514, 132.362831923]) cals.append([7.1523119742e-07, 0.405821707061, -98.2189291548]) fig = go.Figure() for idx in range(len(cals)): fit = np.polyval(cals[idx], rpms) fits.append(fit) fig.add_trace(go.Scatter(x=rpms, y=fits[idx], name='Fit %d'%idx)) #plot each fit #create an array that contains points sampled from each curve #and perform a polynomial fit on all the data to find the average all_data = np.array(fits).flatten('C') all_rpms = np.array([rpms,rpms,rpms,rpms]).flatten('C') #evaluate the average poly fit ply = np.polyfit(all_rpms, all_data, 2) av_fit = np.polyval(ply, rpms) #print the average fit coefficients print('Average Fit coefficients:') print(' pwm_vs_rpm_curve_a0 = ' + str(ply[2])) print(' pwm_vs_rpm_curve_a1 = ' + str(ply[1])) print(' pwm_vs_rpm_curve_a2 = ' + str(ply[0])) #plot the average fig.add_trace(go.Scatter(x=rpms, y=av_fit, name='Average Fit')) #finalize and show the figure fig.update_layout(title='Motor Voltage vs. RPM') fig.update_xaxes(title_text="RPM") fig.update_yaxes(title_text="Motor Voltage (mV)") fig.show() It results in the following plot and average coefficients. You can enter these coefficients into your custom esc parameters xml file. Average Fit coefficients: pwm_vs_rpm_curve_a0 = 45.66215105517507 pwm_vs_rpm_curve_a1 = 0.36025978431449995 pwm_vs_rpm_curve_a2 = 5.01030529655002e-06 [image: 1692214971344-2dd75e2f-f722-464d-be82-5548568ec25b-image.png]
  • New visible cameras not showing up in SW

    Unsolved image-sensor
    3
    0 Votes
    3 Posts
    573 Views
    ModeratorM
    @Davon-Prewitt Can you please take a picture of your setup? Usually when this happens too many extension flex cables have been used and the system is on the margin
  • IMX412 full resolution

    Unsolved image-sensor
    6
    0 Votes
    6 Posts
    1k Views
    modaltbM
    @Gerhold-Ten-Voorde hi @Gerhold-Ten-Voorde yes this snapshot resolution should be supported now as well. I will send an email to you with a link to a nightly build to try out! Thanks! -Travis
  • IMX678 Supported Resolutions

    Unsolved image-sensor
    2
    1 Votes
    2 Posts
    604 Views
    modaltbM
    Sorry for the lag @brycek, we have some pending updates that clean up streaming and add support for full resolution. Let me know if you're up to try any pre-release software and we can try to get you a test build to validate things are OK for you now.
  • NDAA USB Cameras

    Unsolved image-sensor
    2
    0 Votes
    2 Posts
    509 Views
    tomT
    @wilkinsaf I came across this article from Logitech: https://www.logitech.com/en-us/video-collaboration/resources/think-tank/articles/taa-ndaa-compliant-products.html Their webcams have worked well for us in the past so I'd think one of the mentioned products would work.
  • Performance VOXL Mini 4-in-1 ESC

    Unsolved esc
    2
    0 Votes
    2 Posts
    626 Views
    Alex KushleyevA
    Hello @floooH Sorry about that, we will update the performance section soon. The mini ESC has been tested at 16V 15A continuous for 1 minute (15A per each channel, so 60A total). The test condition was under full air flow of 5" tri-blade propellers spinning at around 20K RPM and the temperature of ESC (measured by the MCU) was around 80 degrees C. You generally want to keep your ESC under 100C (temperature is measured by the sensor inside each MCU and reported via ESC feedback). The maximum voltage is 4S (up to at least 18V is safe). Maximum burst current at least 30A per channel (for few seconds) Even though the ESC can handle pretty large currents, due to its small form factor you need to be careful and watch the ESC temperature when you are designing / testing your drone. Small PCB of the mini ESC does not have much area for heat dissipation, so good airflow is required for large current flows. So the ESC is unlikely to break from over current (within reasonable range) but it could overheat if it is not appropriately cooled. In general we recommend the mini ESC to be used on drones < 750g, where you should not have much problem at all with heat dissipation even with minimal cooling. But for any larger drone or racing applications you will need to perform testing to ensure the ESC can stay < 100 deg C (ideally around 60-80C during the whole flight). I hope this helps, let me know if you need more info Alex