センサ、特にMMA8491QR1のFiT / MTBFレートを提供していますか？ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> センサ、特に MMA8491QR1 の FiT / MTBF レートを提供していますか?お客様と共有するにはどこにありますか? 加速度センサ Re: Do we offer FiT / MTBF rates for Sensors, especially MMA8491QR1 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、マイケル。 実際、NXP センサの FIT/MTBF レポートを提供することができます。 この場合、MMA8491QR1 に関して要求された資料を取得するために、 NXP TechSupport 経由で新しい CASE を作成できます。 素晴らしい一日をお過ごしください。 デビッド

Underpressure rating for MPL115A Hi, only overpressure is specified in the maximum ratings in all the datasheets I've seen for pressure sensors. I'm using the MPL115A sensor, and there it's specified 1000kPa overpressure as a maximum. What is the maximum underpressure for this component? Will it handle -0.5 Bar? Pressure Sensors Re: Underpressure rating for MPL115A Roger, you're welcome, please contact us back if you need further support. Have fun! Josh Re: Underpressure rating for MPL115A Thanks for your reply Joshvelle! I got the info I needed. I was unsure how you made these sensors. The reason why I asked the question was because I'm following a procedure to fill a tank with a specific gas (first to make vacuum, when filling it with gas). In the procedure it is said that the electronics inside could be exposed to pressure of -0,5Bar. I would assume they have used a gauge manometer when they made the procedure, to be able to determine the pressure value. - Roger Re: Underpressure rating for MPL115A Hello Roger, Absolute Pressure Sensors like the MPL3115A are designed to measure an external pressure relative to a zero–pressure reference (vacuum) sealed inside the reference chamber of the die during manufacture. You mentioned that you would expose the sensor to -50kPa (-0.5Bar), how did you measure that level? Did u use a gauge manometer? If that’s the gauge pressure level inside a chamber (tank or something similar), then you would be exposing the MPL115A to the atmospheric level minus 50kPa, which is around positive 50kPa (absolute pressure). Please let me know if I misunderstood your question. Hope it helps! Josh

About Hard iron offset compensation. Hi.. I have a question about Hard iron, Soft iron offset compensation.   if i understood exactly. To compensate Hard iron, I have to give a movement to magnetometer like picture. and This is the first and last time i will do To compensate Soft iron, the SW have to be executed using a Task( void MagCal_task(uint32_t task_init_data) ) and This is lasting 1 time/min until Power down     Question. 1. if I do compensation of Hard iron offset at power up, i don't need to compensate Hard iron offset again. is it right? 2. if it is right, After compensation of Hard iron, and  if I write the Hard offset variable to NVM Before Power down , I don't need to compensate Hard iron offset forever?( even after board rebooting)   Thank you SensorFusion Re: About Hard iron offset compensation. Set the thisMagCal.iValidMagCal to a non-zero (C true) value after reading in the calibration from flash so that the software knows to apply the hard and soft iron correction. In the V5 code we use 0 (C false) to denote no calibration and 4, 7, 10 (C true) to denote a valid calibration and the actual solver used for that calibration. Re: About Hard iron offset compensation. Hi. Thank you for quick reply. I tried to store the values of  fV[], finvW[][], fFitErrorpc, gyro offset before Power down. and I read them on power up. I think that the above process will help me not to do rotation of board for calibration. but every time I power up, I should rotate the board for the same prior magnetometer yaw value. Without rotation, the value is differ from the previous value badly so should I store another value? for example, Magbuffer[] or all Magcalib structure?? - my Environment - Step 1. Rotating a board for Mag calibration. and Waiting until stabilization of Roll, pitch, yaw. Step 2. Power down,( Until next power up, the board is same place and The environment is not changed.) Step 3. Power up. and it have to have a same Roll, Pitch, Yaw ( Error is not considered ) it is important because  I have to fix a development kit not to move from the second Power up Please Give an advice to me. Thank you. Re: About Hard iron offset compensation. Both the hard iron and soft iron use measurements in the magnetic buffer. The more sophisticated 7 and 10 element algorithms which do fit the soft iron simply require more measurements than the 4 element algorithm. It's like having just 5 noisy points on a graph. Fitting a straight to 5 points will be ok, fitting a quadratic will be more error prone and fitting a cubic even more error prone. So to get a quick calibration as soon as possible we do the four element calibration which fixes the main magnetic inteference which is the hard iron offset. Then when we have more measurements we move to the more sophsticated solvers and fix the much small soft iron terms. Magnetometers and magnetic sensors are sensitive to temperature which is the reason for the continual background calibration which is for both hard and soft iron. Here's what you need to store in NVM: fV[], finvW[][], fFitErrorpc and read in on power up. I use a header byte which has a value different from the 0xFF that would be read from erased NVM so I can distinguish whether the NVM is erased or has data. I do not store the magnetic buffer. That gives an immediate power on calibration and no measurements in the magnetic buffer. Then as soon as enough measurements are available I still perform the  standard 4, 7, 10 element calibration as more measurements come into the magnetic buffer. The reason is that the magnetic calibration could have resulted from a different temperature and therefore be erroneous. So the only change should in the power on initialization in function fInitMagCalibration where you need to add a test for the presence of stored coefficients and then copy then in if they are available. Re: About Hard iron offset compensation. Hi Mike, I noticed the following issue: I have saved 10-point calibration data and use them after the system power on/RESET. Then it keep running calibration routine. I found that the heading is not as good as the saved data. I checked  that it runs 4-point calibration data in real-time now. I will becomes good again when it is running in 10-point again. How can I use 10-point data always to make the heading good enough? Thanks, Christie Re: About Hard iron offset compensation. Dav, You are incorrect.  BOTH hard and soft iron effects are computed via the MagCal task.  The equations are such that we optimize the total set of coefficients each time MagCal is run, including both the 3x3 inverse soft iron matrix and the 3x1 hard iron offset. Some magnetic sensors (ours included) have a non-negligible temperature coefficient, which also can affect these coefficients.  So for mobile applications we recommend that magnetic calibration be run continuously as a background task.  This negates the effects of temperature. Applications where this is not possible need to be addressed on a case-by-case basis. FYI, Version 6.00 of the fusion library (currently under development) will add the capability to cache current coefficients to MCU flash so that the device boots with previously computed coefficients.  These will then be replaced as soon as enough data points are available to compute updated numbers.  Some users of the library are already doing this, and we've decided to add generic functions to make it easier going forward.  Look for this version in 1Q2016. Regards, Mike

sensor type MPXH6300A for sensor type MPXH6300A is there an option for a more media resistant gel ? current device has a florosilicone type gel Pressure Sensors Re: sensor type MPXH6300A Tomas,  In the "as received" condition there are a mix of cloudy and the clear gel on the same reel....does the cloudy appearance impact performance or is this an acceptable condition ? Re: sensor type MPXH6300A Hi Phil, No, there is not. There are only the MPXHZ6250A and MPXHZ6400A series available with the media resistant gel. Best regards, Tomas PS: If my answer helps to solve your question, please mark it as "Correct". Thank you.

FXPS7140P4 un-programmed default PSI5 communication Hi Can I communicate with FXPS7140P4 sensor with default setting? or it has to be programmed through PSI5 first in order to receive sensor data from it? If I can communicate with default setting then what is the default mode? asynchronous, synchronous, 10bit/16bit data, parity or CRC ? Regards, J Pressure Sensors Re: FXPS7140P4 un-programmed default PSI5 communication Hi Joe, Yes, but it can be shared under NDA only. If you have not signed the NDA with NXP yet, please create a standard case for my colleagues who are in charge of the NDA process and can eventually help you with that. Best regards, Tomas Re: FXPS7140P4 un-programmed default PSI5 communication Hi @TomasVaverka : Hope you are doing good. Is the official datasheet for FXPS7140P4 released yet ? We are waiting for it. You mentioned about the release date is around end of January 2022.  Best Regards, Joe Re: FXPS7140P4 un-programmed default PSI5 communication Hi Thomas, I got one more question for you. Can I set value 0x1A to register $25. Especially, the DATA_EXT bit, it allows us to read data range between -480 to +480 LSB according to the draft document(negative 16% to positive 16% for relative pressure). I have tried writing value 0x8A to register $25, it is working fine but again according to the draft document, it only allows us to read -102 to +307 LSB (which I can only read 3% of negative pressure change and 10% of positive pressure change ). Regards, Joe Re: FXPS7140P4 un-programmed default PSI5 communication Hi Tomas, Thank you for the detailed explanation and the pressure range again. With your word, I can rest assured that there is not thing bad happening during the programming. It was me changing the value in register $40 which resulted in OTP MEM fault. Although I have broken some samples here, you save me some samples that I was going to test. Thank you. I will look forward to the release of the document for this pressure sensor. Best Regards, Joe Re: FXPS7140P4 un-programmed default PSI5 communication Hi Joe, The pressure range cannot be changed in this device otherwise it will set the errors. The intension initially was to be able to change the range if a large opportunity presented itself and this can be evaluated on a case by case bases. With this said $40, range has been revised to "Reserved". This will be updated in a future release of the datasheet which I am guessing should be ready in the end of January 22. The datasheet will have the following for this register: The pressure range should be 40 kPa to 140 kPa. Best regards, Tomas Re: FXPS7140P4 un-programmed default PSI5 communication Hi Thomas,  We got a few samples here from local NXP, I cannot seem to understand the register 0x40. Whenever I set USER RANGE[1:0] bit to 0x01, and programed the chip with the rest of register setting indicated by programming manual. It resulted in MEMTEMP_ERR and U_OTP_ERR, which I cannot read sensor value. (would always read 0x1EB). However, if we set the USER RANGE[1:0] to 0x00 with the same setting of the other registers (again specified by programming manual and not modifying the 0x16 COMM bit), it would read pressure value just fine, and there is no MEMTEMP_ERR & U_OTP_ERR bits set. (the voltage setting and sync pulse width all conform to the sensor manual ) As our manual dose not elaborate on USER RANGE bit, we just want to confirm that the setting of 0x00 for register 0x40 can read the range as document specified 50kPA to 126 kPA for sensor FXPS7140P4. Regards, Joe Re: FXPS7140P4 un-programmed default PSI5 communication Hi Tomas, Thanks for your reply Regards, Joe Re: FXPS7140P4 un-programmed default PSI5 communication Hi Joe, All registers are set to 0 for any PSI5 configuration. So register 25 is 00 (PSI5_CFG). If you have a PSI5 device (FXPS7140P4), then you have to use PSI5 to use/comm to the device. With this said, the COMMTYPE bit field is set to 1 in register 16. If you try to changes this, it will produce an error so caution must be taken if you want do any over writes to the UF2 region in that this should be masked. Best regards, Tomas

FXAS21002 gyro group delay versus ODR and lowpass filter setting Hi, I would like to know the group delay of the FXAS21002C for a given ODR (output data rate) and lowpass filter shown in Table 33 on page 39 of the data sheet.  For example, at 400Hz ODR, Table 33 has the following entries for the lowpass filter bandwidth: Table 33. FXAS21002C LPF Cutoff Frequency BW ODR = 400Hz 0b00 128 0b01 64 0b1x 32 The group delay likely increases by 2x for each 2x decrease in the LPF (lowpass filter) cutoff frequency. Also the group delay likely increases by 2x for each 2x decrease in the ODR setting.  Therefore, the group delay for any value in Table 33 would be highly useful. If the z-transform of the lowpass filter and the sample rate before decimation is known, that would also answer the question.  For example, if a moving average filter is used as the lowpass filter (sometimes called a SINC filter), knowing the sample rate and filter length, prior to decimation to the ODR, would allow the group delay to be calculated. Thanks in advance for your replies. Jon Gyroscope Re: FXAS21002 gyro group delay versus ODR and lowpass filter setting Thank you for the information.  That is very helpful. Jon Re: FXAS21002 gyro group delay versus ODR and lowpass filter setting Hi Jon, Here is the response from the Design team, sorry it has taken so long. The LPF of the FXAS21002C is a CIC (cascaded integrator-comb) decimator of 2 nd order. It has the advantage of down-sampling and filtering lower than the Nyquist rate. This is not a simple moving average filter or sinc. The group delay of this filter is “N*M-1” samples with N the decimation factor and M the differential delay. - Knowing that the ADC run at 6400Hz, the decimation factor goes from 8x to 512x (ODR from 6400/800 to 6400/12.5). - The differential delay is either 1, 2 or 4 for the BW = 00, 01 or 0x respectively. Thus, group delay = (6400/ODR*M-1)*156.25us. I hope it helps. Regards, Tomas Re: FXAS21002 gyro group delay versus ODR and lowpass filter setting Hi Jon, I just want to inform you that I have requested assistance from our Apps/Design team to clarify your question. I will update this thread once I have their answer. Regards, Tomas

FXLS896xAF AN12004 - 'No Motion' vs 'Freefall' In the AN12004 Application Note, the basis for detecting  both 'No Motion' (3.2) and  'Freefall' (3.4) is that all 3 axes are within some threshold. So that's the key to distinguishing 'No Motion' and  'Freefall' - as they're both detected on the same basis? Accelerometers Re: FXLS896xAF AN12004 - 'No Motion' vs 'Freefall' Still wondering about the significance of Data[n]-Data[n-1] vs Absolute reference? Also, rather than using the 'AND' logic of all 3 axes, what would be the pros/cons of just using the VECM (vector magnitude) ? Re: FXLS896xAF AN12004 - 'No Motion' vs 'Freefall' So you're just assuming that a "brief" period of "no motion" must be "freefall" ? The other difference is that the "no motion" example uses the Data[n]-Data[n-1] reference update mode, whereas "freefall" uses the Absolute mode. What's the significance in that? Re: FXLS896xAF AN12004 - 'No Motion' vs 'Freefall' Hello Andrew, The key to distinguishing between the two lies in the setting of the debounce time (2.55s vs. 100ms). And yes, we also recommend to use slightly different threshold values (±100mg vs. ±200mg). BR, Tomas

SGS for MPX2300DT1 Hi could you help to provide the sgs for MPX2300DT1,Thanks.my email is  caesar.song@avnet.con  Re: SGS for MPX2300DT1 Hi Caesar, In order to get the requested SGS report, please create a standard support request.   Thank you for your understanding!   Best regards, Tomas

Usage of register pointer read and write in G-Sensor (MMA690xKQ) Hello, I am using High Accuracy Low g Inertial Sensor (MMA690xKQ) in my project. I have read the specification but I am unable to find the use case of Register Pointer Read and Register Pointer Write in Table 3.4, 3.5, 3.6, 3.7. Kindly let me know how to use Register Pointer Read and Register Pointer Write and also the meaning of bits A[7:0] is the same tables. Accelerometers Re: Usage of register pointer read and write in G-Sensor (MMA690xKQ) Hello For any register reading I am getting E6 or FE response can you please help me on exact response clock is good and CS pin also ok Re: Usage of register pointer read and write in G-Sensor (MMA690xKQ) Hello register address: e       register address:14     message transmitted STATUS is 0xe0-0x00-0x00-0x00 E0 00 STATUS is 0xe0-0x00-0x00-0x00 serialNo - 0:e0 printf device status register register address:1   register address:30    message transmitted STATUS is 0xff-0xff-0x00-0x00 FF FF STATUS is 0xff-0xff-0x00-0x00 serialNo - 0:ff printf device status register register address:0   register address:20    message transmitted STATUS is 0xe6-0x00-0x00-0x00 E6 00 STATUS is 0xe6-0x00-0x00-0x00 serialNo - 0:e6 this is the response I am getting Please help me on the exact response Re: Usage of register pointer read and write in G-Sensor (MMA690xKQ) Hello Manojkumar, The SPI protocol for the MMA690x devices does not allow for transmission of both a register address and register data in the same command.  The address must be set by a previous command.  This is the purpose of the Register Pointer Write command.  The Register Pointer is the address at which data will be read from or written to when a Register Data Write or Register Data Read is executed.  So the normal sequence for a register read or a register write will take at least 2 commands:   Register Read: Send a “Register Pointer Write” command to set the pointer to the register address to be read Send a “Register Data Read” command to retrieve the data from the register pointed to Register Write: Send a “Register Pointer Write” command to set the pointer to the register address to be read Send a “Register Data Read” command to retrieve the data from the register pointed to   Note that the MISO response for each MOSI command will come on the subsequent transfer.  As shown in the image below. Here are a few examples. Read Register $10 (DEVSTAT) Register Pointer Write to $10 MOSI                    = 0x1410 Expected MISO  = 0x0800 Register Data Read MOSI                    = 0x2000 Expected MISO  = 0x1000              (assumes no flags set in DEVSTAT) Write 0x01 to Register $0E (Enable Positive Self-Test) Register Pointer Write to $0E MOSI                    = 0x140E Expected MISO  = 0x0800 Register Data Write MOSI                    = 0x3001 Expected MISO  = 0x180E              (includes address echo) Register Data Read to Confirm MOSI                    = 0x2000 Expected MISO  = 0x1401 I hope this is clear. Best regards, Tomas

MMA8451Q Int not clearing Description:  I'm using one of your MMA8451 3axis devices with a Nordic Semi nrf51822.  I'm using the built-in function to detect a tap and a flip.  The tap is directed to INT1 and the flip is directed to INT2.  I can currently detect both interrupts and distinguish between them based on which GPIO pin on the nrf51822 is driven.  The GPIO pins are configured as pull-up's. I've been using int1 and the tap detection for a while with no problem.  I added the flip detection to INT2 today and now, occasionally, after the int serv. routine is triggered one, or the other (depending on which was triggered) will not reset after reading the appropriate status register.  I do read both status registers each time to be safe - PL_STATUS_REG and PULSE_SRC_REG - and the values look correct. I'm measuring the INT pin voltages and once this occurs either INT1 or INT2 stays low and no more interrupts are generated by the accel until a power cycle. Can you help with some suggestions as to what I'm doing wrong? The init routing to set up the accel is in the attached file after the pre-processor. void accel_init(void) {     uint8_t regValue, newRegValue;     turn_off_accel();     newRegValue = 0x10;     regValue = twi_read_register(0x3A, 0x2A);     twi_write_register(0x3A, 0x2A, (regValue & 0xC7) | 0x10);     twi_write_register(0x3A, 0x21, (0x00 | 0 << 6 | 0 << 5 | 1 << 4 | 0 << 3 | 1 << 2 | 0 << 1 | 1 << 0));     uint8_t ac = ((uint8_t)((double)1.575/0.063));     twi_write_register(0x3A, 0x23, ((uint8_t)((double)1.575/0.063)));     twi_write_register(0x3A, 0x24, ((uint8_t)((double)1.575/0.063)));     twi_write_register(0x3A, 0x25, ((uint8_t)((double)2.65/0.063)));     twi_write_register(0x3A, 0x26, ((uint8_t)(50 / 2.5)));     twi_write_register(0x3A,0x27, ((uint8_t)(140 / 5.0)));     twi_write_register(0x3A, 0x2A, 0x10 | 0 << 2);     twi_write_register(0x3A, 0x2B, (0x00 | 1 << 0 | 1 << 3 | 1 << 1 | 1 << 4 | 0 << 2));     twi_write_register(0x3A, 0x2C, 0x00);     twi_write_register(0x3A, 0x2D, (0x00 | 0 << 2 | 1 << 3 | 1 << 4));     twi_write_register(0x3A, 0x2E, (0x00 | 0 << 2 | 1 << 3 | 0 << 4));     twi_write_register(0x3A, 0x11, 0x40);     twi_write_register(0x3A, 0x13, 0xC0);     twi_write_register(0x3A, 0x14, (0x07 << 3 | 0x01));     twi_write_register(0x3A, 0x12, ((uint8_t)(100 / 5.0))); Accelerometers

What is the proper method for retrieving samples from the CRTouch using the FIFO? Hello, After reading the CRTouch Datasheet, I am not sure how the FIFO buffer gets read using interrupts.  I understand that the FIFO watermark can trigger an interrupt to the CPU. But, once the FIFO interrupt has occurred and you send the command to read the FIFO buffer; what is the method for reading the FIFO so that the CPU doesn't run ahead of the 100Kbs rate of the CRTouch?  I would like to use an interrupt method, but it looks like I have to use a polling method, is that correct? The docs don't give a description of reading the FIFO.  Maybe I'm missing something basic... my apologies in advance. Duane Touch Sensors Re: What is the proper method for retrieving samples from the CRTouch using the FIFO? Hi Duane Owens, You are correct, unfortunately it is not possible to read the FIFO buffer using Interrupt method, you would need to use a polling method to read it. Have a great day, Jose Reyes ----------------------------------------------------------------------------------------------------------------------- Note: If this post answers your question, please click the Correct Answer button. Thank you! -----------------------------------------------------------------------------------------------------------------------

MMA8652 Z axis MSB is showing as being maxed out About this problem, I found it in this community improved by PCN 15581. I want to know, ・Whether it is an improved device from the product year/week marking on the IC. ・Result of analysis by NXP. Cause, improvement, details of this problem, Re: MMA8652 Z axis MSB is showing as being maxed out Dear Takeshi-san, This issue is being discussed internally with Norihiro-san through the Case #00114001. Best regards, Tomas

MPX5010 vs MPX2010 Dear Freescale, I currently use MPX2010 in a dual port configuration.  I am looking to move to the MPX5010 with the integrated amplifier but had a few questions: 1.) Is the sensor the same in the MPX2010 and the MPX5010? 2.) Are there any application recommendations for interfacing to the MPX5010? Sincerely, Jason Pressure Sensors Sensing Platforms Re: MPX5010 vs MPX2010 Hi Jason Haedt, Answering to your questions: It is a very similar sensor with the difference (that you already noticed) that the MPX5010 is on-chip amplified, but both have the same pressure range and general functionality. It is actually very simple to interface the MPX5010 since it’s already amplified, temperature compensated and calibrated, so the only think you need to add are just a few capacitors (as seen on Figure 3 of the datasheet) and the signal goes directly to your mcu’s ADC. Click here to find all the documentation available for the MPX5010. Have a great day, Jose Reyes ----------------------------------------------------------------------------------------------------------------------- Note: If this post answers your question, please click the Correct Answer button. Thank you! -----------------------------------------------------------------------------------------------------------------------

MPX5010 与 MPX2010 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 亲爱的飞思卡尔 我目前使用的是双端口配置的 MPX2010。 我想改用带集成放大器的 MPX5010，但有几个问题： 1.)MPX2010 和 MPX5010 的传感器是否相同？ 2.)是否有与 MPX5010 接口的应用建议？ 此致敬礼 杰森 压力传感器 传感平台 Re: MPX5010 vs MPX2010 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好，杰森-海特、 回答您的问题： MPX5010 和 MPX5010 是非常相似的传感器，不同之处（您已经注意到了）在于 MPX5010 采用了片上放大技术，但两者的压力范围和一般功能相同。 实际上，接口 MPX5010 非常简单，因为它已经过放大、温度补偿和校准，因此您唯一需要添加的只是几个电容（如数据表的图 3 所示），信号会直接传送到您的 mcu 的 ADC。 单击此处查找 MPX5010 的所有可用文档。 祝您愉快， 何塞-雷耶斯 ----------------------------------------------------------------------------------------------------------------------- 注：如果本帖回答了您的问题，请点击正确答案按钮。Thank you! -----------------------------------------------------------------------------------------------------------------------

MMA8453 Detect false double tap Hi, MMA8453 is placed inside a device which a person can carry while traveling. We've enabled double tap feature which the person can use in case of emergency. The problem is we're getting false double taps when the vehicle is moving. Configuration: REG_PULSE_CFG 0x2A REG_PULSE_THSX 0x20 REG_PULSE_THSY 0x20 REG_PULSE_THSZ 0x40 REG_PULSE_TMLT 0x18 REG_PULSE_LTCY 0x28 REG_PULSE_WIND 0x3C Thanks, Prakash Re: MMA8453 Detect false double tap Hi Prakash, I have never heard of a similar problem and it is hard to provide any specific setting that would eliminate such unwanted triggers. My only recommendation is to adjust the threshold and duration values by testing it in a vehicle. Best regards, Tomas

Using a MMA8451 FIFO Interrupt I am using the 8451 in the following configuration. - ODR 800 Hz 4G scale - I2C at 400kHz rate - Sleep modes disabled. always in active mode -FIFO in Circular Buffer mode. -The only interrupt configured is "FIFO full" vectored to the Int1 pin. That is No watermarks or pulse/landscape/freefall detection enabled. - On the interrupt I flush the FIFO 14 bit data...192 bytes. - For speed of operation and hence current consumption I do not read either:    (a)The status register at 0x00. as I can guarantee I will service the interrupt and read out some data before the next sample is done 1.25mS later.    (b) The Interrupt source register at 0x0C as I only have one interrupt source. This appears to works OK. The interrupt on INT1 pin goes high approximately half way through the 5.2mS FIFO flush However it is not clear from the datasheet that for correct operation you must  read the interrupt source register to clear it. Question: Must I clear the interrupt source register by reading it for correct operation regards John Campbell Re: Using a MMA8451 FIFO Interrupt Tomas, Thanks very much for your prompt response to this and my other question. This is a relief as I release my software on Wednesday for a major production run for an automotive client. Best regards and thanks again Johnc Re: Using a MMA8451 FIFO Interrupt Hi John, Yes, there is no need to read the INT_SOURCE register (0x0C), the SRC_FIFO bit is cleared and consequently the INT1 pin deasserted by reading all the X, Y, Z output data registers (0x01 – 0x06). Best regards, Tomas

FRDM-KW40Z 上的传感器融合库 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 是否计划在 FRDM-KW40Z 上支持传感器融合库？ 如果是，时间框架是什么？ 传感器融合 Re: Sensor Fusion Library on the FRDM-KW40Z <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 马修 目前还没有任何计划。 我们的总体策略是甚至不尝试为所有 Freedom板提供固定解决方案。相反，我们的重点是为每一类 MCU 提供有代表性的项目以及非常详细的文档，以便为客户提供足够的信息，轻松地移植到他们所选择的任何 MCU。 由于 KW40Z 集成了 BLE，我们将来可能会重新审视它，但不会是今年。 我认为最大的问题不是移植传感器融合，而是为 BLE 改造我们的工具包。 我要提一下，我们即将向这个社区发布该库 5.00 版的预版本。因此，请密切关注本频道：smileywink： Mike

MMA8652 パルスフィルタリング設定 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MMA8652 でパルス検出を設定しようとしていますが、データシートに曖昧な点が見つかりました。 レジスタ 0x0F HP_FILTER_CUTOFF の説明によると、ビット 5 が設定されている場合はパルスプロセッシング用のハイパス フィルタがバイパスされ、ビット 4 が設定されている場合はローパス フィルタが有効になります。ビット 5 が設定され、ビット 4 がクリアされると、生のセンサ データがパルス プロセッシングに使用されると推測できます。ただし、ビット 5 がクリアされ、ビット 4 が設定されている場合、何が起こるかは明らかではありません。これは単に無効な状態なのでしょうか、それとも HPF または LPF のいずれかが優先されるのでしょうか? 加速度センサ Re: MMA8652 Pulse Filtering Settings <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、 役に立つアプリケーション ノートがありますが、これは MMA865x に類似した MMA845x ファミリ用に設計されていますが、一部のレジスタが異なる可能性があることに留意してください。 このドキュメントは次のリンクにあります: https://www.nxp.com/docs/en/application-note/AN4072.pdf すてきな一日を、 ホセ --------------------------------------------------------------------------------- 注記： - この投稿があなたの質問への回答である場合は、「正解としてマーク」ボタンをクリックしてください。ありがとう！ - スレッドは最後の投稿から7週間フォローされます。それ以降の返信は無視されます。 後ほど関連する質問がある場合は、新しいスレッドを開いて、閉じたスレッドを参照してください。 --------------------------------------------------------------------------------- Re: MMA8652 Pulse Filtering Settings <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ありがとうございます。アーキテクチャ図がなかったので、デバイス内に LPF と HPF の両方に使用されている単一の LPF があると想定していました。 この質問の答えは既にわかっていると思いますが、脈拍検出について説明しているアプリノートはありますか?データシートに記載されている「データ操作と基本設定」ドキュメントについては承知していますが、実際にはパルス検出についてはまったく説明されていません。 Re: MMA8652 Pulse Filtering Settings <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、 パルス検出は、ハイパス フィルターとローパス フィルターの両方を通過するように設定できます。これにより、HPF カットオフ周波数のカスタマイズにより、よりカスタマイズ可能で調整可能なパルス検出方式が提供されます。 ご質問にお答えすると、ビット 5 が設定され、ビット 4 がクリアされている場合、生のセンサ データがパルス プロセッシングに使用されます。 ビット 5 がクリアされ、ビット 4 が設定されている場合、ハイパス フィルターとローパス フィルターの両方が有効になります。この場合、オフセットと加速度データの緩やかな変化を除去するために、ハイパス フィルターのカットオフ周波数 (ビット 0 とビット 1) を設定できます。 ただし、単純なパルス検出の場合、ローパス フィルターを有効にし、ハイパス フィルターをバイパスすることをお勧めします。SO、ビット 4 Pulse_LPF_EN を ('1') に設定し、ビット 5 Pulse_HPF_BYP を ('1') に設定します。 * ハイパス フィルターがバイパスされると、機能はモーション検出と同様に動作します。 すてきな一日を、 ホセ --------------------------------------------------------------------------------- 注記： - この投稿があなたの質問への回答である場合は、「正解としてマーク」ボタンをクリックしてください。ありがとう！ - スレッドは最後の投稿から7週間フォローされます。それ以降の返信は無視されます。 後ほど関連する質問がある場合は、新しいスレッドを開いて、閉じたスレッドを参照してください。 ---------------------------------------------------------------------------------

Sensor Fusion Library on the FRDM-KW40Z Are there plans to support the Sensor Fusion Library on the FRDM-KW40Z?  If so, what is the timeframe? SensorFusion Re: Sensor Fusion Library on the FRDM-KW40Z Matthew, There are no plans in place at this time.  Our general strategy is to not even attempt to provide canned solutions for all Freedom boards.  Instead, our focus is on providing representative projects for each class of MCU as well as very detailed documentation to provide customers enough information to easily port to ANY MCU of their choice.  We may revisit the KW40Z in the future because of its integrated BLE, but it won't be this year.  The biggest issue I see there is not porting the sensor fusion, but retrofitting our toolkits for BLE. I will mention that we ARE about to post to this community a pre-release of Version 5.00 of the library.  So keep your eyes glued to this channel Mike

FRDM-KL25Zを使用した転倒検知と歩数カウント <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> さて、私は Freescale FRDM-KL25Z 開発プラットフォームに取り組んでいますが、次のサンプル コードを入手できません。 - 落下時にLEDを点滅させる方法（基本的には落下検出） - 人体に装着して歩数を数える方法。 誰かこの件について助けてくれませんか?本当に緊急なんです… よろしくお願いします。 センサ・フュージョン Re: Fall Detection and Step Count using FRDM-KL25Z <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、メーガンさん。 FRDM-KL25Z は、MMA8451 加速度センサを搭載したマイクロコントローラ ボードです。 自由落下のようなイベントをキャプチャするには、自由落下を検出し、MCU にイベントを通知する割り込みを生成するように、レジスタに設定を書き込むことによって、I2C 経由で加速度計をプログラムする必要があります。その後、MCU はオンボード LED をオンにして表示することができます。以下の手順に従って例を構築します。 さて、歩数を検出するには、加速度センサのデータを読み取って歩数を計算できる歩数計アルゴリズムが必要になります。歩数検出には、以下に示す例を使用できます。 https://mcuxpresso.nxp.com/をご覧ください--> ボードの選択 --> ボード --> Kinetis --> FRDM-KL25Z --> MCUXpresso SDK のビルド --> ソフトウェア コンポーネント ISSDK を追加し、SDK アーカイブをビルドしてダウンロードします。 自由落下検出の場合、サンプル boards\frdmkl25z\issdk_examples\センサ\mma8451q\mma845x_interrupt を開始点として使用し、アプリケーションノートAN4070.pdfに従って自由落下検出サンプルを作成します。 歩数計の場合、サンプル boards\frdmkl25z\issdk_examples\algorithms\pedometer\pedometer_mma8451 が目的にかなうはずです。