by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Isaac A.
@tenten8401
Does anyone know where I'd find the current list of APJ_BOARD_ID's?
Is there a certain numbering convention for these or is it basically just pick whatever as long as it doesn't conflict
creating a v2 target for the Kakute F7 Mini, guess I'll prob just pick 146 for that
Isaac A.
@tenten8401
wtf
so it's already defined as an MPU6000 but the pins are named after the ICM gyro
in addition to that I've seen this code and I'm not sure if that means it'd be better to move it or what? is USART3 in third order for a reason or what?
# order of UARTs (and USB), USART3 should be in second place to map order with the board's silk screen
SERIAL_ORDER OTG1 USART1 USART2 USART3 UART4 EMPTY USART6 UART7
Andrew Tridgell
@tridge
@tenten8401 please use a number in the 1000+ range, and ask me to allocate it (need to give me the name). I'll add it to the file
Isaac A.
@tenten8401
I just tried out the regular kakute target and it works without issues (except for the weirdness in target file)
only weird thing is BRD_ALT_CONFIG doesn't exist so I can't use uart6 rx
@tridge while you're here though can you allocate one for the MambaF405 target I'm working on?
Andrew Tridgell
@tridge
@tenten8401 BRD_ALT_CONFIG param gets auto-created in a master build if you have some ALT() lines in the hwdef.dat
Isaac A.
@tenten8401
weird, the wiki says I should be using it to get that RX pin and I'm using official builds
Andrew Tridgell
@tridge
@tenten8401 MAMBA405 is now 1019
Isaac A.
@tenten8401
Sweet thanks
this is the part I was referring to, "TX only unless BRD_ALT_CONFIG=1" but the parameter just doesn't exist, tried in QGC and mission planner
seems to be in the hwdef though
Andrew Tridgell
@tridge
@tenten8401 are you talking about KakuteF4 or KakuteF7 target?
Isaac A.
@tenten8401
KakuteF7Mini
Andrew Tridgell
@tridge
that has one ALT(), so should have BRD_ALT_CONFIG param
Isaac A.
@tenten8401
yeah not seeing it, let me check one more time just to be sure
nope, got brd boot delay and all that others but no alt_config
Andy Piper
@andyp1per
I am using a KakuetF7Mini with BRD_ALT_CONFIG set and it's working fine
@tenten8401 the uart ordering for the mini was made so that the numbers in the docs match the serialn_ numbers
murata,katsutoshi
@muramura
@rmackay9 san. I am currently getting the altitude with inertial_nav.get_altitude().
For me, the change in altitude due to throttle operating values seems to be delayed.
I want to get a value that highly reflects the throttle operation value.
Which method should I use?
nikan8
@nikan8
Currently trying to get rangefinder readings to be used with LUA scripting. Could anyone suggest a proper rangefinder distance method to be exposed in bindings.desc? Thank you very much.
Don Gagne
@DonLakeFlyer
Did something change in master with respect to COMPASS_PRIMARY. Getting reports from user about QGC complaining about this parameter no longer existing. Running master SITL shows it gone as well.
Vincent Randal
@vtrandal
Hi. I just built Copter-4.0 for board=Pixhawk1. Is there any hope this will work on my SkyViper drones? The bin created from make_abin.sh is about 3MB which seems huge. What's in there? Will it even load on a SkyViper?
Mark Whitehorn
@kd0aij
why not select one of the skyviper boards?
type waf --help to see the list
Isaac A.
@tenten8401
Is there any reason on my KakuteF7Mini 5 of the outputs just won't go to dshot?
output 6 will, rest just don't, got them enabled with SERVO_BLH_MASK
image.png
image.png
Vincent Randal
@vtrandal
So I tried that [board=skyviper-v2450 (my drone)] and got this build error [/ArduCopter/toy_mode.cpp:1068:36: error: no matching function for call to 'Compass::configured()']. I can try to fix that. In 2018 board=px4-v3 (now Pixhawk1) worked on skyviper-v2450 hardware if my git clone was forked from SkyrocketToys. Today, my git clone is forked from Ardupilot/ardupilot because the 2015 ARM tool chain has been removed (making SkyrocketToys/ardupilot largely useless). My git checkout is set to Copter-4.0 (and not something older) because the 2017 Arm tool chain is still there. I can try to fix this build error or ask that the 2015 ARM tool chain be restored in hopes that's all that's broken in SkyrocketToys.
Tharindu Ranaweera
@InsanitySquared
Hey guys! I'm intrested in making a minimalist version of ardupilot. You can see more details about this endeavour and post any suggestions here: https://discuss.ardupilot.org/t/minimalist-ardupilot-firmware/57119
Andy Piper
@andyp1per
@tenten8401 I use SERVO_BLH_MASK
Isaac A.
@tenten8401
@andyp1per yeah it's enabled, just doesn't seem to work
wiki page says all 6 outputs are dshot capable and only the 6th works
Andy Piper
@andyp1per
these are my BLH settings:
SERVO_BLH_DEBUG,1
SERVO_BLH_MASK,15
SERVO_BLH_OTYPE,0
SERVO_BLH_POLES,12
SERVO_BLH_PORT,0
SERVO_BLH_REMASK,0
SERVO_BLH_TEST,0
SERVO_BLH_TMOUT,0
SERVO_BLH_TRATE,20
I have dshot on all four motors on a mini
the outputs are in groups, if you have PWM on any in a group they will all be PWM
Isaac A.
@tenten8401
SERVO_BLH_MASK is set to 63 which should be channels 1-6, OTYPE is dshot300
image.png
image.png
Isaac A.
@tenten8401
guess I should post this on the forums instead of here