Search found 21 matches
- Sun Jun 03, 2012 11:54 am
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
I assume that you have a correct dimensioned volt divider for 4S which brings 0-16,8V to 0-5V, if so in config.h change "#define HOTTV4_VBATLEVEL_3S VBATLEVEL2_3S" to something like "#define HOTTV4_VBATLEVEL_3S 129" if you want to be notified when current voltage gets below 12,9V...
- Sat Jun 02, 2012 4:50 pm
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
Ok, now I see what you mean. Should be possible, because the Mikrokopter voice files are officially available from Graupner and I think it should be possible to get such a behavior as shown in the video. Not planned yet to implement it, there is a little time left next week were I could take a look...
- Mon May 21, 2012 10:31 pm
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
As described on the GitHub Page - currently transmitted data are: LiPo voltage, relative height over ground, and flight time since copter has been armed.
Cycle time increases up to 35ms each time telemetry data are getting updated, that why the data are updated with 0.5Hz.
Cycle time increases up to 35ms each time telemetry data are getting updated, that why the data are updated with 0.5Hz.
- Sat May 19, 2012 2:01 pm
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
Ok, now I see what you mean. Should be possible, because the Mikrokopter voice files are officially available from Graupner and I think it should be possible to get such a behavior as shown in the video. Not planned yet to implement it, there is a little time left next week were I could take a look ...
- Sat May 19, 2012 9:49 am
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
Any Plans about Voice Output ? somethink like that : m Voice Output is made by the transmitter, e.g. MX-12, and not by the receiver. If you have a working telemetry, just enable voice output on your MX-{12,16,20} and select the values you wanna hear and put the voice output on a trigger. E.g. I hav...
- Wed May 16, 2012 11:25 pm
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
OK, I'll try to describe it better (don't hesitate to ask again, if it won't work. I will also update the github page in a couple of days). First thing, I don't have any idea how to connect a LLC because I don't use one. I just recommend to use one, so I don't want that someones Copter goes down due...
- Wed May 16, 2012 2:02 pm
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
I don't own a MC-32, but the website says:"Integrated Graupner HoTT 2.4 GHz transmission system", so it should be capable of handling HoTTv4 data telegrams. And yes, RX/TX together, because HoTT uses one wire to transmit and receive data (the extension handles this and shuts down RX when d...
- Mon May 14, 2012 12:34 pm
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
Finished implementation of PID value adjustments via Graupner HoTTv4.
http://www.youtube.com/watch?v=rItCvYUPo_o
http://www.youtube.com/watch?v=rItCvYUPo_o
- Tue Apr 24, 2012 1:58 pm
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
I'm not following this road on using a second arduino. As far as I know fred_fr is investigating this. What I can tell you so far is, that the "lag" which happens every 2 seconds when telemetry data are updated doesn't influence QuadCopter stability (from what I can tell, see m). The twich...
- Wed Apr 18, 2012 10:52 am
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
Yes it does run on the FC arduino. Currently running on a Mega2560, I hope it bloats the code not to much so it can run on a ProMini too.
- Tue Apr 17, 2012 10:57 pm
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
Next dev step will include PID reporting and changing
- Wed Apr 11, 2012 11:25 pm
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
Hi Hamburger,
I'm going to change it immediately to GPLv3, it was absolutely my mistake for being not accurately enough.
Thank for pointing it out.
oli
I'm going to change it immediately to GPLv3, it was absolutely my mistake for being not accurately enough.
Thank for pointing it out.
oli
- Wed Apr 11, 2012 8:33 pm
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
Current development of HoTTv4 in MW2.0 can be found here: http://github.com/obayer/MultiWii-HoTT
- Mon Apr 09, 2012 1:09 pm
- Forum: Software development
- Topic: VBAT incorrect value
- Replies: 19
- Views: 8123
Re: VBAT incorrect value
I had the chance to test it yesterday with the solution Alex described, nothing changed so far. I reflashed the Mega2560 board with the original MW2.0 and my telemetry extension and it worked without any problem, so I think that it's not a MW2.0 problem, maybe one of my cables is the problem. I will...
- Mon Apr 02, 2012 11:15 am
- Forum: Software development
- Topic: VBAT incorrect value
- Replies: 19
- Views: 8123
Re: VBAT incorrect value
Thanks Alex, will try it this weekend and will let how know how it works.
- Sun Apr 01, 2012 10:16 pm
- Forum: Software development
- Topic: VBAT incorrect value
- Replies: 19
- Views: 8123
VBAT incorrect value
Hello, today after switching to MultiWii 2.0 I discovered that VBAT readings are not correct anymore, or rather not correct after some flight time. I'm getting the VBAT reported via telemetry and when I start, VBAT says 12,6V which is totally correct after flying around for a couple of minutes it st...
- Sat Mar 31, 2012 5:19 pm
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
@chriszero Yes and No, what I determined is, that the HOTT receiver is very generous regarding the delays. The range gets from 650us up to 4ms between each byte. Furthermore do I not use a LLC, just a diode between RX and TX, that's all (maybe I should consider using one). Although I'm spending 3500...
- Mon Mar 26, 2012 12:46 pm
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
Timing issues also applies to the Mega2560 boards, because you still have to wait between each byte that is being transmitted. The advantage of the Mega2560 board is that you don't have to share your serial interface that is used for parameter programming. HOTT telemetry uses only one wire to transm...
- Fri Mar 09, 2012 10:10 pm
- Forum: Software development
- Topic: MultiWii 2.0 is coming
- Replies: 256
- Views: 107941
Re: MultiWii 2.0 is coming
Is there any reason, why SIGNAL is used in Serial.ino to define interrupt routines? As far as I know, SIGNAL is deprecated and should not be used any longer, but ISR.
Futhermore SERIAL_COM_SPEED is not used in any SerialOpen() state and therefore has no influence.
Futhermore SERIAL_COM_SPEED is not used in any SerialOpen() state and therefore has no influence.
- Fri Mar 02, 2012 6:37 pm
- Forum: Ideas
- Topic: HOTT Telemetry integration
- Replies: 63
- Views: 36279
Re: HOTT Telemetry integration
I'm having a working HoTT implementation in my own 1.9 version of the MultiWii Software. It is currently able to send you the LiPo voltage and relative height from ground. It uses the same Arduino that is used for FlightControl to generate telemetry data on serial out. The only problem is, that the ...
- Thu Jan 05, 2012 11:25 am
- Forum: Software development
- Topic: BUG: GYRO_ORIENTATION is not applied to WMP
- Replies: 6
- Views: 2822
Re: BUG: GYRO_ORIENTATION is not applied to WMP
Would it be possible to fix this bug within the next release?
I would also move the GYRO_ORIENTATION macro into Gyro_common, because it affects all Gyro sensors and you follow the rules of "Don't repeat yourself".
I would also move the GYRO_ORIENTATION macro into Gyro_common, because it affects all Gyro sensors and you follow the rules of "Don't repeat yourself".