3D Hall (Magnetic sensor) Forum Discussions
we purchased TLE493DW2B6A0 samples from digikey and built our system prototype.
everything works with multiple of TLE493DW2B6A0 sensors.
the I2C address we used for TLE493DW2B6A0 is 0x6A / 0x6B.
now, we purchased TLE493DW2B6A1HTSA1 and used address 0x44 / 0x45 and it does not seems to work.
it seems to ignore the read/write command as if the address is not intended for it.
Can you please advise if there is anything else that we are missing besides setting the address to 0x44/0x45?
BTW, when driving to 0v on CLK and Data line, what is the minimum acceptable voltages? is it 0.4v max?
our Output low Voltage is about 0.48v. is it acceptable?
please see the attachment.
Thanks and Best Regards,
What is the total calculated sensor drift in mT for temperature range -40 to 125 °C as per table 11 given in the datasheet.
What is LSB12/mT, is it equal to 0.098mT
I am looking for a sensor that can measure the position of a flywheel of an engine.
Usually this is done with inductive sensors or hal sensors however my engine has 4 magnets on the flywheel so I think those would interfere with the signal I need.
The sensor would need to take over the ignition timing for my engine so I need one that is precise enough to do that..
I was thinking optical to measure teeth on the flywheel with one teeth grind out so it knows where the rotation starts/ends. Would this work for something like this? Rpm range would be up to 8000rpm and should work from standstill if possible for hand starting. Any help is echatrandom appreciated.Show Less
I am using the W2BW 3 axis hall sensor from the 2go kit and I am picking up some spurious noise on the magnetic field z Measurement. The Figures below show a measurement from a sensor when a parmanent magnet is held toward the sensor six times. As can be seen, while the x and y measurements seem to be clean, there is some spurious noise on the z component.
I thought it might be crosstalk from the I2C communication but I'm not sure.
I am setting the sensor to Master-Controlled Mode and issue an I2C read command at a frequency of 500Hz using the 1-Byte Protocol.
I set the trigger mode in the CONFIG register to 10 (e.g. ADC trigger should be after register 0x5H has been sent).
I also attached an image of the I2C waveform. On the lower graph.
I am trying to use the generic library to interface with the TLI493D-W2BW 3D Hall Sensor from a TI microcontroller. I implemented the interface but the library fails to initialize the sensor which does not seem to respond to any I2C commands, e.g. it does not generate an ACK on the bus (see also attached image).
I have SDA and SCL pulled up via 1.2kOhm resistors to 3.3V and the /INT is pulled up via a 10kOhm resistor to 3.3V.
I verified that the calls to _POWER_ENABLE and _POWER_DISABLE pull the VDD line of the sensor to 3.3V (LED on) and 0V (LED off) respectively.
I'm not sure if I am missing something obvious here?Show Less
I recently purchased Hall sensors (TLE49641KXTSA1) through Mouser.
I request because I need a certification certificate of specification for the hall sensor.
- UL Safety Specification Certification Certificate
Please check. Thank you.
4. But worst of all is the seemingly inconsistent behavior of the device. Let me explain.
On power up I reset the device by sending 0xFF 0xFF 0x00 0x00 with the start and stop conditions. (This is very badly explained in the datasheet imo btw.)
Next I configure the registers CONFIG and MOD1. I leave MOD2 alone as it has just one bit to change, and I can leave it at default.
The device is now working... I can read data from it, get the VERsion data etc.
However, if I add to my setup code a modification to MOD2, any subsequent reading of the device fails, except for one case that I have found.
If I set bit 7 (write 0x80) ---> subsequent reads fail.
If I send 0xFF, 0xE0, 0xC0, 0x00, these all cause read failure.
The only exceptions I can find is if I send 0x01 or nothing to MOD2. In these cases the device seems to work fine.
Now, perhaps I am doing something silly in my code, or perhaps MOD2 is broken, which would not surprise given how the poor design of the A1B6 device whose ADC randomly locked up requiring reset.
Very unhappy customer here.
So what exactly is hidden in MOD2 that would cause writes to it to break reads from the device?
It generally works, but not robustly.
I'm polling at 5 second intervals and I hit maybe 5% of the time where the CH/FR indicates that it hasn't finished conversion.
Yes, I can try another read.
Since the MCM mode doesn't actually power down, you can't use the PD flag to check for completion.
Some of the time it indicates that conversion is finished but the binary value of the temperature read is zero (XYZ is good).
Sometimes, it seems to lock up the bus completely.
Yes, I have full recovery methods working, but I'm not impressed.
The reference manual says:
5.6 ADC hang up in Master Controlled or Fast Mode
In the Master Controlled Mode (MCM) or the Fast Mode (FM) the ADC conversion may hang up.
Say what? Show Less
I recently got the Infineon 3D Magnetic Sensor 2Go development board (based on the XMC1100 microcontroller) and I would like to know how to read input from the 3D Magnetic Sensor which is interfaced through I2C. I am new to the Infineon development system, so I do not know how to gather and process input from the sensor.
Here is what I know so far:
The main microcontroller is an Infineon XMC1100-Q024F0064
The 3D Magnetic Sensor is connected to the XMC1100 via I2C
How to program and control the GPIO on the XMC1100
How to use the supplied stand-alone applet to view data from the Sensor
I have the DAVE IDE, the APPs extension, and I am writing my code in C. I need to use DAVE to accomplish my desired end result, but I would be interested to know the Arduino method as well.
Thank you in advance for your help!Show Less
I want to get the three coordinates values of the magnetic field measured by the sensor of my phone. For this, I get a handle to the
SensorManager by using
sm=(SensorManager)getApplicationContext().getSystemService(Context.SENSOR_SERVICE), then get the sensor with
cm=sm.getDefaultSensor(SensorManager.SENSOR_MAGNETIC_FIELD). I then register a
SensorEventListener to the
SensorListener is a class of my own implementing the
SensorEventListener interface. In it's
OnSensorChanged method, I get the values from the sensor and I display them. The problem is that I only get the values 1,0 and 0. And they are rarely updated (I have put a counter on the
onSensorChanged calls to see how often the update takes place). Changing the time to
SENSOR_DELAY_NORMAL doesnot improve anything.
To check if the problem was related to the magnetic sensor, I have added, in the same way, a listener to an accelerometer sensor. The result is very confusing : now, the magnetic sensor generates updates, but not the accelerometer one. And if I remove the accelerometer sensor event listener, I still receive the magnetic sensor events which where missing before adding the accelerometer sensor event listener.(???????????)
Any idea about what is wrong in my code?Show Less