×

Notice

The forum is in read only mode.
  1. Forum
  3. Development
  5. Protocol Development
  7. New Hubsan Upgraded Version on the way

New Hubsan Upgraded Version on the way

More
03 Jan 2014 17:23 - 03 Jan 2014 17:24 #17864 by SeByDocKy
Replied by SeByDocKy on topic New Hubsan Upgraded Version on the way

goebish wrote: not HOLD, HOLD1:

[channel7]
template=simple
[mixer]
src=HOLD1
dest=Ch7
curvetype=expo
points=0,0


It's what I had ... :( and not working (yet) ....

I will make another small video ...
Last edit: 03 Jan 2014 17:24 by SeByDocKy.
More
03 Jan 2014 17:29 - 03 Jan 2014 17:51 #17865 by goebish
Replied by goebish on topic New Hubsan Upgraded Version on the way

vlad_vy wrote: Probably you need to change two bits, set one to 1 and second to 0 and vice versa.


No, here's what my "Extra" firmware is doing:

packet[9] = 0x02; // this bit must always be set
packet[9] |= (1 << Model.proto_opts[PROTOOPTS_EXTRA]) & 0xff;

it only set one bit, and it's working

it's the same than:
packet[9] = 0x02;
packet[9] |= 0x01;
if Model.proto_opts[PROTOOPTS_EXTRA] is set to 0

I don't understand why it wouldn't work
Last edit: 03 Jan 2014 17:51 by goebish.
More
03 Jan 2014 17:39 #17868 by goebish
Replied by goebish on topic New Hubsan Upgraded Version on the way
I rebuilt the firmware, maybe I made a mistake sending the previous one and sent an old one, don't know, better double check:
speedy.sh/m8fzN/deviation-devo7e-Unknown.zip
More
03 Jan 2014 17:56 #17872 by SeByDocKy
Replied by SeByDocKy on topic New Hubsan Upgraded Version on the way

goebish wrote: I rebuilt the firmware, maybe I made a mistake sending the previous one and sent an old one, don't know, better double check:
speedy.sh/m8fzN/deviation-devo7e-Unknown.zip



The same ....

It's very strange ... :(
More
03 Jan 2014 17:58 #17873 by goebish
Replied by goebish on topic New Hubsan Upgraded Version on the way
Can you check in channels monitor if channel 7 > 0 with the HOLD switch set to 1 ?
More
03 Jan 2014 17:58 #17874 by SeByDocKy
Replied by SeByDocKy on topic New Hubsan Upgraded Version on the way
The "Extra" version video :


More
03 Jan 2014 18:03 #17875 by PhracturedBlue
Replied by PhracturedBlue on topic New Hubsan Upgraded Version on the way
Can you please post your .ini file?
And did you remember to change the # of channels to 7? otherwise the 7th channel won't apply.
More
03 Jan 2014 18:26 #17878 by SeByDocKy
Replied by SeByDocKy on topic New Hubsan Upgraded Version on the way

PhracturedBlue wrote: Can you please post your .ini file?
And did you remember to change the # of channels to 7? otherwise the 7th channel won't apply.


Haha I didn't :)
More
03 Jan 2014 19:09 #17879 by SeByDocKy
Replied by SeByDocKy on topic New Hubsan Upgraded Version on the way
Ok ... set to 7ch but nothing improved :( ...


File Attachment:

File Name: model5.ini
File Size:16 KB



The video I did 2h ago

Attachments:
More
03 Jan 2014 19:16 #17881 by PhracturedBlue
Replied by PhracturedBlue on topic New Hubsan Upgraded Version on the way
Your ini is still wrong.

Try this one

File Attachment:

File Name: model2.ini
File Size:2 KB


the problem is that you have trim enabled which is reuslting in a multiplicitive factor.
Attachments:
More
03 Jan 2014 21:19 #17889 by SeByDocKy
Replied by SeByDocKy on topic New Hubsan Upgraded Version on the way

PhracturedBlue wrote: Your ini is still wrong.

Try this one

File Attachment:

File Name: model2.ini
File Size:2 KB


the problem is that you have trim enabled which is reuslting in a multiplicitive factor.



Thanks :)


It's working now :)
More
03 Jan 2014 21:22 #17890 by goebish
Replied by goebish on topic New Hubsan Upgraded Version on the way
Mystery solved, thanks :)

Please share your H102D profile in the appropriate forum when it's working as you like.
More
03 Jan 2014 22:14 #17892 by SeByDocKy
Replied by SeByDocKy on topic New Hubsan Upgraded Version on the way

goebish wrote: Mystery solved, thanks :)

Please share your H102D profile in the appropriate forum when it's working as you like.



Yep :)
More
11 Jan 2014 08:10 - 13 Jan 2014 03:08 #18352 by gke
Replied by gke on topic New Hubsan Upgraded Version on the way
Additional field decodings for telemetry packets carrying the 0xe1 tag (thanks Goebish) in byte 0 for the X4 V1 are:

enum Tag0xe0 {
    TAG, 
    ROC_MSB, // ??
    ROC_LSB, // ??
    XUNK3,
    XUNK4, 
    XUNK5,
    XUNK6,
    XUNK7,
    XUNK8 
    Z_ACC_MSB, 
    Z_ACC_LSB, 
    YAW_GYRO_MSB, 
    YAW_GYRO_LSB, 
    VBAT,
    CRC0,
    CRC1
  };

  enum Tag0xe1 {
    TAG1, 
    PITCH_ACC_MSB,
    PITCH_ACC_LSB,
    ROLL_ACC_MSB,
    ROLL_ACC_LSB, 
    UNK5,
    UNK6,
    PITCH_GYRO_MSB, 
    PITCH_GYRO_LSB, 
    ROLL_GYRO_MSB, 
    ROLL_GYRO_LSB, 
    UNK11,
    UNK12,  
    //VBAT,
    //CRC0,
    //CRC1
  };
Last edit: 13 Jan 2014 03:08 by gke.
More
11 Jan 2014 10:32 - 11 Jan 2014 10:58 #18358 by goebish
Replied by goebish on topic New Hubsan Upgraded Version on the way
Thanks gke :)

Have you checked packets starting with 0xe0 on a H107 (X4 v1) ?
Last edit: 11 Jan 2014 10:58 by goebish.
More
11 Jan 2014 16:05 #18367 by vlad_vy
Replied by vlad_vy on topic New Hubsan Upgraded Version on the way
Can be unknown fields Z_ACC and YAW_GYRO?
More
11 Jan 2014 23:20 - 13 Jan 2014 09:57 #18383 by gke
Replied by gke on topic New Hubsan Upgraded Version on the way
-
Last edit: 13 Jan 2014 09:57 by gke.
More
11 Jan 2014 23:20 - 13 Jan 2014 09:59 #18384 by gke
Replied by gke on topic New Hubsan Upgraded Version on the way
Hi Vlad,

The values don't seem to change with my Hubsan V1. I have a V2 board so I will check that as well as exploring the 0xe0 tagged telemetry.


... seems like the yaw and accz may be in the 0xe0 packet...thanks Goebish.
Last edit: 13 Jan 2014 09:59 by gke.
More
13 Jan 2014 12:35 #18466 by goebish
Replied by goebish on topic New Hubsan Upgraded Version on the way
We might try to code heading hold and head free modes thanks to those data !

Well done gke :)
More
13 Jan 2014 13:32 - 13 Jan 2014 13:34 #18472 by vlad_vy
Replied by vlad_vy on topic New Hubsan Upgraded Version on the way

goebish wrote:

midelic wrote: So only 0xE1 is with voltage telemetry?


At least on the H107 (X4 v1).


With 0xE0 VBAT, H107 always show 0,2V. With 0xE1 VBAT is OK.
Last edit: 13 Jan 2014 13:34 by vlad_vy.
  1. Forum
  3. Development
  5. Protocol Development
  7. New Hubsan Upgraded Version on the way
Time to create page: 0.155 seconds
Powered by Kunena Forum
Force desktop display