NOR-8451 I2C - error 301742

Similar Questions

• LM92 with NOR-8451 I2C temperature sensor

  Hello!

  I try to communicate with a temperature sensor LM92 via the NI USB-8451 box by I²C Protocol. I have a problem with the address because the sensor 7-bit address is 1001011 (A1 and A0 set to 1) but the LM92 works in little endian (LSB first) and Labview adds the R/W bit at the end of the address, so that full frame sent to the LM92 is 1001011R/W.

  I'll try to find a solution to reverse the complete frame before seending to communicate with the LM92.

  LabVIEW returns the 301742 error because the address is not the wright one and I can't find how to send the address in little endian.

  I just need to read the record of the temperature of the sensor so I need to write anything in it.

  Does anyone have an answer?

  To solve the problem:

  The problem of addressing is not the address sent in Big Endian, my LM92 was on a Board and a pilot forbade LM92 sensor to connect with my USB-8451 (I don't know why yet).

  So I unsolder just my LM92 and improvement directly + 5V SDA SCL and GND wires on him and it works with examples of Labview you will find in HELP from-> examples

  Thanks for trying to help me MrHappyAsthma !

• NOR-8451 with embedded Windows

  The NOR-8451 is not compatible with Windows Embedded? I have LabVIEW on but I can't get 8451 drivers to install. When I run the installation of the drivers I don't get the error messages to give me an indication that something was wrong. Thanks for the help.

  Hi jmountney,

  Yes, the OR-8451 is compatible with Windows Embedded.   Depending on your version of Windows, you may need to add additional packages.  The model recommended to register is the "application compatibility", which should include everything you need.

  Nick

• bit of banging with NOR-8451

  Hi all!

  So I have a Board that has two 12-bit DAC (LTC1257). They are cascaded with the doubt of a DAC in the din of the other. So, basically, I need to switch to 24 bits to get my two voltages output analog 12-bit. I tried to use the script of writing SPI API with some success, but there are times where my output voltages have no sense and I think it's because the timing is not always right. Therefore, I want to try some good old fashioned bit - banging on the OID of the NOR-8451 lines and see if it works. Deadlines for the DAC are attached, which I am trying to imitate with 3 lines of DIO. One for the clock, one for the DAC data for the LOAD line. However, I have a problem syncing of all signals for a schedule just as it should. I don't know if I'm limited due to hardware or if I just do it the right way.

  My code (LV 2011) and also a JPEG of my code is attached. I tried several ways, but the best I have so far is running 2 loops at the same time, a loop for clock and data and the other for the outbreak of my load line (which is not very accurately). If I run a signal at a time and check my reach, the signal seems ok, but when I try to run 2 or 3 signals at the same time, the timing of the signals get funky on the scope, which makes me think it could my hardware that cannot follow. Any advice on how I should approach this would be greatly appreciated!

  Thank you

  Serge

  they are updated very slowly (in the order of 100-150 Hz)

  and there's a jitter of considerations on these updates so

• Use of NOR-8451 talk to TI BQ20Z60-> question address Chip

  I'm working on the product test this chipset use the TI LI-ON "gas gauge".  The chip talk bus smb and chip address 0 x 17.  In order to access some features you need to do a series of Scriptures to register 0 x 77 with the data 0 x 48, followed by a reading of the register 0 x 78.

  I can talk all day to the device using the smb TI-2300 adapter but can't seem to understand the sequence necessary to specify address 0 x 17, then the address of register 0 x 77 & 0 x 78.

  So I guess that the line background question how do you manage the addresses of the chip with the NOR-8451?

  I found the answer.  The chip required a PEC byte at the end.  I had to calculate the CRC and add it to the transaction among other things.

• 8451 SPI error with ADXL346

  All,

  I have an error when you try to use the Analog Devices ADXL346 with the NI USB-8451 on SPI case.  I have the following error:

  "Error 301713 has occurred to the property node (arg 1) in SPI_Simple_forum.vi.

  Possible reasons:

  NOR-845 x: an input parameter, or a combination of parameters is not valid. An example of this error may be defining an invalid baud rate or allowing the I2C ACK mark 10-bit addressing. »

  The interesting thing about this is that it only occurs when I/O voltage is anything but 3.3V.  When it is 3.3V I do not get the error.  However, the I/O of the device voltage is set at 2.5V, so I think I need to set the I/O 8451 voltage to 2, 5V and thus get the mentioned error.  Because the error occurs when I change the voltage, I can conclude he does not like the selection of the tension, but I don't know why.  Any idea?  Thank you.

  My VI and sheet are attached.

  Hey,.

  Sorry, but I'm sure you get the error because the USB-8451 case is not capable of variable voltage levels.  If you look at the NOR-845 x Hardware and software manual, Appendix A, it says nothing to be able to change the voltage on the USB-8451 case levels.  If you scroll a little to the section USB-8452, it does.  If you have other questions about this, please do not hesitate to ask!

  Best,

• 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

  
  

• 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

• 8451 I2C loop runs slow when reading data

  Hi all

  I have searched the boards for a solution to my problem, but have not been able to find an answer.

  I have a ST LIS3DH accelerometer connected to the NI USB-8451 using the I2C interface.  I'm just trying to read acceleration data chip and write to a file.  However, despite the fact that I say the loop to run every 1 ms, it seems that the faster, it can perform each read is about 12 ms (which is about 80 Hz).  I'm trying to ultimately collect data at 1000-5000 Hz, which would mean the execution of the loop each 0.2-1 ms.

  I'm new to Labview and realize that I might have some inefficiencies in my code.  I don't know if the code optimization will be enough to solve the problem or if Labview or 8451 all simply cannot hold to these speed.

  I'm running on the following system

  Windows 7 64 bit

  1st generation core i5

  8 GB RAM

  LabVIEW 2009

  Any idea is apprecieated.

  I enclose my vi and the datasheet for the LIS3DH.  Thanks in advance for your help.

  
  

• NOR-DAQ + NOR USB-4431: error 233054

  Hello everyone,

  First of all, here is my config:

  -Dev PC: Win 7 32-bit

  -LabView 2009 - 32-bit

  - NI DAQ 9.7.5

  -Card acquisition: NI USB-4431

  The problem:

  When I run my app just after connect my DVR to my PC (or after startup) card, the DAQ Assistant gives me error 233054:

  

  I not found any explanation on this wonderful tool that is the internet, so I come here!

  The only way I Born to move forward, is the NOT-MAX aperture, ask to make an acquisition, ask to do a generation (that work) and then I can go back in LabView and run my program!

  The problem seems to come from the initialization. But I don't see what I need to do to make it work every time! Any idea?

  Best regards

  Harold

  Hello

  I just checked the daqmx and labview driver compatibility. I noticed your 9.7.5 daqmx driver version is not compatible with labview 2009, therefore, you have this agreement.

  The latest version of LabVIEW 2009 daqmx is 9.7 see below

  DAQmx and LabVIEW version compatibility:

  http://digital.NI.com/public.nsf/allkb/B0D5630C0A50D5C6862578E800459248

  So is this you can 9.7.5 uninstalling and reinstalling daqmx 9.7 see this link

  Uninstall the software

  http://digital.NI.com/public.nsf/allkb/AC6ED75D3D93375686256E8E00245F0D

  Best regards.

• NOR-DAQmx 50103 error 'the specified resource is reserved.

  Suddenly, I get this error when I try to run my program. I looked at the page for orientation:

  http://digital.NI.com/public.nsf/allkb/485201B647950BF886257537006CEB89

  I followed the steps for the case 1 (traditional DAQ driver reset), but I still get the error. Other cases concern problems with the program itself, and this cannot be my cause because my program was working fine when I left him before the holidays! Does anyone know if there is anything else without not my program that could be cause of this error?

  Thank you!

  Christina

  Glance, I see nothing in your program. I guess that other programs can run.

  However, I would certainly create and delete tasks only once. At the beginning and at the end - it could theoretically help. I also suggest you to split your large loop for in 2 loops.

  BTW, a task that throw you the error?

• 8451 I2C simultaneous and IO USB

  Hello

  I use the USB8451 OR communicate with a BQ77910A of TI by I2C. I2C communication works read at the moment but to write the EEPROM registers that I provide 3.3 v using the IO signals.

  I tested the IO and generated a signal successfully. My question is: is it possible to simultaneously run I2C and e/s on the USB8451. They need to be on the same VI in order to exploit?

  Thank you

  Vid

  Hey Vid,

  seems reasonable to use two digital lines (what do you mean by "IO"?) and the I2C at the same time. Did you habe problems using both resources at the same time?

  In general it makes no difference if you use two resources in a VI or two screws separate

  Best regards

  Christoph

• I2C errors after 2.2 (6 c)

  It seems that cscue49366 was raised its ugly head again after the update since a 2.2 (3rd) functional to 2.2 (6 c) that we are fighting with the symptoms described in this bug report (fans @ 100% or non-functional, no reading of power supply). After working with TAC for a week, it's decided, the last thing to try is a full stop of chassis.

  I hope it will come without mistakes, heads for those who seek to be updated.

  Ryan,

  I think it is expected for the subordinate not to pull this information from fan (instead, we rely on the primary current), so the State "UNKNOWN" you see.

• I2C communication slows down over time using USB-8451

  Hi all!

  I try to communicate via a device slave using a USB-8451 I2C and I noticed that after a while the communication speed slows way.

  I can send and receive data very well and apparently my system seems to work. But the problem is that over time the speed of data transfer slows down so much so that if I let it run all night it has slowed to a crawl in the morning. My ultimate goal is to gather data, draw and save every second and at the beginning it is easily achievable, but after 10-15 hours I can no longer collect data as fast I need. I'm not quite sure if this is a problem with my code LabVIEW, the NI USB-8451 box or the slave device. But if I stop running the LabVIEW program and start it again, everything returns to normal.

  The slave device is a personalized card with a microchip PIC which acts as a slave I2C and returns the data at the request of the master. I can't imagine anyone will be able to determine if this is a problem directly, but if we can rule out the other two (code LabVIEW or the NOR-8451) as the source of the problem so I know it's my slave device.

  I've greatly simplified the LabVIEW code that I used to collect data on I2C and I see even this gradual slowing down over time. Attached, it's that the very simplified VI and the data file, it produced. I only ran it for about 45 minutes, but from the beginning to the end we see again that the enforcement timeframe is rising.

  I hope I'm just doing something stupid, thanks in advance!

  -Aaron

  Aaron,

  Do not have the additional module responsible for these functions, but I'm sure I know whats going on.  It seems that each time through the loop 'OR-845 x I2C Create Configuration Reference.vi' creates a new reference.  After a while it will start to slow things down.  Better to open the reference before the while loop starts and spend just the reference in the loop.  Don't forget to close the reference after the loop stops.

• basic components of nore 10: Error 1706. What is it and what do I do.

  Basic components of the Nore 10

  Error 1706: No valid source was found for this Nero Core Components 10 product, The Windows install cannot continue.

  Nore Core folder is empty.

  Previously, I tried to install Nore Core, with no success evidenly.

  What I do now, I'm trying to reinstall?

  You're talking about two different products?  I know that Nero is but never heard talk of Nore Core.  He could not find in a Google search either.

  If you are talking about two different products, I would like to uninstall both and reinstall.  Make sure that you have compatible versions of Windows 7.  A lot of older versions do not work with Windows 7.  I had to get a new version of Nero.

  I hope this helps.  Good luck.