U-blox announces the F9 platform with L1/L2/L5 frequencies supported



6 thoughts on “U-blox announces the F9 platform with L1/L2/L5 frequencies supported”

  1. In the initial set of release notes for u-Center 8.28, u-blox “accidentally” refereed to :
    u-blox M9 / u-blox F9 with ROM 0.40, ROM 1.01
    in section 2.2 Supported Receiver Generations.
    and in section 3.1:
    Added firmware update support for u-blox M9/F9 including “update to ram” and no fis features.
    Within days this was removed, ans is nowhere to be found in either the current 8.28 or 8.29 release notes.

    u-blox already has multi frequency support in the M8 product. Having 2 RF chains, one supporting Glonass. Multi Constellation support introduced in firmware 3.01 is also now in the ROM versions of most M8 products.
    Applying Moore’s law to the M8 product, with an updated Cortex M4 and RF chains they should be able to provide what the F9 system promises.
    As to when is anyone’s guess, but ST & Broadcom have both announced competing products. IMHO from the “unintentional” slip up in the release notes, we have a pretty good idea that u-blox is going to have a product soon.


  2. Hello Tim,

    this is a very interesting announcement indeed. Can you comment or maybe even a bit speculate on it? Do you think this is going to be the “killer product/chipset” for the low-cost precise positioning in terms of value and solution robustness? Where can we expect the price to be around? Seems like the features are pretty similar to the Chinese boards, but still u-box is a better brand…


    1. Hi Kozuch. I don’t know any more than what is in the announcement but if u-blox can deliver the same combination of low-cost and high-performance that they have done for L1 then it should be a great product. I was pleased to see that they announced it will be available with or without RTK capability so hopefully they will retain a similar pricing model to the M8T/M8P where the non-RTK capable version is significantly more affordable than the RTK capable version.


      1. Thanks for your comment. Yes the RTK/non-RTK product policy is interesting and I hope it will introduce a nice low-cost multi-frequency/multi-GNSS raw measurement product. Although RTKLIB seems not to be able to handle the multi-freq measurements very well (how can be seen from your latest tests), but maybe a nice product will attract more developers to address this issue.


        1. Hi Kozuch. I felt that the results of my most recent experiment showed that any weakness in RTKLIB (at least related to tracking moving rovers in challenging environments) was more related to the quality of the observations and not to anything specific to dual frequency. If the new multi frequency u-blox receivers maintain the quality of observations of the current generation, then I suspect that RTKLIB will work quite well with them.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s