DRONEFIGHTER2017 / Protocol / Intro
Modified : 2018.02.08

1. DRONE FIGHTER 2017 Introduce

DRONE FIGHTER 2017 is the firmware created to use the drone fighter in the Entry.

2. Data transfer structure.

The DRONE FIGHTER 2017 communicates with the PC either by connecting to a drone via the controller or by connecting a USB direct to the drone.

0	1	2	3	4	5	...	N-1	N
Start code		Header				Data	CRC16
Start code		DataType	Length	From	To	Data	CRC16
0x0A	0x55	-	-	-	-	-	-	-

Each item is explained as follows.

Area		Explaine
Start code		Data transfer notify
Header	DataType	Data types
	Length	Data length
	From	Transfer device's DeviceType
	To	Receiver device's DeviceType
Data		Transer data
CRC16		Header and Data check if it was delivered correctly. http://www.menie.org/georges/embedded/crc16.html

Data and the CRA16 zone use Little Endian. When Little Endian is present, If more than two bytes, low byte is front of the array. You can change it conveniently using Bitconverter in C#.

HEX value	0x1234
Array index	0	1
Big Endian	12	34
Little Endian	34	12

HEX value	0x12345678
Array index	0	1	2	3
Big Endian	12	34	56	78
Little Endian	78	56	34	12

3. Precautions in use

All devices only send data in response when requested.
If a device is specified to receive data, the device will send Ack when it is not requested.
If the data is transmitted via broadcast, If a command is not a data request but a typical one, the device that can process it runs the received command.
If the data is transmitted via broadcast a data requests, the device can be respond data. If more than one device responds to the same data, this can cause conflicts between sending and receiving data. Be careful when you use it.
Ack is not answered for the broadcast.

4. Configure parameters for serial port

Area	Setting value
Baud Rate	115200
Parity	None
Data Bits	8
Stop Bits	1

5. Driver install

If you already install DRONE FIGHTER simulater do not need additional driver.
You can install drivers from the entry hardware program.

DRONE FIGHTER 2017

Index