F-90 acquisition error

I use transaction type 100 for F-90, if I enter inter-company vendor, it pops up below message:
Transaction type not possible (Posting to affiliated company)
Message no. AA390
Diagnosis
For the current document, you specified either implicitly (via the customer/vendor), or explicitly (with a manual entry), that this posting is to an affiliated company. In this case, Asset Accounting requires you to use special transaction types.  This enables the system to separately identify such transactions.
Procedure
Check the line items that you have already entered, and the transaction type you entered.
if third party vendor, it is ok, so what's the t-code I use to copy  transtion type 100 and made change, thanks

Hi,
please check the following:                                                                               
A transaction type is used which post against affiliated company      
although no affiliated company has been indicated.                    
  Solution: Please use another transaction type or enter a            
  affiliated company.                                                                               
A transaction type is used which doesn't post against affiliated      
company although a affiliated company has been indicated.             
  Solution: Please use another transaction type or don't enter a      
  affiliated company.                     
regards Bernhard

Similar Messages

  • Acquisition error: can't use transaction type

    I want to use F-91or other t-code to post asset acquisition, my requirement and expected entry is as follows:
    (1)Dr: Asset 1000
    Cr: accumulated depreciation 300(including prior year accumlated depreciation 200, and current year 100)
    Cr: AP vendor-intercompany 700
    (2). in asset explorer, it should have ordinary depreciation , fiscal year start 200, change 100
    I go to AO73 and define a transaction type Z01,using gross method, but when i use F-91, error is below:
    You cannot post with transaction type Z01 here
    Message no. AA495
    Diagnosis
    The transaction type used (Z01) specifies the posting of an acquisition to the asset with the depreciation that has already accrued on the acquisition and production costs.  This type of posting is not possible with the current transaction.
    System Response
    The transaction type is rejected.
    so how to post to AP?  also in ABSO, I can't post to AP vendor account and accumulated depreciation 300 go to value adjustment line in explorer, this is not I wanted, any solution? thanks

    Are you scanning from MP Navigator or ImageCapture?
    on the 10.9 or 10.10 computers I'd download the ICA driver and the Scanner driver, along with the latest version of MP Navigator from the website and install them, then reboot.
    http://usa.canon.com/cusa/support/consumer/scanners/canoscan_series/canoscan_lide210#DriversAndSoftware
    Try to scan using MP Navigator. If you get the error, close MP Navigator and try to scan using ImageCapture. Do you still get the error?
    I'm not including suggestions for El Capitan because there aren't drivers available for it yet, so I wouldnt expect it to work.

  • Vision acquisition error 2147023898

    I'm working with a usb3.0 camera to and labview vision acquisition.
    I just want to have a simple live image.
    in the configuration the image is shown and everything works fine, but when a finish this and run the vi i get an error.
    Error -2147023898 and is undefined in labview.
    Could someone help me with this problem
    in the attacement 2 images show the error and the working configuration
    Attachments:
    ids acquisition.PNG ‏42 KB

    Dont use express vi. Use imaqdx open outside the while loop. Use a snap inside the while loop and use a close outside the loop.

  • PCI 1200 board 2 channel acquisition error -10403

    I have been acquiring single channel data using a PCI1200 board/Igor Pro 4.01 software and NIDAQ tools 1.22 on a Mac running OS 9.2.
    I want to acquire triggered data traces on two channels simultanously. While I am able to run the acquistion in a continuous mode, when I try to acquire a single time limited trace on two channels simultaneously i get an error -10403.
    Is this application possible using this board.

    Ben,
    Your description makes it sound like you are attempting to perform a finite acquisition of two analog input channels. This is definitely possible with the PCI-1200. The description of error -10403 is the following:
    "The specified device does not support the requested action (the driver recognizes the device, but the action is inappropriate for the device)."
    It appears that the IGOR NIDAQ Tools software is making a call to the NI-DAQ driver that is not supported by the PCI-1200. Thus, you may want to verify with WaveMetrics that the IGOR NIDAQ Tools software supports this particular operation. Below, I have included a link to their support resources:
    WaveMetrics Support Resources
    Good luck with your application.
    Spencer S.

  • Asset Acquisition Error: Global Company is not supported

    Dear All
    i am trying to post and asset acquisition through F-90 when i try to save the document i am getting the
    following message
    Global company XXXXX is not supported
    Message no. GI102
    Diagnosis
    The direct posting function could not find the global company specified. The global company has either been entered in the document or read from table T001 based on the transferred company code.  Each global company must be defined in table T880.
    System Response
    Direct posting to General Ledger cannot take place.
    Procedure
    Check the document as well as tables T001 and T880.
    Please tell me how to rectify this problem
    Regards
    Bilal

    Hi Have a look to SE16 if the values are in both tables are the same.
    In SM30 you can fill in the table name  and click on the button Customizing to found where you have to change the settings
    Paul

  • F-90 asset acquisition - error

    Hi
    i m trying to  post asset acqusition , while saving the transaction i m getting one error  :" contact your system administrator , table error"
    "no accounts have been entered for dep area 01 for allocation of (asset) in chart of account ".
    thanx

    Dear Sir,
    Please check whether you have assigned the GL accounts at spro/financial accounting/asset accounting/integration with gl ledger/assign gl accounts. Here you need to select the account determination and assign gl account in balance sheet accounts and depreciation  also.
    Hope this will clarify you
    regards
    harikishan

  • IMAQDX Start Acquisition error

    I have a system deployed with a Basler Racer developed in LV2011.
    I have deployed 15 of these systems and one is getting an error on start:
    -1074360271  Cant find this code in the database.  System is licensed and it appears that the system is opening the camera.  I dont have remote access to the system so it is hard to debug, I have to speculate on the cause of the camera not communicating.
    Possibly a network setting?  This system was working and the camera was priviously plugged into the motherboards networs and the network plugged into the GigE port (since been corrected).
    Anyone seen such behavior?
    Paul Falkenstein
    Coleman Technologies Inc.
    CLA, CPI, AIA-Vision
    Labview 4.0- 2013, RT, Vision, FPGA

    Just want to warn you with something that made me mad a few weeks ago : when you change the network configuration of your GiGE ports it can change the computer ID that NI uses for software activation, which means you'll have to re-activate all NI Softwares.
    When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

  • No video at startup of Labview program gives me error. How do I automatically reacquire periodically?

    I have a PCI 1411 running Labview NI-IMAQ 3.0. I am hooked to a military infrared device. I need to be able to power on the camera with a Labview program. Therefore, I have no video at startup and need to be able to acquire once I start. Now, if no video is running when I start, I never see video and I get an acquisition error. What should I do? Thanks!

    This depends on how you plan to power on the camera. Are going to switch the AC power to the camera, toggle a digital enable line, or send a serial command? Without knowing how this camera works it's difficult to say how to turn it on, but more than likely LabVIEW (with the right hardware) will acommodate your camera.
    Once you have the camera powered, you can proceed with the acquisition as normal. If there's no way to know whether the camera is powered, you could just call a snap command in a loop periodically and exit when you no longer see an error or you get tired of waiting.
    Cheers,
    Brent

  • Can anyone tell me why my Macbook pro keeps crashing

    This is the first report I've had.
    I was thinking it was due to me putting my iPhoto on an external drive but it still crashes when this is unplugged.
    I also have trouble getting back in - booted up  - often taking 3 or 4 goes!!
    Its been doing it for two weeks now and I've only managed to run the Disk Utility check and repair but to no avail.
    I have only had a mac for a short time so don't understand how I can fix things - please, someone, help!!!
    Thank you
    J
    Anonymous UUID:       764EFA51-0C45-707B-3F78-3B2150CD0D7E
    Mon Dec 30 23:04:42 2013
    panic(cpu 2 caller 0xffffff8021233bc4): "Spinlock acquisition timed out: lock=0xffffff80218ca528, lock owner thread=0xffffff802d11f450, current_thread: 0xffffff802d318140, lock owner active on CPU 0x7, current owner: 0xffffff802d11f450"@/SourceCache/xnu/xnu-2422.1.72/osfmk/i386/locks_i386.c:365
    Backtrace (CPU 2), Frame : Return Address
    0xffffff80a1753c80 : 0xffffff8021222f69
    0xffffff80a1753d00 : 0xffffff8021233bc4
    0xffffff80a1753d40 : 0xffffff8021233ad7
    0xffffff80a1753d60 : 0xffffff802124f09d
    0xffffff80a1753d90 : 0xffffff802121659a
    0xffffff80a1753dd0 : 0xffffff80212163b4
    0xffffff80a1753e30 : 0xffffff8021213bdd
    0xffffff80a1753ea0 : 0xffffff8021226ed2
    0xffffff80a1753ed0 : 0xffffff7fa1dc4b68
    0xffffff80a1753ef0 : 0xffffff80216ada80
    0xffffff80a1753f30 : 0xffffff80216ac522
    0xffffff80a1753f80 : 0xffffff80216ac5f7
    0xffffff80a1753fb0 : 0xffffff80212d6aa7
          Kernel Extensions in backtrace:
             com.apple.iokit.IOHIDFamily(2.0)[1185D338-98A5-345E-84F8-E59DF819A61B]@0xffffff 7fa1da6000->0xffffff7fa1e17fff
                dependency: com.apple.driver.AppleFDEKeyStore(28.30)[558B2575-5197-3C4C-BAD2-8CB465638FA8]@ 0xffffff7fa1d9b000
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    13B42
    Kernel version:
    Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
    Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393
    Kernel slide:     0x0000000021000000
    Kernel text base: 0xffffff8021200000
    System model name: MacBookPro8,2 (Mac-94245A3940C91C80)
    System uptime in nanoseconds: 648897422500
    last loaded kext at 270616763113: com.apple.filesystems.msdosfs          1.9 (addr 0xffffff7fa1b74000, size 65536)
    last unloaded kext at 345860447038: com.apple.driver.AppleUSBUHCI          650.4.0 (addr 0xffffff7fa1e68000, size 65536)
    loaded kexts:
    com.apple.driver.AppleHWSensor          1.9.5d0
    com.apple.driver.AudioAUUC          1.60
    com.apple.driver.AGPM          100.14.11
    com.apple.iokit.IOBluetoothSerialManager          4.2.0f6
    com.apple.filesystems.autofs          3.0
    com.apple.driver.AppleMikeyHIDDriver          124
    com.apple.driver.AppleUpstreamUserClient          3.5.13
    com.apple.kext.AMDFramebuffer          1.1.4
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.driver.AppleHDA          2.5.3fc1
    com.apple.driver.AppleMikeyDriver          2.5.3fc1
    com.apple.driver.AppleIntelHD3000Graphics          8.1.8
    com.apple.AMDRadeonX3000          1.1.4
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.AppleMCCSControl          1.1.12
    com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport          4.2.0f6
    com.apple.driver.AppleMuxControl          3.4.12
    com.apple.driver.AppleHWAccess          1
    com.apple.driver.AppleSMCLMU          2.0.4d1
    com.apple.driver.AppleIntelSNBGraphicsFB          8.1.8
    com.apple.driver.AppleLPC          1.7.0
    com.apple.driver.SMCMotionSensor          3.0.4d1
    com.apple.kext.AMD6000Controller          1.1.4
    com.apple.driver.AppleSMCPDRC          1.0.0
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.driver.AppleThunderboltIP          1.0.10
    com.apple.driver.AppleUSBTCButtons          240.2
    com.apple.driver.AppleUSBTCKeyboard          240.2
    com.apple.driver.AppleIRController          325.7
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          35
    com.apple.iokit.SCSITaskUserClient          3.6.0
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCIBlockStorage          2.4.0
    com.apple.driver.AppleUSBHub          650.4.4
    com.apple.driver.AirPort.Brcm4331          700.20.22
    com.apple.driver.AppleFWOHCI          4.9.9
    com.apple.iokit.AppleBCM5701Ethernet          3.6.9b9
    com.apple.driver.AppleSDXC          1.4.0
    com.apple.driver.AppleAHCIPort          2.9.5
    com.apple.driver.AppleUSBEHCI          650.4.1
    com.apple.driver.AppleSmartBatteryManager          161.0.0
    com.apple.driver.AppleRTC          2.0
    com.apple.driver.AppleACPIButtons          2.0
    com.apple.driver.AppleHPET          1.8
    com.apple.driver.AppleSMBIOS          2.0
    com.apple.driver.AppleACPIEC          2.0
    com.apple.driver.AppleAPIC          1.7
    com.apple.driver.AppleIntelCPUPowerManagementClient          216.0.0
    com.apple.nke.applicationfirewall          153
    com.apple.security.quarantine          3
    com.apple.driver.AppleIntelCPUPowerManagement          216.0.0
    com.apple.iokit.IOSCSIBlockCommandsDevice          3.6.0
    com.apple.iokit.IOUSBMassStorageClass          3.6.0
    com.apple.iokit.IOSerialFamily          10.0.7
    com.apple.kext.triggers          1.0
    com.apple.iokit.IOSurface          91
    com.apple.iokit.IOBluetoothFamily          4.2.0f6
    com.apple.driver.DspFuncLib          2.5.3fc1
    com.apple.vecLib.kext          1.0.0
    com.apple.iokit.IOAudioFamily          1.9.4fc11
    com.apple.kext.OSvKernDSPLib          1.14
    com.apple.iokit.IOAcceleratorFamily          98.7.1
    com.apple.driver.AppleSMBusController          1.0.11d1
    com.apple.iokit.IOBluetoothHostControllerUSBTransport          4.2.0f6
    com.apple.driver.AppleBacklightExpert          1.0.4
    com.apple.driver.AppleGraphicsControl          3.4.12
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.driver.AppleSMBusPCI          1.0.12d1
    com.apple.iokit.IONDRVSupport          2.3.6
    com.apple.kext.AMDSupport          1.1.4
    com.apple.AppleGraphicsDeviceControl          3.4.12
    com.apple.driver.AppleSMC          3.1.6d1
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.driver.IOPlatformPluginFamily          5.5.1d27
    com.apple.driver.AppleHDAController          2.5.3fc1
    com.apple.iokit.IOGraphicsFamily          2.3.6
    com.apple.iokit.IOHDAFamily          2.5.3fc1
    com.apple.driver.AppleThunderboltDPInAdapter          2.5.0
    com.apple.driver.AppleThunderboltDPAdapterFamily          2.5.0
    com.apple.driver.AppleThunderboltPCIDownAdapter          1.4.0
    com.apple.driver.AppleUSBMultitouch          240.6
    com.apple.iokit.IOUSBHIDDriver          650.4.4
    com.apple.driver.AppleUSBMergeNub          650.4.0
    com.apple.driver.AppleUSBComposite          650.4.0
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.6.0
    com.apple.iokit.IOBDStorageFamily          1.7
    com.apple.iokit.IODVDStorageFamily          1.7.1
    com.apple.iokit.IOCDStorageFamily          1.7.1
    com.apple.iokit.IOAHCISerialATAPI          2.6.0
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.6.0
    com.apple.driver.AppleThunderboltNHI          1.9.2
    com.apple.iokit.IOThunderboltFamily          2.8.5
    com.apple.iokit.IOUSBUserClient          650.4.4
    com.apple.iokit.IO80211Family          600.34
    com.apple.iokit.IOFireWireFamily          4.5.5
    com.apple.iokit.IOEthernetAVBController          1.0.3b3
    com.apple.driver.mDNSOffloadUserClient          1.0.1b4
    com.apple.iokit.IONetworkingFamily          3.2
    com.apple.iokit.IOAHCIFamily          2.6.0
    com.apple.iokit.IOUSBFamily          650.4.4
    com.apple.driver.AppleEFINVRAM          2.0
    com.apple.driver.AppleEFIRuntime          2.0
    com.apple.iokit.IOHIDFamily          2.0.0
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          278.10
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.AppleKeyStore          2
    com.apple.driver.DiskImages          371.1
    com.apple.iokit.IOStorageFamily          1.9
    com.apple.iokit.IOReportFamily          21
    com.apple.driver.AppleFDEKeyStore          28.30
    com.apple.driver.AppleACPIPlatform          2.0
    com.apple.iokit.IOPCIFamily          2.8
    com.apple.iokit.IOACPIFamily          1.4
    com.apple.kec.corecrypto          1.0
    com.apple.kec.pthread          1
    Unable to gather system configuration information.Model: MacBookPro8,2, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2 GHz, 4 GB, SMC 1.69f4
    Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB
    Graphics: AMD Radeon HD 6490M, AMD Radeon HD 6490M, PCIe, 256 MB
    Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
    Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.100.22)
    Bluetooth: Version 4.2.0f6 12982, 3 services, 23 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: TOSHIBA MK5065GSXF, 500.11 GB
    Serial ATA Device: MATSHITADVD-R   UJ-898
    USB Device: FaceTime HD Camera (Built-in)
    USB Device: Hub
    USB Device: BRCM2070 Hub
    USB Device: Bluetooth USB Host Controller
    USB Device: Apple Internal Keyboard / Trackpad
    USB Device: Hub
    USB Device: IR Receiver
    Thunderbolt Bus: MacBook Pro, Apple Inc., 22.1

    Found this on another site and thought it might help you figure out what's going on. The gist is that some 3rd party extension might be making your system unstable. This will at least tell you what you have on your system and you can decide if you want to unistall anything.
    Kernel panics like the spinlock acquisition error cannot be caused by applications. This is either a hardware defect or a kernel extension malfunction. Especially 3rd-party extensions can have bugs. To get a list of all non-Apple extensions you have to go to the terminal and type the following command: ~ kextstat | grep -v com.apple.
    You’ll get a (probably different) list of extensions as a result:
    Index Refs Address            Size       Wired      Name (Version) <Linked Against> 48    0 0xffffff7f8121b000 0x46000    0x46000    at.obdev.nke.LittleSnitch (3894) <7 5 4 3 1> 49    0 0xffffff7f81a87000 0x3000     0x3000     com.rogueamoeba.InstantOn (6.0.2) <5 4 3 1> 90    0 0xffffff7f81a60000 0x22000    0x22000    com.rogueamoeba.InstantOnCore (6.0.2) <89 5 4 3 1> 100    0 0xffffff7f80fe4000 0x5000     0x5000     com.logmein.driver.LogMeInSoundDriver (1.0.0) <89 5 4 3> 105    0 0xffffff7f807c2000 0x5000     0x5000     com.Cycling74.driver.Soundflower (1.5.3) <89 5 4 3> 124    0 0xffffff7f82c01000 0x18000    0x18000    com.github.osxfuse.filesystems.osxfusefs (2.5.4) <7 5 4 3 1>
    Try deinstalling these and test if your system stops crashing. If you’ll still get crashes, it’ll probably be a hardware defect. You can either try to run a hardware test or even better: contact Apple support.

  • Reading status of camera's connected to CVS

    i have 3 cameras connected to 1 CVS.I want to read the status of the cameras whether they are healthy or not and also the CVS status to display in PC at remote location. So, how i can access(read) this data from the CVS into the labview software to generate fault message or output as alarm. please suggest us the solution.

    When using LabVIEW RT all VIs are targeted to the CVS and executed by the RT Engine. The RT Development System (your remote PC) displays the front panel of the VI while the RT Engine executes the block diagram code. Therefore, to determine if the cameras connected to your CVS are "healthy", check for acquisition errors from the cameras (such as a timeout error) in the VI running on the CVS, and then illuminate an LED or display a message on the front panel of the remote PC if an error occurs.
    You could also use something called a watchdog timer to monitor software on the CVS and to take action if the software is not responding. The watchdog timer is described in more detail on page 4-10 of the Compact Vision System User Manual and in the tutorials below:
    NI 1450 Series Compact Vision System User Manual
    Developer Zone Tutorial: Software Watch-Dog Timers
    Developer Zone Tutorial: Using a Hardware or Software Watchdog in a Real-Time Application
    I hope this helps! Best wishes with your application.
    Kind regards,
    Dawna P.
    Applications Engineer
    National Instruments

  • PXI Controller will not boot when 6071E is in chassis. (new problem).

    My PXI contoller stopped upon an acquisition error, and then would not reboot until I removed the 6071E card from the chassis. When I put the 6071E back in the chassis the controller again fails to boot.

    I agree.  It sounds initially as though it is a faulty card.  I would try the card in a different slot and if possible, try a different card.  If niether of these solves the issue, then I would call in and RMA the card.
    -Jeff P.
    National Instruments Applications Engineer
    Jeffrey P.
    LabVIEW Product Management
    National Instruments

  • Bad quality colorbust

    I have a IMAQ 1408 and a NTSC camera (alm-2451g wireless microcamera,
    like this: http://www.prymesecurity.com/2451g.htm ) and i can't snap
    Still-color images because i get this acquisition error message:
    bad quality colorbust.
    I know that colorbust is color synchronization signal: someone can
    tell me why IMAQ 1408 can't find it?
    With other acquisition cards i can capture color videos and images
    easy, but with IMAQ 1408 i can just snap and grab in monochromatic
    mode (selecting disabled in "still color" combo).

    Hello.
    With other acquisition cards i can capture color videos and images
    easy, but with IMAQ 1408 i can just snap and grab in monochromatic
    mode (selecting disabled in "still color" combo)
    This is a little surprising, as the error message that you get is almost always related to a non-color camera being connected to a PCI-1408 (or 1409) in still-color mode. This error comes when the signal is not as expected. Based on what you have mentioned, I am guessing this is a composite color camera. There are only a few remaining things to check/change:
    1. Be sure composite is selected in the still-color mode.
    2. Be sure that NTSC is selected as the camera (right-click on channel and select Camera_NTSC).
    3. Go to the property page for the channel and ve
    rify that the reference voltages and other settings are according to the specs of the camera.
    I hope this helps lead to the answer!
    Regards,
    Colin C.
    Applications Engineering
    Colin Christofferson
    Community Web Marketing
    Blog

  • PCI-1422 Windows7 32bit Problems

    I have a legacy program that I am trying to port from WindowsXP to 32bit version of Windows7.  This program is based on the PCI-1422 frame grabber.
    For historical purposes, I have to use NI-IMAQ version 2.5.3, which installs version 2.0.3.17 of NI-MAX
    From a clean build of Win7 x32, I can install NI software, and the old application which creates correct camera definition files.
    When I add the frame grabber card, Windows device manager is happy... the card is correctly identified and seems to use driver files which match the old WinXP install.
    When I look at the card with NI-MAX, the camera correctly appears in the configuration list.  If I highlight Channel 0 device and run 'Diagnostic' all tests seem to pass correctly.  (Again the displayed output matches the results from the same operation on the old WinXP box)
    However if I try to 'Snap' or  'Grab' a frame, I get the following error box:  Title = 'Acquisition Error'   and there is NO TEXT in the error description, only a yellow ! warning icon.
    (The legacy program performs all controlling functions via two other PCI cards, but halts when trying to grab a frame as well.  The above behavior can be seen with or without these additional PCI cards)
    I have tried both installing and executing the EXE files with or without 'Run as Admin'  and/or 'WinXP SP3 compatibility mode'.  In some cases, the available camera list disappears, but nothing I have done has been succesful at grabbing a frame from the camera.
    Any suggestions about compatibility and/or why the error box is missing all text?
    Thanks in advance,
    Jim

    Good questions...
    I have been asked to 'upgrade' a commercial system that was developed 10 years ago.  The system works currently... an XP based system with old frame grabber.   I was asked if I could upgrade the PC, because of concerns of PC failure with a 10 yr old box.  We found a new motherboard that supports the necesary 3 PCI slots for frame grabber, and newer CPU of course.
    The question remains however, can we migrate to Win7, or...   do we try to install WinXP on the new PC hardware, with the older interface cards.  To add to the difficulties, the original company than produced the software is no longer in business.  Fortunately I have remained in contact with some of the developers that are giving me some support, but they haven't supported the product for years either.
    The basic issue remains...  hardware and software that worked on XP, has been migrated. The devices appear in some sense to be detected correctly.  But the critical important issue, grabbing a frame from the camear, fails.  What can be done?

  • DAQCard6062E hangs intermittently during acq

    Code written in VC++ 6.0, NIDAQ 6.9.3, OS: Win2000&98, various laptops from P2-450MHz to P3-1.2GHz.
    Using SCAN_Start for continuous mode acquisition to a single buffer (16 channels, 20KHz). After a variable number of samples acquired (usually around 1e6 to 14e6), acquisition hangs. At this point DAQ_Monitor returns error -10845 (overFlowError) once, and then -10608 (noTransferInProgError) thereafter. At this point, the acquisition must be stopped and restarted.
    The hangs only occur after many cycles through the acquisition buffer, so I don't think it is a buffer boundary problem. Hangs also occur even if there are no transfers to secondary buffers (via DAQ_Monitor), so I don't think it's a memory access conflict.
    Greatly lowering acquisition bandwidth (e.g. 20kHz X 1 channel) eliminates the problem, but the driver hangs at acquisition rates well below maximum bandwidth (e.g. it hangs using 20kHz X 8 channels = 160KHz aggregate).
    I have included a simple console app that demonstrates the problem. This app does not actually do anything but monitor the acquisition once it starts. When the acquisition hangs, a beeping message is displayed.
    I hope someone can help me solve this problem, or at least tell me what I'm doing wrong. I am at wit's end!
    John Burt
    Attachments:
    daqtest1.zip ‏52 KB

    John,
    Actually, the error -10845 is a hardware, not software, overflow error. This error occurs when the NI-DAQ driver cannot read data from the DAQ device's FIFO buffer fast enough to keep up with the acquired data. In your case, this is probably because the FIFO buffers on a PCMCIA card are much smaller than those found on a PCI card. Furthermore, the PCMCIA bus does not support Direct Memory Access (DMA) which is used for fast transfer. The DAQCards rely on interrupts to transfer data from their FIFO to PC memory. Unlike DMA transfers, interrupt transfers consume processor time and are thus highly system dependent. Additionally, they are much slower than DMA transfers.
    There are two primary solutions to this issue. There are lowering the sampl
    e rate or using a much faster computer to process the interrupts at a higher rate. Additionally, the FIFO on this board is limited to 8,192 samples. You should ensure that you are not acquiring more than this many samples at a time.
    Please reference the following Knowledge Base article for more information on this subject.
    Data Acquisition Errors -10845 and -10846, What Is the Difference?
    http://digital.ni.com/public.nsf/websearch/70C74F12DC728114862568EB007F5338?OpenDocument
    Regards,
    Justin Britten
    Applications Engineer
    National Instruments

  • Can i reset nidaq status codes, after +10846 code?

    (sorry for my english) I use nidaq with hard real-time acquisistion in win2000, in double-buffered mode. Sometimes, my application, don't read the halfbuffer and 10846 code (is plus, is a warning) occur. After, every check of DAQ_DB_HalfReady return 10846 code, and i can't see if another failure in read occur. How can i reset the status code? Thanks, Piero.

    Search the Knowledge Base for the document titled "What Is the Difference between Data Acquisition Errors -10845 and -10846?" It will explain what the error is and how to correct it.
    The status code is updated and returned after each function call in NI-DAQ. There is no function call to go in and clear the error condition in the DAQ device (this is an eror in the software buffer anyway, not the hardware, so NI-DAQ may actually be generating it, not a status bit on the card). If subsequent functions generate an error (or message) then you can ignore it or write a wrapper for whatever error handling routines you are using to clear the value of the status variable. Error handling is something you should handle in software; but, most people use the error handler in th
    e examples folders.

Maybe you are looking for