how to use Pressure Measurement Characteristic to calculate Pressure hi, I'm working in a project with TPMS. using the example program i get de array gu16UUAA, looking at the formula i dont know how to calculate de pressure using that table. please any guide will be appreciated Pressure Sensors Re: how to use Pressure Measurement Characteristic to calculate Pressure Hi Javier, You only need to substitute the values in this transfer function. P = ΔP1500 x PCODE + (100 – ΔP1500) Example: ΔP1500 = 2.750 kPa/count (Should be in the datasheet on pressure measurement characteristics) PCODE = 0x20 = 32 P = 2.750 kpa/count x 32 count + (100 - 2.750 kPa/count) P = 88 kPa + 97.25 kpa P = 185.25 kPa You can also refer to the attachment for more detail in the correspondence between compensated data in common units. Regards, Darío

未从 FXOS8700C 收到 ACK <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您好， 我无法从 FXOS8700C 收到 ACK。看起来应该很简单。我将 BRKT-STBC-AGM01 与我自己的 MCU 一起使用，甚至尝试了两块板以防其中一块损坏。我也引用了这篇文章：https://community.nxp.com/message/926172?q=BRKT-STBC-AGM01%20connections 我在下方板上的人脉关系： J3.1、J3.3 - Vdd（3.3V） J3.2、J4.5 - 电源 J3.4 - SCL J3.5 - SDA 以下是范围捕获： 我无法与任何一个传感器通信。我的板与其他连接的传感器通信良好。 有什么想法吗？谢谢。 Re: Not getting ACK from FXOS8700C <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MCU 上的 GPIO 需要配置为 "漏极开路"，之前配置为 "推/拉"。希望这能在将来帮助到其他人！

mpx5500 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 尊敬的各位， 我需要将 MPX5500 连接到 PIC18F MCU 这样 MCU 才有自己的比较器或者我可以使用单独的运算放大器 将 MPX5500 连接到 MCU 的最合适方法是什么？ 请大家帮忙 Re: mpx5500 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您好， MPX5500 是集成式压力传感器，这意味着传感器已在内部进行了温度补偿、校准和放大，因此传感器的输出电压为 0 至 5.0V，具体取决于所施加的压力。 将其连接到微控制器所需的硬件很少，您可以在数据表的图 4 中找到推荐的连接方式： http://cache.freescale.com/files/sensors/doc/data_sheet/MPX5500.pdf 此致， 何塞

MPX5500 压力传感器的分辨率 您好！ 我想购买一个压力传感器，型号为 MPX5500。我找到了https://www.nxp.com/docs/en/data-sheet/MPX5500.pdf上的技术资料，但遗憾的是，它没有提到传感器的测量分辨率（单位：千帕）。我在哪里可以找到这些数据？ 谢谢！ Re: Resolution for MPX5500 pressure transducer 请参阅数据表中的灵敏度：

MMA8451Q hello, I have a problem and I need your help I want to calculate the speed through the accelerometer sensor of freescale KL46Z and I want to save it to an excel file I want a clear expliquation about the CodeWarrior and C code for this program thank you. Re: MMA8451Q Hi naifar mourad, In theory it is possible to calculate speed of an object using an accelerometer sensor. If the acceleration of an object is known, we can get a proportional approximation of the speed data if an integration is applied. Unfortunately we do not have any updated document with information about how to do this with the MMA8451Q/KL46Z, however, we do have an application note that mentions how to calculate velocity/speed (and positioning) using the accelerometer MMA7260 (which is no longer manufactured), but you can use this document as a reference to create your own code. Application note: AN3397 “Implementing Positioning Algorithms Using Accelerometers” You can also use the bare metal example project of the MMA8451Q that can be found in Freescale communities: https://community.freescale.com/docs/DOC-98836 I hope this helps. Have a great day, Jose Reyes ----------------------------------------------------------------------------------------------------------------------- Note: If this post answers your question, please click the Correct Answer button. Thank you! -----------------------------------------------------------------------------------------------------------------------

FXLS8471Q - FIFOフィルモードのサンプルコード ここ： https://community.nxp.com/t5/Sensors-Knowledge-Base/FXLS8471Q-FIFO-Fill-mode-example-code/ta-p/1108021 @TomasVaverkaより 最初のコード ブロックでは、CTRL_REG4 に対するコメントが間違っている (または少なくとも誤解を招く) と思います。 void FXLS8471Q_Init (void) { FXLS8471Q_WriteRegister(CTRL_REG1, 0x00); // Standby mode FXLS8471Q_WriteRegister(F_SETUP_REG, 0xA0); // FIFO Fill mode, 32 samples FXLS8471Q_WriteRegister(CTRL_REG4, 0x40); // Enable FIFO interrupt, push-pull, active low FXLS8471Q_WriteRegister(CTRL_REG5, 0x40); // Route the FIFO interrupt to INT1 - PTA5 FXLS8471Q_WriteRegister(CTRL_REG1, 0x19); // ODR = 100Hz, Active mode } データシートによると、CTRL_REG 4には割り込み有効化ビットのみ含まれており、プッシュプルやアクティブ ロー制御は含まれていません。 プッシュ プルおよびアクティブ ローの制御は CTRL_REG 3にあります (デフォルトはプッシュ プルとアクティブ ローです)。 Re: FXLS8471Q - FIFO Fill mode example code ありがとうございます。 FXLS896xAF 用のこのようなサンプルがいくつかあれば便利です。 Re: FXLS8471Q - FIFO Fill mode example code こんにちは、アンドリュー。 フィードバックをいただき、ありがとうございます。おっしゃる通り、出力モード (プッシュプル vs. オープンドレイン) と極性 (アクティブ ロー vs. ハイ) は、どちらも CTRL_REG3 レジスタのビット pp_od と ipol を使用して設定可能です。 これを明確にするために、FXLS8471Q_Init 関数を更新しました。 void FXLS8471Q_Init (void) { FXLS8471Q_WriteRegister(CTRL_REG1, 0x00); // Standby mode FXLS8471Q_WriteRegister(F_SETUP_REG, 0xA0); // FIFO Fill mode, 32 samples FXLS8471Q_WriteRegister(CTRL_REG3, 0x00); // Push-pull, active low interrupt FXLS8471Q_WriteRegister(CTRL_REG4, 0x40); // Enable FIFO interrupt FXLS8471Q_WriteRegister(CTRL_REG5, 0x40); // Route the FIFO interrupt to INT1 - PTA5 FXLS8471Q_WriteRegister(CTRL_REG1, 0x19); // ODR = 100Hz, Active mode } BR、トーマス

NTM88_GenFSK_Beacons PTA0 CS not used? Hi, I am reviewing the NTM88_GenFSK_Beacons example beacon, and it seems that the PTA0 CS is not being detected at NTM88. Is this correct? I am going to connect the NTM88 to TI BLE MCU. If the TI BLE MCU pulls the CS line low, the NTM88 would read the sensor data and save to buffer array. I do not need the Wake Up and KBI. Would my intended functionality work if I read PTA0 before reading the sensors, see code modification below. Then I just need to comment out the codes below for WAKEUP_PIN_HIGH and waiting for acknowledgment at PTA3/KBI. Regards, Markel Re: NTM88_GenFSK_Beacons PTA0 CS not used? Thanks,  Re: NTM88_GenFSK_Beacons PTA0 CS not used? Hi, What I am saying the PTA0 is not being read at NTM88. Seems like it serves no purpose at the NTM88_GenFSK_Beacons example program. I intend to connect the NTM88 to TI BLE MCU using SPI interface. The TI BLE MCU needs to be discoverable and connectable. So, I can not have the NTM88 wake it up every 2 seconds. I also have a SPI external flash connected on the SPI bus. After I configure, the TI BLE MCU GPIO's as SPI, I may not be able to re-configure 1 SPI pin to serve as KBI input to NTM88. Using the PTA0 as KBI interrupt is a good option. But, after I pull the PTA0 low from host MCU, would the NTM88 keep running? It seems how the NTM88 KBI is configured is that, I have to pull the KBI input low every time the host MCU would need to get sensor data from NTM88. I will check out the example project you shared. Regards, Markel Re: NTM88_GenFSK_Beacons PTA0 CS not used? Hi Markel, PTA0 is used as SPI chip select. What do you mean by “not being detected as NTM88”? No, if KBI is not used it will not work. When the NTM88 is in sleep (either STOP1 or STOP4), the SPI block is disabled. When the NTM88 is in sleep, if KBI is disabled and the host MCU pulls the CS pin low, this will have no effect on the NTM88 (i.e. the NTM88 will not wake up). The only way for the host to wake up the NTM88 from sleep via GPIO is to use the KBI block. KBI interrupt can be configured on any of the PTA0 to PTA3 pin. So it is possible to use PTA0 as KBI pin instead of PTA3. In that case, the NTM88 would go to sleep with KBI enabled on PTA0. When the host pulls PTA0 line low, the NTM88 would wake up on KBI interrupt. Once the MCU is in RUN, the application can enable SPI so the BLE MCU can read the NTM88 memory. In the GenFSK Beacons demo, it is the NTM88 that wakes up the BLE host. If the desired implementation is the other way around (i.e. the BLE host wakes up the NTM88), then the demo project “NTM88_BLE_Beacons_mode_8” would be more appropriate as a starting point. This demo project can be found in the package at: https://www.nxp.com/webapp/Download?colCode=NTM88-KW38-BLE-BEACONS&appType=license Best regards, Tomas

部品情報：MPXH6115A6T1 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> センサ MPXH6115A6T1 - NXP の推奨リフロー プロファイル温度を教えてください (例:フリースケール）。ウェブサイトではピーク温度 250°C のみが記載されていますが、リフロー プロファイル温度のグラフに記載されている以下の詳細も必要です。 - 予熱温度。 - 予熱時間 - 最高気温。 - ピークタイム。 - ランプアップ/ダウン - 200℃以上の時間 Re: Information for part : MPXH6115A6T1 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、アニルさん。 はんだ付けの推奨事項については、 AN3150 - 圧力センサデバイスのはんだ付け推奨事項を参照してください。 このデバイスのリフロー温度プロファイルは、J-STD-020C 規格に準拠する必要があります。 よろしくお願いいたします。 トーマス

MPXH6400A の 3D STEP モデルはどこで入手できますか? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MPXH6400A センサの 3D STEP モデルを探しています。 ありがとう！ 圧力センサ Re: Where can I locate a 3d STEP model for MPXH6400A? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> トーマスさん、本当にありがとう！ポイントがあったらあなたにあげたいのですが Re: Where can I locate a 3d STEP model for MPXH6400A? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、マット。 要求された 3D STEP モデルは、ここからダウンロードできます。 3D STEPモデル: SSOP アキシャルポートパッケージ 1317A よろしくお願いいたします。 トーマス 追伸: 私の回答が質問の解決に役立った場合は、「正解」とマークしてください。ありがとう。

Guidance on Using Flash Memory for Both Code and Data Sections in NTM88Jxx5S TPMS Hello, I am currently working with the NTM88Jxx5S Tire Pressure Monitor Sensor from NXP and have a few questions regarding its memory usage. As per the datasheet, the 64 bytes of low-power “always on” NVM parameter registers are used to store data, but this data may be lost during power loss or disturbances. To ensure data retention during abnormal power cycles, I would like to utilize a portion of the (currently used only for code sections) to store critical data. I would like to know: Is it possible to allocate a portion of the 16KB flash memory for data storage alongside the code? If yes, could you please provide a step-by-step process or guidelines for implementing this? Are there any existing examples, reference code, or application notes to help in achieving this configuration? I am attaching the datasheet and feature details for reference. Any insights, suggestions, or resources to move forward would be highly appreciated. Looking forward to a quick response. BR, Vinith Ramarapu. TPMS-SW NTM88 #flash_memory Pressure Sensors Re: Guidance on Using Flash Memory for Both Code and Data Sections in NTM88Jxx5S TPMS Thank you mate, but this still doesn't answer my initial questions. I just need to know whether splitting the 16KB RAM into Data and code sections is possible. If so curate some references or examples as such. Thank you in advance. Re: Guidance on Using Flash Memory for Both Code and Data Sections in NTM88Jxx5S TPMS Please go to https://www.nxp.com/products/sensors/pressure-sensors/tire-pressure-monitoring-sensors-tpms/ntm88-highly-integrated-tire-pressure-sensor-family:NTM88 Scroll down to Software and click on Starter Package for NTM88 and NCK2910. Re: Guidance on Using Flash Memory for Both Code and Data Sections in NTM88Jxx5S TPMS The link you provided for NTM88 – RAM and FLASH Memory Organization document included in the Starter Package for the NTM88 and NCK2910 is not working and it's unable to access that Re: Guidance on Using Flash Memory for Both Code and Data Sections in NTM88Jxx5S TPMS Hello,  Please see this community post: https://community.nxp.com/t5/Sensors/Splitting-Flash-Memory-for-Code-and-Data-in-NTM88Jxx5S-TPMS/td-p/2006117 As it addresses the same question, I will follow up there. If you have further questions, please post them in that thread.

MPX5700AP and other pressure sensors failling, can't get to know why Hi all, I've recently bought severals sensor pressure from the Freescale brand, the MPX5700AP was the most appropriate as it is a 700kpa pressure sensor. I needed it to measure the pressure in my air pneumatic circuit of maximum 45PSI. All of the sensors I had died in few hours. I can't understand why. They're all receiving 5V in Vcc in pin 3. Pin 2 is linked to ground. Pin 1 to an arduino analog pin. Why are they dying? Is this an electrical circuit issue? If yes, what is the correct way to plug them into an electrical circuit? My V supply is limited to 5V so I don't see how they could have received over voltage or so forth. Same for Over pressure, my compressor can't go over 60PSI. MPX5700AP are normallt 4.75V to 5.25 in full span now the Vout is  around 1V to 1.50V ish for one of them. I have no idea why they're stop functinning. Are they really sensible? Is it because I'm using pneumatic air and therfore it "can" contain humidy? Is there any electrical schematic I should use that i'm not? I'm completely lost here Any idea on the matter would be glady appreciated Pressure Sensors Re: MPX5700AP and other pressure sensors failling, can't get to know why Hello again Valentin. I cannot catch any problem in your hardware, I ran a test with the very same pressure sensor connected to a pressurized tank at 100PSI, for almost a month without any problems. I would highly recommend you to use the filter shown in figure 4, that would reduce noise measurement (if any). You also mentioned that your compressor cannot go over 60PSI. The MPX5700 has a pressure range from 0 to 700kPa (101.05PSI). Let's say that your compressor reaches the 60PSI, that would be ~59.11% of the pressure range, which equals to an output voltage of ~2.57v. Also, please notice that you're using the AP version (MPX5700AP) which is an absolute pressure sensor, hence you're measuring atmospheric pressure PLUS the pressure in your tank. Your application requires a gauge pressure sensor (MPX5700GP or DP), so you can measure the differential pressure between the compressor tank and the atmospheric pressure (gauge pressure type). Please double check your measurements, 1.5v output voltage would correspond to ~27psi. Hope it helps. Josh Re: MPX5700AP and other pressure sensors failling, can't get to know why Hey Josh, Thanks for your answer. I can't share anything right now I'm not at the office but basically: - Pin1 of the sensor is directly connected into the A0 arduino pin. - Pin2 of the sensor, to the ground - Pin3 to Vcc. So no capacitors nor resistances are inbetweens. I can read value on my arduino serial monitor, so it does work. But after few hours it stopped. By that I mean the serial value number where totally random which meant that A0 wasn't receiving any voltage so if I unplugged the sensor or plugged it, the value were not changing (still totally random). The sensor is cold so totally normal. It just stopped working. The current is (from memory) 7.0mA. I'm measuring Volts inbetween ground pin and Vout and it's around 1v and 1v5 when I apply pressure. It's low. The value changes so it works in a certain way but it's not 4.58V or 4.81 as it should. For the two others sensors, the Outpout voltage is 0 yes. I wonder if peak pressure can't "break it"? My compressor delivers 45 PSI in the circuit but the tubes are of 6mm and maybe when solenoids turned HIGH, the peak of pressure that comes in the sensor is much higher than its burst limit? Would that be possible? Re: MPX5700AP and other pressure sensors failling, can't get to know why Hello valentin, I have used that very same sensor for a similar application and I didn't have any problems with it. When you said "died in few hours" what exactly happens to the sensor? is the output voltage zero? is the sensor hot to the touch? how much current is the sensor consuming?. The only _recommended_ (but not required) circuitry for this sensor is shown in Figure 4, page 4 of the datasheet: http://cache.freescale.com/files/sensors/doc/data_sheet/MPX5700.pdf Could you please share your schematic? please include the arduino part too. Regards, Josh

MPX5999D 漏电流问题 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我们有一个关于 MPX5999D 的漏气问题。我们通常会发现少量的硅凝胶从坏零件环氧树脂外壳的某个位置泄漏出来。凝胶泄漏可能首先发生，需要很多时间。普通测试很难检测到。 问题是 1. 2. 造成这种现象的原因是什么，如何避免？ 压力传感器 Re: MPX5999D leakage issue <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好，谢尔盖 漏电流是未指明的，因此不能保证我们设备的性能特性。不幸的是，MPX5999D 的漏电流率没有特征。 很抱歉。 此致， 何塞 NXP Semiconductors Re: MPX5999D leakage issue <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我的意思是你的测试设备允许检测的最低漏电流率。本主题中的描述： https://community.nxp.com/thread/444621 Re: MPX5999D leakage issue <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好，谢尔盖 恩智浦是否对未移植的设备进行 100% 的漏电流测试？ 是的，在将所有压力传感器出厂之前，我们会对它们进行泄漏测试。 MPX5999D 的最大允许漏电流是多少？ MPX5999D 不应有压力泄漏。 此致， 何塞 NXP Semiconductors Re: MPX5999D leakage issue <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 谢谢你，何塞。您的回答很有帮助。实际上，在我们的设计中，当 O 形圈密封泄漏率足够高时，端口 P2 的压力可以大于端口 P1。我们将尝试使用胶水，并改进端口 P2 室与大气之间的连接。 恩智浦是否对未移植的设备进行 100% 的漏电流测试？MPX5999D 的最大允许漏电流率是多少？ Re: MPX5999D leakage issue <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您好， 1.新传感器（未使用过的）本体的密封性和坚固性是否有保证？ [A1] MPX5999D 是差压传感器，可测量高达 1000kPa 的压力。该传感器为正压单向型，这意味着只能对端口 P1 施加正压。该传感器专为 P1 始终大于或等于 P2 的应用而设计。 确保您使用的设备不符合操作特性。 2.造成这种现象的原因是什么，如何避免？ [A2] 通常情况下，只有当端口 P2 的压力大于端口 P1，或施加的压力超过传感器的承受能力时，我们才会看到硅凝胶泄漏。 此致， 何塞

Linux 中的传感器融合工具箱 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您好，   我在 Ubuntu 16 32 位（在 Fedora 23 中使用 Oracle VirtualBox 5.0.20 64 位虚拟化）安装了 Windows 版 "传感器融合工具箱"。     我可以生成 .bin为板 FRDM-K64F 提交文件并顺利安装。     但现在，有一个不利因素。   飞思卡尔传感器融合工具箱应用程序无法打开传感器板的端口。Dialog ERROR say：   检查传感器板是否已开启。如果传感器板从未与这台 PC 配对，则使用控制面板/设备和打印机/添加设备来添加传感器板，然后重新启动此应用程序。   解决方案--> 在 Wine 中设置串行端口   $ ln -s /dev/ttyAMC0 ~/.wine/dosdevices/com1 $ nano ~/.wine/system.reg 加上这个 [Hardware\\Devicemap\\Serialcomm] 1131331688 "COM1"="COM1"   wine SensorFusion.exe   结果：   但延迟很高。     顺祝商祺！ 哈维尔 传感器融合 Re: Sensor Fusion Toolbox in Linux <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 不客气，我很高兴能有所贡献。 我没有 Windows 机器，所以我可以试试 FSFK 项目。虽然速度不快，但还能用。 顺祝商祺！ 哈维尔 Re: Sensor Fusion Toolbox in Linux <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Wow！ 我太感动了 我们从未想过有人会尝试在 Linux 下运行该工具。 我对延迟问题也不感到惊讶。 你需要经历很多软件层才能完成你所做的事情。 感谢分享。 Mike

MMA8451Qを使用してオフセットキャリブレーションをテストする方法 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、 さまざまなシナリオでオフセット キャリブレーションをテストする方法と、予想される加速度センサの出力を確認する方法。平らな面でオフセット校正をテストし、予想される出力を読み取ります。異なる条件でテストして確認したい。情報を共有してください。 ありがとうございました。 Re: How to test offset calibration using MMA8451Q <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、トーマス。 この情報をありがとうございます。これは私たちの問題解決に本当に役立ちました。 再キャリブレーションに関してもう 1 つ疑問があります。データシート「 AN4069 」を確認しました。データシートには、「センサーを PCB に取り付けた後、他の理由でも再校正が必要になる場合があります」と記載されています。たとえば、傾斜アプリケーションのゼロ (0) 位置が常に 15° の角度である場合、アプリケーションではゼロ (0) 参照ポイントを変更して、これを新しい「ゼロ」位置と見なす必要がある場合があります。これらの再調整により、組み立てに追加の手順が加わるため、最終製品の製造コストが増加します。したがって、再調整のメリットとこれらの追加コストを比較検討する必要があるだろう。」 テストシナリオ: 加速度センサーを 15° の角度に保ち、再調整を実行します。 x=0、y=0、z=1 になるのでしょうか? はいの場合、 x=0、y=0、z=1 と同じ値が得られません。 したがって、このようなCASEの再調整方法についてご協力をお願いいたします。関連するデータシートがある場合は、再調整用のソフトウェアフローチャートとともにリンクを転送してください。 よろしくお願いいたします。 デシュヴィル Re: How to test offset calibration using MMA8451Q <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、チェタン。 以下のフリースケールのアプリケーションノートでは、最終的な加速度センサの再調整のさまざまな方法について説明します。 AN4069 - MMA8451、2、3Qのオフセットキャリブレーション: http://cache.freescale.com/files/sensors/doc/app_note/AN4069.pdf AN4399 - 3軸加速度センサの高精度校正: http://cache.freescale.com/files/sensors/doc/app_note/AN4399.pdf​ お役に立てれば幸いです。 よろしくお願いいたします。 トーマス 追伸: 私の回答が質問の解決に役立った場合は、「正解」とマークしてください。ありがとう。

RD-KL25-AGMP01のファームウェアが見つかりません <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ボードを入手し、デフォルトのファームウェアですべて正常に動作していましたが、ボードを少しいじってみたところ、緑色の点滅ライトが表示されなくなりました。デフォルトのファームウェアはどこにありますか?ボードを元の状態にリセットするにはどうすればいいですか? よろしくお願いします。 Re: Cannot find firmware for RD-KL25-AGMP01 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、アラシュさん。 Freedom Sensor Toolbox (CE) インストール フォルダーにあるバイナリ ファイルを使用してください。 C:\Program Files (x86)\NXP\Freedom Sensor Toolbox (CE)\Projects\GENERIC-DATA-LOGGER\Firmwares\ ISSDK\RD-KL25-AGMP01_OnBoard_GDL_2.0.bin ボードをプログラムするための手順が必要な場合は、 RDKL25AGMP01UGの第 3.4 章を参照してください。 お役に立てれば幸いです。 よろしくお願いいたします。 トーマス

手で握手する姿勢 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは！ センサー フュージョン ライブラリ 4.2 と 5.0 をすべてテストしました。私のセンサは、ジャイロ+加速度計付きの6軸のADIS16445です。fusion.h でセンサーノイズに応じてパラメータを調整しました。   1.しかし、これら 2 つのライブラリは、手で継続的に振動している状態ではパフォーマンスが良くありません。たとえば、平らな机の上でセンサーを継続的に振動させると、ピッチとロールがゆっくりと増加します。 私は、Xsens-MTI300 や SBG-IG500 などの AHRS 製品をいくつか使用しましたが、それらはすべて、手に持った状態で振動してもうまく機能し、ピッチとロールは増加せず、振動に応じてわずかに振動するだけです。加速度センサのローパス フィルタリングなど、さまざまな方法を試しましたが、うまく機能しませんでした。どうしてこんなことができるのか分かりません。 2. 増分高速（通常 200 Hz）回転ベクトル rvec（度）を計算するときに、ジャイロ バイアスをマイナスしないようにしました。これによりパフォーマンスが向上するようです。アルゴリズムは操縦中にジャイロ バイアスを正確に推定できないため、不正確な推定バイアスによって姿勢エラーが発生すると考えられます。ジャイロ データを 3 ～ 5 秒で平均化し、これを差し引く初期バイアスとして使用します。 3.線形加速時定数、線形加速減衰係数！このパラメータはどのように設定すればよいですか？このパラメータの意味は何ですか？ センサ・フュージョン Re: attitude under shake condition in hand <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 申し訳ありませんが、ADIS16445 に基づくパフォーマンスについてはコメントできません。V5 ライブラリで Freescale センサを使用した場合、振動の問題は発生していません。Mark Pedley の標準的なテストの 1 つは、IMU をできるだけ速く振って、回復の速さを確認することです。V5 は当社のセンサにより非常に速く回復します。そうは言っても、ライブラリはどのメーカーのセンサとも互換性があるはずです。Mark は、同様の結果で、さまざまなメーカーへの移植に成功しています。ただし、質問しないでください。Freescale は競合デバイスのサポートを提供できません (私のマスターの善意には限界があります )。そのためには、他のコミュニティ メンバーまたは ADI に頼る必要があります。 よろしくお願いいたします。 Mike

mma7361（加速度センサ）の問題 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは。以前、私は mma7361 加速度計のプレートを設計し始めました。このセンサーを販売している市販のパッケージは、提供するアプリケーションに対してかなり大きいため、再度設計することに決めました。このプロセスでは、データシートで提供されている設計を使用し、外部ソースから電力を供給することを考慮して、ソースの制御で少しスペースを節約しました。https://www.nxp.com/docs/en/data-sheet/MMA7361LC.pdfすでにプレート上にある加速度センサをテストしたところ、動作しないことがわかりました。すべてのポイントで導通が確認され、これは正しいのですが、何が問題なのかを特定できません。この加速度センサについて知っていて、私を助けてくれる人はいませんか?ありがとう 加速度センサ Re: Problems with the mma7361 (accelerometer) <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、フアン・パブロさん。 まず、MMA7361 加速度センサは製造中止となっていることをお伝えしておくことが重要です。そのため、アプリケーションを新しいアナログ加速度センサファミリ FXLN83xxq に移行することをお勧めします: https://www.nxp.com/products/sensors/motion-sensors/accelerometers-for-iot/nxp-analog-accelerometers:FXLN83xxQ さて、MMA7361 に関する問題についてですが、ユニットの保管に問題がある可能性があります。MMA7361 は MSL レベル 3 であり、摂氏 30 度、相対湿度 60% の環境で 168 時間の床寿命があることに注意してください。 湿気感度レベル (MSL) は、元の容器を開封した後のコンポーネントの耐用年数、保管条件、および取り扱い上の注意事項を示します。コンポーネントが防湿バッグの外側に留まることができる許容時間（防湿バッグの開封から最終的なはんだ付け工程まで）は、コンポーネントの周囲湿度に対する感受性の尺度となります。 多くの場合、吸湿によりコンポーネント内の水分濃度が高くなり、リフロー処理中にパッケージが損傷するほどになります。閉じ込められた水分の膨張により、ダイまたは基板からのモールド化合物の界面分離（層間剥離）、ワイヤボンドの損傷、ダイの損傷、内部亀裂が発生する可能性があります。最も深刻なケースでは、部品が膨らんで破裂する「ポップコーン」現象が発生します。 したがって、湿気に敏感なコンポーネントを乾燥させ、乾燥剤と湿度表示カードを入れた防湿帯電防止バッグに密封する必要があります。バッグは IPC/JEDEC J-STD-033 に従って真空密封する必要があり、PCB への組み立て直前にのみコンポーネントを取り外す必要があります。 このトピックに関する詳しい情報は、アプリケーションノート AN2265 に記載されています: https://www.nxp.com/docs/en/application-note/AN2265.pdf すてきな一日を、 ホセ --------------------------------------------------------------------------------- 注記： - この投稿があなたの質問への回答である場合は、「正解としてマーク」ボタンをクリックしてください。ありがとう！ - スレッドは最後の投稿から7週間フォローされます。それ以降の返信は無視されます。 後ほど関連する質問がある場合は、新しいスレッドを開いて、閉じたスレッドを参照してください。 ---------------------------------------------------------------------------------

Manchester implementation in NTM88 Hello everyone! I hope you are all doing well. I'm trying to receive data from the NTM88 sensor with 2FSK modulation and Manchester encoding. However, when I send the data, my receiver can't process the preamble and sync word. Interestingly, when I switch to NRZ encoding, everything works perfectly. I asked here in the forum if NTM88 encodes the entire message in Manchester or just the payload, and I was informed that it's the entire message. The strange thing is that when I set up my receiver for NRZ, it receives the preamble and sync word, which should be encoded in Manchester. However, it doesn't receive the payload, and I'm struggling to read it. How is Manchester implemented? Is it via hardware or software? If it's via software, what function is responsible for this? Re: Manchester implementation in NTM88 Dear Israel,  please see below an answer to your question from an application engineer I have contacted.   DESCRIPTION On software side, the application has to enable and configure the RF block, fill the RF buffer using the library function and then trigger the transmission using TPMS_RF_SET_TX, which takes as argument the number of bits to transmit minus 1. The NTM88 does not distinguish between preamble, sync word and payload. The NTM88 RF block encodes and transmits the content of the RF buffer the way it was configured during RF initialization. If the receiver is able to receive the first bytes only, make sure that the appropriate number of bits has been passed as argument when calling TPMS_RF_SET_TX. With Best Regards, Jozef

FXLC95000 and hard reset Hello!   I can't reset my FXLC95000 via RESETB pin. I have implemented one feature in my device recently. I added one more command for firmware version checking. That's how it works: 1. I power on my device 2. Send command 0x00 0x00 to be sure that there is fxlc95000 on I2C bus 3. Then send 0x29 0x00 to start 4. Then send my command for fw version checking 5. If I get not valid number of fw version I update fw.   So here is my problem: If we have any fw in fxlc95000 then everything works perfect. I can compare fw version and make fw updating. But! If we have fxlc95000 without firmware(from factory) or with damaged firmware(for example if we make power off during programming firmware) then when we try to send 0x29 0x00 we have 0xff 0xff answer. Then I understand that I need to update firmware but I can't do it because I have 0xff or 0x00 answer on my any commands. As I understand fxlc95000 is in undefined condition after my command 0x29 0x00 in that case. I desided to make hard reset via RESETB pin and then update firmware without sending 0x29 0x00 command. But it doesn't help. I still have undefined condition of fxlc95000 after command 0x29 0x00 even if I make reset. If I try to programm firmware without command 0x29 0x00 - everything works. Because of that my feature does not make sense because we can have new fxlc95000 or with damaged firmware and I can't programm it in that case.   Here are my question: Maybe there are some settings for hard reset or I should make strong time delays then i manipulate of RESETB pin??? Maybe there is another way to make reset fxlc95000 after sending 0x29 0x00 then there is no any firmware inside? Maybe there is any way to find out is there available (unbroken) firmware inside without sending 0x29 0x00 command? Intelligent Sensing Framework Re: FXLC95000 and hard reset Absolutely, But I suggest you use a different name than flash_opt... For example, I tried the following: uint32 flash_rev @0x1FFF8 = 0x01234567; Then, build and Flash the binary. Finally simple verification using FXLC95000 MailboxTool PC GUI IIC WRITE TRANSACTION :: Starting MB = 00   Write : 09 C8 00 00 00 00 FF F8 // Read 0x01FFF8-0x01FFFF content (no PWD needed as security is disabled) IIC READ TRANSACTION :: Starting MB = 00, No. bytes to read = 10   Read  : 09 80 01 23 45 67 FF FF FF FF Re: FXLC95000 and hard reset Hi jacques! Thank you for your answer. It's a good advice about storing FW version in fixed Flash address. I will try it later because I have another tasks now. How can I define address? Is this string enoght in code if I want to save version 101 for example? I use CodeWarrior and ISF1.0: uint32 flash_opt @0x1FFF8 = 0x00010001; After that when I power up device I can read four bytes using ROM CI_READ_WRITE command. Right? Re: FXLC95000 and hard reset Hi Vitaliy, Let me jump into this thread as I'm supporting also the FXLC95000 device. Yes the use of CRC check is definitively a good and robust solution. There's actually a ROM Command Interpreter utility (cf CI_CRC command in HW ref manual §16.5.7) that can do the CRC computation job. Maybe you are using it already... There's even a possibility to have the device do this CRC check at reset if you tweak the CHECKB bitfield of the NVBOPT Flash byte (address 0x01_FFFE). Then if the verification fails, the device will revert to ROM code. I didn't tried this feature as its documentation is rather scarce but if you're interested in using it, I can dig further. As one of your verification step is to check the FW version, you can also do it from the ROM Command Interpreter, before sending the "boot to Flash" 0x29 0x00 command. - dedicate a fixed Flash address to store the FW version, for example 0x01_FFF8, and define its content within your program code - read the content of this address using the ROM CI_READ_WRITE command (HW ref manual §16.5.5) command: 0x09 0xC4 0x0FF 0xFF 0xFF 0xFF FF F8 // Read 0x01_FFF8 to 0x01_FFFB content (4 bytes). No CI_PW needed if security is disabled Thanks for your interest in our product. Regards,     Jacques Re: FXLC95000 and hard reset Hi Aswin! Thank you for your answer. This is what I've understood: If we have blank flash memory or damaged flash then after sending 0x29 0x00 0xFF 0xFF 0xFF 0xFF and making reset via RESETB pin we will jump to flash memory. After that we will not have ability to send any command because there is not a valid image programmed in flash. So we need to make POWER OFF if we want to send any commands. Am I right? I've found another way to find out do I need to update firmware - I check flash memory CRC and compare it with valid CRC. Then I make decision about firmware updating. Now it works for me. Everything is OK! It is more correct solution. Do you agree with me? Re: FXLC95000 and hard reset Hi Vitaliy,                  I guess this would your problem. From the below figure , (Page 228 in FXLC95000 Hardware Reference Manual), you can see that only on Power on Reset, FOPT[15:8] is initialized which has the BF (Boot to Flash bit).  For a factory device with erased flash, device will boot directly into the ROM command interpreter on power-up. This is because, on POR, BF bit is initialized to 0 which is the inverted bit of Bit 5 of address 0x01_FFFE. So if you are trying to reset via only RESETB pin (not POR) after 0x29 0x00 0xFF 0xFF 0xFF 0xFF you will boot to flash immediately after reset as BF bit is set to 1. Hence any ROM command in this phase is not valid. However if you do POR, since FOPT is initialized BF bit is set to 0 and now you are in ROM mode and any subsequent ROM commands become valid. Hope this answers you question. Please refer the manual for additional details Thanks Aswin Re: FXLC95000 and hard reset Hi Aswin! I'm glad to hear you again. I want to clarify my question. You write: "I think you are getting an error because there is not a valid image programmed in flash ." YES! That's what I'm talking about! It is possible in two situations: 1. We have a new fxlc95000 from factory (without any image in flash). 2. We have damaged image in flash (for example then we had power off during programming flash). Problem is: In those two situations then I send 0x29 0x00 0xFF 0xFF 0xFF 0xFF 0xFF command I have an error answer on that command and any other commands after that. I try to make reset via RESETB pin to reboot it and send 0x00 0x00 again to get "good" answer. But there is no effect. I can get answer without errors only if I make Power OFF and Power ON again. It seems to me that RESETB pin doesn't work if we have not valid image in flash. Is it true? The question is: How to reset fxlc95000 after sending 0x29 0x00 0xFF 0xFF 0xFF 0xFF 0xFF command if we have not valid image in flash? Re: FXLC95000 and hard reset Hi Vitaliy,               I think you are getting an error because there is not a valid image programmed in flash .  What is the stauts of your flash_opt (@0x1FFFC) register in your program? Are you sending the value 0x29 0x00 0xFF 0xFF 0xFF 0xFF to ROM CI to execute the flash? Thanks Aswin

MPX5100DP: strange reading Dear NXP tech. I just bought an mpx5100dp sensor. I tried to read the datasheet but I don't really understand. Especially in the sensitivity which shows 45mV/kPa. I tried to do a test to read analog arduino for each of the 900 data that has been read by five(5) MPX5100DP sensor. in free air. The following is a snippet of the Arduino reading for each type of sensors, dp1 dp2 dp3 dp4 dp5 30 32 34 29 30 30 32 34 29 31 29 31 33 30 32 30 32 34 29 29 29 31 34 29 30 30 32 33 30 30 29.88338 31.45304 33.57585 29.56553 30.66047 *The last row is the average Question: 1. Why can each sensor read differently? 2. Am I justified in subtracting each sensor output by its integer average? even if I subtract it then some will not produce a zero value. Does the company have a solution for this problem? I need these sensors to do readings in a sample in my research so I try to make the resulting data logical. But I think this difference is illogical even though the sensors are placed in the same place at a very close distance. Thanks. Re: MPX5100DP: strange reading Hello Andhy, I hope all is great with you. Thank you for using the NXP communities. In this case, the sensitivity refers to the voltage output for every kPa. Do you mean that you are reading the atmospheric pressure? What is your local atmospheric pressure? In this case, I do recommend performing an auto-zero. I believe that this is caused for the offset error. Sources of offset errors are due to device to device offset variation (trim errors), mechanical stresses (mounting stresses), shifts due to temperature and aging. Performing auto-zero calibration technique will greatly reduce these errors. This technique can easily be implemented when an integrated pressure sensor is interfaced to an A/D and a microcontroller. I hope this information helps. Regards, David