the.Legend

Members
  • Content

    114
  • Joined

  • Last visited

  • Days Won

    1
  • Feedback

    N/A

Everything posted by the.Legend

  1. It's been a year since the last update, eh? Fear not, the project is still moving forward! Now that there's more free time in winter I hope to catch up on what was delayed. Actually, there was another reason for delay - I switched to new display type and then spent countless hours banging my had against the wall trying to figure out why suddenly the image was distorted, but I can say with confidence it was worth the effort. The new display solves the problem of blurry image as well as it lets me display more information at once. Also due to it's size it's nicely positioned in front of the eye and fits under visor (it'll look even cleaner and slimmer once all the boards are hidden) One more benefit of the new display is adjustable focus, meaning people with vision complications can adjust it to their needs raw changes: https://github.com/RomanTheLegend/WingsuitGps/tree/composite_display Two primary tasks for the nearest future are 1) Improve the UI 2) Implement WS competition mode. Now that everything on the screen is clear and readable, I can implement visual gauges to display distance to the gates and deviation from the flight path. But this feature would take some time because reliably detecting the moment when competitor leaves the plane would be tricky. I think of implementing Kalman filter on data stream to detect true-positive downwards acceleration. If anyone has the experience with these please lend me a hand (preferably, in form of github merge requests :) ) P.S. I've been thinking of changing the project name to FlySense. Why? Well, if FlySight doesn't display a thing, calling it FlySense sounds logical because you won't feel anything either. P.P.S. The more I work with ESP32 platform the more awesome possibilities I'm discovering. Potentially, FlySense will be able to replace Sena/Cardo intercoms in the distant future https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/network/esp-wifi-mesh.html#mesh-self-organized-behavior . Very distant future because the scope of work is huge
  2. Out of pure curiosity (i.e.not planning to jump), what would be the biggest and smallest canopy this trick is possible to execute on? And does this require additional setup like trimming or extra weight?
  3. https://en.wikipedia.org/wiki/Short_SC.7_Skyvan According to the list, not many SkyVans still operating, and none in Southern Europe (but you may ask Olympic Air where they sold theirs) Another option is to look for An-28 - it was used as a jump plane in Kharkiv (Ukraine) before the war broke out, and because some units were also produced in Poland back in the days, there's a chance some of remaining 16 still flying somewhere in Europe
  4. Taking canopy downsizing as an example, there has been quite helpful list of drills and exercises a pilot should feel confident to perform before considering switching to smaller size. Likewise, it would be nice to have the same for switching to a bigger wingsuit. For example, I wish I learned to fly whole jump with arm-wings collapsed and palms touching BOC before switching to a bigger suit. What other drills would you recommend for self-evaluation?
  5. Earplugs reduce both sound pressure levels in the same way, yes. The point is that when you reduce everything then amplified loud speakers are no longer too loud and are healthy. Let's say, for example - Wind produces 100 dB noise - Amplified speakers produce 110 dB output If you put on the earplugs that reduce the sound pressure by, say, 60dB then you get 40dB of wind and 50dB of voice - which is all well within healthy limits, and if that's not enough you still have some room for small speakers amplification (sound pressure scale is exponential so you won't need much) (I took just some ballpark figures to explain the idea)
  6. Sena 10R is too old by modern standards because it supports only up to 4 intercoms. Newer models have this thing called Bluetooth Mesh that pairs way more devices, and does this dynamically so if someone gets out of range it doesn't break connection for other. Cardo's PackTalk Slim is so far the most popular among people I know. BTW chinese intercoms can't do that yet. In some other thread I posted about available models in more details: Another reason why stick with Bluetooth is that you need something full-duplex, and none of walkie-talkies in reasonable price range can give that How about trying latest helmets from Cookie or Tony? As far as I'm aware, they are a bit more aerodynamic, and G4 additionally padded so that might bring overall noise level. By the way, top motorcycle helmets follow the same approach - to make them quieter make them more aerodynamic Another simple trick that might work is simple battery-powered sound amplifier, albeit it wouldn't be the healthiest solution because you'd just be fighting loudness with even greater loudness. That being said, what worked for me well in motorcycles is driving with earplugs you'd use in wind tunnel. They cancel wind noise just fine, bringing overall levels, and if you add an amplified sound output in speakers you may actually get good sound
  7. Indeed this is a marvelous achievement by "buzz"-news outlet to finally cover a flight that took place over a year ago
  8. Get 200 regular jumps first. While working on that, investment in canopy flying camps and tracking camps would help. You want to build skills and be prepared for when things go wrong (that would happen sooner that you might expect) After that, there are few good base schools in Europe. Yeah, it's quite far away and is costly (especially knowing KZ income levels), but less expensive that your life. Limska Draga in Croatia is probably the most popular and safest place for FJC and few schools operate there. They have nice facilities for ground training, gear rental and current experts in the area. Won't recommend any school in particular, just google them. In this sport you want to learn from the best athletes you can find. Don't look for shortcuts (https://www.blincmagazine.com/forum/wiki_index.php?title=Reginaldo_Gomes_Da_Silva_Junior ) and slowly build your discipline and skills Few good films that may help you set your thoughts straight: https://www.youtube.com/watch?v=O69eeLTgJb0 https://www.youtube.com/watch?v=vxhlhmlwSB4 (also try to find on VK or something the film called "Выход" Антон Калюжный - it used to be on YouTube but now it's been removed unfortunately)
  9. Project went silent, but not stalled :) There's been a lot of work behind the scenes and I'm releasing major code update tonight: https://github.com/RomanTheLegend/WingsuitGps * Introduced support for TTGO device * Fully redesigned architecture. Everything is modular: modes, devices, features. Each mode is a separate class so it's easy to develop new ones. * You can switch between operation modes using menu * Support for Bluetooth - you can stream GPS data to BASEline on your phone (friendly waving to @platypii ) It's still in Alpha state - code needs lots and lots of optimizations and stability improvements. I'm a novice C++ programmer, and many things done not the way they should. This will be fixed with time as I gain more experience. Meanwhile code review by someone experienced is really appreciated. Next I'll be focusing on 3D models for the body, buttons for TTV and also rewiring stuff in more optimal way (pieces would be plugged to each other via JST) . First model would be tailored for Kiss helmets, other models to come later. What else on the priority list: * Flash GPS to higher baud rates (by default it does only 2 readings per second, I want 5 like in FlySight) * Switch to UBX protocol which is faster than NMEA and more data-rich (FlySight also uses UBX) * Refactoring * Fonts optimization (currently font file for digits is too big, sometimes program fails to flash) * Multi-page menu Less priority: * Settings * Save data between device reboots
  10. I think it just comes down to marketing in a sense that simply a sheer number of cookies all over DZs make you forget there are alternatives. Furthermore, you'd find G3s in stock in every shop out there, while Kisses often come on backorder (at least where I am from) From design perspective both are good helmets with their pros and cons. First time hearing something about particular full-face model having to do with experience. Usually it's about whole category altogether i.e. students don't jump full-faces for a reason.
  11. Thanks! Looks like it boils down to intercoms that have Bluetooth Mesh support and there are only very few of them on the market: Sena 30K, Cardo PackTalk, Midland BT Rush, Interphone U-Com 16, UClear Motion 6, and EJEAS Q4 All are pricey Two notable models: https://www.ejeas.com/product/q4/ is the cheapest - 158$ for a unit which supports up to 4 pilots and https://www.interphone.com/en-es/Interphone/Intercoms/U-COM-16/p/INTERPHOUCOM16 supports up to 24 pilots (also they claim to be the thinnest mesh intercom on the market) Both seem to be out of stock [Edit] Clarification: Bluetooth Mesh is the technology that allows dynamic group configuration, meaning 2 things: 1. If flyer gets out of range, other people do not loose connection. In conventional intercoms fliers are connected one-by-one like links in the chain, but in mesh each flier maintains multiple connections simultaneously. 2. Flyer gets connected automatically once in group range again
  12. Hi everyone, does anyone have an experience with solutions for voice communications mid-flight? I was looking for something for group conversation and so far the options checked: * Group calls - doesn't work because there's no carrier signal at the altitude * Walkie talkie - doesn't cut because only expensive models are full duplex, without it people can't talk and listen simultaneously * WiFi hotspot + app called "Talkie" (link to app on Playstore) - works in general and supports Bluetooth headsets, but is unreliable. If for any reason WiFi connection is interrupted it can't dial back automatically * Motorcycle intercoms - the option I'm about to try. It can automatically reconnect and is full duplex, but the best group limit I found is 5 people: https://www.aliexpress.com/item/4001208979534.html That's probably enough for most of the jumps, but I'm curious if there are any better solutions
  13. It would be the best if someone could film your flight and analyze body position. There are little details that you might not feel while flying which would be evident on footage immediately.
  14. If you record GPS data somewhere you may try Dashware (http://www.dashware.net/dashware-download/) - it's free and can support multiple GPS formats. You can even build your own gauges. I used it for overlaying GoPro's GPS data, although it was tricky and required first exporting the data from the video file via https://goprotelemetryextractor.com/free/# and then linking it back in the app. App's development has been discontinued in 2015, it still works, but it's not always user-firendly. Another bummer GoPro is slow to pick up GPS signal once it starts recording, so you may have data recorded starting from the middle of the jump For basic stats you may use GoPro's moble app and simply put one of stickers they offer (but those are basic, unlike fully custom ones in Dashware) GoPro 6 and later all have this feature enabled by default
  15. LCDs and TFTs are passive by their nature - they require backlight, unlike OLED where pixels are light emitters themselves. Without backlight LCDs can't be used in night jumps. Also they would be harder to read while looking at some dark background even in bright daylight (I did some basic tests and something that's not glowing is in general harder to read). Basically it needs a backlight and that backlight adds extra thickness, and in this case every millimeter counts. I've ordered this one with IPS display, and the whole unit is 8mm thick compared to 1.5mm OLED display (4mm when in 3Dprinted frame): http://www.lilygo.cn/prod_view.aspx?TypeId=50033&Id=1126&FId=t3:50033:3
  16. Yes, I've just ordered few more units for wider testing, one of them is LCD-based. It has ~0.2 inches smaller screen and is a bit thicker, but on the other hand everything is fixed to the board i.e. no flex cables to deal with. And it's colorful. Primary reasons for OLED were transparency (which backfired on me, but still few tests to be done with tinted tape) and the thickness of the display Parcel would arrive around mid October, meanwhile I'll be looking at improving casing, wiring and writing new code.
  17. The unit has been tested through the weekend and I'm really happy that it worked! Unlike previous attempts, when proprietary GPS units couldn't handle freefall, this time GPS data was displayed during all phases of the flight. Update was to 250ms and unit reaction time was pretty accurate. GPS unit rated up to 5Hz, with time it will be upgraded to 10Hz (same as in FlySight) I didn't have time to order tinted tape, so I put black one on the back, and on a bright day digits were readable no problem at all. Despite digits being blurry (the image attached is pretty close to what's in reality) it was easy to read them during the flight. Display is not distracting and could be looked at with quick eye movement. You might need some practice on the ground first just to get used to it, but then during the flight it didn't take an effort to check speed. As promised, basic source code and hastily written assembly instructions: https://github.com/RomanTheLegend/WingsuitGps Contributions are welcome because I won't have enough time to develop this project at a good pace, and there are few quite complex functions to be implemented. Next on the ToDo list: * Make few more units for my friends for wider testing and feedback (mid-October because shipping is only from China) * Make 3D models and wiring cleaner and leaner * Explore the possibility of attaching some control switches - that would allow to write some kind of menu interface in the future P.S. I got carried away a bit and added Bluetooth intercom made from old cheap headset while at it. This helmet gets more and more advanced
  18. Prototype ready and assembled. I tested it today riding a bicycle in cloudy weather and it was readable. In bright sunlight this OLED is too weak on its own, but it could be improved by putting some tinted tape on the back of the frame, or in worst case a piece of duct tape. Will be testing it this Saturday, hopefully, it will be able to catch up with readings. GPS module is rated up to 5 Hz (similar to FlySight) so if anything, the bottlenecks would be in the code. I'm wrapping up the documentation & source code, will post it after field tests
  19. Yes, I'm perfectly are of that problem. I'm trying to overcome it by combining screen big enough so that even blurry text/numbers at close distance are readable, and putting it as far as possible for the best results. So far sticking OLED to the visor on the outside seem to be good enough. That's why it has to be transparent - big screen obscures more view. Also it's placed not directly in front of an eye, but at the bottom and to the side - again to get more distance and obscure less view. LilyGo TTV has arrived about a week ago and actually I'm quite impressed with what they've managed to squeeze in such a small package - it even has WiFi! And plenty of power in the processor, so with time the functionality could be extended. I've hooked up the GPS and it works, now I'm sorting out few technical challenges * Extend wiring so that unit could be hidden in one of audible pockets * Test with different batteries. The stock one is too small, it lasted for just about 1-2 hours working only as a display. For that I had to hook up GPS module to external battery with higher voltage * There's 5-10 seconds delay in GPS readings - displayed speed lags behind actual speed. Likely some bug in the code. Same GPS module on Arduino had better reaction time In few days I'll post an update with link to GitHub for anyone interested
  20. Another alternative is to use transparent OLED display. Surprisingly, there's a product with everything on-board except GPS: http://www.lilygo.cn/prod_view.aspx?TypeId=50032&Id=1354&FId=t3:50032:3 Battery, OLED, drivers - everything is already assembled. It's based on ESP32 and is fully programmable, so adding GPS module won't be that difficult. I'm waiting for the package delivery (in about one month because from China) and will share the test results
  21. My attempt at something similar. Really basic code on Arduino Zero + some LEDs It supposed to show horizontal speed and heading (in degrees) but there's no GPS signal in the apartment Pros: * Cheap and really easy to build * Numbers on LED are kinda readable because it's standard LED numbers font (although it needs some time to get used to) * Easy to program new display information in basic C code * Numbers are readable even in bright light * Size could be reduced by 50% easily (most of the space is used by battery and its charger) Cons: * Numbers on LED are kinda readable (although it needs some time to get used to) Dry tests on the ground so far, not jumped this thing yet (want to reduce its size first) I'm looking for good alternative for LED so it would obscure even less view, but here I'm facing the problem with finding something readable at close range. I thought about monocle displays because they use standard AV input and thus may be used with Arduino too. @Gideon Yampolsky could you please elaborate on what exactly was inconvenient with Vufine display? gps_Full HD 1080p_(1).mp4
  22. Post on FB on some rigger groups - from time to time people are looking for old canopies to practice sewing skills
  23. Interesting. How about replacing the LCD with a monocular then? https://www.aliexpress.com/item/1005001355384065.html
  24. I was watching old video from WS race and noticed that competitors intentionally do a backflip on exit (1:41 on video) What's the reason behind that? Is that because for a second you have head-down dive, so flier gets more initial momentum and also suit inflates faster?
  25. Quick update: battery has been replaced with other, more reliable and I was able to test it today. Long story short - the unit didn't work as well as I'd expected: it was perfectly fine during the climb, showing both ground speed and distance, but during the jump when altitude drops quickly it just stops processing all the readings. Under the canopy it works again, but the moment you do any kind of dive it stops reading again for a second. Well, it wasn't designed for skydiving after all, so nothing to complain about. At least I was able to measure my ground speed under the canopy, so it could be used for some basic canopy piloting drills, but nothing more than that. P.S. Turns out the plane travels in circles roughly 70 km at ~190km/h to climb to a 4k