Member #565915

Member Since: June 24, 2014

Country: United States

  • Hello,

    I’m currently working on implementing this board into a high altitude balloon for studying the eclipse later this year, and after some testing and stuff I realized I really liked the capabilities of the board, but was annoyed at lotsa libraries size and complexity in use and reading when for the most part, I’m just logging the data to an SD card for analysis later.

    So I decided I’d try making my own library for this board. Since the binary commands are relatively simple and can also be read using the configuration software and an arduino to watch the commands being sent, I thought I’d be able to implement a library that can change the settings using functions, which would mean the board could be configured more easily through code in your setup function rather than needing to permanently change settings through the configuration software. I didn’t like the idea of the permanent setting changes because in my experience some setting combinations like 20Hz at 9600 baud would totally mess up the data and make it unreadable, so making sure all saves are temporary prevents this headache that I experienced.

    Anyway, it’s a work in progress that I’ll be updating more over the next few days to finish all the features I need and adding more examples and images for wiring since I could see how a newer person could get mixed up at a lot of points with this board. It would be such a shame for the learning curve to prevent a newbie from using such a cool board. Here it is. Check the page every couple days for updates. https://github.com/Darthpbal/Hermes_Gps_Library

    This lib works trough a readLine, getLine, printLine kinda workflow. It has a filter so if you wanna record all the GPS data, you can set that to raw, and if you ONLY want GGA or RMC, you can turn on the filter and only get that. And if you don’t wanna record the whole line of GGA, but only the latitude, longitude and altitude, I’ve implemented the same field parser from the tutorial, so you can easily extract a particular field within the GGA sentence since it follows the NMEA standard. I don’t have the stuff for changing the GPS settings itself yet, but like I said. That’s coming soon. And I’ll also probably add examples for logging to an sd card as well since I saw that asked somehwere.

    http://www.gpsinformation.org/dale/nmea.htm#GGA

    https://github.com/Darthpbal/Mercury_Gps_Library

    Hope this helps someone.

  • Hello,

    I’m currently working on implementing this board into a high altitude balloon for studying the eclipse later this year, and after some testing and stuff I realized I really liked the capabilities of the board, but was annoyed at lotsa libraries size and complexity in use and reading when for the most part, I’m just logging the data to an SD card for analysis later.

    So I decided I’d try making my own library for this board. Since the binary commands are relatively simple and can also be read using the configuration software and an arduino to watch the commands being sent, I thought I’d be able to implement a library that can change the settings using functions, which would mean the board could be configured more easily through code in your setup function rather than needing to permanently change settings through the configuration software. I didn’t like the idea of the permanent setting changes because in my experience some setting combinations like 20Hz at 9600 baud would totally mess up the data and make it unreadable, so making sure all saves are temporary prevents this headache that I experienced.

    Anyway, it’s a work in progress that I’ll be updating more over the next few days to finish all the features I need and adding more examples and images for wiring since I could see how a newer person could get mixed up at a lot of points with this board. It would be such a shame for the learning curve to prevent a newbie from using such a cool board. Here it is. Check the page every couple days for updates. https://github.com/Darthpbal/Hermes_Gps_Library

    This lib works trough a readLine, getLine, printLine kinda workflow. It has a filter so if you wanna record all the GPS data, you can set that to raw, and if you ONLY want GGA or RMC, you can turn on the filter and only get that. And if you don’t wanna record the whole line of GGA, but only the latitude, longitude and altitude, I’ve implemented the same field parser from the tutorial, so you can easily extract a particular field within the GGA sentence since it follows the NMEA standard. I don’t have the stuff for changing the GPS settings itself yet, but like I said. That’s coming soon. And I’ll also probably add examples for logging to an sd card as well since I saw that asked somehwere.

    http://www.gpsinformation.org/dale/nmea.htm#GGA

    https://github.com/Darthpbal/Mercury_Gps_Library

    Hope this helps someone.

  • Is there any benefit of using the interrupt feature of this board? I understand the sensor collects light for a “shutter time” and the interrupt feature allows an interrupt flag to signal when the integration time is finished. Wouldn’t the value read from the sensor be updated every integration cycle anyway?

  • Figured out what was happening. Basically, it seemed like nothing was being logged because nothing was being logged because my test program was logging short sentences like 1 transmission per sec. But in mode 0 where the logomatic logs everything from UART0, it’s filling up the whole 512 byte buffer before logging, which was just taking a long time to get to. So that’s an entire 512 characters that it needs to collect before logging unless the stop button is pressed. (Also don’t you just love it when you figure something out in experimentation and then find the 5 lines of documentation explaining the problem immediately after?)

  • Hi, I’m having some issues logging data from UART on this board. basically, I only get it to log data when I push the stop button. Is anyone else having this problem? I tried emailing tech support but no response.

    I’m powering the board from the arduino 5V rail into the BATT pin with my arduino TX and RX pins connected to RXI0 and TXO0 and simply periodically sending short UART serial sentences to log. This behavior is on multiple boards, so that makes me think I’m not just dealing with a busted board and that I’m just missing something.