Sensors problem on FlyingF3

[Michal Ulianko]

Hello

I'm experiencing strange problem with Taulabs on STM32 Discovery F3. After connecting power, "Sensors" in alert widget are red and gyro's and accel's data values in UAVObject browser widget are all zero. Sometimes, very rarely, the sensors start up OK.

I have this problem on 'next' branch (from latest commit to at least several months back) and I have it also on 2013.12.12 master.
2013.04.09 master is OK, problem like that I've just described never occurs.

Does anybody have similar problem? Any advice on how to debug this problem quickly? (I can always do git dissection to find where(when) the problem start occur. But it is a long process.)

[Jörg Rohde]

Hello
I have used my FF3 several weeks ago and not tested with the latest software. But the last Master is from the December 23. Perhaps you try this one?
I use it with my Sparky, also F3 CPU.

[Francis Velasco]

i have the 2013.07.13 build and it works fine, i have not tried the latest one yet which im downloading right now

[Jörg Rohde]

Ok I have updated my FF3 with the Master from December 23. and I get an Sensor Error too.
RC Output and Sensors are red,
If I set the ArmSwitch on my TX to ARM and connct the FF3 with the NB - power the FF3 - then the init is ok and the board works.
Befor updating I use NEXT from Oktober but i cann´t say the day.

[peabody124]

Ok thanks for narrowing the window down. I created an issue https://github.com/TauLabs/TauLabs/issues/1073

Francis - you might want to step back a few versions (even to the previous master RC https://github.com/TauLabs/TauLabs/releases/tag/master-20130811 ) while we work on this

[Jörg Rohde]

And to narrow it a little bit more - I´m using PPM and HottTelemetrie on SerPort5

[peabody124]

Ok. I think I tracked it down to the bad commit. It seems to be related to the selectable sensor rates, although I'm not certain why. If you want to try it this PR https://github.com/TauLabs/TauLabs/issues/1073 reverts those changes and seems to work.

[Jörg Rohde]

Changing the Sensor rate from 760 to 380 has worked. i have waited for why the CPU with 760 was to high, the telemerie doesn´t worked with.
Do You have the Date direktly after including the selectable sensor rates, I would like to try this?

[Jörg Rohde]

Hm, I don´t understand this - I just connected my FF3 with my NB and it worked. I have nothing changed since the last test - Master 20131223 PPM HottTelemtrie Ser5.
Tx on - worked
Disconnect from NB - TX on - Connect with USB worked.
Connect 5V - connect USB worked.
TX on - connct 5V - connct USB worked - oh TX was set to armed switch to disarm
connect 5V - connect USB Sensor error!
again connect 5V - connect USB Sensor worked :-(
several time again: 10 working one not.
The last time I tested I could verify the error every time. Ok I now going out with the dogs switched the FF3 on I will see what the compass do, running around like on my Sparky or standing still.

[metRo_]

Can you try this PR https://github.com/TauLabs/TauLabs/pull/1100 and tell if it solved the problem?

[Jörg Rohde]

Can You teach me how I can get your branch easily in my local repo? I have the next  on an mac and compiling works. But I have never before used .git . I think I can make a new directory with all in but I think that is not the right way.
And also to go back to next:)

[José Eduardo S. C. Xavier]

It looks like the problem isn't solved but you can test it with:

1 - git pull origin //update local repo

2 - git checkout pr/<id> //in this case git checkout pr/1100

2014-02-05 Jörg Rohde <joerg...@t-online.de>:

Can You teach me how I can get your branch easily in my local repo? I have the next  on an mac and compiling works. But I have never before used .git . I think I can make a new directory with all in but I think that is not the right way.
And also to go back to next:)

--
You received this message because you are subscribed to the Google Groups "phoenixpilot" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phoenixpilot...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Jörg Rohde]

Sorry that it´s last so long, yesterday I got a new F3.
But the git commnd doesn´t work.
jradmins-Mac-mini:Taulabs jradmin$ git checkout pr/1100
error: pathspec 'pr/1100' did not match any file(s) known to git.
Sorry for my ignorance.

[José Eduardo S. C. Xavier]

I don't know to much about git too. Can you do a "git pull origin" to update your local repo?

--

[Jörg Rohde]

Hi, yes that works, that I use since month.
But to get another Fork or Releasestand I don´t know.

[José Eduardo S. C. Xavier]

Did you do the "git checkout pr/1100" after the "git pull origin"? Cause I try here and it works

2014-02-13 15:46 GMT+00:00 Jörg Rohde <joerg...@t-online.de>:

Hi, yes that works, that I use since month.
But to get another Fork or Releasestand I don´t know.

--

[Jörg Rohde]

Yes, here is the complete console:

jradmins-Mac-mini:Taulabs jradmin$ git pull origin
remote: Counting objects: 260, done.
remote: Compressing objects: 100% (192/192), done.
remote: Total 260 (delta 155), reused 95 (delta 65)
Receiving objects: 100% (260/260), 154.36 KiB | 0 bytes/s, done.
Resolving deltas: 100% (155/155), done.
From git://github.com/TauLabs/TauLabs
   a6ecefe..14fb413  next       -> origin/next
   fbaf2ea..51697db  qt5        -> origin/qt5
Updating a6ecefe..14fb413
Fast-forward
 flight/Modules/AltitudeHold/altitudehold.c         |  4 +-
 .../ManualControl/inc/transmitter_control.h        |  5 +-
 flight/Modules/ManualControl/transmitter_control.c |  3 -
 flight/Modules/Sensors/simulated/sensors.c         | 18 +++++
 flight/Modules/Stabilization/stabilization.c       | 93 ++++++----------------
 .../UAVOFrSKYSensorHubBridge.c                     |  4 +-
 flight/Modules/UAVOHoTTBridge/uavohottbridge.c     |  6 +-
 flight/targets/coptercontrol/fw/pios_config.h      |  3 +-
 flight/targets/discoveryf4/board-info/usb_conf.h   |  4 +
 flight/targets/discoveryf4/fw/pios_config.h        |  3 +-
 flight/targets/flyingf3/fw/pios_board.c            | 13 +--
 flight/targets/flyingf3/fw/pios_config.h           |  3 +-
 flight/targets/flyingf4/board-info/usb_conf.h      |  4 +
 flight/targets/flyingf4/fw/pios_config.h           |  3 +-
 flight/targets/freedom/board-info/usb_conf.h       |  4 +
 flight/targets/freedom/fw/pios_board.c             |  7 +-
 flight/targets/freedom/fw/pios_config.h            |  3 +-
 flight/targets/pipxtreme/fw/pios_config.h          |  3 +-
 flight/targets/quanton/board-info/usb_conf.h       |  4 +
 flight/targets/quanton/fw/pios_board.c             | 13 +--
 flight/targets/quanton/fw/pios_config.h            |  3 +-
 flight/targets/revolution/board-info/usb_conf.h    |  4 +
 flight/targets/revolution/fw/pios_board.c          | 11 ++-
 flight/targets/revolution/fw/pios_board_sim.c      | 21 ++++-
 flight/targets/revolution/fw/pios_config.h         |  1 -
 flight/targets/revolution/fw/pios_config_sim.h     |  3 +-
 flight/targets/revomini/board-info/usb_conf.h      |  4 +
 flight/targets/revomini/fw/pios_board.c            |  7 +-
 flight/targets/revomini/fw/pios_config.h           |  3 +-
 flight/targets/sparky/fw/pios_board.c              |  7 +-
 flight/targets/sparky/fw/pios_config.h             |  3 +-
 flight/targets/sparkybgc/fw/pios_config.h          |  3 +-
 ground/gcs/share/taulabs/pfd/default/Pfd.qml       |  2 -
 ground/gcs/src/plugins/config/airframe.ui          | 26 +++---
 ground/gcs/src/plugins/config/calibration.cpp      |  9 +++
 .../src/plugins/config/configvehicletypewidget.cpp | 13 +--
 ground/gcs/src/plugins/config/vehicletrim.cpp      | 27 ++-----
 make/tools.mk                                      | 16 ++--
 .../uavobjectdefinition/manualcontrolsettings.xml  |  6 +-
 .../uavobjectdefinition/stabilizationdesired.xml   |  2 +-
 40 files changed, 192 insertions(+), 179 deletions(-)

jradmins-Mac-mini:Taulabs jradmin$ git checkout pr/1100
error: pathspec 'pr/1100' did not match any file(s) known to git.

jradmins-Mac-mini:Taulabs jradmin$

[Guilhermo Santiago]

What exactly are you trying to do? There is no branch named PR...

A PR is a pull request from some branch to branch next on the main TauLabs repository. In the case of PR#1100 the branch to be merged to next is flyingf3_sensor_rate_fix from metropt repository. 

So what you need to do is to add the metropt repo as a new remote and pull from there the branch you want (flyingf3_sensor_rate_fix).

Check https://github.com/TauLabs/TauLabs/wiki/Development-Environments#wiki-adding-git-remotes-for-other-developers for more info.

[José Eduardo S. C. Xavier]

I thought was possible to checkout a PR without add user repo.

[Jörg Rohde]

Ok, and how do I get it local?
I don´t want to create my own Repo, only to get a branch from anyone local?

I have make the remote add ok.
I have make git checkout -tb F3fix metropt/flyingf3_sensor_rate_fix :
Branch F3fix set up to track remote branch flyingf3_sensor_rate_fix from metropt.
Switched to a new branch 'F3fix'

And how do I get the code?

[Jörg Rohde]

Ok forgot my question.
I have got sourcetree thats works for me.

[peabody124]

Yeah it is possible, and I'm trying to remember how I configured it. When I type "git branch -r" it lists all the PRs like "upstream/pr/699". From that I can actually type "git checkout upstream/pr/699" to test a PR without adding a user account. 

In my ".git/config" file I have this entry

[remote "upstream"]
        url = g...@github.com:TauLabs/TauLabs.git
        fetch = +refs/pull/*/head:refs/remotes/upstream/pr/*
        fetch = +refs/heads/*:refs/remotes/upstream/*

Which I think is responsible for that.I just don't remember for sure.