Jump to content

trach555

Members+
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About trach555

  • Rank
    RC-Cam Visitor
  • Birthday 02/02/1981

Profile Information

  • Location
    Poland
  • Interests
    statistics, data mining, programming, R language, SQL, Arduino, RC, video games
  1. In case of problem with CleanFlight here is recipe how to install older version (which we know it was working) Please, can you describe PID parameters, because I don't have any idea what I am changing? Even some intuition could be useful. Here is screen from my PID (comparing with yours notice that there is different scale on Proportional and Integral)
  2. Hi, I've uploaded MWOSD firmware and one of its feature is that you can change most of the settings via gui interface using your transmitter and goggles. Best regards gc
  3. Hi, I tried to use yours numbers - I do not know exactly if I did, because in my CleanFlight cfg one column had totally different scale - I think it was column with digits after decimal point (I wanted to upload printscrean img but I have problem with connecting to CF). Your values give model which act like it has altitude hold function. Sometimes there are some small niticable jumps. How generally throttle stick supposed to act. Should I configure it before to be "neutral in the middle"? Problem with CF. When I connected my Rodeo 150 to computer I get a warning about non cleanflight firmware when starting CleanFlight. It is not recognizing my drone. I've attached image - previously I had exactly the same numbers of firmware version and other values like on yours printscreens. I've seen that there was an update of CleanFlight. It doesn't support Rodeo 150 anymore? Thanks for the mic recipe. Best regards gc
  4. Hi, I've finally recieved package MS5611. So I've mounted it and it works. Cleanflight sees it, but I haven't try it in the air yet. I've noticed that without unsoldering two resistors (you mentioned) my Rodeo 150 couldn't start - the beep sequence sounded a little different and I couldn't arm it, but I didn't connect it to Cleanflight to check if the i2c counter drops down. Maybe with BMP280 there is also something with pull up resistors that could be unsoldered? Have you measured how much time of flight decreased with added micro minim OSD and MS5611? By the way, have you been trying to do something with microphone on video transmitter? I'll try to find some time on weekend to test alt hold outside and I let you know how it works. Regards gc
  5. During tests I was using proper sequence of connecting first battery then USB cabel. My vreg is step up and down. When battery is attached it has exactly 3.3v (5v from 6pin jst is lowered to 3.3v). When battery is not attached and the USB cabel is plugged then on 6pin jst is 0.28v which my vreg increase to 2.8v. So even without battery BMP280 has power from USB cabel. Wires are 4cm long (less than 2 inches, about 80%*2 inches). I've read a little about SP Racing F3 controllers and I've noticed that they offer products with MS5611 and BMP280 (cheaper version). So I understand that your guess is that Rodeo's creators messed up something in Rodeo's version of firmware. I'm also waiting for the package with MS5611. When it comes I follow Yours solution and we will see. Maybe there is something wrong with my unit or maybe I mess up something that I am not aware at the moment. Thanks for Your help. I'll write when I get the package and check solution with MS5611 Regards gc
  6. I performed the tests. A. set mag_hardware=1 and set baro_hardware=0: with BMP280 installed i2c error count=1; without BMP280 i2c error count=2 B. set mag_hardware=0 and set baro_hardware=0: with BMP280 installed i2c error count=3; without BMP280 i2c error count=4 The same results I get with grounded SDO and without grounded SDO. I also noticed that there is very small value of voltage (0,28v) on 6pin jst when I connect Rodeo 150 via USB to PC (without battery attached). I used step up/down vreg. So my BMP280 have 2,8v on input without battery (I get the same results of tests with and without battery attached). Is it possible that the problem i caused by my vreg (it has common ground - I used this vreg http://www.ebay.pl/itm/272202572258?_trksid=p2060353.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT).
  7. Yes, exactly this one. I tried your tip, but it didn't help. I also checked i2c address via Arduino Uno, and BMP280 sensor has address 0x76. I also learnt how to use CLI - before I wasn't saving changes. I disabled mag and baro sensor. So, i2c counter was 0. Then I enabled BMP280 (set baro_hardware=4) and the i2c counter was still 0. Do I need to enable something via Cleanflight? I have UART2 enabled (like you show in micro OSD post).
  8. I am using BMP280 board exactly the same as post the image in other post (the purple one). I haven't add any additional resistors. Does it matter if I add resisitors between i2c wires SCL, SDA and vcc (5v) before vreg, or I must add resistors to vcc (3,3v) after vreg?
  9. Hi again, I am trying to add BMP280. I am using vreg to get 3.3v (BMP works with 3.3v). I2c wires I've connected like you did. When I conect my Rodeo 150 to Cleanflight (I connected battery first, before I plugged usb cabel), I can see that baro sensor is missing (there is no green icon of barometer). But i2c error counter drop down to 3. I was trying to use CLI and command set baro_hardware and set mag_hardware (like you described in other post about Rodeo), but those don't change i2c error counter (like you wrote). Do you have any idea from this description what I am doing wrong? I also checked BMP280 sensor with Arduino Uno and it is working. I've heard something about logic level converter. Do I need to use something like this? Regards gc
  10. Hi, I'm going to try with BMP280 barometer sensor. I've noticed it needs 3.3v, so I need to use vreg (on 6pin jst there is 5v). Do I need to do something else? Will I have to unsolder some resistors from BMP280 like you did with MS5611? Regards gc
  11. Hi, Have you tried to setup RSSI on OSD? I don't know if Rodeo 150 + micro MinimOSD has everything what is needed to monitor RSSI. I've noticed that in cleanflight it is possible to set RSSI on some channel, but I don't know if change of this require some changes in hardware. There is also some option connected with RSSI and ADC. Also, the description of MW OSD is not so clear (link below; user guide and calibration files are connected with RSSI). https://github.com/ShikOfTheRa/scarab-osd/tree/master/OTHER/DOCUMENTATION I've tried some setup of RSSI an I follow this movie to calibrate RSSI But, when I turn off the transmitter and turn it on again It doesn't bind with quad, so I can't even click save and exit on OSD. Is there any trick for that issue?
  12. Hi again, I am looking forward to hear some microphone project news. I think it would be nice upgrade. Just like in car, it is usefull to hear engine. I've got another question. I have Devo 7 with firmware in version B. Do you know if the range signal 10mW against 100mW is caused only by firmware version, or there are some hardware differences? Do you know if it is possible to change version B to version A, with some soldering maybe? Do you know if Rodeo 150 is prepared for oneshot125 option? I've noticed in cleanflight this option. Does it change anything if I turn it on? I've read something about it, and I found that ESC must be prepared for oneshot "feature". Does Rodeo's ESCs are compatible?
  13. Hi, I've noticed that my Rodeo 150 has firmware version 1.13. Now, it is available version 1.14.1. Is it save to upgrade firmware via cleanflight tool? Or maybe Walkera interfere to much in original cleanflight code, and it's better to not to update it. Could we say that we have SPRF3 board? I've also noticed that there is a small microphone on vTx in my Rodeo 150. But my Eachine EV800 goggles does not receive audio (there is posibillity that goggles are not working correctly, I haven't got any possibility to check on another equipment yet). Is there any way to turn on audio transmision or this vTx is only for video transmission? Regards gc
  14. Yes, the problem was in wiring. In the original Rodeo 150 camera red wire is ground and black wire is vcc - who would have thought... It works with MWOSD ver 1.6. I've connected Rx and Tx to UART's pins, so it works also. Thanks gc
  15. Hi, I was trying to follow your steps and add micro minim osd to my Rodeo 150. I had problem to compile KV_Team code from link above, so I decided to use MWOSD. I flashed micro minim OSD and connected according to your scheme (I connect RX and TX to UART socket). In GUI I add only AHI and timer (nothing fancy). If I try to turn on my quad (plug in the battery) it won't start (only front led is on; there is no starting bip sequence). Do you have any idea what I could do wrong? Have you try to use MWOSD (ver. 1.6)? Have you try to add micro minim OSD with original Rodeo 150 camera? I've read that there are some compability issues with some cameras, so I wonder if it matters that you've changed camera. If you use UART2 for RX2 i TX2 do you still need those two 1k resistors? Could be any difference if I solder those signals wires exactly like you? Regards gc
×
×
  • Create New...