I2C Write.vi

Labview 8.0 and Windows 2000. I am using NI-8451 USB to I2C Converter
and the I2C Write.vi and I2C Read.vi. My question is how do you tell
these vi's what address to start at? The vi's have no inputs for
address. They have inputs for number of bytes and input data but no
input for start address.
Thanks for your help.

Hi Iec,
You need to use the Create Configuration Reference vi first, then use the Configuration Property node to set the address, address size, and clock rate.  There are two examples that do a basic read and write in the example finder.  Just go to Help > Find Examples, then Browse to Hardware Input and Output > I2C and SPI > I2C Basic.
In this folder are a basic read and basic write example that would be a great point of reference for you.  There is also more information in the NI-845x Software User Manual and the NI-845x API Help.
Hope this helps!
Adam W
Applications Engineering

Similar Messages

  • I2C Write/Read Error

    Error -301742 occurred at NI-845x I2C Write Read.vi
    "Possible reason(s):NI-845x:  The slave did not acknowledge an address+direction byte transmitted by the I2C master. Reasons include the incorrect address set in the I2C configuration or the incorrect use of the 7-bit address. When entering an address to access a 7-bit device, do not include the direction bit. The NI-845x Basic I2C API internally sets the direction bit to the correct value, depending on the function (write or read). If your datasheet specfies the 7-bit device address as a byte, discard the direction bit (bit 0) and right-shift the byte value by one to create the 7-bit address."
    We have connected the pull up resistors on the SDA and SCL line.
    The error seems to be strange in our case,
    We have two setup
    1. Using a push button to power the device and wires through the pull up resistor.
    2. We are trying to communicate using a NI 2569 for the SDA and SLC and the Power supply to the device.
    We do not observe the error in case 1,however, in case 2 we do observe,attached are the waveform pics for the same.
    Noted that we have the clock signal rise delay in case 2, is this because of the relay 2569?
    Any help will be highly appreciated.
    Regards,
    Naru 
    Attachments:
    Case 1.jpg ‏302 KB
    Case 2.jpg ‏302 KB

    I don't quite understand your setup, and I'm not sure what I'm looking at with the figures you posted. What does the 2569 have to do with the 8451? You also said
    1. Using a push button to power the device and wires through the pull up resistor.
    I have no idea what this means.
    It's hard to tell from the pictures, but for the Case 1 figure, it appears that you are generating a correct start condition. It's also indicating that are sending a read transaction. You didn't indicate what device you're talking to, so we can't say for sure if this is correct. 
    In the second case it also appears that you generating a correct start condition. The slow rise times that you are seeing in the clock is probably due to extra capacitance on the bus, or weak pullups, or both. This transaction appears to be a write transaction, but with no data.
    At this point, without knowing what device you're talking to, a better explanation of your setup, and the code itself, I'm not sure how much help we can be. 

  • Trigger oscillosco​pe on specific I2C write?

    Apologies for cross posting this from the Automotive and Embedded forum but there just doesn't seem to be much "traffic" there (no pun intended) I did a search and only found about four posts that even mention I2C. Most are about CAN.
    My only experience with hardware and LabVIEW is controlling instruments using visa. I have an I2C problem I am trying to debug and maybe someone knows if NI makes hardware that will work for me.
    I want to trigger an oscilloscope on an I2C write to a specific 24C32 EEPROM address so I can look at the waveform preceding that. Could one of the DAQ cards do this and would I need LV Real Time?
    I have a Total Phase I2C monitor and I can log the transactions. But some of the transactions are corrupt and there are mysterious erroneous writes to a few different EEPROM memory locations. Interestingly it writes the address of the I2C device to these locations. So I need to look at the waveform immediately preceding one of these unexplained writes.
    Maybe the DAQ card can be the scope if I use analog inputs. If I capture the clock and data is there a vi that already exists that will decode the bit stream?
    The way I might go about this is with a PIC microcontroller. I can write a program for that which I can send commands to through LabVIEW. I could tell the PIC to make a digital line go high when it sees a particular bit stream and use that to trigger the scope.
    What would you do?
    =====================
    LabVIEW 2012

    On a specific write
    That makes it more challenging and could be a pile of work used just one time.
    A continuous acq at a high rate to catch the issue then go back through it manually can get you there but a lot of manual scrolling and decyphering.
    I think there are some FPGA examples available that support low levl protocols. You may be able to start with there work, not sure.
    I'll process this challeng in the background and if I have more ideas I'll share.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Need help - I2C write/read with TAOS TCS3414 light sensor using USB-8451

    Hello, I'm new to labview and need help setting up a vi that will allow me to communicate with a digital light sensor (TAOS TCS3414) using a USB-8451. I need to use the sensor to measure light from a light source that I designed and built as part of a project im working on. I've tried looking at several labview I2C exampled but find them to be very confusing. I've used an arduino to interface with the sensor successfully but need to use labview and dont understand how to write the program. The actions are simple; I need initialize the sensor with a simple command and then request data from 8 data registers and then read that data. The data will then be used in further calculations. The portion i need help with is writing and reading from the sensor. I've attached the datasheet for the sensor as a guide. I can also provide the arduino code that i use to read data from the sensor if that would help. 
    Pleae keep in mind that i am completely new to labVIEW. I really do want to learn from this but need quick results so the more help the better. It would greately appreciate any help or explaination. 
    Attachments:
    TCS3414_Datasheet_EN_v1.pdf ‏1806 KB

    Hi Aaron,
    Here you go, this is made with a USB-8452.
    When you run the code tick the power en dac enable box on.
    Maybe you can help me with my problem, I want to use a fiber to sense light from a led.
    Do you use any fiber hardware with the TCS3414?
    gr,
    Attachments:
    TCS3414.vi ‏63 KB

  • Best way to chain several I2C write / read cycles

    Hi,
    I'm developing a custom sensor that communicates over I2C with the NXT.
    I need to perform sequencially several read / write actions over I2C.
    I know that the NXT toolkit is limited to only one frame sequences and that is possible to chain them with "pink NXT wires" or "any other wire".
    I've tried several times but I only get the first frame working. The other aren't executed.
    Does anyone here has enough experience or advices to perform several I2C operations sequencially in the same VI.
    Many thanks in advance.

    What version of LabVIEW / NXT Module are you using?
    The most recent LVLM supports multi-frame stacked sequences.
    Take a look at the ultrasonic sensor block diagram, it has a configure step followed by actually reading the data.
    One problem can be trying to read/write the i2c channel too fast. You may need to insert some arbitrary wait times in between sequential i2c calls.
    If you post your code it might be easier to tell whats not working.

  • Trigger oscillosco​pe on specific write to I2C EEPROM?

    My only experience with hardware and LabVIEW is controlling instruments using visa. I have an I2C problem I am trying to debug and maybe someone knows if NI makes hardware that will work for me.
    I want to trigger an oscilloscope on an I2C write to a specific 24C32 EEPROM address so I can look at the activity preceding that. Could one of the DAQ cards do this and would I need LV Real Time?
    I have a Total Phase I2C monitor and I can log the transactions. But some of the transactions are corrupt and there are mysterious erroneous writes to a few different EEPROM memory locations. Interestingly it writes the address of the I2C device to these locations. So I need to look at the waveform immediately preceding one of these unexplained writes.
    Maybe the DAQ card can be the scope if I use analog inputs. If I capture the clock and data is there a vi that already exists that will decode the bit stream?
    The way I might go about this is with a PIC microcontroller. I can write a program for that which I can send commands to through LabVIEW. I could tell the PIC to make a digital line go high when it sees a particular bit stream and use that to trigger the scope.
    =====================
    LabVIEW 2012

    Please use the forum post located here.
    Kareem W.
    National Instruments
    Web Product Manager

  • DiB0070 I2C read failed errors on Sony playTV dual tuner.

    Hi Guys,
    As far as I can tell Googl'ing around this error has been aroung since 2008 in the dvb-usb-dib0700 driver.
    I get the following in the log:
    [ 271.882232] DiB0070 I2C write failed
    [ 612.809450] DiB0070 I2C read failed
    [ 792.722569] DiB0070 I2C write failed
    [ 969.609201] perf samples too long (2515 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
    [ 2011.890312] DiB0070 I2C write failed
    When there is enough of them in the log, the tuner stops working. It has crashed at the point as well, see:
    [39237.817501] DiB0070 I2C read failed
    [39648.715000] DiB0070 I2C write failed
    [40324.499602] divide error: 0000 [#1] SMP
    [40324.499637] Modules linked in: udf ctr ccm bnep rfcomm bluetooth parport_pc ppdev arc4 snd_hda_codec_hdmi snd_hda_codec_realtek rt2800usb rt2800lib crc_ccitt rt2x00usb rt2x00lib dvb_usb_dib0700 dib7000p dib0090 dib7000m dib0070 mac80211 snd_hda_intel dvb_usb snd_hda_codec dib8000 rc_imon_mce dvb_core cfg80211 snd_hwdep dib3000mc snd_pcm dibx000_common snd_seq_midi snd_rawmidi imon snd_seq_midi_event rc_core snd_seq snd_timer snd_seq_device hid_appleir joydev snd soundcore snd_page_alloc serio_raw asus_atk0110 lpc_ich mac_hid lp parport hid_generic usbhid hid pata_acpi radeon ttm drm_kms_helper firewire_ohci drm r8169 firewire_core crc_itu_t mii pata_marvell i2c_algo_bit
    [40324.500094] CPU: 1 PID: 2605 Comm: kdvb-ad-0-fe-0 Not tainted 3.13.0-35-generic #62~precise1-Ubuntu
    [40324.500144] Hardware name: System manufacturer P5Q-EM/P5Q-EM, BIOS 2203 07/08/2009
    [40324.500189] task: ffff880079efb000 ti: ffff88007995a000 task.ti: ffff88007995a000
    [40324.500231] RIP: 0010:[<ffffffffa0480b6a>] [<ffffffffa0480b6a>] dib7000p_set_dds+0x3a/0x140 [dib7000p]
    [40324.500292] RSP: 0018:ffff88007995b928 EFLAGS: 00010246
    [40324.500323] RAX: 0000000004000000 RBX: ffff880034fb6000 RCX: 0000000010624dd3
    [40324.500363] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff880034fb79a0
    [40324.500403] RBP: ffff88007995b968 R08: ffff88007995a000 R09: ffffea0001e16c00
    [40324.500444] R10: ffffffff8156b26a R11: 0000000000000000 R12: 0000000000000000
    [40324.500484] R13: 0000000000000000 R14: ffff880034fb6000 R15: 0000000004000000
    [40324.500524] FS: 0000000000000000(0000) GS:ffff88007fc80000(0000) knlGS:0000000000000000
    [40324.500570] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    [40324.500603] CR2: 00007f1fe9d293d0 CR3: 0000000077c69000 CR4: 00000000000007e0
    [40324.500643] Stack:
    [40324.500656] 0000000000000040 0000000000000384 ffff88007995b968 ffff880034fb6000
    [40324.500704] ffff880034fb6000 ffff880034fb6000 0000000000000002 0000000022739480
    [40324.500750] ffff88007995b9b8 ffffffffa0480e9e ffff880078d3a8f0 0000000000000441
    [40324.500797] Call Trace:
    [40324.500818] [<ffffffffa0480e9e>] dib7000p_agc_startup+0x22e/0x480 [dib7000p]
    [40324.500862] [<ffffffffa0483382>] dib7000p_set_frontend+0x72/0x1f0 [dib7000p]
    [40324.500911] [<ffffffffa040e78e>] dvb_frontend_swzigzag_autotune+0x13e/0x350 [dvb_core]
    [40324.500961] [<ffffffff8156b26a>] ? usb_control_msg+0xea/0x110
    [40324.501002] [<ffffffffa040f8aa>] dvb_frontend_swzigzag+0x29a/0x3c0 [dvb_core]
    [40324.501048] [<ffffffff810135da>] ? __switch_to+0x12a/0x4d0
    [40324.501083] [<ffffffff810a5d2d>] ? set_next_entity+0xad/0xd0
    [40324.501118] [<ffffffff810789ff>] ? try_to_del_timer_sync+0x4f/0x70
    [40324.501155] [<ffffffff81078a72>] ? del_timer_sync+0x52/0x60
    [40324.501191] [<ffffffff8175d345>] ? schedule_timeout+0x135/0x250
    [40324.501228] [<ffffffff81078620>] ? call_timer_fn+0x160/0x160
    [40324.501268] [<ffffffffa0412a64>] dvb_frontend_thread+0x454/0x7c0 [dvb_core]
    [40324.501311] [<ffffffff810affd0>] ? __wake_up_sync+0x20/0x20
    [40324.501351] [<ffffffffa0412610>] ? dvb_frontend_ioctl+0x160/0x160 [dvb_core]
    [40324.501393] [<ffffffff8108fb59>] kthread+0xc9/0xe0
    [40324.501423] [<ffffffff8108fa90>] ? flush_kthread_worker+0xb0/0xb0
    [40324.501460] [<ffffffff8176ab7c>] ret_from_fork+0x7c/0xb0
    [40324.501493] [<ffffffff8108fa90>] ? flush_kthread_worker+0xb0/0xb0
    [40324.501528] Code: 7d f8 41 bf 00 00 00 04 48 89 5d d8 4c 89 65 e0 4c 89 6d e8 41 89 f5 4c 89 75 f0 49 89 fe e8 6e ff ff ff 31 d2 41 89 c4 44 89 f8 <41> f7 f4 8b 0d ad 67 00 00 41 89 c7 44 89 e8 c1 f8 1f 89 c3 44
    [40324.501731] RIP [<ffffffffa0480b6a>] dib7000p_set_dds+0x3a/0x140 [dib7000p]
    [40324.501776] RSP <ffff88007995b928>
    [40324.516014] ---[ end trace 6a9fad8fe9eb61e2 ]---
    Anyone know how I can fix this? I have tried upgrading to the latest kernel 2.13 and have compiled and installed the latest v4l drivers.
    I have also tried vairous module parameters for the relevent modules. i.e
    options dvb_usb disable_rc_polling=1
    options dvb_usb_dib0700 force_lna_activation=1
    options dvb_core dvb_powerdown_on_sleep=0
    Nada!
    Any help much appreciated.
    Last edited by bmentink (2014-09-20 03:38:44)

    The first thing to do is use smartctl to test the drive. Start with the short test ( smartctl -t short /dev/sdX ), and if it passes run the long test ( ... -t long ... ).

  • Usb-8451 i2c developement

    Generated a simple program to talk to i2c on NSE5310 using usb-8451.  I get the following error.
    Error -301742 occurred at NI-845x I2C Write Read.vi:1
    Possible reason(s):
    NI-845x:  The slave did not acknowledge an address+direction byte transmitted by the I2C master. Reasons include the incorrect address set in the I2C configuration or the incorrect use of the 7-bit address. When entering an address to access a 7-bit device, do not include the direction bit. The NI-845x Basic I2C API internally sets the direction bit to the correct value, depending on the function (write or read). If your datasheet specfies the 7-bit device address as a byte, discard the direction bit (bit 0) and right-shift the byte value by one to create the 7-bit address.
    I do have pullup resistors of 1.5k on both SDA and SCL.  I've attached the data sheet for the device and a sample program. 
    THANKS FOR YOUR TIME.   Happy Holidays.............................
    Attachments:
    NI-8451 Testing ver2.vi ‏13 KB
    NSE-5310_Datasheet_v1_0.pdf ‏1569 KB

    You are providing the wrong address. As the error message says, you must provide the 7-bit address, excluding the read/write bit. . You are providing the full value of the first byte, including the read/write bit. In other words, you are doing the exact opposite of what the error message tells you to do. If you've set the user-bits to 0 then the correct address is 0x40.
    Side-note: When you set a front panel numeric control to hex display you should also display the radix so that others know that it refers to "81" hex, and not "81" decimal, which are two different values.

  • About Sun Fire E25K I2c read time out error

    Hi,
    Can anybody give me a breif explaination about the following errors
    which capatured by Sun Fire E25K System Controller:
    Nov 7 08:16:36 2006 E25K-ORADR-sc0 hwad[11914]: [1123
    20621355893934396 ERR I2cComm.cc 410] I2c read time out - bus: 10,
    address: 21
    Nov 7 08:16:36 2006 E25K-ORADR-sc0 hwad[11914]: [1128
    20621356152372741 ERR SelectPll.cc 292] Reading bus failed in address
    0, ecode=1123
    Nov 7 18:45:40 2006 E25K-ORADR-sc0 hwad[11914]: [1123
    20659099583593289 ERR I2cComm.cc 410] I2c read time out - bus: 10,
    address: 21
    Nov 7 18:45:40 2006 E25K-ORADR-sc0 hwad[11914]: [1128
    20659099584735868 ERR SelectPll.cc 138] Reading bus failed in address
    0, ecode=1123
    Nov 8 02:15:01 2006 E25K-ORADR-sc0 hwad[11914]: [1124
    20686060070434628 ERR I2cComm.cc 1095] I2c write time out - bus: 10,
    address: 21
    Nov 8 02:15:01 2006 E25K-ORADR-sc0 hwad[11914]: [1129
    20686060083304777 ERR SelectPll.cc 181] Writing bus failed in address
    0, ecode=1124
    What is the reason to cause "I2c read time out" ?
    TIA.
    Rgds,
    Simon

    Hello Simon,
    these forums are user-to-user. The Fire E25K is definetely beyond the scope of these forums (too expensive, too critical for your business, too complex).
    This system should be under Spectrum coverage (Platinum/Gold).
    Open a service case !
    Let's if you get any response to your posting on the Sun Managers mailing list.
    Michael
    Message was edited by:
    MAALATFT

  • Programming NI-8451USB- I2C interface

    Hello,
    I have just installed the software for thew NI-8451 and am able to see it in MAX.  When I attempt to use Labview 7.1.1 to program it the VISA reference is blank, nor reference is available with the following error message:
    Error -301706 occurred at NI-845x I2C Write Read.vi
    Possible reason(s):
    NI-845x:  The device reference is invalid. Verify that the supplied device reference contains a valid device name.
    Is something else I need to do?
    Thanx,
    Karl

    Hi shifti
    The error message you got tells us that the First Byte sent to your I2C Bus, which is usually the Address Byte, got no Acknowledge by your Slave device. This can be related to the address you have specified or to an electrical problem with your connections.
    To the address: The 24LC512, which is the device we are using in the example uses 7-bit addressing and the addressing scheme is 1010nnn, where nnn is the configuration of address lines A0, A1, and A2. This example assumed that these lines are connected to ground, so the default address is 0x50. Depending on how the A pins are connected(refer to the spec for your Slave) there is a addres range from 50 to 57 for EEPROMSs.
    To the electrical: The example assumes that the Microchip 24LC512 EEPROM is connected as follows:
         NI 8451           Microchip 24LC512
    Pin 31 (+5V)              Pin 8 (VCC)
    Pin 32 (GND)              Pin 7 (WP)
    Pin 30 (SCL)               Pin 6 (SCL)
    Pin 29 (SDA)              Pin 5 (SDA)
    Pin 32 (GND)              Pin 4 (VSS)
    Pin 32 (GND)              Pin 3 (A2)
    Pin 32 (GND)              Pin 2 (A1)
    Pin 32 (GND)              Pin 1 (A0)
    In addition, since the I2C SDA and SCL lines are open-drain, they must be externally pulled up to +5 V by connecting a 2.2k or 4.7k resistor between SCL and +5V (pins 30/31) and SDA and +5V (pins 29/31).
    hope that helps
    DirkW

  • I2C test and programming with NI UXB-8451

    hi,
    i want to ask how to see the waveform of 8451 with the example programming.
    It is because i want to clarify if it is working and sending the right data to my slave.
    actually i modify the program as i only want to send 255 set 1byte data to the I2C with some delay time
    can i make use the general I2C write example? i find it is 0 at the read/write bit, so it is write or read? i am confuse when i saw the waveform once a while in the CRO but then i can never catch them again.
    thanks

    Hi,
    The output of the NI-845x I2C Write Read.vi is an array you could connect that array to a Graph or Chart to visually see it or you could use Build Waveform to build the array into a waveform data type.
    As for the General I2C Write Example, currently it is only setup to Write but you could add the read functionality by adding a similar configuration to that of the General I2C Read example. Some more information about the you being able to see the waveform or what you are doing would be helpful.
    Regards
    Krista S.
    Applications Engineering
    National Instruments

  • Nxt2004 (nxt200x) dvb woes

    I'm going to send this to [email protected], but I wanted to check here if anyone knows what's going on.
    I have a pair of K-World ATSC 115 cards for my mythtv setup.  Here's a wiki link to the card: http://www.mythtv.org/wiki/Kworld_ATSC_110  They've worked without any problems for the last 2 years.  Roughly a month ago, an upgrade to kernel 2.6.32.10 caused problems in which nxt200x doesn't initialize properly some of the time (no firmware getting downloaded), and thus there's no /dev/dvb directory getting created.  I believe each card succeeds randomly about 1/3 of the time, so that came out to about 9 reboots to get both cards initialized properly.  After that it worked fine.
    However, when I upgraded to 2.6.33.2 a couple of days ago, I got the same error messages, but the probability of getting a successful firmware download is like 1 in 10.  I haven't succeeded in getting both cards initialized at the same time.  Furthermore, even though I can get one of the cards to initialize (seeing /dev/dvb/adapter0), it doesn't function.  Tuner says locked but never returns a picture in mythtv.
    Here's the information when I do a lspci:
    03:06.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1)
    03:07.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1)
    This is the error from dmesg when init fails on a card:
    nxt200x: nxt200x_readbytes: i2c read error (addr 0x0a, err == -5)
    Unknown/Unsupported NXT chip: 00 00 00 00 00
    saa7133[0]/dvb: frontend initialization failed
    Here's the message from a "successful" init (from error log since dmesg gets spammed with errors after it):
    Apr 10 13:00:19 ruyi kernel: nxt200x: NXT2004 Detected
    Apr 10 13:00:19 ruyi kernel: nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
    Apr 10 13:00:19 ruyi kernel: saa7134 0000:03:06.0: firmware: requesting dvb-fe-nxt2004.fw
    Apr 10 13:00:19 ruyi kernel: nxt2004: Waiting for firmware upload(2)...
    Apr 10 13:00:19 ruyi kernel: nxt2004: Firmware upload complete
    Apr 10 13:00:19 ruyi kernel: nxt200x: nxt200x_readbytes: i2c read error (addr 0x0a, err == -5)
    Apr 10 13:00:19 ruyi kernel: nxt200x: nxt200x_writebytes: i2c write error (addr 0x0a, err == -5)
    Apr 10 13:00:19 ruyi kernel: nxt200x: nxt200x_writebytes: i2c write error (addr 0x0a, err == -5)
    Apr 10 13:00:19 ruyi kernel: nxt200x: nxt200x_writebytes: i2c write error (addr 0x0a, err == -5)
    Apr 10 13:00:19 ruyi kernel: nxt200x: nxt200x_writebytes: i2c write error (addr 0x0a, err == -5)
    Apr 10 13:00:19 ruyi kernel: nxt200x: nxt200x_readbytes: i2c read error (addr 0x0a, err == -5)
    Apr 10 13:00:19 ruyi kernel: nxt200x: Error writing multireg register 0x80
    Then when I tried to tune to a channel it just spams the following error in dmesg forever while no picture gets shown:
    nxt200x: i2c_readbytes: i2c read error (addr 0x61, err == -5)
    nxt200x: Timeout waiting for nxt2004 to init.
    nxt200x: i2c_writebytes: i2c write error (addr 0x61, err == -5)
    nxt200x: error writing to tuner
    Please let me know if you want any additional logs.  thanks
    Ben

    I'm getting a similar error for my Kworld ATSC 110 after upgrading to linux 3.0.4-1.  When loading the saa7134 module, the kernel fails to initialize the dvb frontend:
    [  948.772122] dvb_init() allocating 1 frontend
    [  948.772282] nxt200x: nxt200x_readbytes: i2c read error (addr 0x0a, err == -5)
    [  948.772285] Unknown/Unsupported NXT chip: 00 00 00 00 00
    [  948.772289] saa7133[0]/dvb: frontend initialization failed
    Does anyone have a fix for this?

  • Error message in logs on ASR903 with IOS XE 3.9.0

    Hi all,
    I have the following error message in logs on our ASR903 running IOS XE 3.9.0 :
    Jul 10 10:01:34.273 EET: %IOMD_IMFPGA-3-MDIO_WRITE: SIP1: iomd:  An MDIO write has failed for addr: 0 reg: 1f data: 0
    Jul 10 10:03:58.281 EET: %IOMD_IMFPGA-3-MDIO_READ: SIP1: iomd:  An MDIO read has failed for addr: 0 reg: 1
    Jul 10 10:04:11.281 EET: %IOMD_IMFPGA-3-MDIO_READ: SIP1: iomd:  An MDIO read has failed for addr: 0 reg: 1
    Jul 10 10:04:18.281 EET: %IOMD_IMFPGA-3-MDIO_READ: SIP1: iomd:  An MDIO read has failed for addr: 0 reg: 1
    Jul 10 10:04:26.281 EET: %IOMD_IMFPGA-3-MDIO_READ: SIP1: iomd:  An MDIO read has failed for addr: 0 reg: 1
    Jul 10 11:46:16.627 EET: %IOMD_IMFPGA-3-MDIO_WRITE: SIP1: iomd:  An MDIO write has failed for addr: 0 reg: 1f data: 204
    Any idea what this message could mean and if there is any workaround?
    I found a BUG but it's not well documented :
    CSCuf05039
    Symptom: I2C-WRITE and MDIO_READ error messages are displayed on the Cisco ASR903 router.
    Conditions: This issue occurs after an interface module hard or soft OIR is performed.
    Workaround: There is no workaround.
    show platform    
    Chassis type: ASR-903            
    Slot      Type                State                 Insert time (ago)
    0/0      A900-IMA1X          ok                    5d02h        
    0/1      A900-IMA1X          ok                    5d02h        
    0/2      A900-IMA8S          ok                    5d02h        
    0/3      A900-IMA8S          ok                    5d02h        
    0/4      A900-IMA8S          ok                    5d02h        
    0/5      A900-IMA8S          ok                    5d02h        
    R0        A903-RSP1B-55       ok, active            5d02h        
    R1        A903-RSP1B-55       ok, standby           5d02h        
    F0                            ok, active            5d02h        
    F1                            ok, standby           5d02h        
    P0        A900-PWR550-D       ok                    5d02h        
    P1        A900-PWR550-D       ok                    5d02h        
    P2        A903-FAN            ok                    5d02h        
    Slot      CPLD Version        Firmware Version                       
    R0        11102133            15.3(2r)S                          
    R1        11102133            15.3(2r)S                          
    F0        11102133            15.3(2r)S                          
    F1        11102133            15.3(2r)S           
    show platform diag
    Chassis type: ASR-903            
    Slot: 0, A903-RSP1B-55      
      Running state               : ok
      Internal state              : online
      Internal operational state  : ok
      Physical insert detect time : 00:01:47 (5d02h ago)
      Software declared up time   : 00:03:04 (5d02h ago)
      CPLD version                : 11102133
      Firmware version            : 15.3(2r)S
    Sub-slot: 0/0, A900-IMA1X
      Operational status          : ok
      Internal state              : inserted
      Physical insert detect time : 00:04:02 (5d02h ago)
      Logical insert detect time  : 00:04:02 (5d02h ago)
    Sub-slot: 0/1, A900-IMA1X
      Operational status          : ok
      Internal state              : inserted
      Physical insert detect time : 00:04:02 (5d02h ago)
      Logical insert detect time  : 00:04:02 (5d02h ago)
    Sub-slot: 0/2, A900-IMA8S
      Operational status          : ok
      Internal state              : inserted
      Physical insert detect time : 00:04:02 (5d02h ago)
      Logical insert detect time  : 00:04:02 (5d02h ago)
    Sub-slot: 0/3, A900-IMA8S
      Operational status          : ok
      Internal state              : inserted
      Physical insert detect time : 00:04:05 (5d02h ago)
      Logical insert detect time  : 00:04:05 (5d02h ago)
    Sub-slot: 0/4, A900-IMA8S
      Operational status          : ok
      Internal state              : inserted
      Physical insert detect time : 00:04:10 (5d02h ago)
      Logical insert detect time  : 00:04:10 (5d02h ago)
    Sub-slot: 0/5, A900-IMA8S
      Operational status          : ok
      Internal state              : inserted
      Physical insert detect time : 00:04:21 (5d02h ago)
      Logical insert detect time  : 00:04:21 (5d02h ago)
    Slot: 1, A903-RSP1B-55      
      Running state               : unknown
      Internal state              : offline
      Internal operational state  : unknown
      Physical insert detect time : 00:01:47 (5d02h ago)
      Software declared up time   : 00:00:00 (never ago)
      CPLD version                : 11102133
      Firmware version            : 15.3(2r)S
    Slot: R0, A903-RSP1B-55      
      Running state               : ok, active
      Internal state              : online
      Internal operational state  : ok
      Physical insert detect time : 00:01:47 (5d02h ago)
      Software declared up time   : 00:01:47 (5d02h ago)
      Became HA Active time       : 00:07:08 (5d02h ago)
      CPLD version                : 11102133
      Firmware version            : 15.3(2r)S
    Slot: R1, A903-RSP1B-55      
      Running state               : ok, standby
      Internal state              : online
      Internal operational state  : ok
      Physical insert detect time : 00:01:47 (5d02h ago)
      Software declared up time   : 00:04:12 (5d02h ago)
      CPLD version                : 11102133
      Firmware version            : 15.3(2r)S
    Slot: F0,
      Running state               : ok, active
      Internal state              : online
      Internal operational state  : ok
      Physical insert detect time : 00:01:47 (5d02h ago)
      Software declared up time   : 00:02:49 (5d02h ago)
      Hardware ready signal time  : 00:02:41 (5d02h ago)
      Packet ready signal time    : 00:04:42 (5d02h ago)
      Became HA Active time       : 00:05:56 (5d02h ago)
      CPLD version                : 11102133
      Firmware version            : 15.3(2r)S
    Slot: F1,
      Running state               : ok, standby
      Internal state              : online
      Internal operational state  : ok
      Physical insert detect time : 00:01:47 (5d02h ago)
      Software declared up time   : 00:04:21 (5d02h ago)
      Hardware ready signal time  : 00:04:20 (5d02h ago)
      Packet ready signal time    : 00:05:56 (5d02h ago)
      CPLD version                : 11102133
      Firmware version            : 15.3(2r)S
    Slot: P0, A900-PWR550-D
      State                       : ok
      Physical insert detect time : 00:02:48 (5d02h ago)
    Slot: P1, A900-PWR550-D
      State                       : ok
      Physical insert detect time : 00:02:46 (5d02h ago)
    Slot: P2, A903-FAN
      State                       : ok
      Physical insert detect time : 00:02:47 (5d02h ago)
    Thanks,
    Robert

    Hi Reza,
    Thanks for your reply...yes lldp is enabled...and so far we did:
    - Reapply voice-vlan configuration
    - Disable/Enable LLDP
    - Reboot the Switch
    - Reset the Phones
    ... and only if we do "debug lldp" then it is working...strange

  • Where can I find "NI-845x Close Reference.vi"

    I've downloaded drivers for the NI-845x and IT-E132 and cannot find several VIs, such as "NI-845x Close Reference.vi", "NI-845x I2C Write.vi", and "NI-845x I2C Close Configuration Reference.vi". These VIs are discussed in the user guide so I know they exist. Any help is appreciated.
    Thank you.
    Solved!
    Go to Solution.

    They're right on the main functions palette.
    Never heard of "NI-845x I2C Close Configuration Reference.vi". Don't see it in the Help either.
    Attachments:
    NI-845.png ‏16 KB

  • Cant make calls??? iphone 4

    I dont have any sound  when  making call over call app!
    Used Iphone configuration utilliti and get:
    Nov 14 05:28:47 unknown kernel[0] <Debug>: AUD10: I2C write failed (4): device error
    I am really deperate, need help please or any kind of information!
    What can I do to get it work, i love my iphone 4 ?

    Did you manage to resolve this issue and if so what did you have to do?

Maybe you are looking for

  • Extractor for Acc Doc . Material Doc/Invoice Ref

    Hi All I am looking for an extractor which provides the following information. Purchase Doc --> Material Doc / Invoice --> Acc Doc number Is there any extractor that i can enhance or use which gives me the following information. Thanks Vanaja

  • Question in reading differential measurement

    Hi, I am a new user in Labview and DAQ. I am trying to read pressure data from a Dynisco PT160 pressure transducer (Output vdc: 0 - 10V, 16-32 vdc excitation) via a USB6009. I tried to connect the positive and negative output from the transducer to A

  • No inspection lot existing

    Dear Friends , I want to delete stock of material from aplant.The material is in QC & inspection type 01 is present.But there is no inspection lot for the material in QA32 tr.The material canbe viewed in MMBE.I want to knock off the stock completely

  • Re: Note how to get it after deleting.

    Hi, after the back up most of data can be restored but NOTES. dont know why?

  • Quicktime PlugInHelper for MacBook Pro?

    Hi there -- Is there a QuickTime PlugInHelper for download that works with the Intel MacBook Pro? If not, is one expected anytime soon? If yes, when? If not, why not? I have PlugInHelper for Windows working but the Mac version will not run on my MBP.