We use the MPXV7025DP in our application, our question: The sensor is sealed, hermetic? We use the MPXV7025DP in our application, our question: The sensor is sealed, hermetic? Raul Re: We use the MPXV7025DP in our application, our question: The sensor is sealed, hermetic? Hi Raul, Leakage is an unspecified and therefore not guaranteed performance characteristic of our devices. However, NXP does perform a 100% leakage test on all ported devices after assembly, with a maximum allowable leakage rate (for these devices) of 0.133kPa/sec (with 100kPa applied by a no-added-volume test system). This maximum rate can be considered "worst case" (prior to any handling/processing by the customer which may induce package stresses which affect port-to-package sealing) and the typical production distribution for leakage rate is much better. That said however, our current process and equipment capabilities do not allow us to build and test to (or guarantee) a tighter requirement.  I hope you find this information useful. Best regards, Tomas

MPX4250GP - 絶対圧とゲージ圧 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは皆さん！ MPX4250GPはゲージ型センサ（つまり気圧を超える圧力を読み取りますが、データシートの内容がわかりません。 0～250kPa と記載されており、まずこれは大気圧を超える数値であると推測します。 しかし、データシートの 4 ページ ( http://cache.freescale.com/files/sensors/doc/data_sheet/MPX4250.pdf?fasp=1&WT_TYPE=Data%20Sheets&WT_VENDOR=FREESCALE&WT_… ) には、「図 4. 出力と絶対圧力の関係」とあり、ここから私の疑問が始まります。 これがゲージタイプのセンサである場合、グラフ/図 4 に絶対圧力と表示されているのはなぜですか? このセンサは実際に 0 ～ 250kPa の絶対圧力を読み取りますか、それとも大気圧より 0 ～ 250kPa 高い圧力を読み取りますか? ご回答をお待ちしています。 圧力センサ Re: MPX4250GP - Absolute vs gauge pressure <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、ミゲル。 おっしゃる通り、MPX4240GP はゲージ圧力センサーです。データシートの図 4 のタイトルは無視してください。「図 4. 出力と差圧の関係」とあるはずです。ドキュメント チームに修正を依頼します。お知らせいただきありがとうございます。 楽しむ！ ジョシュ

ウィンドウのツールボックスに関する質問。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、 Fusion Toolbox for window はオープンソースではないため、K64F とのシリアル通信用の MFC プログラムを作成しました。   しかし、MFC プログラムに送信される値は不安定で、急速に変動します。   Fusion Toolboxに送信される値は安定していると思います。 SO is there a filter or another function in the Fusion Toolbox ??? How can I stablilize the value of センサ ? センサ・フュージョン Re: Toolbox for window question. <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> PC および Android アプリケーションは、受信したデータをそのまま表示します。信号プロセッシングは行いません。 PC 側でのパケット プロセッシングは、着信データとの同期、Bluetooth ドロップアウトの修正、パケット バイト 0x7E の開始に対する特別な処理の削除を行うために、非常に複雑です。 PC GUIのソースコードを公開するかどうかを検討中です。その間、 [email protected]までメールをお送りください。できる限り対応させていただきます。

加速度によって磁気センサの値は変化しますか? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 私はfxos8700cqを使用しています。 加速度によって磁気センサの値は変化しますか? 加速度によって磁気センサの値が変化する場合は、それを校正できるドキュメントはありますか? ありがとうございます。 加速度センサ 磁気センサ Re: Does acceleration change the value of the magnet sensor? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、 いいえ、加速度によって磁気感知の値は変化せず、磁気の変化によって加速度感知が発生することはありません。 ただし、磁力計を使用する場合は、磁気干渉を避けるためにセンサーにキャリブレーションを適用することが重要です。詳細については、アプリケーションノート AN4459 を参照してください: https://www.nxp.com/docs/en/application-note/AN4459.pdf 自動キャリブレーションプロセスに使用できるサンプルコードは、次のリンクからダウンロードできます: https://www.nxp.com/docs/en/application-note-software/AN4459SW.zip よろしくお願いいたします。 ホセ NXP Semiconductors

Accelerometer output data saturation Dear Sirs, I have one question about MMA8652. When the acceleration more than a setting range is added to an accelerometer, how is the output data value ? Off course, it is under the Absolute maximum ratings. Is the value saturation (7FF or 800) ? Or is the value unstable ? For example. When the full-scale is set to +- 2g , if the accelerometer will be accelerated to 3g, how is the output data value ? Best Regards, Koichi Sakagami Accelerometers Re: Accelerometer output data saturation Dear Tomas san, Thank you for your answer. I got it. Best Regard, Koichi Sakagami Re: Accelerometer output data saturation Dear Koichi-san, When acceleration on any axis exceeds the accelerometer’s measurement range (±2g, ±4g or ±8g depending on FS[1:0] bits), the corresponding output is clipped at the full-scale value (0x7FF or 0x800). Considering your example, the 12-bit output value would be 0x7FF. I hope it helps. Regards, Tomas PS: If my answer helps to solve your question, please mark it as "Correct" or “Helpful”. Thank you.

MPL3115A2 Altitude question I have verified that both the Temperature and Pressure are correct.  However I can't get the Altitude reading to get even close to the correct altitude. I live in Miami, FL (South Florida).  I'm practically at sea level, 22 miles (33.5 km) from the beach.  Elevation reading from a local weather station is 2 meters. The Pressure today is 1010.38 hPa, again from the local weather station.  The reading on the MPL3115A2 is 101488 PA, which is close enough.  hPa on Miami Beach tonight is 1011.74. Outside temperature tonight is 27.3 C.  I am testing the MPL3115A2 inside my one story house where the temperature is around 23 C.  Temperature reading is correct on the MPL3115A2. The altitude being displayed is ...  25394.xx meters! I read through a document I found on the freescale site and I did see something about adjusting a register to local conditions or something. Notes:  Arduino Uno/Adafruit MPL3115A2/Libraries being used to test are the ones from Adafruit and Sparkfun/ So what is going on here?  Why is the Altitude way off while the other two variables are correct.  The Altitude is calculated correct? I really appreciate anyone's help with this. Thanks Chris - Miami, FL Re: MPL3115A2 Altitude question Hi Saeed, It is hard to say where the problem might be. At first, I would recommend you taking a closer look at my example code for the MPL3115A2 that illustrates how to configure it and compute altitude as well. Looking at your configuration, the SYSMOD register (0x11) only indicates the current operating mode (either standby or active), you should not write to it. The SBYB bit in the CTRL_REG1 register (0x26) is used to select the operating mode. I hope it helps. Regards, Tomas Re: MPL3115A2 Altitude question Hi Tomas, I too have a similar problem when I try to read data from the mpl3115a2. I get values in the range of 25394.xx-35111.xx meters even I I try to configure the mpl to altitude mode like you suggested. It seems like non of the configuration process is being picked up by the sensor. I am able to read from the sensor but I cant get it to output appropriate altitude values. When I display values on terminal, I see the values fluctuation at a very fast rate. I am using Tiva C MCU with code composer studio compiler, and all the codes are written using registers (my own libraries). I have test my code on other sensors (MPU 6050) and I am able to configure the devices properly and read but I just cant seem to have this device configured properly. void configure_PressureSensor(void) {   //system mode register   write_pressureSensor(0x11, 0x00);   // Active barometer mode, OSR = 128   //write_pressureSensor(0x26, 0x39);   //* Set to Altimeter with an OSR = 128 */ and Active altimeter mode   write_pressureSensor(0x26, 0xB8);   //* Enable Data Flags in PT_DATA_CFG */   write_pressureSensor(0x13, 0x07);   // activate   write_pressureSensor(0x26, 0xB9);   //system mode register   write_pressureSensor(0x11, 0x01);   } Re: MPL3115A2 Altitude question Hi Mitesh, Attached you can find the schematic of the board you are using. There are five pins that need to be hooked up in order to start using this sensor. MPL3115A2 sensor board -> Arduino VDD (J3-3) -> 3.3V VDDIO (J2-1) -> 3.3V GND (J2-5) -> GND SCL (J2-4) -> A5 (or SCL) SDA (J2-6) -> A4 (or SDA) If you are using a 5V Arduino Uno, we recommend putting 330 ohm resistors in line to limit the 5V signal going into the MPL3115A2 and prevent damage to the sensor. Regards, Tomas Re: MPL3115A2 Altitude question Hello All, I am very new to this. I would like to get the connection details of arduino and mpl3112 freescale xtrinsic sensor. What I have observed is jumper J1 has 6 pins on its base board and 8 pins on its top pressure sensor board. I am unable to get the connection details. Can you please guide me with the same? I would also be really helpful if you can guide me with proper pdf for connectrion. I am having following sensor. Sensor Toolbox MPL3115A2 Development Kit|Freescale Re: MPL3115A2 Altitude question Glad to hear this, Chris. Now you can adjust the altitude using the built-in OFF_H (0x2D) register that offers user-set altitude offset adjustments in twos complement format with a scale factor of 1 m/LSB. In your case the difference is about 29 meters, so you need to write this value into the OFF_H register. Then this offset value is automatically added to the altitude data and the adjusted resulting value is stored in the output data registers 0x01 – 0x03.   Let me know if you have any other questions. Regards, Tomas Re: MPL3115A2 Altitude question Tomas, Much better!  Still not correct but at least not thousands of meters.  It's -27 meters. It should be 2 meters (or close to 2 meters). So back to the drawing board. Let me know if I should check anything else or you need any further information. Thank you very much. Chris Re: MPL3115A2 Altitude question Tomas, Thank you so much!  I did see that function somewhere in the Arduino library for the MPL3115A2.  I'll check this out tonight as soon as I get back home.  I'll let you know how it goes. Once again, thanks! Chris Re: MPL3115A2 Altitude question Hi Chris, It looks like you are calculating the altitude in the barometer mode. In order to calculate the correct altitude from registers 0x01 – 0x03, the device needs to be in the altimeter mode (ALT bit of the CTRL_REG1 register has to be set). I am not familiar with Arduino libraries in detail, but I guess that there is a function called “setModeAltimeter()” that puts the sensor into altimeter mode. I hope it helps. Regards, Tomas PS: If my answer helps to solve your question, please mark it as "Correct" or “Helpful”. Thank you.

Sensor Fusion FXOS8700CQ and FXAS21002 IC axis mis-alignment. Hi, We are using FXOS8700CQ(6-axis sensor with integrated linear accelerometer and magnetometer) and FXAS21002(3-Axis Digital Angular RateGyroscope) for getting the roll pitch and yaw. Is it mandatory to align the x, y, and z axis of the both the ICs? In our PCB we are not align the x, y, z axis of the both the ICs. Here I am attaching the image how we have connected the ICs on PCB. We are getting the data for the roll, pitch and yaw but values we are getting that is not valid. How we can get the right data by not making any changes to the hardware. Please help to solve the problem. Accelerometers Gyroscope Magnetic Sensors SensorFusion Re: Sensor Fusion FXOS8700CQ and FXAS21002 IC axis mis-alignment. Hello Ankit, You can take a look at our Application Note AN5017 (more specifically paragraph 1.4 and 1.5) to have a better understanding. To give a simple example, let's assume you are using the Aerospace / NED standard. If the accelerometer is mounted horizontally in your end product, it will measure +1g as stated in FXOS8700 datasheet (cf crop of fig.4 below), at least when the product will be layed down horizontally. The earth gravity vector is oriented downward, hence aligned to Z-"Down" axis of the NED XYZ-reference frame. Consequently the Zout = +1g accelerometer reading will also apply directly to the NED frame. If the sensor was mounted upside down in the end product (e.g. located on the bottom side of the PCB), you would need to negate the accelerometer data to match the NED frame convention: Zout = -1g for sensor but Z = +1g in the NED frame (unchanged for the end product). Practically, when the sensor and NED axes are in opposite direction, you can use the sensor data as is, whereas when they are in the same direction, you shall negate the sensor data with the appropriate HAL matrix. This matrix will also handle axes permutation if any. Best regards,   Jacques. Re: Sensor Fusion FXOS8700CQ and FXAS21002 IC axis mis-alignment. Hi Jacques, Jacques Trichet wrote: Please note that NED system is using a “gravity positive” convention whereas our accelerometer is “acceleration positive”. Can you give bit more brief explanation for above statement? I didn't understand. Thanks, Ankit Re: Sensor Fusion FXOS8700CQ and FXAS21002 IC axis mis-alignment. Hi Ankit, I'm assuming you are using our Sensor Fusion source code from ISSDK middleware library that can be added to NXP Kinetis SDK. First of all, you need to define an XYZ reference frame (that follows the right-hand rule), and Coordinate System for your end product. We usually take the Aerospace Coordinate System, also referred as “NED” (North, East, Down). The Coordinate system, associated with the XYZ reference frame chosen for the end product will govern the Pitch, Roll, Yaw angles computation. See AN5017 for more details. Please note that NED system is using a “gravity positive” convention whereas our accelerometer is “acceleration positive”. Then, depending on exact sensor layout within the end product, you may have to apply a transformation Matrix (HAL Hardware Abstraction Layer) to align each sensor XYZ reference frame onto the end product reference frame. This consist usually in swapping and/or inverting axes. Practical example can be found in the hal_frdm_fxs_mult2_b.c source file, contained in the issdk\algorithms\sensorfusion folder. It corresponds to the use of FIFO data reading but can be easily change for single data point reading (remove the loop counter). Also adjust the axis swap/inversion according to the layout of each sensors. With the HAL correction, you can compensate any orientation of the different sensors and align their measurement onto the system reference frame.   Hope this helps,           Jacques.

MMA8452Q I2C specification Does MMA8452Q support I2C normal mode? Its data sheet is written "its I2C is compatible with fast mode and normal mode" in P.16. But its characteristics (P.8 Table 4) is written only fast mode specifications. I care tr and tVD specifications.(below red square values in I2C specification Rev.5 P.48) Best regards, M.Kiniwa Accelerometers Re: MMA8452Q I2C specification Hello Masahiro, Yes, the MMA8452Q is compliant with NXP I²C specification for both Standard and Fast Modes: Best regards, Tomas

差圧センサMPXV7002DPの各ポートの絶対圧力範囲 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MPXV7002DP 差圧センサーの最大圧力範囲はどれくらいですか?データシートには、Pmax = 75 kPa と記載されています。これは各ポートの絶対圧力のことでしょうか、それともP1とP2の最大差圧のことでしょうか？同様に、測定範囲は-0.3～+0.3 PSIですが、これは絶対圧力ですか、それとも差圧ですか？私はこれを使用して対気速度を測定するつもりSO、これらのポートの絶対圧力はほぼ大気圧 (14.7 PSI) になり、ポート間の圧力差は 0.3 PSI 以下になるはずです。これは機能しますか?ありがとう！ 圧力センサ Re: Absolute pressure range on each port of differential pressure sensor, MPXV7002DP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ご挨拶、 デビッド・ディアス・マリン mpxv7002dpで発生している問題に関する今後の更新を心待ちにしています。 便宜上、別の方法で質問しますが、私は乱流状態での空気速度を測定するために MPXV7002DP 圧力センサを使用し、乱流を表す時間平均化を実現するために、十分な時間にわたってさまざまな遅延 (2 回の連続した読み取り間の時間間隔) で実行してきました。 私は以下の内容を含むデータシートを読みました 「MPXV7002DP で注意する必要がある時間特性は、応答時間とウォームアップ時間だけです。 1. 応答時間 = 1.0 ミリ秒 応答時間は、指定された段階的な圧力変化を受けたときに、出力の増分変化が最終値の 10% から 90% になるまでの時間として定義されます。 2. ウォームアップ時間 = 20 ミリ秒 ウォームアップ時間とは、圧力が安定した後、製品が指定された出力電圧を満たすのに必要な時間として定義されます。 つきましては、許容される最小限の遅延についてご意見をお聞かせいただければ幸いです。よろしくお願いいたします。 Re: Absolute pressure range on each port of differential pressure sensor, MPXV7002DP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 親愛なるデイビッドへ ありがとうございます。 BR、 George Re: Absolute pressure range on each port of differential pressure sensor, MPXV7002DP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、ジョージ。 ご連絡ありがとうございます。 この場合、MPXV7002 GPデバイスの最大定格に関しては、完全に同意します。この制限を超えるとデバイスが損傷することになります。 MPXV7002 デバイスの圧力範囲は -2 ～ 2 kPa であることに注意してください。したがって、データシートに記載されている情報を期待するには、この範囲内であることを確認してください。 よろしくお願いいたします。 デビッド Re: Absolute pressure range on each port of differential pressure sensor, MPXV7002DP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> david_diaz様 MPXV7002 GPに関しても同様の質問があります。 ゲージタイプ: MPXV7002 GPの場合、P1 の絶対最大定格として次の理解は正しいでしょうか? 絶対最大定格：最大圧力 = 大気圧 +/- 75kPa ※プラスの値もマイナスの値も同じ量だと理解しています。 よろしくお願いいたします。 ジョージ・フクトミ Re: Absolute pressure range on each port of differential pressure sensor, MPXV7002DP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、デビッド。 私の混乱を解消するために時間を割いていただき、本当にありがとうございます。 幸運をお祈りしています、 テオ Re: Absolute pressure range on each port of differential pressure sensor, MPXV7002DP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、テオ。 それは実に良い質問です。 実際、デバイスの永久的な損傷を避けるためには、P1 と P2 の差は 75 kPa を超えてはなりません。 よろしくお願いいたします。 デビッド Re: Absolute pressure range on each port of differential pressure sensor, MPXV7002DP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、デビッド。 ご返答ありがとうございます。まだ少し不明な点が 1 つあります。「デバイスが損傷する前にサポートできる最大圧力は 75kPa です」とありますが、この最大圧力は 2 つのポート間の差圧のことですか?そうしないと、このセンサーは大気圧によって損傷を受けてしまいます。 よろしくお願いします！ テオ Re: Absolute pressure range on each port of differential pressure sensor, MPXV7002DP <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、テオ。 ご連絡ありがとうございます。 MPXV7002DP は差圧センサです。つまり、センサーの両側 (ポート P1 とポート P2) に圧力が加えられ、2 点間の圧力差が測定されます。 この場合、圧力の範囲は -2kPa から 2kPa になります。これは、デバイスが指定された範囲からの圧力の差に反応することを意味します。 デバイスが損傷する前に耐えられる最大圧力は 75kPa です。 この情報がお役に立てれば幸いです。 よろしくお願いいたします。 デビッド

如何将 KMZ80 的输出信号设置为 SENT 样式？ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我被告知，恩智浦交付的 KMZ80 芯片默认为 AD 信号样式，如果客户想使用 SENT 信号样式，我们必须自己校准芯片，对吗？ 我们能否直接购买 SENT 信号样式的 KMZ80？我没有从 KMZ80 产品数据手册（rev.3）中找到有关输出信号格式设置方法的有用相关描述-- 2019 年 4 月 26 日）。 磁力传感器 Re: How to set output signal of KMZ80 to SENT style? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> > 请联系 [email protected] 好的，我稍后再联系。 Re: How to set output signal of KMZ80 to SENT style? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 谢谢，现在我注意到了。 Re: How to set output signal of KMZ80 to SENT style? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 马亮，你好、 感谢您使用 KMZ80，您需要一个编程套件来对传感器寄存器进行编程，以便切换到 SENT 输出模式，请联系[email protected]获取套件。 编号 文廷 Re: How to set output signal of KMZ80 to SENT style? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 嗨，梁、 正如您在数据手册（第 8 章）中所注意到的，KMZ80 在引脚 OUT/DATA 上提供符合 SAE J2716 SENT 标准的数字输出信号（如果寄存器 SYS_SETTING 中的第 12 位设置为逻辑 1）。 测得的角度 α 被线性转换成一个值，并在 SENT 帧中进行数字编码。为此，可提供正或负的角斜率特性。 顺祝商祺！ 托马斯

MPXV5100GP Long term accuracy Hello, Our client has been using a MPXV5100GP in a product for several years with good success. We are wondering if NXP collects any long term accuracy data? We have read the NXP docs concerning reliability testing at the factory which attempt to infer long term reliability. The product is only used intermittently (not continuous duty) and the max pressure is usually well under 100 kPa. It also typically used indoors so the typical operating temperature is around 25 degrees C. If you have any data or can refer us to any data, please let us know. Thanks, Bart J Pressure Sensors Re: MPXV5100GP Long term accuracy Hello Bart, You can create a standard request (we call it "case") here. My colleagues who are in charge of the NDA process will assist you and then I can send you the FIT data. But keep in mind it is just a statistic about device's reliability, it does not say anything about long term accuracy. Best regards, Tomas Re: MPXV5100GP Long term accuracy Tomas, Yes, lets move ahead on this. What are the next steps on my end? Do I first sign an NDA from you or do I just implement a "standard request" and the NDA will be an outcome of that process? Thanks again! Re: MPXV5100GP Long term accuracy Hello Bart, FIT stands for Failures In Time, you can find more details here.  Best regards, Tomas Re: MPXV5100GP Long term accuracy Tomas, What exactly is the FIT data? Thanks for your response. Re: MPXV5100GP Long term accuracy Hello Bart, Based on the feedback from our QA team, I would be able to share only the FIT data. However, this requires a signed NDA with NXP and entering a standard request. Best regards, Tomas Re: MPXV5100GP Long term accuracy Hello Bart, I assume our qualification testing is all we have in terms of reliability data over the life of the device which includes accuracy, but I have requested input from our QA guys. I will update this thread and let you know what they say in the next few days. Best regards, Tomas

TSS(タッチセンシングソフトウェア)ライブラリの移行 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 専門家の皆様、 現在、冷蔵倉庫制御プロジェクトでは S12ZVC MCU が使用されています。タッチセンシングUIも必要です。 TSS ライブラリを S12ZVC に移行できるかどうか知りたいです。 移行できない場合は、インダストリアルグレードまたはオートモーティブグレードの MCU を推奨してください。MCU には CAN と ADC が必要です (ADC にプログラム ゲイン制御があれば最適です)。 よろしくお願いいたします。 キガー 磁気センサ 圧力センサ センシング・プラットフォーム タッチ・センサ Re: TSS(Touch Sensing Software) library migration <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 親愛なるトーマスへ 本当にご協力ありがとうございました！ Re: TSS(Touch Sensing Software) library migration <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 親愛なるキガー様 TSS は新しいデザインには推奨されなくなり、S12ZVC デバイスのサポートを追加する予定はありません。ほとんどの Kinetis MCU をサポートするNXP Touch Softwareという新しいソフトウェア ライブラリがあります。Kinetis E シリーズは良い選択かもしれませんが、TSI モジュールは CAN モジュールを持たない KE1xZ でのみ使用できます。 したがって、I 2 C を介して S12ZVC に接続できる当社のスタンドアロン タッチ/近接センサー を検討することをお勧めします。 お役に立てれば幸いです。 よろしくお願いいたします。 トーマス 追伸: 私の回答が質問の解決に役立った場合は、「正解」とマークしてください。ありがとう。

Re: MMA8452Q Re: MMA8452Q Are the pads on the bottom of the part connected to the corresponding metal visible tabs on the side of the part? See Page 50 and 51 of the datasheet. Especially Detail G Re: MMA8452Q Hello John, Yes – the Cu seen on the sides of the package are connected to the pads of the device. This is an artifact of the half-etch process used in the design/fab of the leadframe. Best regards, Tomas

SensorFusion 7.0 の方向ドリフトの問題 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 私は、9-DOF MEMS ナビゲーション デバイス ( InvenSense MPU-9250 、できれば NXP の部品を含む) を使用して、カスタム設計されたハードウェア、ソフトウェア、およびドライバでリアルタイムの方向を提供するアプリケーションを開発しています。すべてがカスタムであるため、SensorFusion 7.0 ライブラリを SDK で提供されるコア ルーチンにまで削減する必要がありました。さらに、初期化関数を直接呼び出し、ジャイロ、磁力計、加速度センサの 1 要素 FIFO にデータをロードする独自の関数を作成しました。 MPU-9250 の軸は、下の図のように定義されています。したがって、磁力計の軸を回転させて、ジャイロと加速度センサと同じにします。これは、Z 軸を反転し、X 軸と Y 軸を交換することによって行います。 また、単位が正しいことも確認しました (加速度は g、回転速度は度/秒、磁力計はマイクロテスラ)。整数と浮動小数点数の「単位あたりのカウント数」と「単位あたりのカウント数」の変換係数を適切に設定しました（少なくとも私はそう信じています）。 私はfRun_9DOF_GBY_KALMANアルゴリズムを 200 Hz で実行し、9 つの軸すべてに対して 200 Hz で新しいデータ/サンプルを 1 要素 FIFO にロードしています。デバイスを少し動かすと、 iFirstAccelMagLockフラグが 0 から 1 にスイッチすることがわかりました (これは良い兆候のようです)。 しかし、カルマンフィルタの様々な角度出力は、 fPhiPl; ///< ロール (度) fThePl; ///< ピッチ (度) fPsiPl; ///< ヨー (度) fRhoPl; ///< コンパス (度) fChiPl; ///< 垂直からの傾き (度) fDeltaPl; ///< カルマンフィルタからの事後傾斜角（度） 空間を漂っているように見え、デバイスの実際の回転には反応しません。 静止状態での長期平均を使用して、ジャイロの DC オフセットを測定してみました。それは約 0.5 度/秒なので、これを差し引いても、このドリフトと応答の欠如は解消されません。 したがって、SensorFusion 7.0 ライブラリの使用に関して次の質問があります。 ジャイロの回転方向を含む、9 つの自由度すべてについて、予想される入力軸と単位が正確に指定されている場所はどこですか?X、Y、Z 軸はジャイロ、磁気、加速度に対して一貫している必要があり、ジャイロの回転方向に対しては右手の法則が満たされる必要があると想定しています。しかし、もう一度言いますが、これはどこかに正確に文書化されているのでしょうか? アルゴリズムはジャイロ DC オフセット/ドリフトに対してどの程度敏感ですか?ハードウェアに合わせてこれを正確にゼロにする必要がありますか? メイン ループにキャリブレーション ルーチンが欠けているのでしょうか? SensorFusion (fRun_9DOF_GBY_KALMAN) は磁力計のキャリブレーションに対してどの程度敏感ですか?私の磁力計は 10 倍ずれているようですが、金属がたくさんある場所にあるため、磁場成分 (X、Y、Z) もずれているかどうかはわかりません。磁力計の読み取り値と磁場の歪みが最小限でなければ、アルゴリズムは適切に動作しないと考えられますか?コード内に硬鉄/軟鉄およびキャリブレーション ルーチンがいくつか含まれていたので、これらがキャリブレーションされていない磁力計の補正にどの程度役立つのか疑問に思っています。 iFirstAccelMagLock = 1 の場合、何を意味しますか?これは、SensorFusionが磁力計とジャイロデータが正しく連携して動作していると認識しているという意味でしょうか？それとも、ジャイロと磁力計のデータが何らかの理由で壊れていても、iFirstAccelMagLock = 1 になる可能性はあるのでしょうか？言い換えれば、この変数は正常な動作を示す指標としてどの程度信頼できるのでしょうか？ 9-DOF デバイスを 200 Hz でサンプリングし、1 要素 FIFO を使用して 200 Hz でデータを SensorFusion にロードしています。私のサンプルのアナログ帯域幅は約 50 Hz または 100 Hz です (これを設定することができます)。SV_9DOF_GBY_KALMANの出力も200Hzで読み取っています。このアプローチに何か問題はありますか？ これを適切に動作させるために、他に何かアドバイスはありますか? センサ・フュージョン Re: Problem with Drift in Orientation with SensorFusion 7.0 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ジョナサン、 通常、競争力のある部品のポートのサポートは提供していません (Invensense は NXP の競合です) が、いくつかの質問にお答えしたいと思います (他の方も追加の提案があれば歓迎します)。順番に： 1. ユーザー ガイドのセクション 5.3 では、ハードウェア抽象化の問題について説明します。 2. カルマン フィルタには、追跡する変数 (XY および Z) の 3 つとしてジャイロ オフセットが含まれます。デバイスが回転している限り、それらの推定値は継続的に更新されます。磁力計とジャイロの参照ベクトルは、デバイスが静止しているときに安定性を保つ必要があります。 3. 申し訳ございませんが、コードレビューは提供できません。 4. 適切な磁気校正が非常に重要です。これがないと、9 軸の良好な結果は期待できません。私たちが組み込んでいるルーチンは、一般に、センサに対して空間的に固定された硬鉄/軟鉄源の処理をかなりうまく行います。一般的な干渉を処理するためのコードもいくつか含まれていますが、それをどれだけうまく処理できるかには限界があります。 5. コードのコメントを確認すると、 iFirstAccelMagLock は初期化コードが一度だけ実行されるようにするためのブール変数であることがわかります。この値から全体的な健全性を推測しないでください。 6.MCU に十分な MIPS がある限り、あなたが概説したアプローチに問題はないと思います。 7. マニュアルを読みます。私はできる限り多くの「集合知」をそこに盛り込もうとしました。 よろしくお願いいたします。 Mike

LPC4337 Sensor Fusion Library The NXP Sensor Fusion Toolbox has the Flash LPCXpresso Binary -> OM13070 LPC4337 in the menu Is the source code of this version of the sensor fusion library available? SensorFusion Re: LPC4337 Sensor Fusion Library Hi Pavel, As part of ISSDK enablement for NPIs like RT10xx (RT1050, RT1060, RT1064, RT1020), our Sensors software team  signed up to provide sensor usage examples only as early enablement before their SDK launch. This is the reason that all MCU NPIs where ISSDK has been part of their MRD/PRD for early enablement, we provide ISSDK middleware support to deploy only sensor examples for a custom kit with FRDM-STBC-AGM01 (and not algorithm examples like sensor fusion and pedometer). Best regards, Tomas Re: LPC4337 Sensor Fusion Library Hi Tomas, Thank you, downloaded the LPC54114 AGM01 SDK and it has all the ISSDK and Sensor Fusion library files. I was also looking at the iMXRT1050 so I downloaded the iMXRT1050 with AGM01 SDK and it has the ISSDK and the sensor drivers but the \middleware\issdk\algorithms\sensorfusion\sources are missing from the SDK.  Is there a reason why the sensorfusion/sources are missing from the iMXRT1050 SDK? Thanks, Pavel Re: LPC4337 Sensor Fusion Library Hi Pavel, The binaries available as part of File -> Flash LPCXpresso Binary options in the NXP Sensor Fusion Toolbox were custom made for Sensor Fusion Toolbox v5 (older version) compatible with KSDK v1.2 using the Processor Expert module on Code Warrior toolchain (Kinetis SDK v1.2 is no more available). I do not have the source code or Code Warrior project for this binaries since latest Sensor Fusion Toolbox v7.x is integrated into ISSDK and is compatible with MCUXpresso SDK v2.5.0 (latest version). Even MCUXpresso SDK builder does not support the LPC families listed in the Sensor Fusion Toolbox File -> LPCXpresso Binary tab (i.e. LPC4337, LPC1549 and LPC11U68). The MCUXpresso SDK builder only supports LPC5xxxx and LPC8xxx series of MCUs: So I would recommend to use these LPC MCU families supported by MCUXpresso SDK latest version (since support model will be sustainable) and the ISSDK based Sensor Fusion examples we have for the following LPCXpresso boards: I hope it helps. Best regards, Tomas PS: If this answer helps to solve your question, please mark it as "Correct" or “Helpful”. Thank you.

mystical sensor MPL3115 Hello, developers! Now i make a project " portable weather station" based on MPL3115. Primary functions: display current time, e-kompass, pressure, altitude, temperature and weather forecast. its a batterry-operated devices, and components must have minimal Supply Current. when I found a MPL3115 i been really excited, because this IC have all what i need. But now my project is has stalled. Firstly, i wrote a source code as datasheet recomendations, for set and change mode of MPL3115, read registers and display the results. i test code and sensor at LPC-812 MBED board (because i like LPCXpresso) and sensor board is powered from LPC-812 (3.3 Volt). and I got the some results (pressure, temperature and altitude). Next, i reading a AN3914 ("Modern Altimeter and Barometer System using the MPL115A") and start to adaptation this algorithm for  MPL3115. for  make a weather forecast i need to get  pressure change per 1 hour. for this, i chose a 3-hours/180 minutes interval for collected samples in FIFO every ~20 minutes. User should be able get a weather forecast at any time, so program must compare oldest and newest samples (for example, now is 11-10 AM, oldest sample was obtained at 8-00 AM, newest samples at 11-00 AM. i compare  this samples, divided and get a pressure change per 1 hour. then i make a weatern pattern and display it. next samples update will be at 11-20 AM. ) but i get a first STOP: bytes, reading from FIFO, "deleted from the front of the FIFO buffer" (page24 DS). so if I read values ​​from the buffer, I lost them. and if i make a weather pattern as in the above example at 11-10AM, at 11-20 AM i can't get the data from FIFO. next possibility for 1 hour pressure change i will get only via 1 hour!  all the collected data (from 8-20 AM to 11-20 AM) will be LOST! So. this way is not work.:smileyshocked: Ok, AN3914 have another faster way to make a weather forecast (page 6)! all i need - it's a  pressure and current altutude (MPL3115 must give all of this). i must calculate "ideal pressure" Pweather (for good sunny day) for current altitude by using the equation: Pweather = (101.3 * exp(((float)(CurrentAltitude))/(-7900))). and compare current pressure with "ideal". i wrote a code: set Altimeter mode and get a current altitude, set Barometer mode and get a current pressure, calculate and display result of weather pattern. i live in area at 56—178 meters of sea level. i start the test and get a second STOP  : sensor's PCB is on the table at room temperature (22-24 C) and does not move. source code don't change.  in the morning i have altitude=102 meters, in the dinner =32 meters, in the evening 0 meters. i turn on Debugger and see: when  I read data registers in Altimeter mode, OUT_P_MSB Register= 0xFF, so i get incorrect data from sensor . But i get correct temperature data in this reading operation (i make a cycle read 5 bytes from sensor at one procedure). So,this way does not inspire confidence... I just have to find a shaman! Because I can not find understanding with this really fine sensor. May be anybody help me? Best regards, Ellis Pressure Sensors Re: mystical sensor MPL3115 Hi Ellis, We have some code examples and other documentation available in Freescale communities, perhaps it can be useful: https://community.freescale.com/community/sensors/content?filterID=contentstatus%5Bpublished%5D~objecttype~objecttype%5Bdocument%5D&query=MPL3115A2 Regards, Jose

Error FIFO FXLS8471 I'm working with a FXLS8471 sensor with SPI. My problem is that the reading of the 32  measurements of the FIFO  does not coincide with the reading of the acceleration in the three axes. The sensor interrupted by filling the FIFO but when I try to read the 192 bytes in burst mode, the answer is incomprehensible. Thank you   Carlos Canal Intelligent Sensing Framework Re: Error FIFO FXLS8471 Hello Carlos, Here some suggestions & feedbacks: "Where axis X reading is = FF E0 (AX=0.0024g), axis Y=FD 70 (Ay=-0.0518g) and axis Z= 40 E8 (Az=0.9995g)" Regarding your conversion, AX should be negative FFE0 (hex) = -32 signed 16 bits) = -32/2² = -4 (signed 14bits)  = -4*sensitivity (g or mg). About your reading function, it seems good, I've got: bool FXLS8471Q::bRead(uint8_t __u8_register, uint8_t* __au8_OutValue,uint8_t __u8_length) {     bool __b_result = false;     uint8_t __u8_i;         _t_cs = 0;         _t_spi.write(  (__u8_register&0x7F) | (0x0<<7) ) ;     _t_spi.write(__u8_register&0x80);     for(__u8_i=0;__u8_i<__u8_length;__u8_i++)     {         __au8_OutValue[__u8_i] =  _t_spi.write(0x00) ;     }     _t_cs   =   1;        __b_result = true;     return __b_result; } but again, check your conversion... Are you sure the FIFO is enabled? How did you configure the sensor? Thanks, Anthony Re: Error FIFO FXLS8471 Hello Anthony: I do not get properly read accelerations 32 records stored in the FIFO. For example, a reading of the acceleration of the three axes is:   FF  E0 FD  70  40  E8 Where axis X reading is = FF E0 (AX=0.0024g), axis Y=FD 70 (Ay=-0.0518g) and axis Z= 40 E8 (Az=0.9995g) The following data correspond to a reading of the FIFO For example, axis X =7E  D8 , axis Y =20 60  and axis Z =00 40 7E  D8 20  60  00  40         7E  B8  20  38 00  34          7E D8  20  B8 00  30      7E D8  20  4C 00  18      7E E8  20  90 00  34         7E  F8 20  64  00 18 7E F4  20  40 00  3C          7E  F4  20  30 00  10          7E  D8  20  78  00 3C     7E C0  20  50 7F  F8      7E D0  20  40 00  44         7E  B0 20  6C  00 44 7E  E0 20  50  00 38          7E F0  20  7C 00  08           7E  E0  20  38 00  00      7E  D8 20  50  00  18      7E C0  20  5C 00  10        7E  E0 20  74  00 18   7E E0  20  7C 00  10         7E  D8 20  90  00 10            7E  F0 20  30  00 30       7E E0  20  30  00  38      7E E8  20  60 00  44        7E  E8 20 58  00  2C   7E  E0 20  54  00 3C         7E F4  20  88 00  58            7E D8  20  60 00  2C      7E  B8 20  6C  00 38      7E  A8 20  64  00 20         7E A8  20  64 00  44    7E D0  20  60 00  04         7E  E0 20  58  00 7C  La function para leer los 192 bytes es la siguiente: void IMUREAD2(char reg1, int count, unsigned char array[]){ unsigned int i; unsigned char value; unsigned  char dire, dire1; dire =reg1 &0x7F; dire1= reg1 &0x80; CS_FX=0; WByteSPI1(dire); WByteSPI1(dire1);                 for(i = 0; i < count; i++){                                array[i]=RByteSPI1();//                                } Nop(); CS_FX=1; return;                 } Thank you very much and best regards Carlos Canal Re: Error FIFO FXLS8471 Hello Carlos, Yes, the FIFO works with a 800Hz data rate. You just have to configure the CTRL_REG1 register by resetting the dr[0:2] field (to 0b000) . I attached an application note about FIFO uses in the motion sensors if you want to take a look at. Have a good day. Anthony Re: Error FIFO FXLS8471 Hello Anthony: Thank you very much for your cooperation. This weekend I report my code and put it on this page. I have the following question: Can use a 800 Hz ODR to work with FIFO? Thank you very much and best regards Carlos Canal Re: Error FIFO FXLS8471 Hello Carlos, Can you share your FXLS8471 configuration? I also would like to take a look at your drain function which empty the FIFO. Here my configuration if you want to compare: // CONFIG #define FXLS8471Q_CTRL_REG1        0x2A #define FXLS8471Q_CTRL_REG2        0x2B #define FXLS8471Q_CTRL_REG3        0x2C #define FXLS8471Q_CTRL_REG4        0x2D #define FXLS8471Q_CTRL_REG5        0x2E #define FXLS8471Q_XYZ_DATA_CFG     0x0E // ID #define FXLS8471Q_WHO_AM_I         0x0D #define FXLS8471Q_WHO_AM_I_VAL     0x6A // FIFO #define FXLS8471Q_F_SETUP          0x09 #define FXLS8471Q_F_STATUS         0x00 bool FXLS8471Q::vInit() {     bool __b_result=false;     uint8_t __u8_temp=0xFF;     /* Check presence of the sensor to prevent SPI issues*/     if(bRead(FXLS8471Q_WHO_AM_I,&__u8_temp,1))       if(__u8_temp == FXLS8471Q_WHO_AM_I_VAL)      //Check Sensor ID answer        /* Confugre the sensor */     if(bWrite(FXLS8471Q_CTRL_REG1  ,0x0))        //Standby mode     if(bWrite(FXLS8471Q_XYZ_DATA_CFG,0x2))        //0.976mg/LSB          /* Configure the FIFO */     if(bWrite(FXLS8471Q_F_SETUP    ,0x80))      // FIFO mode2 : stops accepting new samples when overflowed        /* Configure the FIFO interrupt */     if(bWrite(FXLS8471Q_CTRL_REG3  ,0x82))      // FIFO, interrupt active high (rising event)     if(bWrite(FXLS8471Q_CTRL_REG4  ,0x40))      // FIFO interrupt enabled     if(bWrite(FXLS8471Q_CTRL_REG5  ,0x40))      // FIFO interrupt pin routed to INT1     if(bWrite(FXLS8471Q_CTRL_REG1  ,0x11))      //Set ODR to 400Hz & active mode     {         __b_result= true;     }                                            return __b_result; } #define FXLS8471Q_OUT_X_MSB         0x01 bool FXLS8471Q::bGetFIFOAccelData(int16_t __aai16_AccelData[32][3]) {     uint8_t __au8_Buffer[192];     int16_t __i16_SingleData;     uint8_t __u8_i,__u8_j;     bool __b_result;     if(__b_result = bRead(FXLS8471Q_OUT_X_MSB,(uint8_t*)__au8_Buffer,192))     {         for(__u8_i=0;__u8_i<32;__u8_i++)         {             for(__u8_j=0;__u8_j<3;__u8_j++)              {             __i16_SingleData = (int16_t)( (__au8_Buffer[__u8_j*2+__u8_i*6]<<8) + __au8_Buffer[__u8_j*2+__u8_i*6+1]);              __aai16_AccelData[__u8_i][__u8_j] =  (int16_t)( ((float)__i16_SingleData)/4.0);             }           }           }     return __b_result; } Give me more information about your issues. Thanks, Anthony

NTM88 SPIポート こんにちは、 CodeWarrior に NTM88 スターター プロジェクトをロードしました。代わりに SPI インターフェースを使用してセンサ データを別のボードに送信するように変更したいと思います。SPI に関連するライブラリが見つかりません。 よろしくお願いいたします。 マーケル Re: NTM88 SPI Port ありがとうございます。 Re: NTM88 SPI Port こんにちは、マルケルさん。 SPI 経由でホスト MCU に転送されるセンサー データの例は、ユーザー ガイドを含むこのデモ パッケージで入手できます。 以下からダウンロードできます: https://www.nxp.com/products/sensors/pressure-sensors/tire-pressure-monitoring-sensors/ntm88-highly-integrated-tire-pressure-sensor:NTM88?#design-resources よろしくお願いいたします。 トーマス

pitIsrFlag Sensor Fusion SDK Question I just purchased a K64F-AGM01 assembly. Never used the NXP products before. I'm stuck. I've searched the community for hours and hours for answers. Read every documentation I could find. Still can't seem to find the information that I need to build my project. I loaded a SDK example for sensor fusion. Ran the example in debugger, but it runs through the cycle once, and since pitIsrFlag doesn't == true on the first pass, the program ends. I get no data from the sensor fusion functions. Am I supposed to write my own program to call the bare metal main function from a loop I create separately? SensorFusion Re: pitIsrFlag Sensor Fusion SDK Question Randy, You probably don't want to think of the board as a programmable USB peripheral.  That's not the intent.  The GUI uses the OpenSDA UART/USB feature to communicate with the board.  So it has to have the appropriate OpenSDA driver installed on your windows machine - which only embedded developers are likely to have.   The interface in the embedded code has communications to/from the sensor fusion toolbox as it's primary reason for existence.  But of course you are welcome to use it as a starting point for your application.  The protocol (covered in ch. 7 of the user guide) is binary.  So you should not expect to see human readable content in your console.  Nor can you send it ascii commands.  The embedded code is almost always streaming packet types 1, 3 and 4 at a minimum.  You use Sensor Fusion Toolbox commands to select which algorithm is being used to compute the data in those packets. Shoot me an email at [email protected] with your contact info and I'll check on my end to see how I can put the C# file that I use to communicate with the board into your hands. Regards, Mike Re: pitIsrFlag Sensor Fusion SDK Question To add to this.....I've tried writing "Q9 " to the K64F through the serial port in my Visual C# project then calling ReadExisting() to read data from the serial port. ReadExisting gives me an empty string. The only time ReadExisting gives me any data is when I first plug in the K64F, and when it does give me data it is undecipherable. After the first read, in the following calls to ReadExisting it gets an empty string. The ReadLine command gets data, but it appears to be undecipherable as well. Re: pitIsrFlag Sensor Fusion SDK Question Thank you Mike for your help. I've studied everything available that I could find and still stuck. With typical USB hardware peripherals I've programmed to in the past, they have *.dll file(s) I can import into my Visual Studio C# project and use the hardware's custom API data structure calls and send them through the virtual USB to get the data. I've never worked with an embedded system so, while I understand the basics of how it works, I'm having trouble with the syntax to request specific data from the K64F-AGM01. I connect to the port through my C# project and send a ReadLine command. The information I get back is hex numbers. Is this what I should expect? If so, how do I translate them? (As a side note, when I hook the K64F board up to Tera Term, the console just prints a stream of garbage) I was hoping to be able to just send a request to the port from my C# project to get the fRhoPl data from the K64F. If there is a simple line of C code from my C# project to do this, I haven't found it. I see there's a sUARTOutputBuffer in the bare metal code. Is that where can pick up the data from the host? If so, how? Should I write lines of code in the bare metal main program to actually send information to the port, then read it from the port on the host (C# project) side? Thanks in advance, Randy <> Virus-free. www.avg.com <> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sat, Dec 2, 2017 at 7:54 AM, michaelestanley Re: pitIsrFlag Sensor Fusion SDK Question "Sensor Fusion Toolbox" refers to the GUI portion only running under windows or Android.  It communicates to a sensor fusion application running on the embedded board via a UART-based protocol which is documented in the user guide.  The GUI has the ability to program boards with a sample S.F. application.  But that is NOT what you've done.  You've used the development tool to program the board, which is the normal development flow.  ALL calibrations are done on the embedded board.  The GUI is for demo and debug purposes only. You can create your own windows app if desired.  Again, the protocol is specified in the user guide.  And since you have source, you can even change it if desired.  We don't normally supply Windows-side software or headers, as most customers have their own interfaces. calls to initialize the accel and mag calibration parameters are inside function initializeFusionEngine() in file sensor_fusion.c.  The initialization functions for the 6 and 9-axis Kalman filters will either load previously stored gyro offsets from flash OR just use current measurements as the offset.  The latter is why you see that message in the GUI. Much of the above IS covered in the user guide.  You will save yourself a lot of time if you take the time to at least give it a quick skim so you know what is covered.  I also posted links to training videos in this space yesterday. Good luck. Mike Re: pitIsrFlag Sensor Fusion SDK Question Thank you, Mike. I was able to read the compass data and might not need the Windows GUI. A few questions: 1. Is the Sensor Fusion Toolbox flashed onto the K64F when I run the Windows Sensor Fusion Toolbox and thereafter the Windows GUI is reading the processed or calibrated compass fRhoPl heading from the board itself, or is the Sensor Fusion Toolbox a Windows program that is constantly pulling the raw data from the K64F and processing the calibrations in a Windows .exe? 2. If the Toolbox software is actually on the board and running from the board, could I just create my own Windows GUI and pull the calibrated compass data from the serial port, and if so, what header files or library files do I need to include in my Windows C# program? 3. When I first run the Windows Sensor Fusion Toolbox, it asks the user to move the board around to calibrate it. This being the case, when I run the debug in the MCUXpresso IDE and read the fRhoPl data, how does the Sensor Fusion software initially calibrate the sensors? When running the debugger, it doesn't ask me to wave the board around as does the Windows Sensor Fusion program. Thank you for your help. Very grateful. Randy <> Virus-free. www.avg.com <> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Fri, Dec 1, 2017 at 2:01 PM, michaelestanley Re: pitIsrFlag Sensor Fusion SDK Question Randy, You can read the compass heading directly from the global structures.  The field name varies as a function of the algorithm you're using.  See Section 4.2 in the user manual, and specifically Table 6.  The forth row in the table gives you the field name. Let me know if you're still interested in the GUI after checking that out.  We're in the process of adjusting our software release processes in anticipation of the QualComm merger, and I'll need to consult my masters about doing that within the scope of new guidelines. Regards, Mike Re: pitIsrFlag Sensor Fusion SDK Question Thanks Mike, Really appreciate your reply. Yes, everything works when I run Sensor Fusion Toolbox. I'll try putting a break as you suggest.....Another question: Is it possible to get the source code to the Windows GUI for the Sensor Fusion Toolbox? What I'm trying to do is just capture the compass heading (in degrees) after all the offsets and calibration have been calculated (as is displayed in the text box in the Sensor Fusion Toolbox GUI)? Thank you again. Randy <> Virus-free. www.avg.com <> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Fri, Dec 1, 2017 at 11:11 AM, michaelestanley Re: pitIsrFlag Sensor Fusion SDK Question Randy, Let me ask, are you trying to single step through the debugger?  If you try that on the if (true == pitIsrFlag) { statement, you will go nowhere fast.   The reason is that the PIT timer is programmed to "freeze" in debug mode.  From the PIT chapter of the K64 Reference Manual: The good news is that you can put a break at the next line after the IF, RUN to that point, then continue single stepping. Does your board flash green on LED D12 on the K64 when you just power it up outside the debugger?  If so, the app is running fine and this is just a pilot error. The other thing you should do is startup the sensor fusion toolbox and connect to the board.  That will enable you to see it operating correctly. Regards, Mike

nt3h2111はIIC経由ではアクセスできません NT3H2111 チップの使用中に問題が発生しました。問題が発生すると、IIC の読み取り/書き込み操作では常に NAK 結果が返されますが、EEPROM 上の NFC の読み取り/書き込み操作は正常に機能します。 すべての IIC アドレスをスキャンしようとしましたが、有効な ACK を受信できませんでした。 この状況が発生した後、IC を新しいものに交換する必要がありました。確認する方法はありますか？ Re: nt3h2111 cannot be accessed via IIC こんにちは、カイリ はい、チップを交換すると通信の問題は解決します。 問題が発生したとき、ロジック アナライザーを使用して SDA と SCL の実際の波形をキャプチャしました。IIC 波形は正常でしたが、コンポーネント アドレスへの書き込み時に ACK がありませんでした。I²C アドレス スキャンを実行したところ、すべてのアドレスが NAK を返しました。 Re: nt3h2111 cannot be accessed via IIC こんにちは@Jerry_zeng22 そこで、チップを交換すると通信の問題は解決するのでしょうか? また、ロジック アナライザーを使用して、SDA や SCL などの I2C ライン上のデータを監視できますか?