It's definitely possible. ActiveLook sent me a pair of their glasses, and I built a firmware which connected to them, but that's as far as the project got before I had to set it aside for a little while. There are a couple other things I need to take care of before I can get back to this, so it will probably be a few months, but they are still on my desk. :-)
I noticed the new file out (TRACK.CSV) doesn't have the heading anymore (the FlySight 1 file layout had this field). Will it come back? Or can I calculate the heading from the data available in the new file layout?
The new format is a bit different, but does include header information similar to the old format. If you open the file in a text editor, you'll see the "$COL" and "$UNIT" tags, which are similar to the old header, and in the body of the file you'll see "$GNSS" tags which include most of the data that was found in the old files. Only course and course accuracy are missing, as these can be derived from velocity data.
@@RafRukker Course will be atan2(velE, velN). Usually, this result will be in radians, so you'll also need to convert to degrees: deg = rad / pi * 180.
This should be possible, but at the moment you would have to do a bit of software/hardware work to make it happen. Part of the challenge with this particular sensor is that it requires a 5 V supply, but FlySight 2 uses a 3.3 V supply--however, I'm sure there are other differential pressure sensors that use a 3.3 V supply, and you might find it easier to use one of those. I can think of a couple of ways to get this data into the FlySight: 1. The sensor uses I2C, so you might be able to connect it directly to the FlySight's I2C bus, then modify FlySight 2's firmware to add the sensor. This would require drilling holes in the case, which would make it not water resistant, and it would be difficult to make this robust--i.e., to ensure that the wires didn't come loose once in a while. 2. It looks like we'll be able to use "router mode" in FlySight 2's BLE interface. If this is the case, you could turn the sensor into a BLE peripheral (or perhaps find a differential pressure sensor that's already available as a BLE peripheral) and then make changes to FlySight 2's firmware to read from the peripheral. This is a little more complex, but has the advantage that it keeps the FlySight 2 and sensor separate, and would allow for a more robust physical situation.
Update works a little differently with the new units. Currently, there are no firmware updates available, so there is no reason to put the unit into update mode. However, briefly, to update the new hardware, you plug it into USB, then push and hold the power button for 10 seconds. The unit will restart, and when it comes back up as a drive the light will be orange. Next, you copy the firmware update into the "FW" folder on the FlySight, then eject and unplug from USB. The orange light will stay on for a moment, then go off, and a few seconds after this the update is complete.
The footprint is the same, so it will work with Cookie's mount and our aluminum mounts. The shape of the top is a little different, so it won't work with mounts that enclose the whole unit (although Adrenaline Workshop has just released a mount for FlySight 2 that encloses the whole unit, and of course this will work). Each FlySight 2 also comes with one mount which works with the new units. These mounts have the same bolt pattern as Cookie's mounts, so if you've already got one of those, the new mount is basically a drop-in replacement.
@@flysightgps Thanks! Sorry, I mean length and width (height makes no difference for me, I use velcro strap for height). So Flysight 2 will fit the Flysight 1 mounts by length and width, right?
@@pirogovpavel The bottom of the unit is the same, so it will sit in shallow mounts made for the original FlySight. However, the walls on the new unit are angled out slightly, whereas they were angled in slightly on the old unit. So if your mount has vertical walls that are the height of the FlySight, the new unit may not fit properly.
Can you please send me an email at "support at flysight dot ca" including the folder for the track where you're seeing this issue, as well as any recent warm-up folders?
@@sprite2k The IMU sensor is capable of 6 kHz measurement, but the production firmware currently uses a lower logging rate (a) to keep file size reasonable for people who aren't using the extra data; and (b) because there are some additional challenges with logging at the full rate which will take a little time to solve. If you'd like to try the development firmware with configurable rate on the other sensors, please send me an email.
The new hardware includes a Bluetooth Low Energy radio, but we haven't implemented the interface in firmware yet. I'm hoping to get this done in the next 6 months, and when it's done it will be made available as a free firmware update. Unfortunately, though, it's unlikely we will be able to support Bluetooth Audio, because this requires more processor power (to encode the audio) than we have available.
Hi Michael, Current Flysight Viewer cannot use the new voice files during simulation procedure as well as Flysight2 itself cannot use old voice files. Is it possible to make tnem inter-compatible with new and old sounds? Thank you!
Thanks for bringing the issue with FlySight Viewer to my attention. I will try to get this fixed soon. Unfortunately, I don't think it's practical to make FlySight 2 compatible with audio files made for the original hardware, as it would require interpolation of the data. One of the main reasons we're able to play audio at all is because we can transfer audio data efficiently from a memory buffer to the audio peripheral, and interpolation would break that. However, I will see if I can come up with a simple procedure to convert these files using Audacity.
Michael, actually it is not a hard task to re-write old collection of my sound files with a new parameters. The Simulation proc in the Flysight Viewer is much more important, it is very useful thing.
Does the Flysight 2 have barometric sensor? My understanding is that there are some hardware improvements on the new model that just need firmware and software updates to utilize them. If there is a barometric sensor, is the ability to use the device as an audible altimeter on the roadmap?
FlySight 2 does have a barometric sensor, but I don't think it will be a good idea to use it as an audible altimeter. There are a couple of main reasons for this: 1. Even with a barometric sensor, there is still the possibility that earphones could fail. For an audible altimeter, reliability is critical, and I don't think the required level of reliability will be possible with earphones. 2. The development process for FlySight's firmware is not optimized for reliability. Because we have relatively low reliability requirements (i.e., FlySight is not used in a safety critical application), I am able to release firmware updates without a lengthy testing phase (the firmware for an audible altimeter might be tested over the course of thousands of jumps before being released). This allows much more rapid feature development. At the moment, what I have in mind for the barometric sensor is to use it as a low-power way to tell if the FlySight is climbing to altitude. With this, it might be possible to make the unit more automated, so that it can gather data without the need for the user to turn it off/on. We'll see--at this point I'm still not sure it's possible to get reliable data this way, but I wanted to leave the possibility open, so the sensor is in there. 🙂
Hi Michael,
Just wanted to say thanks for an amazing product. Ive had my same flysight for 10+ years now. This has to be the best tool in my gear bag!
Is it possible to connect ActiveLook glasses to FlySight 2 via BLE to get most important data rendered in the glasses?
It's definitely possible. ActiveLook sent me a pair of their glasses, and I built a firmware which connected to them, but that's as far as the project got before I had to set it aside for a little while. There are a couple other things I need to take care of before I can get back to this, so it will probably be a few months, but they are still on my desk. :-)
I noticed the new file out (TRACK.CSV) doesn't have the heading anymore (the FlySight 1 file layout had this field). Will it come back? Or can I calculate the heading from the data available in the new file layout?
The new format is a bit different, but does include header information similar to the old format. If you open the file in a text editor, you'll see the "$COL" and "$UNIT" tags, which are similar to the old header, and in the body of the file you'll see "$GNSS" tags which include most of the data that was found in the old files. Only course and course accuracy are missing, as these can be derived from velocity data.
@@flysightgps Thank you for your answer! How do I derive course from the velocity data?
@@RafRukker Course will be atan2(velE, velN). Usually, this result will be in radians, so you'll also need to convert to degrees: deg = rad / pi * 180.
@@flysightgps Thanks!!!
Is it possible to connect an airspeed sensor (for example aspd-4525) to the FlySight?
This should be possible, but at the moment you would have to do a bit of software/hardware work to make it happen. Part of the challenge with this particular sensor is that it requires a 5 V supply, but FlySight 2 uses a 3.3 V supply--however, I'm sure there are other differential pressure sensors that use a 3.3 V supply, and you might find it easier to use one of those. I can think of a couple of ways to get this data into the FlySight:
1. The sensor uses I2C, so you might be able to connect it directly to the FlySight's I2C bus, then modify FlySight 2's firmware to add the sensor. This would require drilling holes in the case, which would make it not water resistant, and it would be difficult to make this robust--i.e., to ensure that the wires didn't come loose once in a while.
2. It looks like we'll be able to use "router mode" in FlySight 2's BLE interface. If this is the case, you could turn the sensor into a BLE peripheral (or perhaps find a differential pressure sensor that's already available as a BLE peripheral) and then make changes to FlySight 2's firmware to read from the peripheral. This is a little more complex, but has the advantage that it keeps the FlySight 2 and sensor separate, and would allow for a more robust physical situation.
How do I put the new model in update mode?
Update works a little differently with the new units. Currently, there are no firmware updates available, so there is no reason to put the unit into update mode. However, briefly, to update the new hardware, you plug it into USB, then push and hold the power button for 10 seconds. The unit will restart, and when it comes back up as a drive the light will be orange. Next, you copy the firmware update into the "FW" folder on the FlySight, then eject and unplug from USB. The orange light will stay on for a moment, then go off, and a few seconds after this the update is complete.
Can I use old mount for the new model? Is height and width the same?
The footprint is the same, so it will work with Cookie's mount and our aluminum mounts. The shape of the top is a little different, so it won't work with mounts that enclose the whole unit (although Adrenaline Workshop has just released a mount for FlySight 2 that encloses the whole unit, and of course this will work). Each FlySight 2 also comes with one mount which works with the new units. These mounts have the same bolt pattern as Cookie's mounts, so if you've already got one of those, the new mount is basically a drop-in replacement.
@@flysightgps Thanks! Sorry, I mean length and width (height makes no difference for me, I use velcro strap for height). So Flysight 2 will fit the Flysight 1 mounts by length and width, right?
@@pirogovpavel The bottom of the unit is the same, so it will sit in shallow mounts made for the original FlySight. However, the walls on the new unit are angled out slightly, whereas they were angled in slightly on the old unit. So if your mount has vertical walls that are the height of the FlySight, the new unit may not fit properly.
Hi Michael!
We got the flysight2 but we can't get it to make sense.
we're getting a few meters per second vertical speed when we walk horizontally.
Can you please send me an email at "support at flysight dot ca" including the folder for the track where you're seeing this issue, as well as any recent warm-up folders?
@@flysightgps hi, we realized what the problem is. We have gps interference here in Israel. 😅
@@flysightgps why isn't it recording the imu at 6khz? Only 13hz per channel
@@sprite2k The IMU sensor is capable of 6 kHz measurement, but the production firmware currently uses a lower logging rate (a) to keep file size reasonable for people who aren't using the extra data; and (b) because there are some additional challenges with logging at the full rate which will take a little time to solve. If you'd like to try the development firmware with configurable rate on the other sensors, please send me an email.
Just got my flysight2, never used the previous one. How can I connect the Bluetooth headphones?
The new hardware includes a Bluetooth Low Energy radio, but we haven't implemented the interface in firmware yet. I'm hoping to get this done in the next 6 months, and when it's done it will be made available as a free firmware update.
Unfortunately, though, it's unlikely we will be able to support Bluetooth Audio, because this requires more processor power (to encode the audio) than we have available.
Hi Michael,
Current Flysight Viewer cannot use the new voice files during simulation procedure as well as Flysight2 itself cannot use old voice files. Is it possible to make tnem inter-compatible with new and old sounds?
Thank you!
Thanks for bringing the issue with FlySight Viewer to my attention. I will try to get this fixed soon. Unfortunately, I don't think it's practical to make FlySight 2 compatible with audio files made for the original hardware, as it would require interpolation of the data. One of the main reasons we're able to play audio at all is because we can transfer audio data efficiently from a memory buffer to the audio peripheral, and interpolation would break that. However, I will see if I can come up with a simple procedure to convert these files using Audacity.
Michael, actually it is not a hard task to re-write old collection of my sound files with a new parameters. The Simulation proc in the Flysight Viewer is much more important, it is very useful thing.
Does the Flysight 2 have barometric sensor? My understanding is that there are some hardware improvements on the new model that just need firmware and software updates to utilize them. If there is a barometric sensor, is the ability to use the device as an audible altimeter on the roadmap?
FlySight 2 does have a barometric sensor, but I don't think it will be a good idea to use it as an audible altimeter. There are a couple of main reasons for this:
1. Even with a barometric sensor, there is still the possibility that earphones could fail. For an audible altimeter, reliability is critical, and I don't think the required level of reliability will be possible with earphones.
2. The development process for FlySight's firmware is not optimized for reliability. Because we have relatively low reliability requirements (i.e., FlySight is not used in a safety critical application), I am able to release firmware updates without a lengthy testing phase (the firmware for an audible altimeter might be tested over the course of thousands of jumps before being released). This allows much more rapid feature development.
At the moment, what I have in mind for the barometric sensor is to use it as a low-power way to tell if the FlySight is climbing to altitude. With this, it might be possible to make the unit more automated, so that it can gather data without the need for the user to turn it off/on. We'll see--at this point I'm still not sure it's possible to get reliable data this way, but I wanted to leave the possibility open, so the sensor is in there. 🙂
😘👣😂