These are chat archives for PX4/Hardware

28th
Dec 2015
Nick Arsov
@nickarsov
Dec 28 2015 09:20
IMG_2336.JPG
IMG_2337.JPG
IMG_2342.JPG
IMG_2338.JPG
IMG_2339.JPG
IMG_2335.JPG
Lorenz Meier
@LorenzMeier
Dec 28 2015 09:56
Nice!
rohankishore21
@rohankishore21
Dec 28 2015 11:09
Hi Guys! Iam new to pixhawk. I tried to download the PADS schematic file on 3dr website, but when I tried to view the PADS file, looks empty, can someone suggest me or comment please?
Lorenz Meier
@LorenzMeier
Dec 28 2015 11:18
You’re looking at the wrong site
This is the official HW repository
Mark Whitehorn
@kd0aij
Dec 28 2015 15:00
@nickarsov Lots of good-looking new boards there. Congratulations.
Nick Arsov
@nickarsov
Dec 28 2015 15:58
Hi Lorenz, I flashed the latest bootloader ( just the RED LED from the RGB LED blinks quickly ), then tried to flash the PX4FMU_V4 file you have sent me via latest QGC, but when I choose "custom file", the QGC remains silent...no file menu to choose the *.px4 file. Please advice.
Mark Whitehorn
@kd0aij
Dec 28 2015 16:07
It won't ask for the file till you click OK
Nick Arsov
@nickarsov
Dec 28 2015 16:09
I did, but nothing happens...
the QGC says: Found device: Pixhawk ..... and nothing else follow
Mark Whitehorn
@kd0aij
Dec 28 2015 16:11
are you still using Windows?
Nick Arsov
@nickarsov
Dec 28 2015 16:11
:-) yes
Mark Whitehorn
@kd0aij
Dec 28 2015 16:15
just verified that QGC 2.8.0 stable can flash a custom px4 file to PixRacer (running on Ubuntu)
Nick Arsov
@nickarsov
Dec 28 2015 16:19
but your Pixracer is a bit different.....the newest batch has some differences as noted in the latest sch.
Mark Whitehorn
@kd0aij
Dec 28 2015 16:20
QGC has already recognized the bootloader when you set the custom file. Also, if you don't get the file selection menu, the problem is with QGC. Are you running 2.8.0 stable?
Nick Arsov
@nickarsov
Dec 28 2015 16:22
I downloaded the latest stable QGC just in case...the same result
1.png
2.png
Mark Whitehorn
@kd0aij
Dec 28 2015 16:27
maybe the popup menu is hidden behind something else?
Nick Arsov
@nickarsov
Dec 28 2015 16:28
no, just checked this
the QGC is v2.8.0-338-ged5015e(Development)
can this help?.....
3.png
Gus Grubba
@dogmaphobic
Dec 28 2015 16:33
Did you hit OK after selecting Custom firmware file…?
Nick Arsov
@nickarsov
Dec 28 2015 16:33
yes, absolutely
Gus Grubba
@dogmaphobic
Dec 28 2015 16:34
Weird. Just tried it and the file picker came up fine as expected. Mac OS.
Nick Arsov
@nickarsov
Dec 28 2015 16:35
I'm trying the first regular batch where the baro SPI is connected to the FRAM
when I disconnect the board, I have....could not create port. No such file or directory.
Mark Whitehorn
@kd0aij
Dec 28 2015 16:43
Nick, your screenshots were from the dev version. But stable doesn't work either, right?
I assume that stable has been tested on Windows
Nick Arsov
@nickarsov
Dec 28 2015 16:46
where can I find the stable....I picked this from here - http://qgroundcontrol.org/downloads
Nick Arsov
@nickarsov
Dec 28 2015 16:52
the first Pixracer with older bootloader works with QGC
I mean a board from the first revision of Pixracer
Mark Whitehorn
@kd0aij
Dec 28 2015 16:53
has the bootloader changed?
Nick Arsov
@nickarsov
Dec 28 2015 17:07
yes, I also tried the one from November and the latest Lorenz sent me.....the same result.
Mark Whitehorn
@kd0aij
Dec 28 2015 17:34
must be the rev 5 bootloader then. @dogmaphobic Is px_uploader.py bundled in with QGC?
Mark Whitehorn
@kd0aij
Dec 28 2015 23:37

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
Dec 28 2015 23:46
the param command is a mavproxy command
Mark Whitehorn
@kd0aij
Dec 28 2015 23:54
shouldn't it result in a PARAM_SET command to the vehicle?
Lorenz Meier
@LorenzMeier
Dec 28 2015 23:55
Yes, in theory
And I have used it successfully in the past
Mark Whitehorn
@kd0aij
Dec 28 2015 23:55
I must not be getting reliable transmission from vehicle -> gcs
will have to try running mavproxy on a different machine