MSP protocol documentation

This forum is dedicated to software development related to MultiWii.
It is not the right place to submit a setup problem.
Software download
Post Reply
crazyal
Posts: 84
Joined: Tue Sep 04, 2012 11:25 pm

Re: MSP protocol documentation

Post by crazyal »

Crashpilot1000 wrote:Oh, yes shure.

Thats why it reads here http://code.google.com/p/afrodevices/so ... board.h#37:
// Chip Unique ID on F103
#define U_ID_0 (*(uint32_t*)0x1FFFF7E8)
#define U_ID_1 (*(uint32_t*)0x1FFFF7EC)
#define U_ID_2 (*(uint32_t*)0x1FFFF7F0)


Even the comment shows Its intend: Identify the CPU and not for some softwareversion. MSP_IDENT would have been sufficient for versioning.
I already removed that stuff for the next version, once I understood the real intend. Anyway I keep my source public at known places, others burn everything (docu&code) and wait for someone to ask for it.


you are too fucking paranoid.. okay now let's think about a scenario where a unique device ID might be useful..
what about if you have more than one naze32/multiwii board or whatever.. and you have different settings on each board/copter. With a unique ID you could tie every setting to a copter and possibly restore stuff if it gets lost and/or reduce errors on the user side. This is one thing I could think of. Use your imagination. There are quite a few other use-cases for sure.
I mean it really makes zero sense using that stuff for some kind of copy protection of OPENSOURCE-SOFTWARE.
Additionally TC doesn't even have his own GUI and cGießens stuff is just a copy of MultiWiiWingui.
Seriously I don't get why you have to SPAM the forums with such fucking nonsense...
Oh i forgot there is going to be a naze64ultrapro for 1000$ which will make use of this and will crush DJI :mrgreen:

User avatar
ezio
Posts: 827
Joined: Sun Apr 01, 2012 11:03 pm
Location: Paris
Contact:

Re: MSP protocol documentation

Post by ezio »

Could you guys focus on the TOPIC ?

Alexinparis
Posts: 1630
Joined: Wed Jan 19, 2011 9:07 pm

Re: MSP protocol documentation

Post by Alexinparis »

ezio wrote:Hi
Could we have a file with protocol decryption which will be updated when there are the changes in MSP protocol ? (something like this https://www.dropbox.com/s/m1ssij26q61cp94/protocol.ods )

Or could we have a descryption in the Protocol.cpp ?
it is frustrating to find what the values means if they labeled like this:

Code: Select all

struct {
       uint16_t a,b,c,d,e,f;
       uint32_t g;
       uint16_t h;
       uint8_t  i,j,k,l;
     } misc;

come on, can't you use normal names ? :|
Bart


Hi,

Here is a first draft based on your doc.
Attachments
protocol.zip
(15.52 KiB) Downloaded 196 times

User avatar
ezio
Posts: 827
Joined: Sun Apr 01, 2012 11:03 pm
Location: Paris
Contact:

Re: MSP protocol documentation

Post by ezio »

That is perfect!
Thank you very much Alex!
Could we, from this point, put the changes in the protocol in this thread with some decryption ?

User avatar
Hamburger
Posts: 2578
Joined: Tue Mar 01, 2011 2:14 pm
Location: air
Contact:

Re: MSP protocol documentation

Post by Hamburger »

How about discussion here and final documentation in the wiki?

User avatar
ezio
Posts: 827
Joined: Sun Apr 01, 2012 11:03 pm
Location: Paris
Contact:

Re: MSP protocol documentation

Post by ezio »

I found a bug in a documentation

should be

MSP_STATUS
global_conf.currentSet - > UINT8

timecop
Posts: 1880
Joined: Fri Sep 02, 2011 4:48 pm

Re: MSP protocol documentation

Post by timecop »

I found a bug in documentation (and most of the settings)
Their range of values is not documented.
Things that come to mind:
conf.mag_declination (what is its value in processing? why is it /10 there? what?)
various vbat*scale/min/max related shit. they seem to be getting * 10 / 10 stuff in various places. why.

Alexinparis
Posts: 1630
Joined: Wed Jan 19, 2011 9:07 pm

Re: MSP protocol documentation

Post by Alexinparis »

ezio wrote:That is perfect!
Thank you very much Alex!
Could we, from this point, put the changes in the protocol in this thread with some decryption ?


Hi,
I added a page here:
http://www.multiwii.com/wiki/index.php? ... l_Protocol

I hope it will be a better basis to discuss&correct things

Alexinparis
Posts: 1630
Joined: Wed Jan 19, 2011 9:07 pm

Re: MSP protocol documentation

Post by Alexinparis »

timecop wrote:Things that come to mind:
conf.mag_declination (what is its value in processing? why is it /10 there? what?)
various vbat*scale/min/max related shit. they seem to be getting * 10 / 10 stuff in various places. why.

mag_declination is in 1/10 degree. /10 is used because heading is in degree after IMU computation
vbat /10 and * 10 is used only in GUI, no ? It's just to display something in volt with its fraction

cGiesen
Posts: 188
Joined: Wed Jul 18, 2012 7:53 am
Location: Bochum, Germany

Re: MSP protocol documentation

Post by cGiesen »

I like to see a command like
MSP_FIRMWARE

Today there is no way, to see witch firmware is used on the board.

timecop
Posts: 1880
Joined: Fri Sep 02, 2011 4:48 pm

Re: MSP protocol documentation

Post by timecop »

I suggested extension to return firmware version/build/something months asgo, and it was ignored.

cGiesen
Posts: 188
Joined: Wed Jul 18, 2012 7:53 am
Location: Bochum, Germany

Re: MSP protocol documentation

Post by cGiesen »

I know. I hope they forgot that and put it in now ;)

I really don't know how this project work.
What is needed to got things like this?

timecop
Posts: 1880
Joined: Fri Sep 02, 2011 4:48 pm

Re: MSP protocol documentation

Post by timecop »

I suspect you will need to make a patch to 8bit trash + multiwiiconf to make use of new extension/MSP
and wait for it to be either applied or ignored.


EDIT:
Looks like ignoring version / firmware request has been going on for a while, i just found this old post
viewtopic.php?f=8&t=2145&p=19775&hilit=firmware+version#p19775
requesting same thing...

Post Reply