Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 20 13:30
    atmadeep closed #95
  • Aug 20 13:30
    atmadeep commented #95
  • Aug 20 13:17
    dogmaphobic commented #95
  • Aug 20 13:12
    atmadeep commented #95
  • Aug 20 13:01
    dogmaphobic commented #95
  • Aug 20 12:58
    atmadeep opened #95
  • Jun 11 06:35

    LorenzMeier on master

    Readme - fix devcall link (compare)

  • Jun 11 06:35
    LorenzMeier closed #94
  • Jun 11 06:34
    bkueng commented #94
  • Jun 11 00:45
    hamishwillee commented #94
  • Jun 11 00:45
    hamishwillee opened #94
  • Jun 08 09:54

    LorenzMeier on master

    Clarify FMU Open Design Usage Update entry point Minimum changes to make FMU-cen… and 14 more (compare)

  • Jun 08 09:54
    LorenzMeier closed #93
  • Jun 07 06:05
    hamishwillee edited #93
  • Jun 07 05:43
    hamishwillee synchronize #93
  • Jun 07 05:41
    hamishwillee synchronize #93
  • Jun 07 05:38
    hamishwillee synchronize #93
  • Jun 07 05:36
    hamishwillee edited #93
  • Jun 07 05:36
    hamishwillee edited #93
  • Jun 07 05:36
    hamishwillee edited #93
Nick Arsov
@nickarsov
I mean a board from the first revision of Pixracer
Mark Whitehorn
@kd0aij
has the bootloader changed?
Nick Arsov
@nickarsov
yes, I also tried the one from November and the latest Lorenz sent me.....the same result.
Mark Whitehorn
@kd0aij
must be the rev 5 bootloader then. @dogmaphobic Is px_uploader.py bundled in with QGC?
Mark Whitehorn
@kd0aij

Anybody who knows MAVproxy:

I was trying to use it to debug the PixRacer/QGC connection problem, but it doesn't want to load parameters from FMUv2 either. Best I've achieved with the v2 (the following just appeared while I was verifying that I could still graph data; don't know where the "nsh:" and "nsh>" came from and I assume the garbage characters are corrupt or unrecognized messages):

nsh: ~2M73Yk: command not found
nsh> [Kgraph ATTITUDE.roll
Mode(65536)> Adding graph: ['ATTITUDE.roll']
X|0P,Received 376 parameters
Saved 376 parameters to mav.parm

after the params loaded, I was able to display them, but not set them:

Mode(65536)> param set TRIM_PITCH .01
Mode(65536)> timeout setting TRIM_PITCH to 0.010000

Mode(65536)> param show TRIM*
Mode(65536)> TRIM_PITCH       0.000000
TRIM_ROLL        0.000000
TRIM_YAW         0.000000
Lorenz Meier
@LorenzMeier
the param command is a mavproxy command
Mark Whitehorn
@kd0aij
shouldn't it result in a PARAM_SET command to the vehicle?
Lorenz Meier
@LorenzMeier
Yes, in theory
And I have used it successfully in the past
Mark Whitehorn
@kd0aij
I must not be getting reliable transmission from vehicle -> gcs
will have to try running mavproxy on a different machine
Mark Whitehorn
@kd0aij
parameters loaded immediately running mavproxy on Ubuntu 14.04, so there seems to be a USB problem on 15.10
But set <param> value still times out.
Also, SYS_AUTOSTART displays as 0.0 even though it has integer value 4009
Lorenz Meier
@LorenzMeier
@nickarsov Is your bootloader issue persisting?
Phillip Kocmoud
@pkocmoud
Yes
Nick just sent a request via email.
Lorenz Meier
@LorenzMeier
Can you just flash via a Linux box from the shell?
Nick Arsov
@nickarsov
Hi guys. I can flash using just ST-Link utility, but need *.bin file instead
or hex file
Phillip Kocmoud
@pkocmoud
Nick, you are Windows only, correct?
Lorenz Meier
@LorenzMeier
No, I meant flashing the Firmware
Nick Arsov
@nickarsov
yes, I can flash it via ST-Link. Yes, just Windows 7/32
but ST-Link uses only bin or hex files
Phillip Kocmoud
@pkocmoud
You would have to flash the application to an offset address.
Nick Arsov
@nickarsov
yes, sure....can someone tell me the offset?
Phillip Kocmoud
@pkocmoud
Nick you have 2 issues, someone would need to extract the bin from the .PX4 and also the provide the offset.
Lorenz Meier
@LorenzMeier
I can flash fine
Screen Shot 2015-12-29 at 15.27.50.png
Using this daily build QGC version
Phillip Kocmoud
@pkocmoud
This issue is specific to the new PixRacer boards. The beta board still works fine for Nick.
Wonder if it is the Baro SPI bus switch?
Lorenz Meier
@LorenzMeier
That should not influence the bootloader
Were there any USB related changes?
Phillip Kocmoud
@pkocmoud
I have asked for guidance. The older bootloader not longer works.
Lorenz Meier
@LorenzMeier
You really need to flash the board using the proper development tools
The workflow of trying to bring up new boards using customer / consumer tools is just wrong
Phillip Kocmoud
@pkocmoud
Unfortunately that is the only feedback so far. We will need to wait then.
Lorenz Meier
@LorenzMeier
I can’t see how moving the baro would induce any sort of bootloader related change. Nick needs to go back to the schematic and ensure that there are no power or USB related changes
Mark Whitehorn
@kd0aij
Some more observations of USB behavior differences between X2 and PixRacer:
PixRacer issues nsh prompt on /dev/ttyACM0 at boot when connected to a USB3 port. No printout at boot when connected to a USB2 port, and no response to Enter key.
X2 prints nothing on /dev/ttyACM0 when connected to either USB2 or USB3 ports, but responds to Enter key with nsh prompt.
mavproxy connects properly to both PixRacer and X2 after first invoking rc.usb using serial terminal
Mark Whitehorn
@kd0aij
@LorenzMeier Has current master been modified for the changes to the new version of pixracer?
Lorenz Meier
@LorenzMeier
Not yet. Its not very useful to guess until one of the devs has hardware
The bootloader is updated
Mark Whitehorn
@kd0aij
I'm helping Nick test his with a Linux dev environment. Booting up, but of course the baro isn't working
I'd modify the source, but haven't managed to find the relevant config code yet
Mark Whitehorn
@kd0aij
many thanks. will try to get the baro working
Nick Arsov
@nickarsov
Lorenz, can you check whether the FRAM_SCK has been moved from PB13 to PB10 alternative pin?
I can't find this change in board_config