ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. dlee
    3. Topics
    • Profile
    • Following 0
    • Followers 0
    • Topics 13
    • Posts 60
    • Best 4
    • Controversial 0
    • Groups 0

    Topics created by dlee

    • dleeD

      Doodle Add-on board for VOXL2

      VOXL Accessories
      • • • dlee
      6
      0
      Votes
      6
      Posts
      260
      Views

      dleeD

      @Vinny Thanks a lot.

    • dleeD

      Maximum range of ToF v2

      Image Sensors
      • • • dlee
      2
      0
      Votes
      2
      Posts
      129
      Views

      ModeratorM

      @dlee we don't have those benchmarks yet, sorry. The IRS2975C based TOF should go 1-2m further than the old one

    • dleeD

      ToF v2 keeps crashing because of high temperature

      Image Sensors
      • • • dlee
      19
      1
      Votes
      19
      Posts
      1063
      Views

      M

      @Alex-Kushleyev Thanks! This is helpful. Definitely easier to overheat these than the last gen so good to have the specs on it.

    • dleeD

      Question About Installing Capacitors on ESCs for Testing

      ESCs
      • • • dlee
      9
      0
      Votes
      9
      Posts
      387
      Views

      Alex KushleyevA

      @restore , yeah, good plan..

    • dleeD

      Seeking Assistance with Motor Heating and Burnt Smell Issue on New Drone

      ESCs
      • • • dlee
      4
      0
      Votes
      4
      Posts
      261
      Views

      Alex KushleyevA

      @dlee , that is great to hear!

      Since lowering ESC kp and ki to zero helped, it may mean one of the several potential issues outside of ESC:

      the flight controller (gyro) is measuring too much vibration from propellers (is there vibration dampening in your design?) your attitude controller Derivative gain may be too high, causing the noisy gyro data to be amplified and sent to motors

      However, if the vehicle is flying well right now, perhaps you do not need to do anything else. Tuning down the ESC response acts as a low pass filter that filters out the noisy RPM commands.

    • dleeD

      Issue with ros-melodic-cv-bridge and voxl-vision-hub conflict on VOXL2

      ROS
      • • • dlee
      8
      0
      Votes
      8
      Posts
      729
      Views

      Zachary Lowell 0Z

      Hi @dlee and @smilon so if you are installing your vision_opencv into sudo, then the conflicts will wipe out a ton of MPA and SDK programs. This is highly recommended NOT to be done. Instead either use docker, or leverage the package as a third party in a virtual environment or something along that nature.

      voxl-vision-hub should be on target from the SDK installation:

      voxl2:/$ sudo apt-get install voxl-vision-hub Reading package lists... Done Building dependency tree Reading state information... Done voxl-vision-hub is already the newest version (1.7.3). voxl-vision-hub set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 37 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used.

      However, most likely had the deb wiped or reconfigured when installing the opencv you were trying to leverage. Provided you guys are on sdk 1.1.2, you can just go into the tarball that has since been untarred and adb push the voxl-suite/voxl-vision-hub deb to the voxl2 and then do a sudo dpkg -i voxl-vision-hubXXXDEB - that will install it back onto the system. The other option is to either reflash or do a sudo apt-get upgrade which would pull the most recent debs from the modalAI apt repository on the cloud.

      Let me know if this helps either of you!

    • dleeD

      Rotating imx678 hires sensor

      Ask your questions right here!
      • • • dlee
      1
      0
      Votes
      1
      Posts
      131
      Views

      No one has replied

    • dleeD

      Device "wlan0" does not exist

      Ask your questions right here!
      • • • dlee
      4
      0
      Votes
      4
      Posts
      345
      Views

      tomT

      @dlee So you shouldn't expect to see a wlan0 as you have no WiFi add-on.

      But you should expect to see either a usb0 or eth0 network interface from the Microhard modem enumerating. Did you run through the voxl-configure-modem steps for Microhard?

    • dleeD

      ESC Calibration

      ESCs
      • • • dlee
      11
      0
      Votes
      11
      Posts
      848
      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

      2dd75e2f-f722-464d-be82-5548568ec25b-image.png

    • dleeD

      Autotune Feature in PX4 1.14-dev Version for Sentinel Drone (VOXL2 Board)

      Ask your questions right here!
      • • • dlee
      12
      0
      Votes
      12
      Posts
      490
      Views

      Eric KatzfeyE

      @dlee Sent!

    • dleeD

      Color Issue with New Camera Replacement on VOXL2 Board

      FAQs
      • • • dlee
      5
      0
      Votes
      5
      Posts
      413
      Views

      dleeD

      @Chad-Sweet I changed some parameters in voxl-camera-server.conf. I replaced "ae_mode" from lsp to modal. After changing it, I typed voxl-send-command` to calibrate color. That command didn't work and exposure and gain didn't changed. Do you have any advice? Or Is there a camera driver to tune color?

    • dleeD

      ADB Connecting Issue with VOXL2 Board

      VOXL 2
      • • • dlee
      35
      0
      Votes
      35
      Posts
      2280
      Views

      VinnyV

      Hi @dlee
      Can you please double check SW2. From that photo you posted, it seems as if it may stay be in the "ON" position, which would keep it in "EDL" mode and show up as "QUSB_BULK..." instead of an ADB debug device.
      Please be sure to follow this step carefully when performing QDL updates:
      https://docs.modalai.com/voxl2-qdl/
      e7393327-f780-48b8-8b20-4c18a36639ff-image.png
      We do not have many HW failures on Voxl2 in the field from routine use, so to have one so soon is surprising. However, if you are confident you are following all instructions and still wish to RMA it, we'll test it again to check for all basic functionality and debug the root cause of the failure, if any, and prompt you for further actions.
      Thanks!