Rev 50 | Go to most recent revision | Only display areas with differences | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed
Rev 50 | Rev 127 | ||
---|---|---|---|
1 | # RIDDIM |
1 | # RIDDIM |
2 | # -> Remote Interactive Digital Drone Interface Mashup |
2 | # -> Remote Interactive Digital Drone Interface Mashup |
3 | # |
3 | # |
4 | # Author: Marcus -ligi- Bueschleb |
4 | # Author: Marcus -ligi- Bueschleb |
5 | # |
5 | # |
6 | # Contact: ligi |
6 | # Contact: ligi |
7 | # -at- |
7 | # -at- |
8 | # smart4mobile.de |
8 | # smart4mobile.de |
9 | # |
9 | # |
10 | # Project Start: 12/2007 |
10 | # Project Start: 12/2007 |
11 | # |
11 | # |
12 | # Credits: |
12 | # Credits: |
13 | # Holger & Ingo for the Mikrokopter Project ( www.mikrokopter.de ). |
13 | # Holger & Ingo for the Mikrokopter Project ( www.mikrokopter.de ). |
14 | # eduard -- - at - -- hasenleithner.at for the linux x-52 lib |
14 | # eduard -- - at - -- hasenleithner.at for the linux x-52 lib |
15 | # |
15 | # |
16 | 16 | ||
17 | 17 | ||
18 | =Preface= |
18 | =Preface= |
19 | 19 | ||
20 | Project to Control and interact with a MikroKopter. The main Focus on startup is the usage of one X-52 Joystick in combination with one Router. The X-52 has the possibility to Display some something on the Joystick and has lots of Axis and Buttons - so i will prefer it for flying. |
20 | Project to Control and interact with a MikroKopter. The main Focus on startup is the usage of one X-52 Joystick in combination with one Router. The X-52 has the possibility to Display some something on the Joystick and has lots of Axis and Buttons - so i will prefer it for flying. |
21 | 21 | ||
22 | = Documentation = |
22 | = Documentation = |
23 | 23 | ||
24 | http://www.rcmovie.de/view_video.php?viewkey=7ec0047de2d5d1b28a75 |
24 | http://www.rcmovie.de/view_video.php?viewkey=7ec0047de2d5d1b28a75 |
25 | http://www.youtube.com/watch?v=3a0FSJTDQlM |
25 | http://www.youtube.com/watch?v=3a0FSJTDQlM |
26 | http://forum.mikrokopter.de/topic-2554.html |
26 | http://forum.mikrokopter.de/topic-2554.html |
27 | http://www.mikrokopter.de/ucwiki/en/Riddim |
27 | http://www.mikrokopter.de/ucwiki/en/Riddim |
28 | 28 | ||
29 | 29 | ||
30 | = Licence = |
30 | = Licence = |
31 | 31 | ||
32 | http://creativecommons.org/licenses/by-nc-sa/2.0/de/ (Creative Commons / Non Commercial / Share Alike |
32 | http://creativecommons.org/licenses/by-nc-sa/2.0/de/ (Creative Commons / Non Commercial / Share Alike |
33 | Addtitonally to this Licence it is not allowed to use this software in any violent manner. |
33 | Addtitonally to this Licence it is not allowed to use this software in any violent manner. |
34 | This explicitly includes that lethal Weapon owning "People" (e.g. Army & Police) are not allowed to use this Project |
34 | This explicitly includes that lethal Weapon owning "People" (e.g. Army & Police) are not allowed to use this Project |
35 | If you want to use this tool in any Commercial Context - please contact me first! |
35 | If you want to use this tool in any Commercial Context - please contact me first! |
36 | 36 | ||
37 | =Hardware Setup= |
37 | =Hardware Setup= |
38 | 38 | ||
39 | You need: |
39 | You need: |
40 | - 1x MikroKopter ( www.mikrokopter.de ) with bluetooth |
40 | - 1x MikroKopter ( www.mikrokopter.de ) with bluetooth |
41 | - 1x Saitek X-52 ( or X-52 PRO ) - later the support for other Devices can follow |
41 | - 1x Saitek X-52 ( or X-52 PRO ) - later the support for other Devices can follow |
42 | - 1x Hardware with the following minimum requirements: |
42 | - 1x Hardware with the following minimum requirements: |
43 | -> running linux |
43 | -> running linux |
44 | -> usb |
44 | -> usb |
45 | -> bluetooth ( later on bluetooth or wlan will be supportet ) |
45 | -> bluetooth ( later on bluetooth or wlan will be supportet ) |
46 | 46 | ||
47 | In the autohrs setup this will be my notebook ( its better for debug output ) at stage one and one Asus WL500g deluxe running OpenWrt in stage2. |
47 | In the autohrs setup this will be my notebook ( its better for debug output ) at stage one and one Asus WL500g deluxe running OpenWrt in stage2. |
48 | 48 | ||
49 | 49 | ||
50 | 50 | ||
51 | =Compile= |
51 | =Compile= |
52 | $> make |
52 | $> make |
53 | 53 | ||
54 | =Run= |
54 | =Run= |
55 | $> ./riddim |
55 | $> ./riddim [configfile] |
- | 56 | ||
- | 57 | if no configfile is given riddim is trying to load "/etc/riddim.conf". If that fails riddim is using default values ( not very usefull perhaps ) |
|
- | 58 | ||
- | 59 | example socat usage: |
|
- | 60 | socat tcp-l:54321,reuseaddr,fork file:/dev/ttyUSB0,b57600,waitlock=/var/run/rfcomm0.lock |
|
- | 61 | ||
- | 62 | ||
56 | 63 | ||
57 | = Changelog = |
64 | = Changelog = |
58 | 65 | ||
59 | 0.5 - code cleanup |
66 | 0.5 - code cleanup |
60 | 0.4 - Measure time from send command to confirm |
67 | 0.4 - Measure time from send command to confirm |
61 | 0.3 - mode selector |
68 | 0.3 - mode selector |
62 | 0.2 - first version with possibility to fly ( based on FC0.68b commands ) |
69 | 0.2 - first version with possibility to fly ( based on FC0.68b commands ) |
63 | 0.1 - initial release with basic functions and proove of concept Code ( Scanning for Blueooth Devices / read Joy / communicate to MK / ..) |
70 | 0.1 - initial release with basic functions and proove of concept Code ( Scanning for Blueooth Devices / read Joy / communicate to MK / ..) |
64 | 71 | ||
65 | 72 | ||
66 | = ToDo = |
73 | = ToDo = |
67 | 74 | ||
68 | - Force Feedback from ACC Sensor Data |
75 | - Force Feedback from ACC Sensor Data |
69 | - Support more JoySticks -> generalize |
76 | - Support more JoySticks -> generalize |
70 | - Support more Aircraft types -> generalize |
77 | - Support more Aircraft types -> generalize |