I2C bitbanging

Similar Questions

• NFC I2C can not be activated on Win10, TP 10

  The NFC provided I2C does not work well in the device manager after having upgraded to Win10. No one knows how to fix this though? Much appreciated!

  Try this one?
  http://support.Lenovo.com/SG/en/downloads/ds103999

  INF files include an entry for ACPI\BCM2F1F, so presumably it should work.

• 8452 I2C clock stretching

  Hello

  We seek to emulate an I2C sensor that is clock stretching while doing his measure. NOR-USB-8452 clock streching in slave mode support?

  Thank you

  Hi Horsfall,

  Our 845 x manual says that "the I2C specification provides a mechanism to allow the slave slow down the movement of the bus when it is not ready."  This mechanism is known as clock stretching. "In addition, he says that the behavior is different if the device is high speed mode. The USB-8452 is built according to this specification. Therefore, we can conclude that he clock stretch when necessary.

  There is an example of the NOR-8452 making the clock that extends into the following forum post: http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/Use-NI-8452-be-a-Slave-device-in-SMBUS-NI-845...

  Please note that the USB-8452 supports the following (as defined in the I2C 4.0 specifications):

  1 standard mode

  2 fast mode

  3. fast mode more

  4. high speed mode

  I've referenced the manual can be found at the following URL: http://www.ni.com/pdf/manuals/371746e.pdf

  Kind regards

  Kyle S.
  Technical sales engineer
  National Instruments
  http://www.NI.com/support

• Potentiometer digital i2C

  Hi all

  I am trying to install a simple VI on a myRIO-1900 to use a digital potentiometer as a variable resistance. I carefully used a SPI dpot successfully, but I have problems during the transition to a controlled i2C dpot.

  

  The rest of the data sheet available here ( http://www.analog.com/media/en/technical-documentation/data-sheets/AD5241_5242.pdf ), I made the following connections.

  My assumption was a table 1 d of two elements, the first being the byte of the instruction and the second data byte. However, that's just my guess; If you need more information, I could ask the manufacturers of the AD5242 for more information.

• I2C/SMBus Melexis MLX90614 IR Termometr

  I use the interface NOR-8451 read the temperature of the thermometer IR Melexis, who use the SMBus Protocol.
  Use the I2C mode I can read RAM for display of the actual temperature, but can not cooperate with EEPROM. Has no made communication with thermometer?
  There are some specific behaviors: infrared device respond to each address, but there is no result for the address change I2C/SMBus (sholud) command.
  I did all the sugested (such as disconnection/reconnection) shares and still have the view to each address.

  In fact I need three or four devices to one bus and this is the reason why I'm looking for solutions.

  Ok. I see 4 errors in your code

  1. on your Read_Termometer_NI_send.vi, you are only reading 2 bytes on reading when it appears that the Melexis returns 3 bytes (data Low, High Data, PEC).

  2. you do a left shift on the I2C_Termom_Addr of 1. Our API uses a 7-bit address. With the default address of 0, it is well, but when you change the address it will no longer work.

  3. on your writing, you split the request in the multiple Scriptures (writing (command), writing (given Low, High Data, PEC)). This will create the incorrect model on the bus. You must use a single entry with 4-byte. Also, I don't know if reading will do nothing good. You should probably always do a read/write. Again, he would do a reading of 3 and an EEPROM_SMBus_Address to read again just writing.

  4. you get a zero for the PEC. I think it must be correct 8-bit CRC on the first three items (command, Dala Low, High Data) or else command is likely to be rejected by your device.

• I2C sbrio 9636

  Dear all,

  Greetings

  I need assistance to implement an I2C protcol in sbRIO 9636 (KIT of RIO could), I try one of this website (http://zone.ni.com/devzone/cda/epd/p/id/4063) after moving to screw for my kit and deploy it I couldn't have expected results, as shown in figure (start condition) instead, I got the figure of output (output). any suggestion? Help, please...

  Thanks in advance

  Mustafa

  
  

• Receiver with built-in ARM I2C of incorrect data

  Hello together

  For a school project, I have to finish up next week, I need to read a RealTimeClock DS1307 via I2C.

  I use a LM3S8962.

  I tried to communicate via the NI USB-8451 module, which works great.

  Now, I just read the data from the DS1307 and I used the built-in ARM I2C live. I get data, but the data is not correct (for example, it displays a value of 70 in the second register, which is not possible).

  I tried a lot of things, but I couldn't make it work properly.

  Attached a screenshot of how I implemented the reading of the I2C. What I am doing wrong? I really need to get this work otherwise I can't finish my project and this unfortunately causes a bad brand I hope that someone can help me.

  Greetings from Switzerland

  Dominic

  Hi doh.

  are you sure you read from the registry of law?

  According to this datasheet: DS1307.pdf .

  If you want to access the registry seconds we address 0 (Hex-value-0), in your screen shot his 68 decimal. You can change the representation of your constant which is connected to the terminal of the address of your create the Configuration VI reference. Just right click your constant-> visible object-> Radix. After this, you can change its representation to x (HEX).

  In addition, when you read the 7 bits that are casted to unsigned 8 bit you have to notice that the 7 bits are coded as the BCD code.

  So consider your example of reading the value in binary way 70: 70: 100110 with ILO the most significant on the left and the least significant bit on the right side. Now when divide you the values according to the seconds in the table of technical data sheets:

  | 0 | 1 0 0 | 0 1 1 0

  Then you will see, 70 as U8 has value: 0110 = 6 (last 4 bits) and 100 (average 3 bits) = 4, which means that your real value is not 70, but 46.

  So I would say, you must convert the value of U8 to an array of Boolean, divide the bits according to the table mentioned in the manual and then convert them timely.

  Hope this helps, if you have any other questions just after.

  Kind regards

  Lam

• I2C using MyRio

  Hello

  I want to use the I2C myRio. To make things easier, I am currently working on the integration of the MCP9808 a simple thermometer.

  I suppose I created the I2C - VI easier you can imagine a TI does not work. It would be nice if you woul have the look.

  The address is 19. I connected A0 to the 3V.

  

  the vi

• I2C + class motor from examples of robotic controller

  I try to combine (i.e. to use together in the same project) the motor controller class used in "Starter Kit 2.0 Custom FPGA" with I2C of "Communication I2C - sbRIO" in the examples of the Robotics module.

  I have already combined the FPGA code in a single FPGA VI and have tested the two individually.  When I go to use them together, I can't use the same FPGA VI reference because one is designed using a FPGA VI reference in dynamic mode (engines) and the other uses an FPGA VI reference that isn't in dynamic mode (I2C).

  So, what should I do?  I was going to try to convert the I2C in dynamic mode, but the only way I'd be able to do is to open the FPGA reference in each Subvi (since I can't bind to a type in the dynamic mode definition).  It also looks like trying to convert each other would be a nightmare because it would require to change the classes also (which is a mystery to me).

  P.S. I have sbRIO-9632 (Starter to be transferred to a large robot Kit)

  Nathan_B. . I met the same problem, when I mixed the two codes.

  And the only way I found to resolve this problem, configure the device "FPGA" in dynamic mode, then create a control and change of the Subvi in relation to the 'I2C Protocol', with this command (replace the input and output of the 'Sub - VI' - reference fpga). In this way, I realize the work programme. (see attachment).

• USB-8451 I2C slave?

  I have a camera that I have to test that uses the I2C bus.

  The device is a card with a microprocesssor on what is a master I2C

  The USB-8451 case maybe an I2C slave?

  Hi RTSLVU.

  Unfortunately, the box USB-8451 can currently work as a slave on the I2C or SPI bus. Be sure to visit the Centre of Suggestion of product and submitting this function as a product request. The more suggestions that are made, most likely is that this feature is implemented in a future version of the material.

  Best regards

  John M

• NOR-8451 I2C - error 301742

  Back to try to figure out why I can't connect with my AMS AS5510 I2C device.  Device address ID = 56 H.  If this error continues generating once the I2C configuration.  Why am I having this problem?

  Hello dg_lbe,

  When you see this error, 9 out of 10 times the problem is related to something happening at the physical level of the system.  Recheck (value that you use in this configuration?) pullup resistors and look to see if there are wandering connections to the Earth.

  Just to cover all of our bases, could you provide a description of the layout of the circuit?  The 8451 pins are connected to which of your interfaces of the AS5510?

  The error basically tells us "I tried to use this line, but I couldn't take control of it or pull up."  As a general rule, the lines are either not set up in a way conducive to be pulled upward, or something is pushing it down.

  In the event that we have stumbled upon one of those rare cases of 1 in 10, we also wish to re-examine the used addresses.

  101011 is only 6 - bit, and this device is expected to be treated by a 7-bit identifier.

  Page 8-6 of the AS5510 data sheet:

  'address of 7bits slave 101011 x, the last bit of the address x is defined by the axis of the ADR (0 or 1)'

  "ADR = LOW Pin" address I²C = 1010110b (56 h)

  ADR = HIGH pin"address I²C = 1010111 b (57 h).

  In your code, depending on whether the ADDR PIN is high or low, the hexadecimal numbers, 56 and 57 or decimal values of 86 and 87 are probably the right path to take.

  Best regards and good luck!

• How to apply the alias named MAX I2C device

  Hello

  How can I ask the alias of I2C device name that MAX uses in Labview? If the Alias VISA on my system is for example I2C in MAX, I need to ask him in Labview and then write the device referred to in the entry of an I2C vi.

  ARO

  Jick

  
  

• USB-8451 I2C for

  Hello

  I am looking for a starting point.

  My problem is that I have to communicate with the PCA9555 (http://focus.ti.com/lit/ds/symlink/pca9555.pdf). I searched the site of NOR and have met a USB-8451, which seems to be the answer to my problem.  However, I also have to measure current and this device seems to lack this ability.

  First of all, it would be the device that I would like to use to communicate via I2C? The only reason why I have a question is because I can't access the examples that would give me a good idea that I found what I was looking for.

  Second, is there a device like this one offered by OR who would be able to communicate via I2C and be able to measure current? Or what I need to buy 2 separate devices?

  Thirdly, is there anyone out there who has encountered the same problem (possibly with the same PCA9555)?

  Thank you

  Gerardo Hernandez

  
  

• How to use I2C with ELVIS

  I try to connect the sensor ultrasonic NXT to ELVIS, for this I need to use I2C. I was wondering how I can use I2C with ELVIS?

  The Council of ELVIS doesn't I2C communication. Our scanners high speed and the NOR-8451 are the only materials that support the I2C Protocol.

  Scott M.

• I2C SBRIO

  Hi guys,.

  I use a SBRIO-9611 to control a few shavings DAC using I2C. I did some research and found the link below.

  Unfortunately, I'm using 8.5.1 both for my FPGA software and in real time.  I need a kind soul help me downgrade 8.5.1 code so I can open it.

  Thank you

  Ray

  https://decibel.NI.com/content/docs/doc-1151

  Hi Ray,

  Here is the converted project

  Concerning