Recent Posts

Pages: [1] 2 3 ... 10
1
Showroom / Re: My first fixedWing plane
« Last post by Alex H. on Today at 12:00:46 pm »
Long time, nothing posted... the system says "for at least 120days", which is kind of true due to some other events.

Here is a short update on my build, as I'm still building this plane.

I was searching for a device which can carve into the foam, and finally I found one, as the one below, the nice thing is that you can change the same of that hot-wire.


Then I made some cuts into the foam, for battery, cc3d, receiver and servos


Mounted the ruderhornes, and tried to balance it to the front with some lead, temporary glued with tape, but no luck for the moment I still have to put some more :(, I hope it will not be too heavy in the end.


Next I will have to glue some of them with hot-glue and to make a top cover.
If everything is balanced I will try to launch it...
2
Français / Magnétomètre compatibles et dispos en 2019
« Last post by remis on Today at 11:30:45 am »
Bonjour,
Je me permet de refaire un sujet magnétomètre, car ceux disponibles commencent à dater. Le problème c'est la dispo de certains composants. Le HMC5883L est parait il compatible. Je ne peux pas le vérifier car il est obsolète.
Lorsqu'on le trouve , c'est en fait un QMC5883 ( vendu comme un HMC...) , qui n'as pas le même comportement en I2C : pas la  même adresses et je crois pas les mêmes registres. Les lib arduino basique HMC5883 ne fonctionnent pas même avec de petites modifs sur les adresses I2C. Il faut utiliser le code proposer par osoyoo.com que je n'ai pas analyser en détaille et qui fonctionne.

La question devient: Quel magnétomètre externe utiliser en 2019 avec libre Pilot?
Merci
3
Vehicles - Helicopters / Re: Starting PIDs and any other recommendations...
« Last post by TheOtherCliff on September 21, 2019, 05:06:32 am »
It should not be possible for the Atom to cause the receiver to reboot.  Not the Atom's fault, but the unmodified Atom or stock wiring may not handle the amps drawn by multiple high current heli servos.  There may also be vibration intermittent wiring.

If it (receiver reboot) is reproducible there are several fairly simple ways to give cleaner power to the receiver without changing anything else.  If that alone fixes the issue, I would be confident that the issue was understood.

It's hard to test for brief electrical problems.  :(  An overload/undervolt only needs to last for say 1/100th of a second to cause a reset and it requires special equipment, connected at a known problem site (rx in this case) to record something like that.

Did it only happen with the rotor spun up?  If it happened even without the rotor spinning, it is a lot safer to troubleshoot and it might save you some grief to know the cause for sure.  With strange problems, I often find that trying to make the problem go away just makes it harder to reproduce.  Maybe on the bench try to load down several servos by hand to reproduce the problem.  You've got a new FBL unit that you will go back to, but I would put the Atom back in and 100% fix that problem first, to know that the FBL is safe too.

It's very common that the high load servos in a heli cause electrical power overload issues.  Receiver and FC reboot can be the result.  Be careful to watch for the receiver still rebooting.  I hope that your new FBL unit has special filtering in it to keep the receiver running during these load spikes.

Good luck!  :)
4
Vehicles - Helicopters / Re: Starting PIDs and any other recommendations...
« Last post by FlyNFool on September 20, 2019, 10:43:41 pm »
I had to ditch the Atom for this project. I have been having odd Rx reboots and I think it's something to do with this particular Atom, as a change in wiring and a different Rx still exhibit the issue. It will, somewhere around the bottom 20% of collective stick, somehow trigger a reboot of the Rx. I know by monitoring voltage that it's not an overload or high draw problem, like a sticky spot in the collective or jammed servo.
 :-\
I'm going to 3D print a basher quad and stick it in that to see if the problem is just in a heli configuration, or if it persists in a quad configuration.

Feeling less than confident about using a CC3D in this my only heli, I ordered a popular regular FBL unit to use instead. Heli is now flying.

Thank you for all the help. Perhaps I will get a cheap clone FBL heli and try again with a different CC3D in the future.
5
General Discussion / Re: Oplink Relay Station with Telemetry Display and Logging
« Last post by jdl on September 20, 2019, 03:49:11 pm »
I've had success with both HC-05 & HC-06 modules from Banggood and xt-xinte. Old Dell Latitude D630 laptop with Windows7. Never tried on Linux...

Here is a list of instructions I've used to configure BT modules, hope this can help:

--------------------------------------------------------------------------------
HC-06 (slave):

Code: [Select]
Connect to the new module using Arduino Serial Monitor, setup to 9600bps, No line ending.

AT             // just to confirm module is connected
AT+BAUD7
                // Now set Serial Monitor speed to 57600bps! Re-power module!
AT
AT+PIN1234                 // 1234 is the new password
AT+NAMEBIG_RELAY_BT // BIG_RELAY_BT is the new name

--------------------------------------------------------------------------------
HC-05 (slave)

Code: [Select]
Connect to the new module using Arduino Serial Monitor, setup to 38400bps, Both NL&CR

Enter HC-05 command mode by pressing SW while powering module up!

AT                 // just to confirm module is connected
AT+UART=57600,0,0
AT+NAME=BIG_RELAY_BT
AT+PSWD=1234
            

--------------------------------------------------------------------------------
HC-05 (master) - I use it in the antenna tracker station, to connect to oplink relay station(s) and receive the telemetry with GPS data

Code: [Select]
Connect to the new module using Arduino Serial Monitor, setup to 38400bps, Both NL&CR

Enter HC-05 command mode by pressing SW while powering module up!

AT             // just to confirm module is connected
AT+ORGL
// Re-power with KEY pressed

AT             // just to confirm module is connected
AT+UART=57600,0,0
AT+NAME=TRACKER_HOST
AT+PSWD=5678
AT+PSWD="5678" // One HC-05 module came with newer firmware, PSWD command has changed syntax!

AT+RMAAD
AT+ROLE=1
AT+RESET
// Re-power with KEY pressed
AT+CMODE=1 // Must be 1 to be able to connect to anyone of the relay stations (which one is available)
// Passwords of host and slave modules MUST be identical

AT+INQM=0,5,9 // Execute with KEY pressed


AT+INIT // Execute with KEY pressed
AT+INQ // Execute with KEY pressed
// select the address of the desired slave from the list


AT+RNAME?98E3,32,610466 // Execute with KEY pressed, ... just to check the name of desired slave...


AT+PAIR=98E3,32,610466,10 // Execute with KEY pressed

AT+BIND=98E3,32,610466 // ... this may not be necessary as AT+CMODE=1...
--------------------------------------------------------------------------------

6
General Discussion / Re: Oplink Relay Station with Telemetry Display and Logging
« Last post by TheOtherCliff on September 20, 2019, 05:37:13 am »
I think I recall having better luck with the slave only one, but I recall there was still an issue where I had to configure something or other each time I wanted to use it?  Issues with Blueman?  Issues with powering up the chip and the button for the master-slave one?  It's been a while.  :)  The bluetooth was fairly low on the list since it was easy to just connect a 3 meter USB cable to the laptop.

I tried variations on the bluetooth instructions in the wiki, and what I could find on line.  I recall that I did finally find a good set of AT commands that matched my device.  Certainly partly my fault for buying a cheap bluetooth rather than a common bluetooth.  I would like to try again if you know of some fairly complete instructions.  :)
7
General Discussion / Re: Oplink Relay Station with Telemetry Display and Logging
« Last post by karla on September 20, 2019, 04:36:41 am »
Lovely thing!

@cliff, may i guess your reluctant bluetooth unit is a hc-05 with 6 pins and not hc-06 with 4 pins?
I have never been able to successfully configure hc-05, but hc-06 units always works.
8
Vehicles - MultiRotors / Re: Troubleshooting motors/ESC/Revolution
« Last post by TheOtherCliff on September 19, 2019, 10:26:38 pm »
ESC #1 smoked and burned.  Really no need to spend time on it.  It is dead.

FYI: PPM is a receiver signal protocol.  PWM can mean either a receiver or ESC signal protocol.  ESCs don't use PPM but this is not an issue for you.

You can calibrate and test with [email protected] and it will work fine, but when you try to fly it, it will oscillate.  If you successfully calibrated to 1000-1900 using [email protected] you do not need to recalibrate.  Just change to PwmSync or [email protected]

You should start by using a current limited power supply / light bulb for safety (so a bad ESC/motor doesn't fry yet another motor/ESC) and getting all your ESCs and motors tested and working.  It's hard to do a setup from scratch without working ESCs and motors.  Direcly connect the ESC to the RC receiver if you suspect the FC may be bad.

Run LibrePilot setup from the beginning and choose RapidESC from what I recall.  After running setup, you can look at the Output page and verify that you have [email protected] or PwmSync for all motors.

Having very different ESCs or motors won't stop you from setting it up.  Having different ESCs or slightly different motors can cause slight bobbles when flying though.  Unless they are very different (like KV1000 and KV1500) you should at least be able to get it to hover well and start testing moving around.  You haven't got nearly that far yet.

Have you ever connected more than 5 volts to the FC?  I know it says it can take more, but for instance the signals going into the FC can never be higher than 5 volts.

ESC firmware, that is a whole 'nother big topic.  There are gadgets to buy to flash the firmware.  No need to spend more than $5 or so but there is a lot for sale for more than that.  There are two main brands of firmware (SimonK and BLHeli).  There are two main processor (CPU) types and different ways (adapter cables) of connecting to them.  Maybe research BLHeliSuite.  Also (be aware that you don't need an ESC protocol faster than [email protected], but that is a HOTLY contested subject):
https://oscarliang.com/esc-firmware-protocols/

<soapbox>

For a middle of the road quad motor you are probably running say 6000 RPM at hover.  That is 100 revs per second and with [email protected] you are sending "change RPM" commands about 500 times per second.  So even with [email protected] you are changing the RPM 5 times per prop revolution.  Smaller quads and higher RPM motors and full throttle might be 30000 RPM is 500 RPS and you can change the RPM once per revolution.  Now I will tell you that ESC firmware smooths out the input variances which reduces the effective signal rate, but that is an issue to be addressed in the firmware if you think you actually need to change the speed of the prop 5 times in one revolution.  You have to remove the smoothing to get the faster protocols working faster too.

It's not very useful to decrease the control delay from .002 to .000000001 when the human adds .25 to the delay.  To actually significantly change the RPM several times per prop revolution would require huge current draws and generate torque that would snap a quad's prop and even snap it's arms off.  Maybe faster response will be more useful in the future with much better hardware and autonomous control that takes the human out of the loop so that the quad is flying stunts itself.

I will grant you that there are high end cases where one step up in protocol speed (say 8x) is useful today, and that changing to a bidirectional digital signal format is useful, but claiming to need to change the RPM 150 times per revolution even in this worst case (that would be 750 times per revolution in a more normal case)?  Or the other side:  Reducing a typical delay from 1/5 prop revolution to 1/750 prop revolution.

</soapbox>
9
General Discussion / Re: Oplink Relay Station with Telemetry Display and Logging
« Last post by TheOtherCliff on September 19, 2019, 08:41:27 pm »
Ooooooh, I like the telemetry screen!  And that was before I saw that it does logging without a laptop and to an SD card!!!  Automatic logging would be useful in the day to day usage, but especially useful that one time you didn't log and your plane went down and you don't know the GPS coordinates.

With your idea, how long has it been, a couple years ago?  I "built" :) a simpler setup onto an arrow.  Simple but functional.  Arrow point sticks in the ground and the antenna is on top.  RC transmitter to OpLink relay with bluetooth.

The Oplink has an RFM23BP and an added power input (fed from external 5V/6V) and filtering for it.  The added power input feeds the RF directly and also connects to the OpLink mainport/flexiport and thus provides power for everything.  There is also a silicon diode from normal +5V OpLink power input (usb/mainport/flexiport) to the RF so that it will still work at approximately stock RF power if the second power input is disconnected.  I often power it via USB from my laptop/GCS and skip the battery.  BEC has a jumper for 5V/6V so I can actually run it at 6V, but I have never tried that and probably never will.  So RF has 3 different possible power inputs, 4.3V, 5V, and 6V.

The OpLink was one of the ones with a bad RFM22B, so it wasn't a waste even if it didn't work and I really like the SMA connector.

I haven't got the bluetooth working yet.  I fought it a while (bluetooth chip versions on one side and old Linux configuration on the other side), then put it aside.

I am currently limited by FPV video range, but I am considering an RFM23BP Revo mod and using OpMap or the synthesized FPV of OSGEarth for ground based projects, etc.  :)

Below the OpLink hang the BEC, Bluetooth, and RC receiver.  The battery is rubber banded on.

A short extra stub of arrow shaft is glued parallel to the arrow shaft at the top so the antenna is not wobbly.

I note that this relay does add a small control delay.  You've actually got normal RC control delay plus normal OpLink control delay.  This is not enough to generally cause problems, but can make close in FPV hovering even more challenging.
10
General Discussion / Re: libprePilot simulator flight test
« Last post by TheOtherCliff on September 19, 2019, 06:40:39 pm »
It is my understanding that this is done by some developers when testing new flight mode code.  In some modes it uses a joystick or you can use your transmitter if you have a buddybox USB dongle that works with it.

Search the forum for "flightgear" and for "flight gear" and for "simulator".

LibrePilot also supports some other simulators (May be broken.  May require specific simulator versions.)
Quote
[email protected] ~/dev/librepilot/1609 $ find ground/gcs/src/plugins/hitl -iname '*sim*.cpp'
ground/gcs/src/plugins/hitl/xplanesimulator10.cpp
ground/gcs/src/plugins/hitl/xplanesimulator9.cpp
ground/gcs/src/plugins/hitl/simulator.cpp
ground/gcs/src/plugins/hitl/il2simulator.cpp
ground/gcs/src/plugins/hitl/fgsimulator.cpp
ground/gcs/src/plugins/hitl/aerosimrcsimulator.cpp
Pages: [1] 2 3 ... 10