ArduPilot / ArduPilot/SiK

MAVLink packet encapsulated in Sik frame

Open
#90 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
343
Forks
245
PR merge metrics
No merged PRs in 30d

Description

I am using rfd900 radio for communication between my drone and system, Firstly on both sides I used rfd900 and was able to get the data correctly on the system. I was manually serializing and sending the data from transmitter side and reading it on Putty on the receiver side. Now I am using plutoSDR on the receiver side and to get the IQ data. I am running a MATLAB code that generates a CSV file which then I give input to URH and generate a binary data file, Now I am checking the binary file manually to verify Whether I am getting the data correctly, So yes there were Sik frames present in the binary file and was able to extract preamble, sync1, sync2, netID, length fields correctly but the payload of it contains different data then MAVLink. but the Sik payload contains an MAVLink packet. Does anyone have any idea of it? I am sharing a sample packet below that I extracted from the binary file
[0101010101010101010101, 2d, d4, ff f8, 10, 9a 10 8c 33 25 e4 7d d0 24 70 97 6f 08 5a c7 83, ff, ff ff]
[preamble(22 bits), Sync1(1 byte), Sync2(1 byte), NetID(2 bytes), Payload_length(1 byte), Payload, Trailer(1byte), CRC(2 Bytes)].

Contributor guide

No contributing guide indexed for this repository

Research direction

No repository file or test is named. Begin by reproducing the packet extraction from the MATLAB CSV through URH and compare the sample with SiK framing and MAVLink packet documentation; the issue needs a confirmed explanation of the payload difference before implementation can be defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, matlab
Domain
embedded-iot, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.