Welcome new contributors

[bortek]

(This message is addressed to people who are in the list of Assignee, not to everyone else)

Hi guys!

EZwfb project that I am hosting code of on Github is in need of new enthusiasts who love the project and are willing to contribute and continue developing it. Thank you "careyer" for bringin this topic up.

Since you guys have been active on the forum and in the Issues discussions on Git I though you might be one of those enthusiasts :) Therefore I have added you as contributors on Github project which means you can push/pull/merge etc the code. I am sure we all have skills that can benefit the project in a good way. If for some reason you do not wish to be a contributor you can withdraw yourself trough the settings page.

If you have not worked with Github before please read-up about it or watch YT videos on the ways of working with github. Those who have previously worked with it can hopefully help others to get on track. My suggestion for the structure is the following:

Master branch is locked from changes directly and is supposed to be updated via Pull Requests.

There is now the new branch called "develop" which is a default branch where active coding is ongoing. Every time someone makes code changes , it is commited and then pushed to develop branch. This can be done several times before creating PR. When you feel ready create a PR towards master branch, discuss the changes in the PR by commenting. Then someone else other than the PR creator have to approve it. Afterwards it can be merged to master.

Usually after one or several PR when we feel ready for a new version we create a release from the master in Github and add new tag to it. All this is to encourage discussion. Feel free to create Issues and discuss there. It is easy and fun to reffer to the code changes from the Issues. Github is state of the art collaboration tool for dev projects. Sounds complicated? :) Dispair not, it is actually easy when you have done it few times.

Feel free to contact me by commenting here or via bortek666 (at) gmail dot com if you have any questions, thoughts or suggestions.

Regards /Boris

[careyer]

@user1321 : I totally get your idea which I believe is good and indeed the only smart way to go. Unfortunatly I am not a coder myself and all that code related stuff is a bit difficult for me. (most changes in my image have been made by dino.de - he is also on github btw. <- @bortek ;-) ). His changes are profound and almost essiantial for the future sucess and reliablity in regard to a AIO system. They pretty much stabilize the foundation of bi-directional telemetry and RC control and take it to the next level. This is why I suggested taking this as "anker"-image.

Please don't get me wrong: I really like your changes (e.g. configuring via FPV_VR) a lot and I am looking forward that we will integrate them in a common image. But unlike things that stabilize the foundation and reliability/robustness of the image a GUI based configuration feels somewhat a cosmetic thing to me. Again: Don't get me wrong here. It is just all about to make a smart decission from where to start.

@user1321 maybe you could kindly try to dismantle my image and try to apply the 3 steps you just proposed above? Then we would have a good starting point. I am happy to assist you in identifying the changes made to .profile and explain about the v4l2loopback kernel module stuff needed for the Flir/insta360 integration (I have documented this in a step by step guide). All the other stuff (rcswitches, airswitches, mavlink2) should be pretty much file based (c Executables) Would this be a way to go?

[htcohio]

@Careyer,

I'm sorry but I have to 100% disagree that that synchronized configuration settings are cosmetic because, when most people go to the field with multiple aircraft they may go with a long-range fpv plane running 3s, a 6S drone and a 4S plane. Also, it's much easier to work up a instructional guide and video when there's a graphical user interface with selectable options as opposed to text files.

Battery cell count, aircraft type and desired video range settings ultimately need to be easily changed in the field. Having the ability to interface with an app is by far the easiest and most logical way of going about it. I know from experience because I've taken all these things to the field and fiddled for hours trying to SSH or modify the SD cards and it really takes away from the enjoyment.

Furthermore, rpi3+ compatibility is a must because of the benefit of the internal 5g wifi connection.

The usable image situation as of right now is as follows:

@Careyer image functions: •Flir camera campatable •GPIO trigger w/ RC •Mavlink 2 •RC GS osd on/off

@user1321 image functions •GUI config •GPIO 4 camera switcher •PI3 compatibility (working on bugs) *I Believe user1321 has successfully compiled and tested out RespawnDespairs image Builder that works with rpi3b+.

Correct me if I'm wrong but once those bugs are figured out isn't that the lattice that should be used to adapt the other functions from careyer and user1321????

So.... In my humble opinion I think there's 3 priorities as of this moment.

1.) Both of yours have GPIO trigger (those should be able to be merged in addition to the camera switcher which only needs 2 things; 1. PWM values for (1, 2, 3 or 4 cameras). Also, define channel # for switch.

2.) Mavlink 2.3 (this is a must)

3.) Rpi3b+ compatibility

-- Once that is working and stable and fully integrated with the respawndespair image Builder then, work can be done to integrate the other bells and whistles.

-Thermal camera support -RC ground rc/osd control -RTL8812/4 5g compatibility (I'll never use it but I know many people want it but I've tested and it's kind of buggy)

Ultimately, there's a lot of ideas out there but in order to establish a solid foundation for the future, getting the image Builder working is critical.

I think I covered everything here but let me know if I missed anyting.

On Sat, Oct 13, 2018, 5:49 AM careyer notifications@github.com wrote:

@user1321 https://github.com/user1321 : I totally get your idea which I believe is good. Unfortunatly I am not a coder myself and all that code related stuff is a bit difficult for me. (most changes in my image have been made by dino.de - he is also on github). His changes are profound and almost essiantial for the future suucess in regard to a AIO system. They pretty much stabilize the foundation of bi-directional telemetry and RC control and take it to the next level. This is why I suggested taking this as "the anker".

@user1321 https://github.com/user1321 maybe you could try to dismantle my image and try to apply the 3 steps you just mentioned above? Then we would have a good starting point.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bortek/EZ-WifiBroadcast/issues/155#issuecomment-429526931, or mute the thread https://github.com/notifications/unsubscribe-auth/AcSp0jp7kIDYksbRlaLCt-9_HBdiRPl1ks5ukbcrgaJpZM4XYNu2 .

[Yes21]

Guys, I want to ask your opinion... We all have some kind of ISO images... As for me, I got mine by doing modification to working system via SSH terminal and after changes was done I just clone SD card to iso file. But, that is not an option anymore as we agreed store our modifications at GitHub. If we also agreed to use ImageBuilder as base for future releases I see it in next way:

@user1321 : I've seen you made today big progresses in making RespawnDespair's ImageBuilder script to work better. We thank you very much for your efforts !

• When it will be confirmed that this script is able to build a perfectly working EZ-WBC 1.6rc6 image, I suggest that this image could become the starting point of new developments. It will be a "new 1.6rc6" (or 1.6rc7, or 2.0rc1, or ... ?). This image wouldn't have any new features, except a new kernel and support for RPI3B+.
• The code used to generate this "first" image (the one a few restructured by RespawnDespair) should be hosted on this github and become the reference code for future developments.
• After that, each developer of new features (since 1.6rc6) could submit its code to a dev branch on this github.
• Everyone should be able to test the new features by building itself a test image with the ImageBuilder script.
• When the new features are well tested and stable, we could generate and publish a new public image = new version. And the dev branch could become then the master branch.
• And so on ...

@ALL : What do you think of this proposition ?

[htcohio]

Yes, that's probably the best way. So basically an equivalent of 1.6 RC6 that is compatible with pi3b+... If possible, I think it should also include the Mavlink v2 compatibility as well.

2.0 would be a good version. I'm sure this would quickly result in a couple beta (test) versions with the other features previously listed with the intent of eventually getting to ezwfb V2.1

We can all test it out.

[careyer]

Yes this is pretty much perfect! First we need to be able to generate a working 1.6rc6 with @RespawnDespair ImageBuilder. From there we can add feature by feature from the various images arround.

[user1321]

Hi Guys! I what to ask you to help find bugs inside image attached in this post. That image is image that generated by ImageBuilder + it contains all fixes that listed at: https://github.com/RespawnDespair/wifibroadcast-image-builder/issues/10

Reason why I asking you to help is - to find out what else must be fixed before we can use it. I almost sure that it may contain some more bugs that must be fixed before we can use it. So, please dont fly at it! Seriously! Just ground!!! And better to unattach from motors. Just to be in safe! When we will find other bugs and fix them also, we can integrate appended solution list and integrate them to Build script. I think its good place to report about bugs at RespawnDespair GitHub page. I will be checking it from time to time... P.S. I checked it under RPi 3B+ and RPi 2. P.S. Its starts up a little longer than original WFBC 1.6. Dont be surprised. I think some optimization to Linux OS is required. But, first lets find and fix bugs.

Link: https://drive.google.com/open?id=1JJpdEo1xrH97nNVpmZqp_nxmXmPFJWCP

---

ADD:

Just minute ago found another bug. If ground RPi not connected with ethernet (RPi3, RPi2) OSD not appears. I will find out why...Just connect Ethernet if you have to Ground RPi. Bug 11. solution: 8.5 inside osd_rx_functions.sh return back: /tmp/osd >> /wbc_tmp/telemetrydowntmp.txt & ps -ef | nice grep "/tmp/osd" | nice grep -v grep | awk '{print $2}' | xargs kill -9

ADD2: Just in case image with fixed Ethernet dependency: https://drive.google.com/open?id=1bG4b0y8Q5hfiWhDISG8zS9IRHxfiI3MI

[RespawnDespair]

Aside from actually getting the image generator working (many thanks to @user1321 for finding all of the problems) i also promised a suggested git structure.

People who have looked at my repository know i have split everything to different repositories, this is both good and bad, it makes it easier to work on a separate piece, but you loose the overview. My main reason for doing this was the fragmentation that was already happening, i wanted to be able to change the image builder to git clone another repository and then use that.

Since we are now pooling resources i want to suggest the following:

project root
│   README.md
│
└───base
│   
└───osd
│   
└───rc
│   
└───status
│   
└───scripts
│   
└───misc
│   
└───video
│   
└───image-builder

So everything under one repository, separated in folders. This may seem counter-intuitive, but it makes sense since we can then create branches of all the relevant code that makes up EZ-WFB. In such a branche we would prepare the next release image. When done we make a pull-request to master. In this way, we make sure master always represents the latest released image while keeping an overview of all code that makes up the system.

Off course suggestions or improvements are welcome, once i have the image-builder working with @user1321 's changes i will make this structure in my own account. We can then test it and move it to @bortek 's repository once validated. That way we will prevent further annoyance/confusion.

[careyer]

@RespawnDespair - Nice! Maybe add a dedicated "telemetry" directory as well and rename "hello-video" to just "video" (some AddOns might also use make use of GStreamer, ffmpeg and such)

[RespawnDespair]

You are correct on the video folder, i will change that. As for a telemetry folder it would make a lot of sense, but the telemetry code is mixed with other code right now (at least in the last image i checked). If that's still the case we could keep it in misc or base and extract it to a separate folder in the next release...?

[careyer]

sure. You may take a look at the image i have linked above (the MavLink2 version) and investigate if it is still mixed there with the basecode. I can't tell because I did not implement it myself. All that magic was done by dino.de - the current telemetry based on Mavlink v1 must be treated as legacy code causing unneeded trouble.

[RespawnDespair]

I'll try to get all of @user1321 's findings fixed in the separated repos. Then i will merge to one repo. Then we'll do one final sweep over all the different images to make sure we included all the intended functionality! so much work 😄

[careyer]

You are doing a great job - don't worry!

[user1321]

@RespawnDespair , please, don't hurry , I think there are more things to fix. I will say when it's time ) P.s I think its better to set reg zone to US, not to BO or CN

[RespawnDespair]

@user1321 i'm not in a hurry, let's make sure everything works before moving on to the next step. When i implement your regfix i will set it to US instead of BO.

[careyer]

@All: I created a "Help maintain the Wiki Tasklist" on Google - feel free to jump in for a free slot: https://docs.google.com/spreadsheets/d/1o-zk3RvxrfGni4EYF-C5TQYLIx2TO9t_FtJvEVsTzzU/edit?usp=sharing

[htcohio]

@careyer,

I definitely have some notes organized for the wiki list. Before I publish anything I'm hoping to actually field test some of the updated recommendations for the wiki based on the newest image that they are working on. There are just certain aspects that are unclear and I think need a second look and field test such as the SR settings, antenna separation and usb cable length.

My plan is to have a couple craft I'll fly the same Mission with different configurations with antennas and little modifications to see how they compare.

[user1321]

Guys. I just checked mavlink-forwarder program from Image Builder and it generated some error during start: ionice -c 3 nice /home/pi/mavlink-router/mavlink-routerd -e $192.168.2.2:14550 /dev/pts/1:57600

Error: Could not open conf file '/etc/mavlink-router/main.conf' (No such file or directory) Could not set DTR/RTS (Invalid argument)

Probably it can be easly fix, But if I will take a look at it in any case, maybe we replace it with Careyer solution with Mavlink2? (I did`t look at it yet.) Or will stay with default one? How do you All think?

[htcohio]

Guys, Hey, we have $193 in donations so far!!!

Once we hit $400 I'm raffling off a Ubiquiti Wi-Fi station EXT 😉.

We'll have to figure out how it is split ultimately.

As far as I know, user1321 and respawndespair are the only ones primarily working on the updated version correct?

These donations are intended to be applied to all work that started on Friday 10/12.

Could you guys possibly try to track actual hours worked on the code? This way it could be split accordingly. there's no easy way to do this because many people have put many hours into the project but considering the amount of work that's required to decode and establish a solid foundation I'm thinking this should help keep things moving in the right direction.

Great work!

[careyer]

@user1321 : MavLink v1 is legacy and likely to cause more errors in the ongoing work. There is no point in spending time with something that is already end of life and also currently causing a lot of problems and hiccups during operation. We should definitely go with Mav2

[htcohio]

@careyer,

I'm just curious, is V2 actually stable in the image that other guy you were working with developed?

I thought you said otherwise, or is it that the 18ch rc is not yet fixed by the mavlink developers?

Also, as for the donations that are coming in rather quickly, I forget what developer you were working with on some of those enhancements. Perhaps you could help me find out or discover who is doing what from Friday October 12th onward?

**I just don't want a programmer/developer that has put significant time into something being excluded from the total amount brought in from contributors but at the same time, I don't want the "pot" to be diluted too much.

Perhaps the top 2-3 Developers for each stage...

Stage 1:. Complete image Builder with MavlinkV2 compatibility as the base for future development.. (User1321/Respawndespair/ 3rd???)

Stage 2: integrate the newest enhancements previously mentioned.
(Tbd....../tbd...)

Stage 3: bug fixes and continued development. (Tbd...)

*I don't want to over-complicate things nor do I want anyone to feel unfairly excluded from the "active developer" list...

[bortek]

I have now extracted files (including .profile) from careyer's 1.6RC6 image as well as from official 1.6RC6 image and put it up in two separate branches called respectively. Please take a look. Any idea which files should be updated. It is not possible to merge alltogether since files on the img are residing differently than in repo.

[htcohio]

@Bortek,

As of this moment my understanding is User1321 and respawndespair are finalizing the image Builder and I was able to test it yesterday and I think we're about 80% there but I'm not the coder perhaps you should refer to this thread for further information and updates. I also believe user1321 is looking at mavlinkv2 integration from careyer/dino.de image. https://github.com/RespawnDespair/wifibroadcast-image-builder/issues/10

[Yes21]

Probably it can be easly fix, But if I will take a look at it in any case, maybe we replace it with Careyer solution with Mavlink2? (I did`t look at it yet.) Or will stay with default one? How do you All think?

We did decided that the first image created with ImageBuilder should be exactly the same as the legacy 1.6rc6 (except new kernel and Pi3+ support). But if you have too many problems to make Mav1 work again, I can understand that it could be worth to try to replace it right now by Mav2 from Careyer/Dino. Wouldn't it be a too much changes for this first image ? There are so many things to fix before the first ImageBuilder image works perfectly like the last 1.6rc6 ! I don't know the best solution ...

[careyer]

@htcohio :

I'm just curious, is V2 actually stable in the image that other guy you were working with developed? I thought you said otherwise, or is it that the 18ch rc is not yet fixed by the mavlink developers?

There are two sides of the MavLink v2 implemenation: EZ-WBC (Raspi) and ArduPilot (Fligthcontrol). EZ-WBC implematation by dino.de for EZ-WBC works aboslutely flawless and (besides the 24Ch uplink) gives several improvements alongside plain RC-control. Just to name a few: V1 had several problems due to missing message types - e.g. a.) some Mission Planner messages caused the telemetry link to crash completely or b.) the drone just refused to do what the user was commanding it to do - e.g. flight mode changes sent from Mission Planner were just ignored or c.) functions like Compass calibration did not work at all due to missing Ardupilot specific command extensions. Ardupilot uses V2 now per default but is not yet supporting the 18Ch channel extension introduced with Mav 2.3. They are working on it right now. (also RCgroups user davidgp is taking care of it right now) To cut a long story short: We can either be ahead of Ardupilot (without any drawbacks and immediate benefits) or we can stick with old Mav1 (legacy for more than 2 years now) and will get rendered useless within a matter of month. If you have not yet familiarized with the differences of the protocol you should do so.

Also, as for the donations that are coming in rather quickly, I forget what developer you were working >>with on some of those enhancements. Perhaps you could help me find out or discover who is doing >> what from Friday October 12th onward?

**I just don't want a programmer/developer that has put significant time into something being >>excluded from the total amount brought in from contributors but at the same time, I don't want the >>"pot" to be diluted too much.

dino.de and me, we do not want to have any of the donated money at all. You and me, we have talked about this idea before and I believe that I clearly stated that I belived it was not a good idea to initate a donation/reward system. This might work short term but I have seen many projects fail because people got argueing about the equitable distribution of money. I believe this is a hobby project and everyone contributes with the best of energy, time, skill and commitment that he can. I do not believe that this is a question of hours spent or plain skill level but more about passion. And sadly there is no scale for that. You should know that. However this is my very personal view of things. Your opinion and that of others may differ - I am okay with that. But to answer your question in terms of man-hours: dino.de and the team put several month of work and testing into what I have released to the wild above. We are follwoing the project from the very beginning (page 1 on RCgroups so to say) and have seen all the UPs and Downs. Trust the word of a man almost being to old to play with this kind of toys.

Due to a personal tragedy in the closest circle of friends that i got to know just 2 days ago I have decided to reduce my activities here for the time being - Best of luck guys!

Cheers!

[htcohio]

I'm really sorry to hear that man. Go take care of your business. I have you and your friends in my thoughts.

As for the donations, there were several people that expressed interest in this and we're at a point where quite a bit of time and effort is needed to establish a new starting point. This may only be a one-time thing just to accelerate the process since there's so many great enhancements that can be integrated. This is why the intention of the funding is to be directed towards all work that was started on October 12th onward.

[careyer]

Thank you for your compassion! Just one last thought... this is a hobby project. It has stalled for many month .. almost a year. I am happy to have kicked this off but think about it this way: We are not so much in a hurry. It pretty much does not matter if we have that "new build" one, two or three weeks from now. In any case, we will achieve 100 times more than in the past months. Take your time and do it the correct way instead of rushing things. Drive it with passion not money and it will be a long term success story.

[user1321]

Very sorry to hear. Wish you all the best.

[Yes21]

@careyer : I can understand what you say "Trust the word of a man almost being to old to play with this kind of toys." I'm also a soon old man, and know that the life is sometimes making these toys/hobbies not so important. I thank you a lot to have given a new energy to this project. But now take care of you, and of your family and friends. You will be welcome here, when you want. "Bis bald"

Yves

[bortek]

I concur with careyer’s though about donation thing. For me this has been a hobby project on my free time and I will continue to contribute in the same way without needing any donation.

[RespawnDespair]

@careyer take care of yourself, your family and your friends. We'll be here when you feel like you're ready again.

As for being paid to do work on the project i feel the same as most others. This is for me a hobby project, introducing money muddies the waters and will never be 'fair' to all involved. I think the best thing we could do is keep the money centrally and spend it on hardware and/or hosting. Now if anybody does feel like getting paid for their work i won't object, that's a personal choice. @user1321 spends more time on the project than i am able to due to work and family life. His efforts moved the project forward a lot. The same can be said for dino.de 's efforts.

So for me, money is not necessary, now if anybody has a larger wing left over that i can rebuild with EZWFB, that's a different matter (Crashed my ZOHD Orbit...)

[pilotnbr1]

I think one addition to the wiki could also be a common question page. I would be willing to write that up (or at least the questions). Hopefully it would alleviate some of the repetitive question asking on the rcgroups thread. As much as people get encouraged to use the thread search function, few ever do.

@careyer best wishes as you take care of you and yours. Hope to see you come back here renewed. Nice work on the google drive doc assigning wiki pages! Will you still be writing up the rc stuff?

[user1321]

Next image: It contains bug fixes: mavlink-routerd, gst-launch, hotspot, DHCP. Using that image I able to connect via HotSpot to Ground RPi via phone, get parameters vis Ground Сontrol app (Android), receive video over raw h264 and RTSP.

As for RTSP, it confuse me a little. Using RTSP I get video with delay something like 0.5 second +

It`s look to me very strange, because I remember that using one of my images (not published here) It was significantly lower. So, is it normal? ( I am not saying acceptable. Just to know, as we trying to create a copy of original WFBC 1.6)

Also I did same test at "RussianImage" at RPi 3B+ and got same result with build in wifi card (RP 3B+) and with external one. So, please, check it also. And if you remember or know that it must (!) be lower inside GroundControl app ( I am not talking about VR_2018 app) . Please, say about it.

Also, this is not the end. Just some report about progress. P.S. Adjust settings.sh file for your configuration.

https://drive.google.com/open?id=1Mg7O1tQmn-GTEdkfCjWZdnZWXAhG58ga

[careyer]

@pilotnbr1 :+1: a FAQ section is always a good idea. What was I thinking forgetting about that? Go ahead add it to the wiki ;-) And yes, I am still considering adding to the RC section. However this has time and I will follow along the project for a while first. Who knows what is going to happen and going to change.

@All: Thank you for your kind words. I do not intend to completely leave the project behind - not yet. To calm you down: Nobody passed away. It is just that due to a sudden and very severe accident/illness of a close friend I cannot focus my thoughts and energy solely to the project right now. I'm sorry about that and I feel a little guilty to Boris that I have to hand over the rest of the coordination now so soon after I've kicked it all off. That's especially because I feel at the very moment that we're running into a situation where not everyone is going to emerge as a winner and that doesn't benefit the project in the long run. We need to find a way to make decisions democratically and not just get started and present participants with faits accomplis. Otherwise we will loose skilled and knowing people one after the other over the course of time. I have to confess that this uncoordinated fundraising campaign in particular annoys me to such an extent that it spoils my desire to participate. It just doesn't reflect my spirit and mindset.

@user1321 & @RespawnDespair : :+1: I think you are doing a fantastic job and I strongly believe this is the correct way to go. So the above is nothing against you and your work. Just wanted to express my personal feeling about the team spirit and the lack of a roadmap agreed upon all.

[user1321]

Just found one more problem: 13. Some Error (crash ) in case of USB phone connected. So, please, connect it via WiFi at that moment.

[pilotnbr1]

@careyer yes faq is better. Please dont let the fund raising turn you off. Personally I am against this as well. IMHO money detracts from the pure hobbyist nature of this project (most of us already work and think about money the rest of the day). I think the fund raising is well intentioned and htcohio is just trying to contribute. I think perhaps some cultural differences may be at play, since we are like the united nations here (I am american living in Germany traveling in Helsinki), which is an aspect I enjoy as well. However, I do not think compensation is something anyone on here is looking for. Personal time to play with this seems to be the big constraint (can you gift me time lol). I believe any fund raising at this point should be on the side and removed from development as it only spams these already busy threads. We all have already spent some time during an exciting push, to stop and consider this money issue. I will not say where, when, or how any money should be used because I want no responsibility over it. Maybe at some point down the road there will be some financial need, but it is not now.

@careyer I hear you with how uncoordinated development/actions can make this frusterating. Early days of wbc was chaos with scripts being shared and everyone running different images. Rodizio solved it by being a one man band but in the end I think things did not go the way he hoped or expected. Mostly in regards to dronebridge imho. In the end with these open, loose colaborations they can go in directions that nobody predicted or wanted. Github could provide more structure I think. Most important is to all stay together and keep developing. I just hope everyone will continue to be inspired even if things go sideways a little. :)

Edit and sorry if i sound so negative! I am not- I am very encouraged and excited by this latest push! Wbc is a great project and very relevant and useful to many ppl

[Yes21]

I feel a little guilty to Boris that I have to hand over the rest of the coordination now so soon after I've kicked it all off.

We need to find a way to make decisions democratically and not just get started and present participants with faits accomplis.

I can make a proposition to help giving this project a more democratic coordination :

I propose to create a dedicated issue for a proposition of a roadmap. I could write a first draft in trying to gather propositions of the various developers, and to order them on a timeline (without dates or duration). Then each developer could express himself and give his opinion about the draft roamap. I will update the roadmap project untill everybody is ok (if that's possible ...).

(I don't want to coordinate the project because I'm not a developer, but just an engaged user. When I'm using an open source project, I like to try to get it better, especially when the project is awesome. I'm 53 years old, and in a past life I've been an engineer and project manager. I'm a linux user since 15 years, and had a little contributed to a few open source projects for a time (only translations into french, guides or website update). Now I'm working alone, and just begin to try to earn my life with forest cartography, with drones and multispectral analysis (Parrot Sequoia camera).)

I will write this draft of a roadmap only if each implicated developer agree with my proposition.

ps : like the others, I'm not interested by money ...

[user1321]

@pilotnbr1 money detracts from the pure hobbyist nature of this project ...

Brr.... Its good when some one talk own opinion. I think we have good word for that - IMHO But look, starting from Friday I spent at that project something around 25 hours of work (maybe more, I didnt take a lot attention at time). I dont mean when you drink coffee and looking to windows its a work, I mean direct 25+ working hours.

Basically its look like at: from morning till deep night with coffee break and pause to do some homework, shopping... And taking that in attention we still dont have working image.

And now imagine like it can be in normal way. For example 1-2 hours every day after work. So, in that way we will reach same result in half month, maybe more.

That donation it's not normal level of salary even for "Cleaning Man" But why you think I or someone else can`t be rewarded with that kind of promotion?

[bortek]

@yes21 I dicussed with careyer about making a roadmap couple of days ago and that we need to have it. So yes I think it is vital to have one so we can prioritise and decide. If you will do so please do it on Trello. It's a tool just for this purpose where one creates a board with cards and ca discus and which can be linked to Github.

[bortek]

@user1321 I am sorry that it turned out like that to you. But keep in mind that there is no pressure and no one forces us to do what we do and we have no deadlines to deliver. So let's enjoy what we do in a pace that suits each of us and more importantly have fun when we do it. 😊

[pilotnbr1]

Started FAQ page. Feel free to jump in edit/correct/complete!

[htcohio]

@All,

Look, please disregard all of this, it's my fault and it was not my intention to create any issues. I have an entire 6 months of experience under my belt with open source projects and I also own a small business so, in my world if I'd like to see things done quickly paying money is usually the best way to make it happen. Furthermore, several people had inquired over the last few months about how to donate to the project, I saw it as an opportunity that could only bring benefit and ironically had quite the opposite effect from what I intended.

I have refunded all of the public donations with a note that they can feel free to individually donate money or Hardware privately as they see fit.

I apologize again, hopefully we can just drop this whole thing and focus on what needs done.

Justin

[RespawnDespair]

@htcohio No harm no foul, everybody has the best intentions as did you. Open source is probably the only place people will get upset if you try to give them money 😄

Now as you said, we'll keep doing what we where doing!

[user1321]

https://donate.mozilla.org/en-US/?test=no-img https://donate.wikimedia.org/wiki/Ways_to_Give https://ubuntubudgie.org/contribute https://www.archlinux.org/donate/ https://www.debian.org/donations U sure? and so on.. There a lot more...

[bortek]

Thanks Justin, appreciate it! It was rightly done.

Now after this long and somewhat productive discussion, where we got to know each other a little bit better, shell we get going? @RespawnDespair I agree and yes please keep going.

@user1321 we are far from the projects you mention above and if someone is expecting to be compensated for the working hours then I think this is the wrong place to be.

Now before we close this Issue can we agree on the proposal to draft the roadmap as @Yes21 suggested? Just say yes if you agree and if not please come with the suggestion.

[careyer]

Yes

Von meinem iPhone gesendet

Am 16.10.2018 um 18:02 schrieb Bortek notifications@github.com:

Thanks Justin, appreciate it! It was rightly done.

Now after this long and somewhat productive discussion, where we got to know each other a little bit better, shell we get going? @RespawnDespair I agree and yes please keep going.

@user1321 we are far from the projects you mention above and if someone is expecting to be compensated for the working hours then I think this is the wrong place to be.

Now before we close this Issue can we agree on the proposal to draft the roadmap as @Yes21 suggested? Just say yes if you agree and if not please come with the suggestion.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[RespawnDespair]

Yes

[htcohio]

@all,

I test it out this image with rpi3b+ ground, pi0w air.

No apparent issues with Telemetry or RC. Video latency on the rtsp qgroundcontrol app seemed fine, the video was on a big TV and the latency has always been higher on this TV compared to my regular computer monitor.

USB tethering appeared to work fine as well. It did not display the "USB device detected" message however.

2312-25xx mhz appears to be working with full power.

I'll continue to test and update you.

https://youtu.be/Idk2Y4J0eDk

Edit: 2nd video test with pi2 and pi3b+ simultaneously ground/ pi0 air https://youtu.be/pD5k5h0G8SI

On Tue, Oct 16, 2018, 8:06 AM user1321 notifications@github.com wrote:

Next image: It contains bug fixes: mavlink-routerd, gst-launch, hotspot, DHCP. Using that image I able to connect via HotSpot to Ground RPi via phone, get parameters vis Ground Сontrol app (Android), receive video over raw h264 and RTSP.

As for RTSP, it confuse me a little. Using RTSP I get video with delay something like 0.5 second +

It`s look to me very strange, because I remember that using one of my images (not published here) It was significantly lower. So, is it normal? ( I am not saying acceptable. Just to know, as we trying to create a copy of original WFBC 1.6)

Also I did same test at "RussianImage" at RPi 3B+ and got same result with build in wifi card (RP 3B+) and with external one. So, please, check it also. And if you remember or know that it must (!) be lower inside GroundControl app ( I am not talking about VR_2018 app) . Please, say about it.

Also, this is not the end. Just some report about progress. P.S. Adjust settings.sh file for your configuration.

https://drive.google.com/open?id=1Mg7O1tQmn-GTEdkfCjWZdnZWXAhG58ga

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bortek/EZ-WifiBroadcast/issues/155#issuecomment-430211880, or mute the thread https://github.com/notifications/unsubscribe-auth/AcSp0iAyMN5i-zDLxO2akZSJ5vYWSpUDks5ulcvcgaJpZM4XYNu2 .

[pilotnbr1]

👍

[bortek]

Ping @pilotnbr1 @htcohio @user1321

"Now before we close this Issue can we agree on the proposal to draft the roadmap as @Yes21 suggested? Just say yes if you agree and if not please come with the suggestion."

[htcohio]

Yes