Replies

          • Yes  admins can always be added or removed later on, so probably a good idea to start with those currently contributing the most - personally I would think that to be Wolke and Clooney.  In the past chsw (Chris) and lvale (Luis) have contributed the most but haven't seen any sign of chsw lately.  I'd love to be involved but unfortunately haven't had the time to contribute much so far, although hopefully I'll do so more shortly.  Does anyone have good git/github kung fu?

            One of the benefits of moving to the official code space is that I would think we'd be expected to follow more the standard rules of the main projects regarding code formatting, documentation, releases etc.

            I do think this would be an awesome route forward for this project.

            • currently i think Clooneys repo is the most advanced one.

              if i am right i see some re-factoring, splitting special functions to own classes. imo a good starting point. also the new sport class which is used there. so i think maybe clooney or i can create an github organisation where we start with clooneys fork.

              creating github organisation... https://github.com/account/organizations/new . this is cost-free for open-source projects. imo an alternative way if starting to contribution on official dydrone -repo need an warm up or test period to collect all things together.

              i do not test Clooneys new sport class here. mostly because less time and the need of a stable camera platform. in moment I have areal season with my commercial used copter which also is the apm copter. that mean there is less space to use the system as an test platform. hopefully that i earn enough to construct an second apm camera platform in future. then i can used the old one for experiments with new firmware (apm 3.3, opentx2.1). currently i have two taranis transmitter. but because opentx2.1 turn me crazy, currently run 2.0.17 on both of them. but one of them is used only for gimbal and camera control. on this one i will reinstall opentx2.1 next.

              a general question is also which hard- and soft- ware should be the reference for this project?

              pixhawk and clones, taranis x9d, teensy 3.1, ardupilot >=3.3 and opentx>= 2.1.1?

              /g

              wolke

              • I normally have a lot of spare time, but I have not been programming for some year. So if somebody take the lead, I can assist in the work...

              • @Clooney,

                i currently follow the big progress on your fork. also on the lua side:). so i decide to discontinue my fork. this makes no sense any more and will confuse users. i change my readme.md shortly to "discontinued" and link to your fork firstly. also i will put some infos on it that we plan to collaborate (combine) this project.

                if am am right your fork also hold the lua scripts and sd card structure which run on opentx 2.0.17?

                /g

                wolke

    • Agree!!

      I have modified your led 2.0 version to simplify the cabeling on my copter. Also have a modified led_Control.ino to make it work. I am not a skilled hacker, but I have a lot of spare time....

      3702590238?profile=original

      • This reply was deleted.
    • yes,

      this is a good idea. because it looks like that there are currently many things which make problems. firstly sport sync with newer x8r receivers or newer firmware on it. especially eu - firmwares. second opentx2.1 sensor values. currently a main problem for all available lua scripts.  because all getValue(n) do not do the right job with 2.1.

      /g

      wolke

      • This reply was deleted.
        • woww:),

          that s cool. i am impressed. just looking in your fork on github on s-c-l-v-rc-opentx2.1 branch. you use a new sport library.  is sync now ok? and also with eu-firmware?

          /g

          wolke

          • This reply was deleted.
            • Hi all

              Just to remember all that there are changes being made on both platforms, i.e. OpenTX with the future 2.1.2 and specially ArduPilot that even this week had a big change on reporting that might/will affect all the "translators" https://github.com/diydrones/ardupilot/commit/767b4da5b6852a2ba700e....

              There will be a future development on Arducopter that will replace/add to the error messages to error codes.


              I would like to bring to everyones attention a project that might replace our Teensy's and our MinimOSD's. https://sites.google.com/site/alceosd/

              The project at the moment has no support to handle the FrSky but it is quite easy to add it, and the lead developer is open to further enhancements. https://github.com/diydrones/alceosd

              I
              MHO this project combines the needs we have with on the fly telemetry.

              • so that is one board combining teensy 3.1 and minim osd connected to s.port ?

                looks nice

                but hope you wont abandon the old project... 

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @a1k0n: Did I get rid of hand-tuned parameters? Yes. Am I still hand-tuning more parameters? Also yes. I have a few knobs to address the…
yesterday
DIY Robocars via Twitter
RT @a1k0n: I'm not going to spoil it, but (after charging the battery) this works way better than it has any right to. The car is now faste…
yesterday
DIY Robocars via Twitter
RT @a1k0n: Decided to just see what happens if I run the sim-trained neural net on the car, with some safety rails around max throttle slew…
yesterday
DIY Robocars via Twitter
Saturday
DIY Robocars via Twitter
RT @SmallpixelCar: @a1k0n @diyrobocars I learned from this. This is my speed profile. Looks like I am too conservative on the right side of…
Saturday
DIY Robocars via Twitter
RT @a1k0n: @SmallpixelCar @diyrobocars Dot color is speed; brighter is faster. Yeah, it has less room to explore in the tighter part, and t…
Saturday
DIY Robocars via Twitter
RT @a1k0n: I'm gonna try to do proper offline reinforcement learning for @diyrobocars and throw away all my manual parameter tuning for the…
Friday
DIY Robocars via Twitter
RT @circuitlaunch: DIY Robocars & Brazilian BBQ - Sat 10/1. Our track combines hairpin curves with an intersection for max danger. Take tha…
Thursday
DIY Robocars via Twitter
RT @SmallpixelCar: Had an great test today on @RAMS_RC_Club track. However the car starts to drift at 40mph. Some experts recommended to ch…
Sep 11
DIY Robocars via Twitter
RT @gclue_akira: 世界最速 チームtamiyaのaiカー https://t.co/1Qq2zOeftG
Sep 10
DIY Robocars via Twitter
RT @DanielChiaJH: Always a good time working on my @diyrobocars car at @circuitlaunch. Still got some work to do if I’m to beat @a1k0n howe…
Sep 10
DIY Robocars via Twitter
RT @SmallpixelCar: My new speed profile for @RAMS_RC_Club track https://t.co/RtLb7TcgIJ
Sep 10
DIY Robocars via Twitter
RT @SmallpixelCar: Practiced at @RAMS_RC_Club today with my new @ARRMARC car https://t.co/AEu2hCx89T
Aug 28
DIY Robocars via Twitter
Aug 24
DIY Robocars via Twitter
RT @gclue_akira: 柏の葉で走行させてるjetracerの中身 #instantNeRF #jetracer https://t.co/giVvuE4hP7
Jul 4
DIY Robocars via Twitter
Cool web-based self-driving simulator. Click save when the AI does the right thing https://github.com/pncsoares/self-driving-car
Jul 4
More…