by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 02 05:35
    jjatienzo commented on a433340
  • Jun 18 07:00
    juvinski opened #11
  • May 11 06:27

    mirkix on master

    Install python future with apt … (compare)

  • May 11 06:17

    mirkix on master

    Remove prebuild ArduPilot (compare)

  • Jul 27 2019 14:05
    HomeLH commented #45
  • Jul 21 2019 16:11
    mirkix commented #45
  • Jul 21 2019 16:11
    mirkix commented #45
  • Jul 21 2019 02:52
    HomeLH edited #45
  • Jul 21 2019 02:51
    HomeLH opened #45
  • Apr 09 2019 20:21
    mirkix commented #44
  • Apr 09 2019 20:21

    mirkix on master

    Add git pull instructions and c… Merge pull request #44 from Ard… (compare)

  • Apr 09 2019 20:21
    mirkix closed #44
  • Apr 06 2019 16:09
    Ardustorm commented #44
  • Apr 06 2019 15:50
    Ardustorm opened #44
  • Mar 18 2019 04:16

    mirkix on master

    Update ArduPilot (compare)

  • Jul 10 2018 16:36
    jackcarrozzo commented #38
  • Jul 10 2018 16:19
    awright424 commented #38
  • Jul 10 2018 16:17
    jackcarrozzo commented #38
  • Jul 10 2018 16:17
    jackcarrozzo commented #38
  • Jul 10 2018 16:17
    jackcarrozzo commented #38
awright424
@awright424
hmm. wonder why
if you do have a student address email them before purchasing
they were pretty good about the student discount
considered buying a tx1 with a student discount but it was still so much. I have been waiting on the nano. I want to see more be done with it. other than emulators and stationary opencv projects
pablogranolabar
@pablogranolabar
well they finally stabilized the design
i had started working on a carrier board for it last year, just prior to the whole pandemic thing
then they changed the hardware spec three times without notification
but now with the most recent revision, the SOM module is pin compatible with the Xavier NX
which is probably 6X the performance of the nano SOM
So building any design around the carrier board reference specification guarantees pin compatibility with the Xavier NX as well
which is a Volta-class womping GPU
awright424
@awright424
if you guys need someone to test a board. I volunteer. lol
pablogranolabar
@pablogranolabar
haha ok
just bought one of those navio2's. I'll let you know how that goes.
awright424
@awright424
now you have me wondering how much will actually need to be changed on ardupilot besides compiler etc as its a different target to get the navio2 board working with jetson nano
pablogranolabar
@pablogranolabar
In theory it should just be a build of ardupilot on the Nano
things get wonky when cross compilation toolchains are required
both rpi and nano are ARM targets
and that navio2 environment is based on ROS which the Nano natively runs
so it might not be that big of a deal to port.
So in theory just add ESCs and a Crossfire TX
awright424
@awright424
I think you would need to have a target for the board though as some things would be different including the gpio header files
Vinicius Juvinski
@juvinski
hi @luminize , are you using bbbmini or blue? the blue you should use the dsm connector because the pru is attached to serial4, on blue you need to connect on a serial port and change the code under RCIN on linux folder.
Vinicius Juvinski
@juvinski
hi guys, just for resume, the main difference between a lot of linux version boards, until I could see. one thing is running an RT kernel, this mean you have a better response in process, but in true, linux is not a real time operating system following all the principles of real time operating systems.
this can be painfull when you have a high load average on the operating system you can have problems in timings, so this is the main advantage of beaglebone boars. how the pru is the responsible for the input and output, the timings are not affected by the operating system bottlenecks. for instance, I start using bbbmini since 2015, and since them there are version of boards - pixhawk, pixraver, pixhawk 2, cube and the time is passing the this boards are having limitations, and beaglebones still compatible with all code in ardupilot.
regarding the nano, I recommend to use as a companion computer - I have a blue + nano in my research robot - the nano is responsible for the IA - inferences and decisions of paths( in true is a robot that follow people and a ball called bolt)
and the beaglebone cannot deal with both operations - and in my opinion even nano cannot deal both activities ( ardupilot + IA)
Vinicius Juvinski
@juvinski
I'm fighting with 2 battles - cape for pocket - I received the boards on last monday and there is something wrong with the IMU - Or I made a mistake on my circuit or the change to use the icm20948 is not easy I was expeting
and dhot I'm think I
Im having problems with timings - if I send a 1400 value to esc, the motors is running at 60%
is I put a value of 1700 is running at 45% of speed and if I put 2000 is running at full speed.
awright424
@awright424
the icm issues I assume is after changing pin configs and compiling for pocketpilot I would assume. In all honesty that was why I went with breakout boards because I am not skilled enough currently to do more
pablogranolabar
@pablogranolabar
Hi @juvinski, it's nice to meet you! RT kernel provides all of the preemptive locking you mention, sufficient for motor and servo control without the need for a companion computer. But that is the question I have, has the RT support within ardupilot kept up with the BBBMINI targets which use the PRU for sensors?
Vinicius Juvinski
@juvinski
Hi @awright424 in true I research of how to solve the 1.8 volts and the snl74 recommended by Texas kill the spi interface, I removed the snl and I’m trying right now mosfets for level converter - but with that too I’m struggling with the fim support inside the ardupilot
Hi @pablogranolabar nice to meet you too. The rt kernel in true allow a rt but not a rt :smile:
Vinicius Juvinski
@juvinski
If for some reason you have a high load you can have problems in the scheduler and some tasks cannot have the attention of the kernel and you can have problems, on a flying machine this can be dangerous. There are a lot of codes around the web using beaglebone and the pwm outputs to fly - not using pru
Today the pru is used for Rc input and rc output, you can read sensors using pru but today there is no support for that in ardupilot, but the easier way to do that is to write a driver for pru sensor
For instance you can create a pru driver to read and write spi sensors
And create a new interface like baro - ms5611 - using pru to access the sensor - with that you can simplify your implementation instead to rewrite all code necessary to interface with the sensor
Bas de Bruijn
@luminize
Hi @juvinski I’m using a a beaglebone black with the bbbmini-pcb
awright424
@awright424
@luminize what model receiver is it
that would be more helpful. but in the past i have spektrum/dsmx satellite receivers from orangerx and i have a spektrum one. but havent used them in years due to newer smaller receivers
that was with bbbmini as well
@juvinski you would think that level shifter would work for what it is rated for.
Vinicius Juvinski
@juvinski
in true the main problem I see is not the level, is the comunication. if you look the blue schematic, the dsm port is using the uart4, in case of bbbmini all rcin is directly connected to PRU
I was looking the blue code and tou have

static RCInput_AioPRU rcinDriver;

elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_BLUE

static RCInput_Multi rcinDriver{2, new RCInput_AioPRU, new RCInput_RCProtocol(NULL, "/dev/ttyO4")};

elif CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_NAVIO || \

  CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_ERLEBRAIN2 || \
  CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_BH || \
  CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_DARK || \
  CONFIG_HAL_BOARD_SUBTYPE == HAL_BOARD_SUBTYPE_LINUX_PXFMINI

static RCInput_RPI rcinDriver;

Vinicius Juvinski
@juvinski
in case if blue there is a serial port attached to the oru, maybe you on mini can choose one serial port (uar 4 or 5) and connect your receiver and change this file to use this serial port on the pru
awright424
@awright424
@juvinski maybe you can help I have a gps attached to ttys02 and can't seem to get it connected. i have tx connected to rx from the gps and also connected the sda and scl pins for the copmpass. But am not getting anyting. I have added it to the parameters for arducopter -B /dev/ttysO2 and still get nothing