ADIS16300/16305

Thank you for your post!  The primary difference between the ADIS16305 and the ADIS16300 is that the ADIS16305 benefits from a calibration over the industrial temperature range of -40 to +85C.  "Car Navigation" seems to be a hot area of research for using lower-cost sensing technologies (MEMS, even the ADIS16xxxx products, tend to be much less expensive than RLG or FOG solutions), but in most cases, the performance of these lower-cost solutions are not good enough to support the entire navigation solution, on their own.  Therefore, the majority of the research that I am aware of is focused on developing optimal blends of multiple sensor/observer technologies (including MEMS) to support this function.  At this time, it appears like MEMS technology presents enough for inclusion, while the core technology advances to improve key performance metrics. Since there are a lot of unique approaches being developed by our customer base, we tend to focus our specifications on basic sensor behaviors, while helping with application-specific questions through these types of conversations.  Before dig too deeply into this, could you provide a bit more detail on your objectives?

• Given all of the products in our IMU portfolio, what was your criteria for selecting this part?  Sometimes, we have seen that when customers start with the best performance, even when the cost profile will prohibit wide-scale adoption, they are able to get systems up and running quicker.  A working system typically creates a strategic advantage, as it provides a platform for evaluating the performance trade-offs that lower-cost solutions provide.
• Does "car navigation" mean that you trying to track its location in GPS-denied environments or is your intent to develop a a full GNC (guidance, navigation and control) system for a car?  Or, are there other functional objectives?
• Do you plan to have access to other inertial observers?  Wheel speed? Compassing? Radar? Visual-assist?

Thank you for your post!  The primary difference between the ADIS16305 and the ADIS16300 is that the ADIS16305 benefits from a calibration over the industrial temperature range of -40 to +85C.  "Car Navigation" seems to be a hot area of research for using lower-cost sensing technologies (MEMS, even the ADIS16xxxx products, tend to be much less expensive than RLG or FOG solutions), but in most cases, the performance of these lower-cost solutions are not good enough to support the entire navigation solution, on their own.  Therefore, the majority of the research that I am aware of is focused on developing optimal blends of multiple sensor/observer technologies (including MEMS) to support this function.  At this time, it appears like MEMS technology presents enough for inclusion, while the core technology advances to improve key performance metrics. Since there are a lot of unique approaches being developed by our customer base, we tend to focus our specifications on basic sensor behaviors, while helping with application-specific questions through these types of conversations.  Before dig too deeply into this, could you provide a bit more detail on your objectives?

• Given all of the products in our IMU portfolio, what was your criteria for selecting this part?  Sometimes, we have seen that when customers start with the best performance, even when the cost profile will prohibit wide-scale adoption, they are able to get systems up and running quicker.  A working system typically creates a strategic advantage, as it provides a platform for evaluating the performance trade-offs that lower-cost solutions provide.
• Does "car navigation" mean that you trying to track its location in GPS-denied environments or is your intent to develop a a full GNC (guidance, navigation and control) system for a car?  Or, are there other functional objectives?
• Do you plan to have access to other inertial observers?  Wheel speed? Compassing? Radar? Visual-assist?