Error -- Block Diagram is Completely Black

Hello,
I've been working on a relatively complicated .vi that has a good amount of case structures and flat sequences.  As I was testing the front panel and going back and forth between the block diagram, the block diagram became entirely black -- all I see is a black background -- no wires, blocks, etc.  I am still able to add blocks through the menu but can't actually see them being placed or anything.  Is there a way to fix this, or revert back to normal?  I would really not like to redo all this work...
Thanks,
Bryan 

I think there are some unusal observations of you exceed a certain diagram size ( e.g. 16000 (?) in pixels). How big is your diagram?
(Other possibilites are issues with your video card, graphics driver, or color depth setting of the OS.)
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

  • I created boolean references in my main vi block diagram and copied them to my sub vi front panel. when wire my reference in my main vi to one the input node of the sub vi the wire is broken. the error says its a class conflict why?

    i created boolean references in my main vi block diagram and copied them to my sub vi front panel. when wire my reference in my main vi to one the input node of the sub vi the wire is broken. the error says its a class conflict why?

    Expanding and clarifying what BJD said;
    After you create the temporary sub-VI that BJD mentioned, open its front panel and copy the reference control that LV created when it created the sub-VI.
    This reference control will be correct class etc that you need. Use the control to replace the original control that you were attempting to wire up.
    The technique of "create sub-VI...copy" always works for me.
    There is one more thing that you should watch out for.
    The mechanical action of the boolean can not be set for latch action when attempting to read the value using a value property node.
    Trying to help,
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Error cluster constant appears different in two locations on a block diagram

    I am a newbie to LabVIEW. I have taken Core 1 & 2 and Machine Vision and I have not com across this before.
    The image on the right is obviously an Error cluster constant used in the block diagram to create an Error cluster and wire it to an error out terminal. As far as I can tell the image on the left is about the same thing, but why does it look different? The different appearance causes raises a concern that there is a difference in behavior that I do not understand. LabVIEW help suggets that both are Error constants. When I create a new error constant, it always ends up appearing like the right image above.  I have not been able to create someting looking like the image on the left.
    Could someone please confirm what the image on the left is on a blck diagram?
    Thanks,
    Bill
    Solved!
    Go to Solution.

    The image on the left is an error cluster control. It has a front panel presence and can be set either via the front panel or through a property node or local variable. The image on the right is an error cluster constant. It is a static value.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

  • Phone stuck in recovery mode complete black screen will not turn on after recovery and update there was an error and now computer and itunes will not recognize the phone....Anyone know what I can do to get the phone recognized again when it cant be turned

    Phone was not updated on time so it automatically shuts off and you get a plain black screen until it is recovered and updated. Well when i did the update and recovery I received an error. I went through the steps to fix the error, I had to restart my computer and now the phone isnt recognized on my computer or in itunes. The screen is still completely black so pushing the home button and plugging in to computer still does nothing. Device manager shows nothing in usb port, and apple mobile device software is installed and running. Any help?

    Hello agardner37701,
    I found some steps you can take when your iPhone is not recognized by iTunes when in Recovery Mode.  I recommend reviewing the steps in the section titled "If the device is not recognized while in Recovery Mode" under step 5 in the following article:
    iOS: Device not recognized in iTunes for Windows
    http://support.apple.com/kb/TS1538
    Thank you for using Apple Support Communities.
    Best,
    Sheila M.

  • DIO Port Config & DIO Port Write Block Diagram Errors (Call Library Function Node:libra​ry not found or failed to load)

    Hi Guys, need help on this.
    I have this LabVIEW program that used to work on the old computer.
    The old computer crashes most of the time, so I upgraded the computer
    and used its Hard Drive as slave to the new computer.
    I have no idea where are its installers since the guy that made the program 
    is not in my department anymore.
    I downloaded all the drivers needed from NI: NIDAQ9.0, NIVISA,NI488.2, 
    and drivers of some instruments needed in the setup. I'm using LabVIEW8.2.
    Everything's fine until I open the LabVIEW program for our testing.
    Here goes the error:
       DIO Port Config
       DIO Port Write
    Block Diagram Errors
       Call Library Function Node: library not found or failed to load
    Attachments:
    ErrorList.JPG ‏200 KB

    Honestly, I'm a newbie on Labview. I just want this old program to run on the new computer.
    The guys that installed the drivers on the old computer are no longer here in my department.
    And I have no idea where the drivers are. So I just downloaded the drivers needed for my hardware and instruments.
    Here's my hardware: (cards: PCI-DIO-96, PCI-GPIB), (instruments: SCB100,E4407B, HP83623, HP3458, HP8657)
    OS: Windows XP Pro
    By the way, I have unzipped the TraditionalDAQ drivers. First I tried the 7.4.1, but installation error appeared.
    I thought maybe the installer is corrupted, so I downloaded the 7.4.4 and unzipped it.
    But, still same installation error appears. I don't understand, both TraditionalDAQ drivers have same installation error.
    Now I have tried the DAQmx8.7.2 driver, bu still the DIO Port Config and DIO Port Write have errors.

  • Why do I get an Error Code 70229 when running Block Diagram ?

    Hi everyone,
    This error is very weird because at one time I got the block diagram to run and it worked well then when I tried it again after reopening the block diagram I got this error . 
    Can someone help me please ?
    I am using SolidWorks Premium 2014 x64 Edition.
    The attached files show the version I got for SoftMotion and for Labview 2013 32 bit installed . 
    PS. I had Labview 2013 64 bit installed but I removed it. not sure if any files remained that may cause this...
    Thank you,
    Isaiah 
    Attachments:
    Softmotion.JPG ‏54 KB
    Labview2013.JPG ‏55 KB

    Read related topic
    Thank you & Best regards
    syrpimp
    =======================================================
    “You must continue to gain expertise, but avoid thinking like an expert." -Denis Waitley

  • I am trying to create an executable vi that will call out another vi and show its front panel in the executable​. When I try this I recieve this error message "top level vi (my main vi) was stopped at unknown on the block diagram of (my sub vi)

    I am trying to create an executable vi that will call out another vi and show its front panel in the executable.  When I try this I recieve this error message "top level vi (my main vi) was stopped at unknown on the block diagram of (my sub vi)

    Well the most common way is to enclude the vi's in the build spec either directly in the dependancies that the App builder automatically generates OR by declaring them in the build spec as "additional enclusions" (like you must do for dynamic vi calls in your app.
    I have heard rummors about My.app Stuff.vi in a nugget Intaris posted- and I've wanted to dig deaper into Intaris' claims- but have not tried it myself.
    If you go down the stuff.vi route Keep us curious guys posted
    Jeff

  • LabView Crashes When Editing Block Diagram

    When least expected and usually at the most inopportune times the LabView 8.6.1 development environment crashes when I am editing my block diagram. It usually happens when I am moving VI's or wires using the arrow keys. This has happened to me several times. Is anyone else having this problem? Is there a bug fix out there?   Attached are some of the windows error logs
    Attachments:
    lvlog06-17-09-11-01-33.txt ‏2 KB
    lvlog06-16-09-15-52-19.txt ‏9 KB
    lvlog06-15-09-13-53-20.txt ‏2 KB

    There is a known issue with LabVIEW running out of memory slots in it's image table
    http://zone.ni.com/devzone/cda/tut/p/id/7324#36543_by_category
    I have experienced this issue first hand and it does make LV very unstable with crashes at the most inopportune times.
    Try uninstalling those toolkits and drivers that you are not currently using. In my case 8.6.1 became completely stable after that.

  • Red box Highlighting the entire work area of the Block diagram

    I have a thin red box highlighting the entire work are of the block diagram...I've checked for breakpoints but dont see any. I run the code and after completion the entire work area turns black for a couple seconds and then the red box flashes and the continue button on the tool bar is hightlighted. Any assistance would be great
    tks

    This is indeed a breakpoint.
    You should be able to clear it by selecting your breakpoint tool from the tools palette and clicking outside of your main code area.
    When your breakpoint tool is going to set a breakpoint, the tool is filled in with black. When is is going to clear a breakpoint, it is not filled.
    You can also search for breakpoints from the Edit menu Find function. Click the Select Object icon goto Others and select Breakpoint. This will find all your breakpoints. Sometimes they get set by mistake and you don't know it.
    Ed
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

  • Block diagram wont open properly

    I have written a big labview program for my application. I have been workig on it for 6 months. I keep adding the peice of code every day and save it with a new name every week.
    At one point when I added some code into my program, the block diagram started acting weird and wont let me work on the program easily. For If I add an add function, it would take time and insert this function a couple of inches away where I pionted my cursor. Another issue was that; if I add a while loop or for loop or any other structure it would take time and one added it would add a couple of inches away and expand the main program window (Block Diagram) too.
    since then, I started using my company's laptop to develop the code. I have no issues with that lap top till today.
    But now when I tranfer this program back to my desk top. It wont open the Block Diagram and wont let me edit it. When I try to open the block diagram. the window appear black out and the LabView stops working.
    Is this issure ralted to the graphics of my compute or any thing else? Please help me. Thanks
    Mansoor

    There is a maximum size that a VI can be. What that exact size is I don't know. It does sound like you have one HUGE VI. If that is the case you really need to think more about using subVIs. It will make your program much easier to maintain and extend.
    Also, rather than renaming it once a week you should consider using source code contol. Even if you are the only developer it is a much better way to manage your code. SVN is free and very easy to set up. If you do use source code control make sure you separate the compiled code from the source code. This is an option in the VI properties.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

  • How can I open a vi and show the block diagram?

    Hi,
    I am opening an vi using "Open VI Reference" and "Invoke Methodpen FP", but I want to open the vi and show the block diagram, but I haven´t found any method (Invoke Method) to do that and any property.
    Any idea?
    Thanks!
    Gracinda

    OK, I can come up with a reason.  I have written a program that will search the entire VI Hierarchy of a program and update all of the descriptions for all VIs with the top level program part #, the name of the top level program that the VI is used in, the company copyright info, the ITAR notice, company address, the name of the engineer performing the update, along with the date and time.  This will also place as a background image on all the VIs, a watermark of the company name, legality stuff and the copyright. It works very slick in that if there are thousands of sub-vis, such as what I'm working on now, it goes through all of them, makes sure the data is there as per company policy without having to open every one of them look at them and update or not whichever the case may be. The one portion that is tough is that the program will detect if there is a description written about what funtion the VI performs and if there is not a description, then it pops up a dialog requesting the user to write a description. The problem is that without looking at the block diagram for the VI, it can be nearly impossible to write a description for the functionality of the VI. So is there a way to programmatically open a VI, show its block diagram (this would only be in the case of a missing description) and then upon completion of the updates, close the block diagram? (I already open and close the VI programmatically in order to read the VI DESC and update as needed, but that is in the background and of course you can't see the block diagram).
    Thanks,
    Dan

  • All PDF print as completely black pages.  I can read the PDF fine.  This is true on any printer.

    All PDF print as completely black pages.  I can read the PDF fine.  This is true on any printer.
    A google search shows others have had this problem, but I have not seen a solution posted.
    I have uninstalled and reinstalled Acrobat, without help.  I'm wondering if this is a registry problem.
    I saw some post that referred to a stuck switch of print colors as black, but I know nothing about this.
    Please help!

    I am using a Mac (all software latest version - Mt. Lion and Safari as web browser).  I see this exact problem but NOT with all PDFs.  As you might not know, PDF creation is built-into all Macs and I do NOT have a problem with any of those, nor has anyone complained to me about those.  Also, Macs have a bulit-in PDF viewer ("Preview") which also can NOT view the file correctly.  If I try to open the file once it has been stored on the desktop, Acrobat gives me an "incorrectly formatted PDF file" error.
    My AMEX statement is unprintable and some other stuff that comes from our local school board, and other online sources.  (My suspicion is that these files are not perfectly formatted).
    Here was my work-around:
    I use FIREFOX browser to retrieve the same PDF and it prints fine.
    I, too, would LOVE to know why this is happening because it is annoying.

  • ORA-00333: redo log read error block

    ORA-01033: ORACLE initialization or shutdown in progress ...
    / as sysdba
    SQL> shutdown immediate;
    SQL> startup nomount;
    SQL> alter database mount;
    SQL> alter database open;
    ORA-00333: redo log read error block 8299 count 8192
    SQL> SELECT * FROM V$VERSION;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Product
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    SQL> select group#,members,THREAD, STATUS,ARCHIVED,BYTES,FIRST_TIME,FIRST_CHAGE#,SEQUENCE# from v$log;
    GROUP# MEMBERS,THREAD,STATUS,ARCHIVED,BYTES,FIRST_TIME,FIRST_CHAGE#,SEQUENCE#
    1 1 1 CURRENT NO 52428800 29-FEB-12 1597643 57
    2 1 1 INACTIVE NO 52428800 29-FEB-12 1573462 56
    Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
    Wed Feb 29 19:46:38 2012
    Recovery of Online Redo Log: Thread 1 Group 1 Seq 56 Reading mem 0
    Mem# 0 errs 0: C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_7LZYZK8S_.LOG
    Wed Feb 29 19:46:40 2012
    Completed redo application
    Wed Feb 29 19:46:40 2012
    Completed crash recovery at
    Thread 1: logseq 56, block 6568, scn 1597642
    270 data blocks read, 270 data blocks written, 1460 redo blocks read
    Wed Feb 29 19:46:43 2012
    Thread 1 advanced to log sequence 57
    Thread 1 opened at log sequence 57
    Current log# 2 seq# 57 mem# 0: C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG
    Successful open of redo thread 1
    Wed Feb 29 19:46:43 2012
    SMON: enabling cache recovery
    Wed Feb 29 19:46:55 2012
    Successfully onlined Undo Tablespace 1.
    Wed Feb 29 19:46:55 2012
    SMON: enabling tx recovery
    Wed Feb 29 19:46:56 2012
    Database Characterset is AL32UTF8
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=19, OS id=3024
    Wed Feb 29 19:47:09 2012
    Completed: alter database open
    Wed Feb 29 19:47:14 2012
    db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Wed Feb 29 20:33:30 2012
    MMNL absent for 1537 secs; Foregrounds taking over
    Wed Feb 29 20:33:31 2012
    MMNL absent for 1540 secs; Foregrounds taking over
    Wed Feb 29 20:33:31 2012
    MMNL absent for 1540 secs; Foregrounds taking over
    MMNL absent for 1540 secs; Foregrounds taking over
    Wed Feb 29 20:33:32 2012
    MMNL absent for 1540 secs; Foregrounds taking over
    Wed Feb 29 20:33:33 2012
    MMNL absent for 1540 secs; Foregrounds taking over
    Wed Feb 29 21:45:24 2012
    MMNL absent for 4318 secs; Foregrounds taking over
    MMNL absent for 4318 secs; Foregrounds taking over
    MMNL absent for 4322 secs; Foregrounds taking over
    Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
    Wed Feb 29 22:30:01 2012
    ORACLE V10.2.0.1.0 - Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Windows XP Version V5.1 Service Pack 3, v.3244
    CPU : 2 - type 586, 2 Physical Cores
    Process Affinity : 0x00000000
    Memory (Avail/Total): Ph:3097M/3546M, Ph+PgF:5143M/5429M, VA:1943M/2047M
    Wed Feb 29 22:30:01 2012
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =10
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.1.0.
    System parameters with non-default values:
    sessions = 49
    __shared_pool_size = 201326592
    __large_pool_size = 8388608
    __java_pool_size = 4194304
    __streams_pool_size = 0
    spfile = C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DBS\SPFILEXE.ORA
    sga_target = 805306368
    control_files = C:\ORACLEXE\ORADATA\XE\CONTROL.DBF
    __db_cache_size = 587202560
    compatible = 10.2.0.1.0
    db_recovery_file_dest = C:\oraclexe\app\oracle\flash_recovery_area
    db_recovery_file_dest_size= 10737418240
    undo_management = AUTO
    undo_tablespace = UNDO
    remote_login_passwordfile= EXCLUSIVE
    dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
    shared_servers = 4
    local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=winsp3ue)(PORT=1522))
    job_queue_processes = 4
    audit_file_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\ADUMP
    background_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\BDUMP
    user_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\UDUMP
    core_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\CDUMP
    db_name = XE
    open_cursors = 300
    os_authent_prefix =
    pga_aggregate_target = 268435456
    PMON started with pid=2, OS id=2176
    PSP0 started with pid=3, OS id=2204
    MMAN started with pid=4, OS id=2208
    DBW0 started with pid=5, OS id=2212
    LGWR started with pid=6, OS id=2220
    CKPT started with pid=7, OS id=2240
    SMON started with pid=8, OS id=2460
    RECO started with pid=9, OS id=2464
    CJQ0 started with pid=10, OS id=2480
    MMON started with pid=11, OS id=2484
    Wed Feb 29 22:30:02 2012
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=12, OS id=2492
    Wed Feb 29 22:30:02 2012
    starting up 4 shared server(s) ...
    Oracle Data Guard is not available in this edition of Oracle.
    Wed Feb 29 22:30:02 2012
    alter database mount exclusive
    Wed Feb 29 22:30:06 2012
    Setting recovery target incarnation to 2
    Wed Feb 29 22:30:06 2012
    Successful mount of redo thread 1, with mount id 2657657770
    Wed Feb 29 22:30:06 2012
    Database mounted in Exclusive Mode
    Completed: alter database mount exclusive
    Wed Feb 29 22:30:07 2012
    alter database open
    Wed Feb 29 22:30:07 2012
    Beginning crash recovery of 1 threads
    Wed Feb 29 22:30:07 2012
    Started redo scan
    Wed Feb 29 22:30:15 2012
    Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_2544.trc:
    ORA-00333: redo log read error block 10347 count 6144
    ORA-00312: online log 2 thread 1: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG'
    ORA-27070: async read/write failed
    OSD-04016: Error queuing an asynchronous I/O request.
    O/S-Error: (OS 23) Data error (cyclic redundancy check).
    Waiting for Help
    Regards

    Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_2544.trc:
    ORA-00333: redo log read error block 10347 count 6144
    ORA-00312: online log 2 thread 1: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG'
    ORA-27070: async read/write failed
    OSD-04016: Error queuing an asynchronous I/O request.
    O/S-Error: (OS 23) Data error (cyclic redundancy check).Might your redo log file is corrupted or not exist, check physically. -> C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG
    is it archivelog mode?
    perform fake recovery and open resetlogs.

  • LabView applicatio​n hangs up when scrolling the block diagram

    Hi all.
    I attached you "Main.vi" that is part of my LabView project. I don't know what's going on, but when I scroll the block diagram to the maximum right, the LabView application hangs up. There are a lot of things in this block diagram because is an outline yet. My plan was to make it more structural, but now I can't do anything because this error don't allow me to edit the diagram.
    Please, try to open it (ignore all the dependencies) and check if it hangs up also in your computer.
    If it does, is there any way to recover it? It's really important for me because I don't have any backups since two weeks ago...
    Regards,
    Francisc
    Hi all.
    I attached you "Main.vi" that is part of my LabView project. I don't know what's going on, but when I scroll the block diagram to the maximum right, the LabView application hangs up. There are a lot of things in this block diagram because is an outline yet. My plan was to make it more structural, but now I can't do anything because this error don't allow me to edit the diagram.
    Please, try to open it (ignore all the dependencies) and check if it hangs up also in your computer.
    If it does, is there any way to recover it? It's really important for me because I don't have any backups since two weeks ago...
    Regards,
    Francisco
    Attachments:
    Main (v3.1).vi ‏257 KB

    It didn't hang up on my computer, but it did make me nauseous, luckily I keep a bucket by my desk.
    You might have video card issues. Try this: open the VI, and hit Auto Cleanup, then save. Close LabVIEW, reopen. If that does not work, try to get to the far right side by going to the Front Panel, and double clicking something that will take you there. If you get there successfully, use the disable structure to disable ~ 1/8 or more of the diagram on that side. Save, reopen.
    Richard

  • HT3275 Time Machine error. Unable to complete backup. An error occurred while copying files to the backup volume. Tried restarting, remounting external WD drive. Still cannot backup.

    Time Machine quit backing up files. Bought a new WD external drive. Worked for awhile, then quit backing up. Tried restarting computer, remounting drive. Message: Time Machine Error. Unable to complete backup. An error occurred when copying files. Suggestions?

    Thanks so very much for your help!! I'm boggled by it and now just about ready to dump the whole idea of Time Machine and backup using a cloning program. Maybe TM is only guaranteed to work well with Time Capsule these days?
    Today there again was no backup. I did as you suggested, looked into Console. It showed many lines of "(Error) DiskStore: No block in wakeup" and also repeatedly "(Warning) DiskStore: Ignored bogus fetch...".
    So I created a marker and attempted to initiate a backup, keeping Console open and refreshed. Here's what I got:
    8/19/13 5:18:40.385 PM Console:  Marker - Aug 19, 2013 5:18:40 PM
    8/19/13 5:19:48.844 PM com.apple.backupd: Starting standard backup
    8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.508 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:38ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.510 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:40ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:20.000 PM kernel: USBF:          58091.976          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:20:51.000 PM kernel: USBF:          58122.985          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:21:22.000 PM kernel: USBF:          58153.992          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:21:53.000 PM kernel: USBF:          58185.  2          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:22:24.000 PM kernel: USBF:          58216. 14          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:22:55.000 PM kernel: USBF:          58247. 25          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:23:26.000 PM kernel: USBF:          58278. 41          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:23:57.000 PM kernel: USBF:          58309. 51          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:24:28.000 PM kernel: USBF:          58340. 59          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:24:59.000 PM kernel: USBF:          58371. 68          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:25:30.275 PM xpchelper: for uid: 501 -- timeout while waiting on FSEvents flush; clearing cache.
    8/19/13 5:25:30.000 PM kernel: USBF:          58402. 82          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:26:01.000 PM kernel: USBF:          58433. 96          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:26:32.027 PM com.apple.backupd: Backing up to: /Volumes/TMBackups/Backups.backupdb
    8/19/13 5:26:32.000 PM kernel: USBF:          58464.112          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:27:02.653 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David’s iMac size:37
    8/19/13 5:27:02.657 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David’s iMac size:37
    8/19/13 5:27:03.000 PM kernel: USBF:          58495.121          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:27:12.668 PM com.apple.backupd: Backup failed with error: 2
    During this 9-minute timeframe Finder also was inoperative - according to Activity Monitor: "Not Responding".
    I'm thinking it's the standalone Buffalo backup drive not waking up, and so everything comes to a screeching halt. Do you also think I should abandon TM and just do manual backups every day using a clone program?

Maybe you are looking for