johnwalicki / node-red-tello-control Goto Github PK

Node-RED flows to control the Ryze Tello Drone

License: Apache License 2.0

tello tellodrone node-red ryze-tello-drone dji djitello drone ryze nodejs

node-red-tello-control's Introduction

Node-RED-Tello-Control

Node-RED flows to control the Ryze / DJI Tello Drone

This repository contains Node-RED flow examples that demonstrate how to control the DJI Drone using the Node-RED visual editor.

Introduction

Flying the Tello drone with the Android/iOS mobile apps is amazing fun but the Tello has another fantastic feature. The Tello includes a programming interface that developers can use to send commands to control the drone. Programming APIs can also receive telemetry and video stream data from the Tello. Ryze and DJI provide SDK programming documentation to help developers learn how to program the drone. Tello programming has grown so popular that they have released a Tello EDU version that has additional SDK documentation. An entire open source community has formed around programming the Tello. If you are a developer, a good place to start is the TelloPilots forums. There are dozens of github repositories that have programming examples written in Python, Go, Swift and Node.js. This Node-RED implementation was inspired by the Tello Scratch node.js example.

How this git repository is organised

To help you get familiar with Node-RED and how to control the Tello drone this git repository is split into a number of sections, where you have tasks to complete in each section. If you just want to have fun with the drone and prefer not to do the tasks then jump into the flows folder and use the solutions.

Tasks

As a reminder, Safety First! Take caution when flying your drone. Fly your drone indoors at your own risk. Also, be respectful of your neighbors and public property when flying your drone outdoors. When recording video and taking pictures, be mindful of other people's privacy. Obey all FAA regulatory restrictions posted about UAV flight prohibitions.

Authors

Enjoy! Give us feedback if you have suggestions on how to improve this tutorial.

License

This tutorial is licensed under the Apache Software License, Version 2. Separate third party code objects invoked within this code pattern are licensed by their respective providers pursuant to their own separate licenses. Contributions are subject to the Developer Certificate of Origin, Version 1.1 (DCO) and the Apache Software License, Version 2.

Apache Software License (ASL) FAQ

node-red-tello-control's People

Contributors

Stargazers

Watchers

Forkers

b0bbybaldi jtmoderate876 tecnavix nibalizer wesbos jabrils romeogoon binnes gmdit alejandrodelgado direkshan-digital crystal-butler malikehsan smacm lukavia gank498 nullartist loriaustin yasirjanjua jonnydubowsky sangyy neolu abhit05 gsanchez10 ayatokura andyuk5 alexcvig adminx23 jonqiao trevor-walker32 jahmah jgkong halildogan ubiyen jblann rohit-yadav damahe88 yangligit f41ardu williammolina dennisknie thomassuedbroecker grant-steinfeld ksmadhu magdig pfveiga taxbymsg154 vpathalam samux87 ejigsonpeter utsingh fecom jastill foozzy lrconcepcion mr-777 quad-a nathanb999 79212 data-ss akshayk967 lgib2u sandra-calvo wicked7578 girirajrawat ceoger tdasuk-frankr schnausser leeseungmin-sr arahman0 ibm-developer-austin dicksonchow ju3tin ttklm20 zhu849 miura55 crisdeodates ioaday a-vi-shek ezverev1980 sergiogama slametgithub asdfash a-bulcke

node-red-tello-control's Issues

I don't understand the udp connections

Hello,
Sorry to bother you. I have imported solution 4 and everything works but I don't understand very well what is done.
What is the purpose of the UDP connection "52955" and why is the UDP "8889" linked to it?
Thanks in advance for your answer!
Maxime

Tello node red

Accidentally I closed my previous issue about Tello nodes

In your part6 flow diagram, there are some nodes that are Tello. Am I reading it wrong?

Tutorial Step 5 Take pictures with the drone

Hi, i imported the solution flow and in the dashboard i dont see anything. The Watson image panel actually show the direct image or i have to press "Take Picture" button and see the image?. I have to change something please help
Thanks

Tello nodes for node red

How do I get the various Tello nodes in node red? Is there a npm install for the same?

Thanks

Tutorial Steps

Hi John,
Step 1.1 - "Add inject and change nodes to enable the following drone commands:"

May I know where do I add the commands after importing the "commands starter flow"

thanks,
Ashish

Solution Flow for Part 6 missing delays after 90 degree turns in Patrol Mission

I added a 2000 ms delay after the 90 degree clockwise turn in the patrol mission.

I also edited the SET name properties to add the values to the name string and rejiggered the layout a bit to make it more readable.

part6_solution_proposed.json.zip

Can't view the image from tello

I need some help, the camera is not working

I have some problem viewing the image lively from tello even after I import the solution flow and connect to my tello via wifi.

Can someone help me with this...

Thank you,
-Haren

How to Store Videos/Images Recorded/Captured by Drone in PC thru Node-RED?

Hi John,

Firstly I want to give you big thanks for Node-RED and Tello Drone implementation in such a easy and interesting way.

It would be great if you can suggest me how can I store drone Recorded/Captured videos/images in my laptop?

Please find some screen shots of Video streaming image by Drone.

Thanks & Regards,
Mudit Khare

Tello Picture Dash Error

I am using a Tello Edu and trying to run the Tello Picture Dash. I am getting an error

function : (error)
"TypeError [ERR_INVALID_ARG_TYPE]: The "offset" argument must be of type number. Received type object"

which is coming from the 'Tello Send Cmd' after receiving a message from the Ack FileSizeMsg function with a payload of
object
TelloCmdId: 98
data: array[1]
0: 0x0
packType: 2

Also is there a API document that describes the protocol for requesting the picture.

Thanks

Storing pictures and videos

Hi just is it possible to store pictures and videos from the tello drone in my pc

Tello does not give back telemetry data via UDP 8890

Hi John
first of all thanks for this great tutorial :-)
I was able to fly the drone by the flow/control buttons on the dashboard.
Unfortunately I don't receive data back from the drone.

Commands are transfered and I receive the "OK" back - so basic coversation works on Windows 10 and Mac OS-X. On both machines I switched of firewall and checked with TCPView or netstat for a listening software at UDP 8890 towards 192.168.10.1 - but could not find anything listening.

Any Idea?

I did not check with linux yet because I wanted to use it under Windows and I am pretty sure, that ports are open.

Best Regards,
Axel

Can't receive back data telemetry

Hello,
I try to redo your project with my drone DJI Tello. My computer uses Windows 10

-I have followed the explanations of the installation
-I imported the flow solution "Receiving Tello Telemetry Data".
-I opened port 8890 in the firewall
-I connected the computer to the Wi-Fi of the drone

I can launch the drone and make it move but I can't receive telemetry information.
This error is displayed in the debug and in the command prompt :
[udp in:bd7e5975.45fad8] error: EACCES

Do you know how to fix this error so that I can access the telemetry information?

node red installation

Hi,

i tried to install node-red and was successful but when i wanted to install dashboard, i got 2 error stated: npm WARN [email protected] no desription and npm WARN [email protected] no repository field. i did a check for the error, it need to update the version but i was unable to update.Please help

Doing Watson AI on laptop

Hi there,

I just want to clarify about this tutorial and all the Tello connectivity related.

It won't work with Watson if your laptop does not have an Ethernet (wired) Internet connection right?

Because when you're connected to the drone via the laptop's Wi-Fi to send command, you won't have any other Internet connection to talk to Watson?

Thanks

how to use face detection

hi i tried to use face detection but was unable to.Is there any solutions for these?

Node-Red dashboard has error to add ui nodes

I have gone through tutorial and I am having problems with the Node-Red when I launch the dashboard. It says "Please add some ui nodes to your flow and redeploy". I have copied several solution flows that have plenty of buttons (after I tried to do it myself.) I'm at a loss.

C:\Users\scott.bowen>node-red -log
12 Jul 22:46:46 - [info]

Welcome to Node-RED

12 Jul 22:46:46 - [info] Node-RED version: v0.20.7
12 Jul 22:46:46 - [info] Node.js version: v10.16.0
12 Jul 22:46:46 - [info] Windows_NT 10.0.16299 x64 LE
12 Jul 22:46:47 - [info] Loading palette nodes
12 Jul 22:46:48 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
12 Jul 22:46:48 - [info] Dashboard version 2.15.5 started at /ui
12 Jul 22:46:48 - [info] Settings file : \Users\scott.bowen.node-red\settings.js
12 Jul 22:46:48 - [info] Context store : 'default' [module=memory]
12 Jul 22:46:48 - [info] User directory : \Users\scott.bowen.node-red
12 Jul 22:46:48 - [warn] Projects disabled : editorTheme.projects.enabled=false
12 Jul 22:46:48 - [info] Flows file : \Users\scott.bowen.node-red\flows_SLC-WL-13310.json
12 Jul 22:46:48 - [info] Creating new flow file
12 Jul 22:46:48 - [warn]

Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.

12 Jul 22:46:48 - [info] Starting flows
12 Jul 22:46:48 - [info] Started flows
12 Jul 22:46:48 - [info] Server now running at http://127.0.0.1:1880/
12 Jul 22:49:01 - [info] Stopping flows
12 Jul 22:49:01 - [info] Stopped flows
Terminate batch job (Y/N)?
^C
C:\Users\scott.bowen>node-red-log
'node-red-log' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\scott.bowen>node-red -log
12 Jul 22:49:16 - [info]

Welcome to Node-RED

12 Jul 22:49:16 - [info] Node-RED version: v0.20.7
12 Jul 22:49:16 - [info] Node.js version: v10.16.0
12 Jul 22:49:16 - [info] Windows_NT 10.0.16299 x64 LE
12 Jul 22:49:17 - [info] Loading palette nodes
12 Jul 22:49:17 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
12 Jul 22:49:18 - [info] Dashboard version 2.15.5 started at /ui
12 Jul 22:49:18 - [info] Settings file : \Users\scott.bowen.node-red\settings.js
12 Jul 22:49:18 - [info] Context store : 'default' [module=memory]
12 Jul 22:49:18 - [info] User directory : \Users\scott.bowen.node-red
12 Jul 22:49:18 - [warn] Projects disabled : editorTheme.projects.enabled=false
12 Jul 22:49:18 - [info] Flows file : \Users\scott.bowen.node-red\flows_SLC-WL-13310.json
12 Jul 22:49:18 - [info] Creating new flow file
12 Jul 22:49:18 - [warn]

Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.

12 Jul 22:49:18 - [info] Starting flows
12 Jul 22:49:18 - [info] Started flows
12 Jul 22:49:18 - [info] Server now running at http://127.0.0.1:1880/

Type of drone

Can you please give me the exact name and description of the drone so I don't purchase the wrong type?
the drone is mentioned here
https://developer.ibm.com/tutorials/program-ryze-dji-tello-drone-using-sdks-and-node-red/#1-send-commands-to-the-drone-using-node-red-and-the-dji-apis

Error on using Watson Image Recognition

Hello Everyone,

I am learning how to use Node-red to programing a drone. I imported the solution flow, and I got the Camera working, but after I put my API key from the Watson service, it gave me an error:
getaddrinfo ENOTFOUND iam.bluemix.net

Following this tutorial, https://www.youtube.com/watch?v=9NoxljNbovM, I wrote a test flow to check if image recognition is working. It showed that the Watson Service is working correctly, and give me the correct result

Could anyone help me to solve this issues? Are there any problems with the solution flow?

Thank you

not getting info back

Hi Great tutorial but I can not get information back from the Tello.
I have turned off my virus and fire wall but still not getting anything back.
am I missing something.

I don't see any information in the dashboard

I can start the drone and give commands using Node-RED that means: starting, landing and turn works, but I can not see any information inside the dashboard of Stats, Accel or Movement. What I am doing wrong?

Mac OS 10.14.5
Chrome: Version 74.0.3729.169 (Official Build) (64-bit)

Here is the output of the Node log for the Node-RED instance:

`Welcome to Node-RED

21 Jun 15:54:25 - [info] Node-RED version: v0.20.6
21 Jun 15:54:25 - [info] Node.js version: v8.14.0
21 Jun 15:54:25 - [info] Darwin 18.6.0 x64 LE
21 Jun 15:54:25 - [info] Loading palette nodes
21 Jun 15:54:25 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
21 Jun 15:54:26 - [info] Dashboard version 2.15.4 started at /ui
21 Jun 15:54:26 - [info] Settings file : /Users/thomassuedbroecker/.node-red/settings.js
21 Jun 15:54:26 - [info] Context store : 'default' [module=memory]
21 Jun 15:54:26 - [info] User directory : /Users/thomassuedbroecker/.node-red
21 Jun 15:54:26 - [warn] Projects disabled : editorTheme.projects.enabled=false
21 Jun 15:54:26 - [info] Flows file : /Users/thomassuedbroecker/.node-red/flows_Thomass-MBP-3.fritz.box.json
21 Jun 15:54:26 - [info] Creating new flow file
21 Jun 15:54:26 - [warn]

Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.

21 Jun 15:54:26 - [info] Starting flows
21 Jun 15:54:26 - [info] Started flows
21 Jun 15:54:26 - [info] Server now running at http://127.0.0.1:1880/
21 Jun 15:57:04 - [info] Stopping flows
21 Jun 15:57:04 - [info] Stopped flows
21 Jun 15:57:04 - [info] Starting flows
21 Jun 15:57:04 - [info] Started flows
21 Jun 15:57:04 - [info] [udp in:e8fa8d62.5ba14] udp listener at 0.0.0.0:52955
21 Jun 15:57:04 - [info] [udp out:eaec231.1a027e] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:05:23 - [info] Stopping flows
21 Jun 16:05:23 - [info] [udp out:eaec231.1a027e] udp output stopped
21 Jun 16:05:23 - [info] Stopped flows
21 Jun 16:05:23 - [info] Starting flows
21 Jun 16:05:23 - [info] [udp in:f0a7b791.8fbdd8] udp: port 52955 already in use
21 Jun 16:05:23 - [info] Started flows
21 Jun 16:05:23 - [info] [udp in:e8fa8d62.5ba14] udp listener at 0.0.0.0:52955
21 Jun 16:05:23 - [info] [udp in:f0a7b791.8fbdd8] udp listener at 0.0.0.0:52955
21 Jun 16:05:23 - [info] [udp out:eaec231.1a027e] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:05:23 - [info] [udp out:bc7c5bb9.f7ae08] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:06:13 - [info] Stopping flows
21 Jun 16:06:13 - [info] [udp out:eaec231.1a027e] udp output stopped
21 Jun 16:06:13 - [info] Stopped flows
21 Jun 16:06:13 - [info] Starting flows
21 Jun 16:06:13 - [info] [udp in:f0a7b791.8fbdd8] udp: port 52955 already in use
21 Jun 16:06:13 - [info] [udp in:bc6a5c5a.dc92b] udp: port 52955 already in use
21 Jun 16:06:13 - [info] Started flows
21 Jun 16:06:13 - [info] [udp in:e8fa8d62.5ba14] udp listener at 0.0.0.0:52955
21 Jun 16:06:13 - [info] [udp in:f0a7b791.8fbdd8] udp listener at 0.0.0.0:52955
21 Jun 16:06:13 - [info] [udp in:bc6a5c5a.dc92b] udp listener at 0.0.0.0:52955
21 Jun 16:06:13 - [info] [udp out:eaec231.1a027e] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:06:13 - [info] [udp out:bc7c5bb9.f7ae08] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:06:13 - [info] [udp out:ed91acb.4b6765] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:08:54 - [info] Stopping flows
21 Jun 16:08:54 - [info] [udp out:eaec231.1a027e] udp output stopped
21 Jun 16:08:54 - [info] Stopped flows
21 Jun 16:08:54 - [info] Starting flows
21 Jun 16:08:54 - [info] [udp in:f0a7b791.8fbdd8] udp: port 52955 already in use
21 Jun 16:08:54 - [info] [udp in:bc6a5c5a.dc92b] udp: port 52955 already in use
21 Jun 16:08:54 - [info] [udp in:6d0293d0.7830fc] udp: port 52955 already in use
21 Jun 16:08:54 - [info] Started flows
21 Jun 16:08:54 - [info] [udp in:e8fa8d62.5ba14] udp listener at 0.0.0.0:52955
21 Jun 16:08:54 - [info] [udp in:f0a7b791.8fbdd8] udp listener at 0.0.0.0:52955
21 Jun 16:08:54 - [info] [udp in:bc6a5c5a.dc92b] udp listener at 0.0.0.0:52955
21 Jun 16:08:54 - [info] [udp in:6d0293d0.7830fc] udp listener at 0.0.0.0:52955
21 Jun 16:08:54 - [info] [udp in:610c4dfa.510b74] udp listener at 0.0.0.0:8890
21 Jun 16:08:54 - [info] [udp out:eaec231.1a027e] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:08:54 - [info] [udp out:bc7c5bb9.f7ae08] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:08:54 - [info] [udp out:ed91acb.4b6765] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:08:54 - [info] [udp out:bdd1e889.8e4d98] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:11:36 - [info] Stopping flows
21 Jun 16:11:36 - [info] [udp out:eaec231.1a027e] udp output stopped
21 Jun 16:11:36 - [info] [udp in:610c4dfa.510b74] udp listener stopped
21 Jun 16:11:36 - [info] Stopped flows
21 Jun 16:11:36 - [info] Starting flows
21 Jun 16:11:36 - [info] [udp in:f0a7b791.8fbdd8] udp: port 52955 already in use
21 Jun 16:11:36 - [info] [udp in:bc6a5c5a.dc92b] udp: port 52955 already in use
21 Jun 16:11:36 - [info] [udp in:6d0293d0.7830fc] udp: port 52955 already in use
21 Jun 16:11:36 - [info] [udp in:a4572688.a2c728] udp: port 52955 already in use
21 Jun 16:11:36 - [info] [udp in:a0193be4.e9f708] udp: port 8890 already in use
21 Jun 16:11:36 - [info] Started flows
21 Jun 16:11:36 - [info] [udp in:e8fa8d62.5ba14] udp listener at 0.0.0.0:52955
21 Jun 16:11:36 - [info] [udp in:f0a7b791.8fbdd8] udp listener at 0.0.0.0:52955
21 Jun 16:11:36 - [info] [udp in:bc6a5c5a.dc92b] udp listener at 0.0.0.0:52955
21 Jun 16:11:36 - [info] [udp in:6d0293d0.7830fc] udp listener at 0.0.0.0:52955
21 Jun 16:11:36 - [info] [udp in:a4572688.a2c728] udp listener at 0.0.0.0:52955
21 Jun 16:11:36 - [info] [udp in:610c4dfa.510b74] udp listener at 0.0.0.0:8890
21 Jun 16:11:36 - [info] [udp in:a0193be4.e9f708] udp listener at 0.0.0.0:8890
21 Jun 16:11:36 - [info] [udp out:eaec231.1a027e] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:11:36 - [info] [udp out:bc7c5bb9.f7ae08] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:11:36 - [info] [udp out:ed91acb.4b6765] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:11:36 - [info] [udp out:bdd1e889.8e4d98] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:11:36 - [info] [udp out:5a993ab9.2a1764] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:13:03 - [info] Stopping flows
21 Jun 16:13:03 - [info] [udp out:eaec231.1a027e] udp output stopped
21 Jun 16:13:03 - [info] [udp in:610c4dfa.510b74] udp listener stopped
21 Jun 16:13:03 - [info] Stopped flows
21 Jun 16:13:03 - [info] Starting flows
21 Jun 16:13:03 - [info] [udp in:f0a7b791.8fbdd8] udp: port 52955 already in use
21 Jun 16:13:03 - [info] [udp in:bc6a5c5a.dc92b] udp: port 52955 already in use
21 Jun 16:13:03 - [info] [udp in:6d0293d0.7830fc] udp: port 52955 already in use
21 Jun 16:13:03 - [info] [udp in:510246f1.e52d88] udp: port 52955 already in use
21 Jun 16:13:03 - [info] [udp in:8b04569b.24a2c8] udp: port 8890 already in use
21 Jun 16:13:03 - [info] Started flows
21 Jun 16:13:03 - [info] [udp in:e8fa8d62.5ba14] udp listener at 0.0.0.0:52955
21 Jun 16:13:03 - [info] [udp in:f0a7b791.8fbdd8] udp listener at 0.0.0.0:52955
21 Jun 16:13:03 - [info] [udp in:bc6a5c5a.dc92b] udp listener at 0.0.0.0:52955
21 Jun 16:13:03 - [info] [udp in:6d0293d0.7830fc] udp listener at 0.0.0.0:52955
21 Jun 16:13:03 - [info] [udp in:510246f1.e52d88] udp listener at 0.0.0.0:52955
21 Jun 16:13:03 - [info] [udp in:610c4dfa.510b74] udp listener at 0.0.0.0:8890
21 Jun 16:13:03 - [info] [udp in:8b04569b.24a2c8] udp listener at 0.0.0.0:8890
21 Jun 16:13:03 - [info] [udp out:eaec231.1a027e] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:13:03 - [info] [udp out:bc7c5bb9.f7ae08] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:13:03 - [info] [udp out:ed91acb.4b6765] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:13:03 - [info] [udp out:bdd1e889.8e4d98] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:13:03 - [info] [udp out:327c07ef.f86218] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:20:18 - [info] Stopping flows
21 Jun 16:20:18 - [info] [udp out:eaec231.1a027e] udp output stopped
21 Jun 16:20:18 - [info] [udp in:610c4dfa.510b74] udp listener stopped
21 Jun 16:20:18 - [info] Stopped flows
21 Jun 16:20:18 - [info] Starting flows
21 Jun 16:20:18 - [info] [udp in:f0a7b791.8fbdd8] udp: port 52955 already in use
21 Jun 16:20:18 - [info] [udp in:bc6a5c5a.dc92b] udp: port 52955 already in use
21 Jun 16:20:18 - [info] [udp in:6d0293d0.7830fc] udp: port 52955 already in use
21 Jun 16:20:18 - [info] [udp in:f8512254.2873c] udp: port 52955 already in use
21 Jun 16:20:18 - [info] [udp in:ac5c6d3b.5f8d3] udp: port 8890 already in use
21 Jun 16:20:18 - [info] [udp in:91649fa.603c66] udp: port 52955 already in use
21 Jun 16:20:18 - [info] Started flows
21 Jun 16:20:18 - [info] [udp in:e8fa8d62.5ba14] udp listener at 0.0.0.0:52955
21 Jun 16:20:18 - [info] [udp in:f0a7b791.8fbdd8] udp listener at 0.0.0.0:52955
21 Jun 16:20:18 - [info] [udp in:bc6a5c5a.dc92b] udp listener at 0.0.0.0:52955
21 Jun 16:20:18 - [info] [udp in:6d0293d0.7830fc] udp listener at 0.0.0.0:52955
21 Jun 16:20:18 - [info] [udp in:f8512254.2873c] udp listener at 0.0.0.0:52955
21 Jun 16:20:18 - [info] [udp in:91649fa.603c66] udp listener at 0.0.0.0:52955
21 Jun 16:20:18 - [info] [udp in:610c4dfa.510b74] udp listener at 0.0.0.0:8890
21 Jun 16:20:18 - [info] [udp in:ac5c6d3b.5f8d3] udp listener at 0.0.0.0:8890
21 Jun 16:20:18 - [info] [udp out:eaec231.1a027e] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:20:18 - [info] [udp out:bc7c5bb9.f7ae08] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:20:18 - [info] [udp out:ed91acb.4b6765] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:20:18 - [info] [udp out:bdd1e889.8e4d98] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:20:18 - [info] [udp out:327c07ef.f86218] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:20:18 - [info] [udp out:44d94dbd.d7c874] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:11 - [info] Stopping flows
21 Jun 16:21:11 - [info] [udp out:eaec231.1a027e] udp output stopped
21 Jun 16:21:11 - [info] [udp in:610c4dfa.510b74] udp listener stopped
21 Jun 16:21:11 - [info] Stopped flows
21 Jun 16:21:11 - [info] Starting flows
21 Jun 16:21:11 - [info] [udp in:f0a7b791.8fbdd8] udp: port 52955 already in use
21 Jun 16:21:11 - [info] [udp in:bc6a5c5a.dc92b] udp: port 52955 already in use
21 Jun 16:21:11 - [info] [udp in:6d0293d0.7830fc] udp: port 52955 already in use
21 Jun 16:21:11 - [info] [udp in:99c591bd.1f0ac] udp: port 52955 already in use
21 Jun 16:21:11 - [info] [udp in:7728ffcb.04117] udp: port 8890 already in use
21 Jun 16:21:11 - [info] [udp in:91649fa.603c66] udp: port 52955 already in use
21 Jun 16:21:11 - [info] [udp in:679f0974.f22048] udp: port 52955 already in use
21 Jun 16:21:11 - [info] Started flows
21 Jun 16:21:11 - [info] [udp in:e8fa8d62.5ba14] udp listener at 0.0.0.0:52955
21 Jun 16:21:11 - [info] [udp in:f0a7b791.8fbdd8] udp listener at 0.0.0.0:52955
21 Jun 16:21:11 - [info] [udp in:bc6a5c5a.dc92b] udp listener at 0.0.0.0:52955
21 Jun 16:21:11 - [info] [udp in:6d0293d0.7830fc] udp listener at 0.0.0.0:52955
21 Jun 16:21:11 - [info] [udp in:99c591bd.1f0ac] udp listener at 0.0.0.0:52955
21 Jun 16:21:11 - [info] [udp in:91649fa.603c66] udp listener at 0.0.0.0:52955
21 Jun 16:21:11 - [info] [udp in:679f0974.f22048] udp listener at 0.0.0.0:52955
21 Jun 16:21:11 - [info] [udp in:610c4dfa.510b74] udp listener at 0.0.0.0:8890
21 Jun 16:21:11 - [info] [udp in:7728ffcb.04117] udp listener at 0.0.0.0:8890
21 Jun 16:21:11 - [info] [udp out:eaec231.1a027e] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:11 - [info] [udp out:bc7c5bb9.f7ae08] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:11 - [info] [udp out:ed91acb.4b6765] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:11 - [info] [udp out:bdd1e889.8e4d98] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:11 - [info] [udp out:327c07ef.f86218] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:11 - [info] [udp out:44d94dbd.d7c874] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:11 - [info] [udp out:d256ff94.22cd1] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:57 - [info] Stopping flows
21 Jun 16:21:57 - [info] [udp out:eaec231.1a027e] udp output stopped
21 Jun 16:21:57 - [info] [udp in:610c4dfa.510b74] udp listener stopped
21 Jun 16:21:57 - [info] Stopped flows
21 Jun 16:21:57 - [info] Starting flows
21 Jun 16:21:57 - [info] [udp in:f0a7b791.8fbdd8] udp: port 52955 already in use
21 Jun 16:21:57 - [info] [udp in:bc6a5c5a.dc92b] udp: port 52955 already in use
21 Jun 16:21:57 - [info] [udp in:6d0293d0.7830fc] udp: port 52955 already in use
21 Jun 16:21:57 - [info] [udp in:a4d98e09.1299d] udp: port 52955 already in use
21 Jun 16:21:57 - [info] [udp in:23ad3213.d4df8e] udp: port 8890 already in use
21 Jun 16:21:57 - [info] [udp in:91649fa.603c66] udp: port 52955 already in use
21 Jun 16:21:57 - [info] [udp in:679f0974.f22048] udp: port 52955 already in use
21 Jun 16:21:57 - [info] [udp in:834ea885.7a8108] udp: port 52955 already in use
21 Jun 16:21:57 - [info] Started flows
21 Jun 16:21:57 - [info] [udp in:e8fa8d62.5ba14] udp listener at 0.0.0.0:52955
21 Jun 16:21:57 - [info] [udp in:f0a7b791.8fbdd8] udp listener at 0.0.0.0:52955
21 Jun 16:21:57 - [info] [udp in:bc6a5c5a.dc92b] udp listener at 0.0.0.0:52955
21 Jun 16:21:57 - [info] [udp in:6d0293d0.7830fc] udp listener at 0.0.0.0:52955
21 Jun 16:21:57 - [info] [udp in:a4d98e09.1299d] udp listener at 0.0.0.0:52955
21 Jun 16:21:57 - [info] [udp in:91649fa.603c66] udp listener at 0.0.0.0:52955
21 Jun 16:21:57 - [info] [udp in:679f0974.f22048] udp listener at 0.0.0.0:52955
21 Jun 16:21:57 - [info] [udp in:834ea885.7a8108] udp listener at 0.0.0.0:52955
21 Jun 16:21:57 - [info] [udp in:610c4dfa.510b74] udp listener at 0.0.0.0:8890
21 Jun 16:21:57 - [info] [udp in:23ad3213.d4df8e] udp listener at 0.0.0.0:8890
21 Jun 16:21:57 - [info] [udp out:eaec231.1a027e] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:57 - [info] [udp out:bc7c5bb9.f7ae08] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:57 - [info] [udp out:ed91acb.4b6765] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:57 - [info] [udp out:bdd1e889.8e4d98] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:57 - [info] [udp out:327c07ef.f86218] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:57 - [info] [udp out:44d94dbd.d7c874] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:57 - [info] [udp out:d256ff94.22cd1] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:21:57 - [info] [udp out:9297f027.bc6b] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:29:16 - [info] Stopping flows
21 Jun 16:29:16 - [info] [udp out:eaec231.1a027e] udp output stopped
21 Jun 16:29:16 - [info] [udp in:610c4dfa.510b74] udp listener stopped
21 Jun 16:29:16 - [info] Stopped flows
21 Jun 16:29:16 - [info] Starting flows
21 Jun 16:29:16 - [info] [udp in:f0a7b791.8fbdd8] udp: port 52955 already in use
21 Jun 16:29:16 - [info] [udp in:bc6a5c5a.dc92b] udp: port 52955 already in use
21 Jun 16:29:16 - [info] [udp in:6d0293d0.7830fc] udp: port 52955 already in use
21 Jun 16:29:16 - [info] [udp in:db213c2c.21a8a] udp: port 52955 already in use
21 Jun 16:29:16 - [info] [udp in:86a1abd2.8da938] udp: port 8890 already in use
21 Jun 16:29:16 - [info] [udp in:91649fa.603c66] udp: port 52955 already in use
21 Jun 16:29:16 - [info] [udp in:679f0974.f22048] udp: port 52955 already in use
21 Jun 16:29:16 - [info] [udp in:834ea885.7a8108] udp: port 52955 already in use
21 Jun 16:29:16 - [info] Started flows
21 Jun 16:29:16 - [info] [udp in:e8fa8d62.5ba14] udp listener at 0.0.0.0:52955
21 Jun 16:29:16 - [info] [udp in:f0a7b791.8fbdd8] udp listener at 0.0.0.0:52955
21 Jun 16:29:16 - [info] [udp in:bc6a5c5a.dc92b] udp listener at 0.0.0.0:52955
21 Jun 16:29:16 - [info] [udp in:6d0293d0.7830fc] udp listener at 0.0.0.0:52955
21 Jun 16:29:16 - [info] [udp in:db213c2c.21a8a] udp listener at 0.0.0.0:52955
21 Jun 16:29:16 - [info] [udp in:91649fa.603c66] udp listener at 0.0.0.0:52955
21 Jun 16:29:16 - [info] [udp in:679f0974.f22048] udp listener at 0.0.0.0:52955
21 Jun 16:29:16 - [info] [udp in:834ea885.7a8108] udp listener at 0.0.0.0:52955
21 Jun 16:29:16 - [info] [udp in:610c4dfa.510b74] udp listener at 0.0.0.0:8890
21 Jun 16:29:16 - [info] [udp in:86a1abd2.8da938] udp listener at 0.0.0.0:8890
21 Jun 16:29:16 - [info] [udp out:eaec231.1a027e] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:29:16 - [info] [udp out:bc7c5bb9.f7ae08] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:29:16 - [info] [udp out:ed91acb.4b6765] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:29:16 - [info] [udp out:bdd1e889.8e4d98] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:29:16 - [info] [udp out:327c07ef.f86218] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:29:16 - [info] [udp out:44d94dbd.d7c874] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:29:16 - [info] [udp out:d256ff94.22cd1] udp re-use socket: 52955 -> 192.168.10.1:8889
21 Jun 16:29:16 - [info] [udp out:9297f027.bc6b] udp re-use socket: 52955 -> 192.168.10.1:8889`

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.

johnwalicki / node-red-tello-control Goto Github PK

node-red-tello-control's Introduction

Node-RED-Tello-Control

Introduction

How this git repository is organised

Tasks

Authors

License

node-red-tello-control's People

Contributors

Stargazers

Watchers

Forkers

node-red-tello-control's Issues

Welcome to Node-RED

You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change.

Welcome to Node-RED

You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change.

`Welcome to Node-RED

You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change.

Recommend Projects

Recommend Topics

Recommend Org

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.