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.

MMA8452Q I2C 规格 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MMA8452Q 是否支持 I2C 正常模式？ 其数据表写道"，其 I2C 兼容快速模式和正常模式" ，见 P.16。 但其特性（P.8 表 4）只写了快速模式规格。 我关心 tr 和 tVD 的规格。I2C 规范第 5 版第 48 页中的红色方块值）。 顺祝商祺！ M.Kiniwa 加速度传感器 Re: MMA8452Q I2C specification <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好，正弘 是的，MMA8452Q 符合标准和快速模式的 NXP I²C 规范： 顺祝商祺！ 托马斯

保密协议通过了，但无法下载 MC33771C 功能安全手册文档。 我买了 MC33771，它正在开发中。 但是，接收功能安全手册时存在问题 我知道，一旦 NDA 完成，就可以下载该文件。但当我进入文档下载窗口时，却显示 "需要激活帐户"，无法下载。 请咨询如何下载 MC33771C 功能安全手册文档。 电池传感器 Re: NDA went through but MC33771C Safety menual document could not be downloaded. 两种解决方案： 1: 通过打击链接提交票据并上传您的 NDA： 主页 (nxp.com) 2: 继续等待 Docstore 的下载批准。

MMA8452Q I2C仕様 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MMA8452Q は I2C 通常モードをサポートしていますか? データシートの16ページに「I2Cは高速モードと通常モードに対応しています」と書かれています。 ただし、その特性（P.8 表4）には高速モードの仕様しか記載されていません。 私はtrとtVDの仕様を気にしています。（以下I2C仕様書Rev.5 P.48の赤い四角の値 よろしくお願いいたします。 キニワ 正治 加速度センサ Re: MMA8452Q I2C specification <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、マサヒロさん。 はい、MMA8452Q は標準モードと高速モードの両方で NXP I²C 仕様に準拠しています。 よろしくお願いいたします。 トーマス

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

2状態カルマンフィルタに推奨されるMCU <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、 加速度センサを使用して高頻度かつ高加速度を監視する回路基板を設計したいと考えています（発破センサ、建設機械センサ）。センサは 3 方向すべてを監視しますが、センサは回転しない (1 度未満の動き) ため、これらを個別にフィルタリングします。3方向MEMSセンサと速度を測定する3つの独立した地震計が装備されます。 フィルター MEMS センサとジオフォンを 2 ～ 4 kS/s (おそらく 4 kS/s) でサンプリングし、単純なカルマン フィルターを実行します。フィルターごとに 1 つの方向のみを調べるため、状態は加速度と速度の 2 つ、測定補正は 2 つだけになります。 このフィルターは方向ごとに 3 倍になります。 時間と最新情報 フィルタからの出力は、GSM/無線経由で基地局/サーバーに送信されます。これは、センサ上の特定のしきい値を下回る動きがあったときに実行できるため、フィルターを実行する必要はありません。 MCU このフィルターにはどの MCU をお勧めしますか?3 x 2 状態フィルターを 4 KHz で実行すると、センサ ボードに問題が生じますか? 敬具 ヨハン センサ・フュージョン Re: Recommended mcu for 2-state kalman filter <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、ヨハン。 デジタル センサの場合、実際のセンサ データ レートよりも高いレートでフィルターを実行しても大きな利点はありません。 そのため、アルゴリズムをセンサ ODR の近くで実行する必要がある場合があります。 センサの最大サポート速度よりも大幅に高い速度でセンサー データを読み取るとノイズが発生する可能性がありますが、それ以外はセンサーまたはセンサー ボードに問題が発生することはありません。ただし、MCU 側では、センサの ODR よりも高速に読み取るときに同じデータを単に返すトランザクションが追加されます。 フュージョンアルゴリズムと通信プロトコルをサポートするシステムの場合、ARM M4 コアベースの MCU で十分です。オプションとして、Kinetis FRDM-K22F MCU ボードを検討することもできます。

MPX5700GP 表面贴装？ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我有一位客户希望使用 MPX5700GP。 他们希望对部件进行表面贴装。 这可能吗？ 我在应用程序说明中注意到这可能是可行的。 您是否有可以提供的引导成形工具？ 你们有客户过去这样做的例子吗？ 压力传感器 传感平台 Re: MPX5700GP Surface Mount? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 嗨，亚当、 据我所知，我们没有或没有提供任何工具来重新定位引线框架。 我相信，大多数供应商构建和组装参考设计都可以制造出可以为客户做到这一点的夹具。 此致， 托马斯

MPX2010 センサを搭載したボードを構築しています。MPX2010 センサーを自動洗浄プロセスにかけることはできますか? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MPX2010 センサを搭載したボードを構築しています。できる MPX2010 センサを自動洗浄プロセスにかけるのですか? インテリジェント・センシング・フレームワーク Re: We are building a board with the MPX2010 sensor on it. Can we put the MPX2010 sensor through an automated wash process? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちはピーター、 Freescale では、ウェーブはんだ付け後にデバイスを水で洗浄するための推奨手順を提供していませんが、ポートに水が入らないように注意する必要があります。デバイスの P1 側には保護ジェルコーティングが施されています。ゲルコーティングはダイのアクティブ表面を保護しますが、ゲルが濡れるとデバイスの信頼性が損なわれる可能性があります。また、ゲルは濡れると特性が変化し、デバイスが仕様通りに動作しない場合があります。水洗浄プロセス中はポートを覆う必要があります。 圧力センサ デバイスをクリーニングする場合は、注意すべき特別な考慮事項がいくつかあります。センサー圧力開口部に入るクリーナーは、デバイスに悪影響を及ぼす可能性があります。特にデバイスをアルコールに浸すと悪影響が出ます。SO、部品のアクセス ホールをカプトン テープで密閉することが絶対に推奨されます。 超音波洗浄はワイヤボンド、ゲル、ダイヤフラムに損傷を与える可能性があるので注意してください。 この情報が皆様のお役に立てれば幸いです。 ご質問を誤解していた場合は、遠慮なくお知らせください。喜んでお手伝いさせていただきます。 素晴らしい一日をお過ごしください。 デビッド・ディアス。 ----------------------------------------------------------------------------------------------------------------------- 注: この投稿で質問が解決した場合は、「正解」ボタンをクリックしてください。ありがとう！ -----------------------------------------------------------------------------------------------------------------------

pressure sensor MPXV7002 temperature range The pressure sensor MPXV7002 has following temperature ranges: operating: TA +10...+60°C Do may cause permanent damage if operating at -10°C...+9°C? [yes or no] I can accept in my project that the error will increase outside of the compensated temperature range (+10...+60°C), but I cannot accept that the sensor will be permanent damaged, as stated in the datasheet (Table 4. Maximum Ratings, note [1]). Thank you for your help. Re: pressure sensor MPXV7002 temperature range Dear Andrea, yes, you can use the MPXV7002DP outside of the compensated temperature range (TA +10...+60°C), from -30°C to 100°C without damage. But as you mentioned the error is increased outside of the compensated area and we cannot guarantee how much. With Best Regards, Jozef

Xtrinsic pressure sensor / altimeter The relativelly new high-precision pressure sensor for altitude detection designed to help users further leverage advanced navigation capabilities and emerging location-based services such as GPS assist and e911. The Freescale Xtrinsic MPL3115A2 pressure sensor, based on micro-electromechanical systems (MEMS) technology, complements the accelerometers and magnetometers in the Xtrinsic portfolio to meet the growing demand for these types of components in smart mobile devices. The Xtrinsic MPL3115A2 smart digital pressure sensor processes pressure and temperature data locally, requiring fewer computations assigned to the applications processor and thereby reducing power significantly compared to systems using basic sensors directly managed by the host processor. The pressure sensor features optimal efficiency with a FIFO (first-in/first-out) memory buffer, a standby mode of 2 micro amps and a low-power mode of 8.5 micro amps for current consumption savings depending on conditions of the processor and output data rates chosen. The Xtrinsic MPL3115A2 pressure sensor is designed to address the increasing popularity of mobile location-based services used in sophisticated handsets by delivering 30 cm resolution, which enables the device to identify elevation at a granular level. For example, a phone could detect the exact floor a user is on within a high-rise building or a shopping mall, allowing location-based services to more accurately reflect immediate surroundings. Beyond the smart mobile device market, the Xtrinsic MPL3115A2 pressure sensor has many other potential applications, including tracking assets in business and industrial settings, providing precise locations in emergency search and rescue missions, forecasting climate changes in desktop weather stations and monitoring home cooling and heating systems. In addition, the sensor is ideal for medical applications, including respiratory equipment and health monitoring and detection systems that can help identify the location of patients within their homes or other environments. About the Xtrinsic MPL3115A2 pressure sensor Freescale’s Xtrinsic MPL3115A2 pressure sensor offers advanced accuracy and sampling rates combined with low power consumption to increase performance. The device provides barometric and altimetry pressure detection up to 30 cm of resolution and delivers a digital output in either meters or pascals, based on user preference. The MPL3115A2 sensor also includes embedded functions and user-programmable options, such as temperature compensation, with variable sampling rates up to 128 Hz. Smart features include autonomous data acquisition with two interruptions on thresholds detection. To enhance efficiency, the device regulates auto-wake and sleep modes (to avoid unnecessary use of power) and requires zero data processing for mobile devices and medical and security applications. Freescale has a history of providing long-term production support for its products. The MPL3115A2 device is part of the Freescale Product Longevity program, with a minimum of 15 years of expected supply. See www.freescale.com/productlongevity for details, terms and conditions. Availability, price and development support Sample quantities of the Xtrinsic MPL3115A2 pressure sensor are available now from Freescale. Production quantities and samples are already available from Freescale and its distribution partners starting at a suggested resale price of $1.43 (USD) in 10,000-piece quantities. The Freescale Sensor Toolbox offers hardware, software and accessories in a common platform for acceleration, magnetic, pressure and touch sensors. In addition, the DEMOSTBMPL3115A2 includes the Xtrinsic MPL3115A2 pressure sensor development board and a USB board for a suggested resale price of $99 (USD). Electrical specs for the MPL3115A2  pressure sensor include: Pressure Range: Calibrated: 50 kPa to 110 kPa Operational: 20 kPa to 110 kPa Equivalent Altitude Range: Calibrated: 5574.4m down to -698.3m Operational: 11774.9m down to -698.3m Temperature Range:  -40C to 85C Numerical Output Ranges: Pressure: -131072 to +131071.75 Pa Altitude: -32768m to 32767.9375m Temperature: -128C to 127.9375C Supply Voltage: 1.95V to 3.6V core 1.6V to 3.6V I/O Supply Current at 1 Hz update rate: 8.5 microamps (no oversampling) 265 microamps (128X oversampling) Standby Current: 2 microamps 400 kHz I 2 C digital interface Resolution: 20 bit output field implies (2 X 131072 Pa / 2 20 bits) = 0.25 Pa/LSB Noise: 1.5 Pa RMS at 128X oversample rate You may be wondering how the MPL3115A2 generates altitude estimates. It’s actually simple math: Altitude = K1 X (1 – (P/P0) K2 ) meters, where K1 = 44300.77 meters K2 = 0.190263 (unitless) P0 = 101325 Pascals http://www.engineeringtv.com/video/Freescale-Xtrinsic-MPL3115A2-Sm;Engineering-TV-Embedded-Videos

X/Y/Z translation I've got the sensor fusion toolbox running on both Windows and Android and connecting to a FRDM-KL25Z (I also have a FRDM-K22F but it doesn't seem to have the appropriate firmware available) with a FRDM-FXS-MULT2-B.  The orientation display works quite well.  What I really want to know, though, is whether it's possible to display translation.  I'd like to see how accurately it can show the board moving side to side or up and down while it's rotating.   I see that there's linear acceleration available in the display.  Am I just going to have to integrate that to get translational movement?   Thanks,   Scott SensorFusion Re: X/Y/Z translation Scott, The K22F will definitely work with the toolbox.  I'm not sure why the toolbox couldn't locate the binary for you.  If you'll shoot me an email at [email protected], I'll respond with the .bin you need.  This should be equivalent to the one you got by compiling the project under KDS. I actually find that Bluetooth works more reliably for me than the wired serial/USB, but you do have to have the appropriate Bluetooth drivers installed and you have to have previously paired with the device in the "Devices and Printers" page. Mike Re: X/Y/Z translation My protégé here, who has some experience with mechatronics (and has been in school a whole lot more recently than me), also just suggested those two.  And my ex is a university professor who teaches rigid body dynamics so I can probably get some input there as well. Last time I gave her what I thought would be a fairly straightforward problem it turned into a student's master's thesis.  I've been using the FRDM-KL25Z so far because I haven't been able to get it to work with the FRDM-K22F (which is much closer to the intended platform).  The Kinetis Interface Tool shows AGM01 - FRDM_K22F in the available firmware list but it says "No file at specified Firmware path" when I try to load it.  I did get the FSFK_K22F project to compile and load from KDS but I haven't looked at it closely and I'm not clear on whether that's supposed to work with the sensor toolbox. I've only been able to get it to work over Bluetooth to an Android device (despite trying 3 different BT interfaces, but that's probably the fault of Windows), and hacking it to work with the Bluetooth radio in the hoop seems like it'd be more trouble than it's worth.  If I can get the K22F code running I'll see if I can adapt that to write to mass storage.  Worst case... we've got a working FRDM-KL25Z and a bunch of duct tape. Thanks, Scott Re: X/Y/Z translation Scott, The fusion algorithm is optimized to make the best possible estimate of device orientation.  Once it has that, it is trival to subtract computed gravity from the measured acceleration.  The toolbox has plots for both.  The sensor readings are plotted on the "Sensors" tab, and the linear acceleration on the "Dynamics" tab.  There are a number of free Matlab clones on the web that you can use to post-process log files.  Scilab and GNU Octive come to mind. Regards, Mike Re: X/Y/Z translation I've already done some captures via Bluetooth (without the fusion algorithms) and I'll probably need to revisit that.  Can you tell me if the linear acceleration readings I'm seeing in the sensor fusion graphs include a centrifugal component, or is that removed by the algorithms using the gyro data? Seems like it would need to know the radius of the hoop for that, but I don't have a strong grasp of the underlying math of the fusion algorithms. A basic off-body move called an isolation has the hoop vertical and the center fixed while the hoop rotates.  A single gyro axis does a beautiful job of capturing this.  An iso pop is a similar move but at some point in the rotation the center of the hoop translates one hoop diameter in a straight line in the plane of the hoop and returns on the same line.  If the sensor fusion algorithms can cancel out the centrifugal part from the steady rotation then it seems like this sort of move would be easy to capture.  Many moves involve a constant rotation component and a quick excursion and return on some axis.  Slow drift of the hoop's calculated position shouldn't be a major concern and hoop dancers tend to move around anyway.  It's the hypocycloid motion that concerns me. The motion should look something like this: Hypocycloid Enter 200, 130, and 130 for the radii and click start and you'll see what I'm talking about. It looks like the motion of the sensor should briefly stall at multiple points for each hoop rotation.  There are a number of academic papers on hula hoop motion, but I get the feeling that they're mostly things drunk mathematicians write as gags for their department holiday parties. At the time of the initial design about two years ago the Bosch part was the only 9-axis sensor available. Freescale was expecting one out within a year.  I assume that one got cancelled?  My first prototypes used an FXOS8700 and Bosch BMG160.  Board space is limited (< 5/8" wide, < 1/2" for future versions) so I'm trying to keep the component count down.  Our own SMT line is just barely adequate for some of the tiny DFN or QFN parts and even with a CM doing most of these boards, inspection and rework are a pain. Also, board flex is hard to avoid in a hoop and hidden lead parts can be trouble.  The BMX055 is at the far end of the board from its attachment point to try to reduce that. That's good to know about the compromises with MEMS gyro and accelerometer construction.  The existing sensors have been good enough for things like determining when the hoop is not in use and can go to sleep and to create motion-reactive patterns in the LEDs.  I think the magnetometer is worth keeping because it allows for things like a simple odometer type measurement - you can just count zero-crossings to count revolutions.  Also, this is not a very cost-sensitive board.  The sensors account for less then 2% of the retail price.  It has a 120 MHz K22F and a minimum of 32 MB of external flash to work with and the effect on the power budget is minimal. Any sensor that I can cram in there that might potentially be useful down the line is worth considering.  I'd have capacitive touch sensors all the way around the circumference if I could figure out a cost effective way to do it. Since the sensor fusion toolbox doesn't show translation, can you suggest any reasonably simple simulation framework that might?  Simulink's probably a little out of our budget for this project. Thanks, Scott Re: X/Y/Z translation Scott, I'm not sure what the motion of a stationary point on a hula hoop looks like over time.  I think you would need to chart out the acceleration values over a number of rotations of the hoop to make sure that (from the sensor's perspective), you don't have some near constant accelerations.  Those could play havoc with the algorithms. Yes, you are welcome to use the algorithms with any vendor's sensors.  You will need to replace the drivers, and NXP's support is (of course) limited to use of NXP sensors.  NXP does not have a 9-axis sensor available. You probably don't need a mag for this application.   I would recommend the MMA8652 accel and the FXAS21002 gyro. I can't comment one way or the other on the device you mention.  I do know that use of a separate gyro can sometimes yield better performance than an integrated device, depending upon what design tradeoffs were or were not made with that integrated device.  Gyros like to have evacuated cavities for the MEMS, as gas can dampen motion of the MEMS masses, decreasing the gyro's Q factor (think power efficiency).  Conversely, consumer accels are typically not evacuated.  Gas damping for the accel is desirable to achieve an overdamped response curve.  It's something to consider as you evaluate options. Regards, Mike Re: X/Y/Z translation Thanks for the fast and informative response!  Before I trouble you any further I'll tell you what my application is and you can tell me if it's nuts to even try.  The board is in a hula hoop, so it mostly moves in what I guess would be a hypocycloid path.  Centrifugal forces can be around 6 Gs.  Not sure about linear acceleration, but there are a large variety of common moves, some fairly linear and some mostly rotational.  There are plenty of useful things that orientation sensing can let me do, but calculating linear movement, even if it has some drift, would be really handy.  The hoop's usually not going far from the hooper but there can be a lot going on Also, I believe the library will work with other brands of sensors, right?  We use a Bosch BMX055 in all of the existing devices.  I thought Freescale had a 9-axis sensor in the works but I can't find it now .  Is there a Freescale alternative to the BMX055, and will it work with the sensor fusion library? Thanks, Scott Re: X/Y/Z translation Scott, There is a build available for the K22F, but only under KDS.  You can also flash the board from the Sensor Fusion Toolbox if you just want to play with the standard build. Double integration of acceleration sounds great until you realize that any noise and/or offset in the sensor also get doubly integrated, and quickly explodes.  Of the two, post-board-mount offset is probably the worst culprit.   The algorithms in the toolbox correct for gyro offset and drift, but not accelerometer.  We haven't included position charts in the published version of the fusion toolbox because we know how disappointing the results will be. In the NEXT version under development, we plan to include routines to allow you to do a one-time calibration of the accelerometer that will dramatically improve accelerometer offsets/rotations before the signals are fed into the Kalman filter.  At that point, you've got a solution that should work well for positioning/navigation aid applications.   I believe Mark (the primary developer, and my partner in crime on the fusion library) plans to release the new version in late Q1.  If your product timeline needs something sooner, drop me an email at [email protected] and we can discuss options. Regards, Mike

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

need a pressure sensor that operates at -40C and stores at -51 was using MPXV5004DP MPXV5004DP This part was used in a legacy design. We inherited the design and noticed the part's spec didn't match our requirements (-40C operating and -51C storage). This sensor seemed to adequately worked when tested at those values but we couldn't knowingly leave an out-of-spec part in our design. We changed to another part that was rated for -40C operation but it actually works worse than the NXP sensor that isn't rated for it. We are trying to find alternatives. Does anyone know of differential pressure sensors that can operate in this environment: -40C to +51C operational -51C to +73C storage temp Max pressure > 4 psi needs to sense pressure in the 0-1 psi range (more is fine) Operates off of 5V SMT (small form factor such as the package of the current part) Re: need a pressure sensor that operates at -40C and stores at -51 was using MPXV5004DP Hi, Unfortunately, we do not have any data information for out-of-spec data, so we don’t have any performance information on the MPXV5004DP working at -40C. We can only recommend to use this sensor with a min operational temperature of 0C.   From the current portfolio, for the low pressure range, working at -40C temperature, I can only recommend the MPXV7007DP sensor: https://www.nxp.com/docs/en/data-sheet/MPXV7007.pdf Regards, Jose

圧力センサ MPXV7002GC6U を使用する場合、このセンサを SMT はんだ付けし、高水性クリーナーで洗浄しますか? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> SING 圧力センサー MPXV7002GC6U は SMT はんだ付けして高水性クリーナーで洗浄しできますか? Re: USING Pressure sensor MPXV7002GC6U can this sensor SMT soldered and be cleaned in a high aquious cleaner? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、ジョン。 残念ながら、センサーの圧力開口部にクリーナーが入ると、デバイスに悪影響を与える可能性があります。 したがって、部品のアクセス ホールをカプトン テープで密閉することが絶対に推奨されます。清掃する前にセンサにキャップを付けることもできます。該当する場合は、クリーニング プロセス中に、センサの背面にある小さな通気口もカプトン テープで覆う必要があります。 キャップは次のサプライヤーから入手できます。 http://www.stockcap.com/products.asp なお、超音波洗浄は、周波数によってワイヤボンドの相互接続が損傷する可能性があるため、推奨されません。 多くのお客様は、洗浄操作を行わないか、スプレーが直接センサー穴に入らない方向にスプレー洗浄を行っています。 詳細については、次のリンクから Freescale コミュニティのThreadをご覧ください: https://community.freescale.com/thread/307192 すてきな一日を、 ホセ・レイエス ----------------------------------------------------------------------------------------------------------------------- 注: この投稿で質問が解決した場合は、「正解」ボタンをクリックしてください。ありがとう！ -----------------------------------------------------------------------------------------------------------------------

MMA8652 対 MMA8451 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、 現在、新しいアクセラレータを選択中です。私は選択肢を 2 つのチップ、MMA8652 と MMA8451 に絞りました。一方が 12 ビットでもう一方が 14 ビットであり、パッケージが異なること以外は、複雑さの点ではどちらも同様であると考えるのは正しいでしょうか?つまり、一方のチップがもう一方のチップよりもプログラムや構成が容易というわけではないということです。 また、低電力バッテリー駆動製品の設計の観点からは、INT ピンをプルアップするほうがよいですか、それともプルダウンするほうがよいですか? 最後に、MMA8652 のデータシートを見ると、回路図にはチップの周囲に極性のあるコンデンサが示されていますが、これらは極性がないはずだと思います。私の考えは正しいでしょうか? ありがとうございます 加速度センサ Re: MMA8652 vs MMA8451 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、デビッド。 ご返信ありがとうございます。 念のため確認しますが、データシートでは 4 つのコンデンサすべてが有極性と記載されていますが、これはタイプミスだと思います。無極性コンデンサを4つ使用しても大丈夫でしょうか? ありがとうございます。 Re: MMA8652 vs MMA8451 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、 1. 基本的に、上記のデバイス間の主な違いは解像度とパッケージ オプションです。 2. ご指摘の複雑さに関しては、どちらのデバイスも I2C インターフェースを使用しています。 必要なデバイスをプログラムおよび構成するためのソフトウェアの例をここで見つけることができます。 3. INT ピンにプルアップまたはプルダウンを配置するかどうかは、アプリケーションによって異なります。 割り込みピンはプッシュプルまたはオープンドレインに設定でき、アクティブ ハイまたはアクティブ ローのいずれかにすることができます。オープン ドレイン設定の割り込みピンにプルアップ抵抗を使用する場合は、加速度センサをアクティブ Low に設定する必要があります。プルダウン抵抗を使用する場合は、割り込みピンをアクティブ ハイに設定する必要があります。これはレジスタ 0x2C (MMA8451、2、3Q) で行われます。 詳細については、アプリケーションノート AN4077 を参照してください。 AN4077 - MMA845xQ デザインチェックリストとボード実装ガイドライン 4. 最後に、BYP ピンのコンデンサは、残りのコンデンサがデカップリング コンデンサである間に内部レギュレータの安定性を保証するためにそこに配置する必要があります。 この情報が皆様のお役に立てれば幸いです。 ご質問を誤解していた場合は、遠慮なくお知らせください。喜んでお手伝いさせていただきます。 素晴らしい一日をお過ごしください。 デビッド・ディアス。

[Harman] [IPCF] IPCF4.3のサポートに関する議論 このThreadを追跡のためにコミュニティに持ち込みます - 添付の電子メールThreadを参照してください。 Harman は、IPCF デモでの core1 の起動プロセスにいくつかのエラーがあることを報告しています。現時点での想定では、これは起動時にコアに影響を与える PE デバッガー スクリプトに関連していると考えられます。PE スクリプトでは、これは期待どおりに開始されません (これは IPCF コンテキスト外でも当てはまることを確認できます)。 最高、 ブライアン IPCF Re: [Harman] [IPCF] Support for IPCF4.3 Discussion こんにちは、ブライアン。   Harman は、当社の参照例でサポートされていないカスタマイズされたブート フローを使用しており、フィードバックに基づくと、これは IPCF の問題でも RTD/プラットフォーム ドライバーに関連する問題でもないため、このトピックに CESS チームも関与させることを提案します。   また、この投稿にはメールは添付されていません。   よろしくお願いいたします。 ダニエル

Can gPTP run with GMAC0 instead of PFE_MAC on S32G3? Hi,  I have found an example application for gPTP but it uses PFE instead of GMAC. Later on I want to integrate PTP with LWIP based application which uses GMAC0. So I will need to either move LWIP to use PFE or gPTP to use GMAC0. I want to understand if gPTP with GMAC is already available to work out of box for S32G399, and if not what is the effort and success chance to port gPTP to GMAC for S32G399? Rizwan Re: Can gPTP run with GMAC0 instead of PFE_MAC on S32G3? Hi,rizwan_at_disru ptdotcom Thank you for contacting us. You can refer to the PFE_DRV_MCAL_S32G_RTM_1_6_0_D2505 for the LWIP PFE using.  Customer can access the timestamping on the GMAC, but does not supply gPTP stacks reference to customer. BR Joey Re: Can gPTP run with GMAC0 instead of PFE_MAC on S32G3? Hello @Joey_z  do you mean its possible to run gPTP on GMAC, but a reference port is not available for it from NXP? Best regards, Rizwan Re: Can gPTP run with GMAC0 instead of PFE_MAC on S32G3? hi，rizwan_at_disru ptdotcom The gPTP receives the ingress timestamp through the PFE SW driver and sends the egress timestamp. The gPtP package provided are for the PFE scenario. We did not provide relevant content or information to apply gPTP to GMAC. BR Joey

import project When I select Import Example from the SDK and choose another name, the project should be generated using my new name rather than the example name provided in the SDK. Re: import project Hello, did you check in cmakelist.txt ? Re: import project Hello @gtecaskari , Sorry that we’ve only just noticed your post, possibly due to a community system issue. Apologies for keeping you waiting. I just tested it on my side, and it seems that the issue has been resolved. Please check the attached screen recording. If you have any further questions or concerns, feel free to reach out to us anytime. Have a nice day. BR Celeste Re: import project I just checked cmakelist.txt, it still displays the original SDK name. I will create an internal ticket and report it to the MCUXPresso VSCode team. Thanks for your feedback.

PF8121 在 U-boot/Linux 中调整 低压差线性稳压器(LDO) 电压 我正试图通过 I2C 将 LDOOUT1 的输出电压从 3.3V（OTP 存储器中闪烁的值）调整到 1.8V。但是，当我更改 VLDO1_RUN 的值时，PMIC 会重置。我怀疑我触发了欠压事件，因为当我关闭 LDO1VMON_EN 时，PMIC 无法 RESET，但我无法弄清楚电压与哪个寄存器进行比较。我猜测它正在与 OTP_VLDO1 进行比较，但我似乎无法读取该寄存器的值，所以不能确定。 u-boot= > i2c md 0x08 0xCE 0x3 00ce：00 00 00... u-boot= > 必须禁用电压监测器才能更改电压轨的值似乎有点极端，我想问一下我是否遗漏了有关如何在 I2C 上正确交换 LDOOUT1 电压轨电压的信息？ Re: PF8121 adjusting LDO voltages in U-boot/Linux 您能提供帮助并在此分享您的原理图吗？ 还请告诉我 PF8121 的完整零件编号？ Re: PF8121 adjusting LDO voltages in U-boot/Linux PMIC 完整编号为 PC32PF8121A0EP。我还附上了我们设计中 PMIC 的图片。 Re: PF8121 adjusting LDO voltages in U-boot/Linux 对于您的示意图 1: Pin47 需要 2.2uF 去耦电容 2: LDOX 的输入电容为 1uF 3：48 号引脚接地。 4:21 引脚用 100K 上拉至 VDDIO 5：您可以尝试读取以下寄存器来确认故障。 我将关闭您的 00958417 号案件，请忽略其调查请求。 最后，请告诉我更新电路图后读取寄存器的结果。 Re: PF8121 adjusting LDO voltages in U-boot/Linux 1:PC32PF8121A0EP 是空白部分，这意味着我们无法识别真正的 OTP 部分，因为我认为它已经完成了 OTP。 2：我现在手上没有 PF8121，但我有 PF8100 我通过启用监视器和 UV/OV 状态对其进行了测试，然后调整 LDO1 值，没有发生 RESET 的情况。 因此，你可以直接更改 LDO1 的值，至少在我这里，直接更改 LDO1 的值已经没有问题了。

Unable to get Xtensa ISS license for HiFi4 DSP on i.MX 8M Plus Hello everyone, I am encountering a critical license error when trying to use the Xtensa Instruction Set Simulator (ISS) for HiFi4 DSP development on the i.MX 8M Plus platform. I would greatly appreciate any insights or guidance from the community. 1. The Error: When launching or debugging within the Xtensa IDE/Xplorer, the process fails with the following error: text *ERROR* Unable to get license(cexit exit requested from context '[ hifi4_mscale_v2_0_2_prod ] Xtensa ISS' ( rc = -1 )) *WARNING* fatal error(s) caught ( rc = -1 ) This prevents me from using the ISS for simulation and debugging. 2. My Development Environment: Target Chip: NXP i.MX 8M Plus (with Cadence HiFi4 DSP core). Xtensa Core: hifi4_mscale_v2_0_2_prod. Tool: Xtensa IDE / Xplorer (V10.1.11). Operating System: ( Windows 10). 3. What I Have Already Checked/Tried: To rule out common issues, I have verified: License Server: The FlexLM/LMGRD license server is running and accessible from my machine. License File: The license file contains a valid INCREMENT line for the Xtensa_ISS feature (or a similarly named feature) and has not expired. Environment Variables: I have set the correct license path environment variables (XTENSA_LICENSE_FILE, LM_LICENSE_FILE, etc.), pointing to the server (e.g., 27000@server_hostname). Despite these checks, the error persists. The return code rc = -1 seems to indicate a specific denial from the license server for this particular core/context. 4. My Specific Questions: Has anyone successfully set up the Xtensa ISS for the HiFi4 DSP (hifi4_mscale_v2_0_2_prod) on the i.MX 8M Plus platform? Are there any known specific configuration steps, environment variables, or license feature names required for this combination? Could there be a mismatch between the core configuration and the licensed features? Any advice on troubleshooting steps, correct license feature names, or configuration details would be extremely helpful. Thank you in advance for your support! Best regards, Re: Unable to get Xtensa ISS license for HiFi4 DSP on i.MX 8M Plus Sure, I have already installed the certificate. It seems to be a tricky question. Thank you for your reminder！ Re: Unable to get Xtensa ISS license for HiFi4 DSP on i.MX 8M Plus I wonder if installing a local license works for you? Go to https://tensilicatools.com/download/i-mx-8-hifi-4-sdk/ and Click on the link at the bottom of the page named 'Click to get a license key for imx8mplus sdk'. Otherwise, I think you need to contact Cadence support.