こんにちは。FXOS8700CQ 加速度センサは FIFO モードを使用するとデータ解像度が低下するかどうかご存知ですか? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 他のタイプの加速度センサではこれが問題になることに気づきました。できるだけ高い精度を求めているので、他にお勧めできる製品があれば教えていただけるとありがたいです。 ありがとうございます。 Re: Hello, do you know if your FXOS8700CQ accelerometer decreases its data resolution when using the FIFO mode? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、アレックス。 他社製品についてはコメントできませんが、選択した FIFO モードに関わらず解像度に制限はありません。これは、FXOS8700CQ (加速度センサ + マグネトマー) だけでなく、MMA8451Q と FXLS8471Q (加速度センサのみ) にも適用されます。 よろしくお願いいたします。 トーマス Re: Hello, do you know if your FXOS8700CQ accelerometer decreases its data resolution when using the FIFO mode? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、トーマス。 私が見つけたこの問題は他社の製品に関係するものなので、FXO を購入したいと思っています。製品の詳細が必要な場合は、お送りします。正確な言葉は「FIFOが使用される場合、通常モードでは10ビットのデータ解像度があり、低電力モードでは8ビットのデータ解像度があります（FIFOが使用されていない場合は12ビットのデータ解像度と比較して）。 使用済み）"。ADC のデータ解像度は、通常モードでは 16 ビットです。間違っているかも知れませんが、それが私の理解です。 ご返信ありがとうございます Re: Hello, do you know if your FXOS8700CQ accelerometer decreases its data resolution when using the FIFO mode? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、アレックス。 そのような問題については聞いたことがありません。14 ビット データまたは 8 ビット データのいずれかにアクセスできる必要があります。 調査結果についてもう少し詳しく説明していただけますか?使用している FIFO モードとテスト設定は何ですか? よろしくお願いいたします。 トーマス

attitude under shake condition in hand Hello! I have tested the sensor fusion library 4.2 and 5.0 all. My  sensor is ADIS16445,a 6-axis with gyro + acc. I have tuned  parameters according to my sensor noise in fusion.h.   1.Bu all this two libraries don't performance well in continuous shaking condition in hand.For example ,i shake sensors in a flat desk continuously，the pitch and roll will increase slowly. I have used some AHRS products like Xsens-MTI300 or SBG-IG500,they all performance well in shaking condition in hand,their pitch and roll don't increase ,but only  a little oscillation according to the shake.I have tried many methods,like low pass filtering the accelerometers,but can't performance well. I don't know how can they do this? 2.When computing the incremental fast (typically 200Hz) rotation vector rvec (deg),i tried to not minus the gyro bias,this seems performance well.I think  the algorithm can't estimate the gyro bias accurately under  maneuvering，so the inaccuracy estimated bias will cause the attitude error.I average the gyro datas in 3-5 sec，and use this as the inital bias to be deducted. 3.the linear acceleration time constant,linear acceleration decay factor ! How should I set this parameter？？  What is the meaning of this parameter？ SensorFusion Re: attitude under shake condition in hand Sorry, I can't comment on performance based on the ADIS16445.  We have not seen a problem with shake when using Freescale sensors with the V5 library.  One of Mark Pedley's standard tests is to shake the IMU has fast as he can to see how fast it recovers.  V5 recovers very quickly with our sensors.  That said, the library SHOULD be compatible with any manufacturer's sensors.  Mark has successfully ported to a number of different manufacturers with similar results.  But please don't ask - Freescale can't offer support on competitive devices (the good will of my masters only goes so far ).  You'll need to rely on other community members or ADI for that. Regards, Mike

手で握手する姿勢 <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

为什么 MMA8452 在从待机模式过渡到运行模式时会产生中断？ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 配置如下 1.启用 Z 轴 2.将阈值计数设为 4 3.将去抖动计数设为 1 4.设置为低功率，ODR = 1.56Hz 5.启用瞬态检测中断 6.将瞬态中断路由至 INT1 然后，我们激活加速度计，INT1 引脚上立即出现一个 780 毫秒的中断。 为什么会出现这种情况？ 加速度传感器 Re: Why does the MMA8452 generate an interrupt when transitioning from standby to active mode? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 嗨，阿曼达、 很抱歉迟迟没有回复你。 我能够重现并理解这种行为的根本原因。内置的高通滤波器具有一定的响应时间，因此零件的绝对输入（Z = 1g）不会立即被过滤到 0g（当零件处于静止状态时），而是以很小的步长进行过滤。因此，在这一响应时间内的高通滤波器输出会导致杂散瞬态中断。根据部件的绝对输入量和所选的 ODR，这个时间可能在几秒钟左右。已与设计团队确认了这一问题，解决方法是首先提高瞬态阈值，使其大于静态方向的加速度。 如果您对此事还有任何疑问，请告诉我，我们对由此造成的不便深表歉意。 顺祝商祺！ 托马斯 Re: Why does the MMA8452 generate an interrupt when transitioning from standby to active mode? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好，托马斯 当我启用 x 或 y 轴时，它不会触发中断。而加速度计的方向是平放在桌面上的，所以我猜 Z 轴会立即发生变化。 使用用户偏移寄存器是设置初始偏移的方法吗？ 谢谢！ 阿曼达 Re: Why does the MMA8452 generate an interrupt when transitioning from standby to active mode? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 嗨，阿曼达、 在我深入研究之前，能否请您在这里发布一张快照，显示意外中断触发时 INT1 引脚以及两条 I2C 线路的情况？禁用 Z 轴并启用 X 轴或 Y 轴时是否会出现这种情况？它对初始方向敏感吗？ 顺祝商祺！ 托马斯

使用 AVR Studio 与 Atmega16 接口时，如何使用 spi 在 MMA7455 加速计的寄存器 0x16 中写入 0x01 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 在这方面帮帮我，我被困在我的项目之间。 Re: how to write 0x01 in register 0x16 of MMA7455 accelerometer using spi when interfaced with Atmega16 using AVR Studio <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好，阿比舍克 由于您使用的是 ATmega16 微型处理器，我建议您将此问题发布到 AVR 论坛。 有关 MMA7455L SPI 通信和通信例程示例的简要说明，请参阅附件。 希望对您有所帮助。 此致， 托马斯 PS： 如果我的回答有助于解决您的问题，请标记为"正确" 或 "有帮助"。谢谢。

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

MPXV5004 出力電流? MPXV5004 の最大出力電流はいくらですか? https://www.nxp.com/docs/en/データシート/MPXV5004G.pdf 圧力センサ Re: MPXV5004 output current ? こんにちは、セルジュさん。 MPXV5004 は、Vout で最大 0.5mA の電流を供給でき、Vout 電圧を仕様範囲内に維持できます。 よろしくお願いいたします。 トーマス

MPL3115A2 accuracy clarification Hello,  i would like some help to clarify the +- .4kPa absolute accuracy parameter in the MPL3115A2 data sheet: has this accuracy to be intended as an offset error which stays constant over the whole measurement range? I need to measure not an absolute pressure but pressure intervals over time, so, on reading P1 and P2, i wouldn't mind an offset  error, as long as it stays constant for both readings, cancelling itself out during the calculations. Conversely, a variable uncertainty (of  -.4 to + .4 kPa) on every reading wouldn't be acceptable. So, is the true pressure accuracy for differential readings the +-.05 kPa stated on the data sheet? Is the "pressure absolute accuracy" an offset error, constant over the rated pressure range?  Thanks and best regards, Daniele Paesani PS I am aware that other sensor with different ranges/methods may seem to be better suited for this application. Pressure Sensors Re: MPL3115A2 accuracy clarification Hello Daniele, Yes, the absolute pressure accuracy of ± 400 Pa is an offset error within the pressure range from 50 to 110 kPa and over the specified temperature range. Take a closer look at chapter 6 of the AN4528 describing this in more detail. Best regards, Tomas

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

Marking for the traceability date code for MMA9553LR1 Dear Support, Please advise if the marking for the traceability date code for MMA9553LR1 is 4 characters only for (Assembly Site, Lot Code and Workweek) the actual part have only 3 characters which is "BJA", Is this valid traceability for date code? Please advise if you have any PCN related to markings. Thanks Re: Marking for the traceability date code for MMA9553LR1 Thomas, Does this change also apply to MPN: MMA8452QR1? I have the following marking: 263 8452 NXDN The MFG label for the parts list DATE: 2024 Please advise Re: Marking for the traceability date code for MMA9553LR1 Hello Tomas, Thanks for checking this. Can you please share document which confirms above details. Regards  Vraj  Re: Marking for the traceability date code for MMA9553LR1 Hi Vraj, As far as I know, there is no PCN available, but parts produced in 2014 and later have 3 characters traceability code (third line). Here is the marking scheme: *263 9553 YWZ Best regards, Tomas

fxas21002C dropout I see data dropouts up to 40% of the time with my gyro.  Is there a known issue which causes this? Andy. Gyroscope Re: fxas21002C dropout Hi Andy, OK, glad to hear you resolved the issue by proper declaration of an array. Yes, FreeMASTER is a very useful and valuable tool, but perhaps not very well known among developers. Best regards, Tomas Re: fxas21002C dropout Tomas, This problem is now resolved When I read data from the Gyro, I save the bytes to an array called Gyro_Receive[].  I use FreeMaster to debug my hardware and software.  I implemented a recorder in the tool and in the I2C read function to capture a sequence of data in real time.  That is a wonderful tool! Gyro_Rate_X is Gyro_Receive[1] << 8 | Gyro_Receive[2].  I first plotted Gyro_Rate_X and found the data dropouts reported originally.  I then plotted the status byte with Gyro_Rate_X to see if there was a problem with data in the gyro.  The status byte was always 0x0f.  I then plotted Gyro_Receive[1] with Gyro_Rate_X and that byte was always zero.  That was as expected because I have the recorder set to trigger on a positive angle rate.  I then plotted Gyro_Receive[2] with Gyro_Rate_X and found that the signal was smooth, but when there was a dropout, the two variables were overlaid and negative.  I then realized that the problem was with the declaration of Gyro_Receive[]. I had declared that array as char.  When I changed it to unsigned char, then the data was properly assembled into Gyro_Rate_X and the problem was resolved. Kind of dumb, I know.  Especially because it took me so long to discover the cause.  I can now explore some of the filtering features of the gyro, to see what will work best in my system. I am using an ODR of 400 Hz and full scale of 500 deg/sec.  I had tested two parts which told me that my problem was either software or setup.  The layout is as described in the data sheet for I2C operation.  Re: fxas21002C dropout Hi Andy, Could you please elaborate a bit more on this issue? It might also be useful to see your schematic, source code and output data illustrating this behavior. How many parts have you tested so far? Best regards, Tomas 

FXOS8700 对齐错误 我正在看这张桌子 =https://community.nxp.com/t5/Sensors/freescale-9-axis-sensor-fusion-specification/m-p/1165124#M6316 在 13.7 度的表面上，传感器的输出为 13 度。根据该表，每一度的祖先度数为 0.05 度 表中的加速度计对准误差是每度吗？ 希望我没说错

FXOS8700 アライメントエラー 今、この表を見ています = https://community.nxp.com/t5/Sensors/freescale-9-axis-sensor-fusion-specification/mp/1165124#M6316 13.7 度の表面で 13 度のセンサ出力が得られます。この表によると、1度あたり0.05度の祖先がいると書かれています 表にある加速度センサの調整誤差は度あたりですか?間違っていなければいいのですが

zstar tri-axial accelerometer I have an older Freescale ZStar tri-axial accelerometer board and USB stick that I have used in the past to do remote vibration sensing.  The number for this kit with the two boards was RD3473MMA7360L.  Computer died and lost the PC program that interfaced to these boards.  The PC software was Triax ver 1.0 software I think.  Can anyone point me to where I can download this, I know these boards are old but was hoping to find the software so that I can use them for a project.  If the software is not available, does NXP have a newer alternative to these boards such that I can place the one board on the unit being tested for vibration, plug the other board into the PC USB port, and be able to collect data remotely Accelerometers Sensing Platforms Re: zstar tri-axial accelerometer Hi Larry, Please try to use the attached drivers. I hope it helps. Best regards, Tomas Re: zstar tri-axial accelerometer Also having some issues when I select the Scope tab, it’s looking for “National Instruments.UI” version 8.1.20.256. Is there a zip file somewhere that contains all the necessary installation files and drivers that were on the original installation disk for this kit. Tom, Got the devices working on one computer but on the other computer it didn’t automatically install the drivers when I plugged it in. Could you send me the drivers or point me to where I can find the drivers for the zstar tri-axial board that I have. Larry Re: zstar tri-axial accelerometer Tom, Got the devices working on one computer but on the other computer it didn’t automatically install the drivers when I plugged it in. Could you send me the drivers or point me to where I can find the drivers for the zstar tri-axial board that I have. Larry Re: zstar tri-axial accelerometer Tomas, Thanks, I know these boards are old but it handy plugging the one module into the USB and attaching the other module to the device for measure acceleration and having the data transmitted wireless. Wish NXP would come up with a newer version of this. Regards, Larry A. Gunseor Re: zstar tri-axial accelerometer Hi Larry, Please find attached the requested PC GUI software. Best regards, Tomas PS: If my answer helps to solve your question, please mark it as "Correct" or “Helpful”. Thank you.

MMA8652FCR1 Problems with WHO AM I Hi, Currently running a MMA8652FCR1 in a prototype system. We are basically looking to validate comms and then configure the device. We are not getting the expected response from the WHO AM I register reading. I have attached a plot of the comms link. I2C is in normal mode and is operating at 98kHz based on the attached. We have seen a similar, but incorrect, response from a few devices. Has anyone any experience of this? Thanks in advance, KMC Accelerometers Magnetic Sensors Re: MMA8652FCR1 Problems with WHO AM I Thanks Tomas. I do use other I2C devices with this method an I don;t have issues....  I will impliment directly . Many thanks, Kevin Re: MMA8652FCR1 Problems with WHO AM I Hi Kevin, Looking at your screenshot, there is the stop condition between the second (0x0D) and third byte (0x3B). This is incorrect. You need to change your source code so that SDA transitiones to high before the SCL goes high in order to eliminate this stop condition. The transaction should look as follows: 1. Send a start sequence 2. Send 0x3A // MMA8652FC slave address with the R/W bit low or 0x1D << 1 3. Send 0x0D 4. Send a start sequence again (repeated start) 5. Send 0x3B // MMA8652FC slave address with the R/W bit high or (0x1D << 1) | 0x01 6. Read the data byte from WHO_AM_I register 7. Send NAK and the stop sequence Hope it helps. Best regards, Tomas Re: MMA8652FCR1 Problems with WHO AM I Sorry, I forgot to mention that we started to look at a series of bytes as the first byte we see as a response was always 0x00. The plot shows 4 byte response of 0x00 / 0x9D / 0xFC / 0x89 - We expect to see 0x4A  Thanks again

FXSL8471 - 线性和偏移 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如何保证 ctm 的线性度和偏移参数？FXLS8471 进入批量生产

MMA8652FCR1 我是谁的问题 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您好， 目前在原型系统中运行的是 MMA8652FCR1。我们基本上是在验证通信，然后配置设备。 我们没有从 "世卫组织上午新闻 "中得到预期的回应。我在附件中附上了通讯线路图。I2C 处于正常模式，工作频率为 98kHz。 我们已经看到了一些设备的类似但不正确的响应。有人有这方面的经验吗？ 提前感谢！ KMC 加速度传感器 磁力传感器 Re: MMA8652FCR1 Problems with WHO AM I <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 谢谢你，托马斯。 我确实用这种方法使用其他 I2C 设备但我没遇到问题... 我将直接实施。 非常感谢、 凯文 Re: MMA8652FCR1 Problems with WHO AM I <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 嗨，凯文、 查看屏幕截图，第二字节 (0x0D) 和第三字节 (0x3B) 之间存在停止条件。这是不正确的。 您需要修改源代码，使 SDA 在 SCL 变为高电平之前过渡到高电平，以消除这种停止条件。 交易应如下所示： 1.发送启动序列 2.发送 0x3A // MMA8652FC 从站地址（R/W 位为低电平）或 0x1D<< 1 3.发送 0x0D 4.再次发送启动序列（重复启动） 5.发送 0x3B // MMA8652FC 从站地址，R/W 位为高或 (0x1D<< 1) | 0x01 6。从 WHO_AM_I 寄存器读取数据字节 7.发送 NAK 和停止序列 希望对你有所帮助。 顺祝商祺！ 托马斯 Re: MMA8652FCR1 Problems with WHO AM I <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 抱歉，我忘记提及我们开始查看一系列字节，因为我们看到的第一个响应字节始终是 0x00。该图显示了 0x00/0x9D/0xFC/0x89 的 4 字节响应-我们预计会看到 0x4A 再次感谢

FXSL8471 - 直線性とオフセット <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 例えばctmの直線性とオフセットパラメータをどのように保証するかFXLS8471が量産開始

FXLN8372QR1のキャリブレーション方法 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 3 軸アクセラレータの調整を手伝ってくれる人はいますか。FXLN8372QR1を使用しています Re: How to Calibrate FXLN8372QR1 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、デビッド。 ご返信ありがとうございます。共有していただいた内容は役に立ちました。 ありがとうございます。 よろしくお願いいたします。 アミス Re: How to Calibrate FXLN8372QR1 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、アミスさん。 ご連絡ありがとうございます。 最も簡単なオフセット調整方法は、X が 0g、Y が 0g、Z が +1g になるようにボードを平らな面に置き、16 個のサンプルを記録して平均化することです。Z の想定される 0g オフセット値を計算するには、+1g の読み取り値から既知の感度を差し引く必要があります。 詳しい情報については、以下の文書をご覧ください。 FXLN8371Q - ベアメタルサンプルプロジェクト この情報が役に立つことを願っております。 よろしくお願いいたします。 デビッド