MultiWii

copterrichie wrote:Please, EOSBanbi, may I ask for the addition MP_GPS_TIME to the protocol or to expansion the MSP_SET_RAW_GPS to include the GPS Time? Reason being, the Raspberry Pi does not have a realtime clock as well as many OSDs. I can set the time zone in my application.

Thank you.

EOSBandi wrote:It's not only the question of the protocol. GPS time does not used and not decoded.

struct diyd_mtk_msg {
        int32_t  latitude;
        int32_t  longitude;
        int32_t  altitude;
        int32_t  ground_speed;
        int32_t  ground_course;
        uint8_t  satellites;
        uint8_t  fix_type;
        uint32_t utc_date; <---
        uint32_t utc_time; <---
        uint16_t hdop;
    };

BeringBullet wrote:looks like the MultiWii 2.3 navi beta4 is a bad upload only a 2,567k file

Perry wrote:Hello!
I tried to load the firmware
radio ~ hm_trp.ihx
on the two radio modules 3dr
but I do not understand how do it.
Where the files should be placed?
I might have a little help?
thanks

Perry

Imen wrote:

Perry wrote:Hello!
I tried to load the firmware
radio ~ hm_trp.ihx
on the two radio modules 3dr
but I do not understand how do it.
Where the files should be placed?
I might have a little help?
thanks

Perry

Hi perry, you should use newest 3dr radio software, then you choose "upload custom fimware" then select hm_trp.ihx from EOS

dm571 wrote:My MultiWii_2.3-navi-b4-xmas-fix doesnt work with WinGUI_2.3pre7(b4)-xmas. Neither USB nor with BT. Old version of GUI works fine with b4-xmas. Am i doing smth wrong?

dm571 wrote:Yeah, there was 57600 and both ver GUI didnt work. I changed to 115200 and old version works fine. But x-mas still reports an error. P.S. Sorry for my English..

EOSBandi wrote:

dm571 wrote:Yeah, there was 57600 and both ver GUI didnt work. I changed to 115200 and old version works fine. But x-mas still reports an error. P.S. Sorry for my English..

I can look into it in this evening. Please send me your config.h and state what kind of board are you using.

Norf wrote:Hi,

I tested the Nav Beta too today ( Xmas release )
Works fine so far.
Only thing is if you use a larger distance between 2 ponits it overshots very much.
I try to reduce max navigation speed 150 cm/s.

Tested it with the EZ-Gui Beta and all works fine.
Only when trying the POI function the copter makes crazy stuff

Norbert

Rcg4scuba wrote:Hello,
I hope this is the place to ask this; I cannot launch WinGui 1.04 or 2.1 an error pops up-

Invalid Data Options files contains invalid data around Line:7
Unable to continue!
I am running Win7 64bit

Thanks for your assistance- before posting here, I have looked/searched through this forum and others for an answer with no success.

I have checked/installed the pre-requisites listed (.Net, etc)

Again- thank you.
RG

EOSBandi wrote:If you want use WinGUI on the field without internet connection, you can cache satellite map images for a given region. To do that, zoom out to show your planned flight zone, then with ALT+left click mark the area you want to cache, then click on the FETCH MAP button. The satellite images for all zoom level are cached to the disk and available offline.

Norf wrote:Hi again,

second Testday over - short Video later!

Works fine with WinGui so far only POI Problem is the same as with EZ-Gui :

When I set a POI and the a circle arround ( in my setup today 25m circle 16WP and 1 for direction ) the copter starts to fly to first WP and then does strange things.
The Copter flies big circles and it looks like he can´t find a waypoint.
Nothing else happens. After 2 Minutes crazy flying I canceld the Mission

Is there a mistake in the code maybe?

I will post the Video later!

Norbert

EOSBandi wrote:

copterrichie wrote:Please, EOSBanbi, may I ask for the addition MP_GPS_TIME to the protocol or to expansion the MSP_SET_RAW_GPS to include the GPS Time? Reason being, the Raspberry Pi does not have a realtime clock as well as many OSDs. I can set the time zone in my application.

Thank you.

It's not only the question of the protocol. GPS time does not used and not decoded.

haydent wrote:

EOSBandi wrote:

copterrichie wrote:Please, EOSBanbi, may I ask for the addition MP_GPS_TIME to the protocol or to expansion the MSP_SET_RAW_GPS to include the GPS Time? Reason being, the Raspberry Pi does not have a realtime clock as well as many OSDs. I can set the time zone in my application.

Thank you.

It's not only the question of the protocol. GPS time does not used and not decoded.

it does not necessarily need to be decoded or used by MW, just a common format agreed apon, that could be as it is in the ublox millisecond of week format, in that case it can simply be added to the MSP

haydent wrote:Thanks. I appreciate your efforts particularly as you are busy with the gps nav work. I would not have bothered you except it seems you are likely the one heading this area of development in mw project.

Another failsafe scenario. Copter moving away from desired position, not closer. ie. due to high wind, poorly or incorrectly defined MAG, etc, craft should land + disarm or something other than flying further away.

haydent wrote:go to designated waypoint at current altitude
go to designated waypoint at given altitude

just brainstorming ...

Another failsafe scenario. Copter moving away from desired position, not closer. ie. due to high wind, poorly or incorrectly defined MAG, etc, craft should land + disarm or something other than flying further away.

yes abort flight option, as i have had a fly away in wind too

felixrising wrote:What situation requires to ignore stick inputs? Personally I think you are right the be frightened, in my opinion sticks should never be ignored under any circumstances.

-ralf- wrote:

felixrising wrote:What situation requires to ignore stick inputs? Personally I think you are right the be frightened, in my opinion sticks should never be ignored under any circumstances.

+1

-ralf- wrote:

-ralf- wrote:

felixrising wrote:What situation requires to ignore stick inputs? Personally I think you are right the be frightened, in my opinion sticks should never be ignored under any circumstances.

+1

but when "Stop Mission" is still avaiible, it's ok

Imen wrote:Hi EOS

some time (often ) when I navigate through mission map I get this error message, not sure if this a bug or not, just close and reopen the WinGUI

Imen wrote:Hi EOS

I just zooming both in and out and sometimes pan the map, like I said, not every zoom or pan event give error message.
I use the newest one b4

thanks