SR830 VERY unreliable data transfer

Please help!
I am using the Stanford Research SR830 Lockin Amplifier and I need to transfer the data from the instrument buffer to my computer. Usually this would just be a simple GPIB write/read sequence. I am using the SPTS? command to query the number of points in the buffer and the TRCL? command to write the data into the I/O buffer. The program sometimes runs successfully but in most of the cases it fails. It seems there always remains some garbage in the buffer or that the transfer is not ready when I want to read the data.
I looked-up the LabView help and fell on the concept of Service Requests. I subsequently modified the program to include SRQ. This should prevent that I read the data too early. So a typical command sequence would be *CLS;*SRE16;TRCL?1,0,{number of points}
So how does this work? *CLS; should clear the whole status register; *SRE16 enables status bit number 4 (2^4=16) which is the service request bit. The vi SRQ wait should continuously query when the SRQ status bit changes. All this should make the data query much more reliable. In practice what happens is that the VI waits in wain for SRQ until it times-out. I put the time-out value up to 60 seconds, this should definitely be enough to transfer 1000 data points. I don't understand what is wrong. I also tried the NI packet GPIB spy to monitor the traffic on the GPIB bus and everything seems to be normal. I attached the Labview library. Any ideas?
Attachments:
SR830_VISA_binary_transfer.llb ‏91 KB

Hi David,
I noticed you said you used GPIB spy.  I was wondering what version of the 488.2 and VISA drivers you had? 
Also, I was wondering if you had tried using the LabVIEW instrument driver for the SR830?  If you have a 488.2 instrument, you should be able to use this driver.  There are a few exaple vi's including a Data Storage Example that recovers data from the instrument's buffer.  It may be worth a look if you haven't already tried it.
Hope this helps!
Adam W
National Instruments

Similar Messages

  • VERY slow data transfer to my hard drive attached to the Airport Extreme

    Hi
    Ive got a Macbook Pro and Mac Pro. In order to access large files from both I got a 2TB drive connected to my Airport Extreme and it shows up fine in both Macs under SHARED.
    When I copy files from and to that harddrive from my Macbook Pro its impressively fast. Seems as fast as a USB stick.
    However when I try to do the same with my Mac Pro its extremely slow. A 1GB file takes about 15 minutes.
    Are there any settings that I might have overlooked on the Mac Pro?
    Thanks
    Jorg

    This won't be of any help for you , but I happen to have the exact same problem. My AEBs is linked to a LaCie external HD, my wireless network include a macmini aluminum, a Macbook Air, a MacBook Pro, a MacPro Dual-COre Intel 2.66 GHz. . Everything works fine expect for the MacPro which is painfully slow to get data to and from. The MacPro Airport Card is of the Airport Extreme type (0x14E4, 0x87), like my other macs…
    I use WPA2 with a n protocol to connect to the base station.
    Still at a loss about this issue, wonder how to solve it…

  • TM with very, very slow data transfer (700 MB/h)

    Hello Dear Mac-Users,
    After changing my DSL modem my TM works very, very slowly. Normally I store on an external hard drive, divided into three partitions, one for my MacMini, MacBook and my iMac. Except my iMac everything works fine. Does anyone have an idea what's going wrong at the moment? Did I have to delete some old *.plist? I am grateful for any good proposal.
    Frank

    Does that iMac connect to the Time Capsule via Wi-Fi?  On any of your Macs that use a Wi-Fi connection, hold down an "option" key while you pull down the Wi-Fi menu bar item.  Report here the values of RSSI that you see.

  • Data transfer very slow on mac pro!! mac H/W unable to fit specifications.

    Hi,
    I am installinginternal disks on the quad mac pro and the transfer ratet in the mac are very slow!!!
    the disks are: barracuda 7200.10 disks, 500 GB. Sta II 300, max ST3500630AS firmware 3.AAE . throughput:300mb.jumpred off to get the 300.
    MAC tells that the QUAD MAC Pro equipment (2x2.66ghz dualcore intel xeon) comes with a 3.Gigabit specification/ 300MB/sec. (Intel ESB2 AHCI, speed: 3.0 Gigabit. AHCI version 1.10 supported)...
    And the benchmarks of the disk ST3500630AS show maximum 80MB/sec and a minimin of 37.3MB/sec, average 63.1 MB/sec. (anandtech tests).
    According to seagate.com the maximum sustained data transfer rate:78MB/s
    but in the mac the reallity is different: I am getting a transfer rate of 22MB/sec!!!!! . with out any application running and only making copy of the files!!!!
    that means that the mac is only providing only 1/3 of the expected transfer rate for the disks..
    so, is there a way that the MAC Pro gets all the normal transfer rate for those disks???
    Is the Quad MAC Pro hardware unable to get the maximum throughput of the disks???
    It seems that the mac is unable to get also the average transfer rate of those disks.. how to correct it???
    thanks a lot
    Alberto
    ps. just for fun: I am getting a faster transfer rate from an old power pc ,and old pc, and firewire 400 and old ide disks!!! (36MB/seg!!!)

    Yup.
    BThe latest Mac Pro are better, so if you have a new or 2 month old unit, Seagate should work, though I think there should be later firmware.
    Some would say those drives take the cake or woRSe.
    http://www.barefeats.com/hard91.html
    SEAGATE PUZZLES
    +Firmware version 3.AEE or later solves the slow sustained large block write speed issue for a single 7200.10 inside the Mac Pro.+
    +The remaining performance issue is slow small random read speeds for one, two, three or four drives. No matter how many drives you configure in RAID 0 sets, the average random read speed for combined block sizes from 64K to 1024K is less than 30MB/s (based on QuickBench 3 testing).+
    +Until Seagate fixes this, we can't recommend the 7200.10 series as the ideal boot drive for the Mac Pro (or Power Mac).+
    http://www.barefeats.com/quad08.html

  • Very slow network directory listing - but fast data transfer speed once listed?

    Hello,
    I have really tried to sort this myself before opening up to the community, however I have run out of ideas, and hope someone can offer the magic solution I have missed.
    I am currently using the 3.4ghz i7 iMac on a 1GB LAN, running OSX10.7.2 - connecting to a Windows Server 2008 (Running Release 2) over ethernet.
    If i go to a network directory that i haven't recently accessed it can take up to 60 seconds to show the contents of that directory. Once i have accessed that folder, if i come out of it and go back in it will be instant again - but the first time it lists the directory it looks like i have opened an empty folder - which after anything from 10seconds to 1 minute will suddenly show the files that are there.
    Internet connectivity is fast through the network, and file transfers across the LAN are fast. (showing as approx 300mb per second) I can play and edit HD content across the network with no slowdown so I am confident that this issue is not related to the network speed itself, and is more to do with a setting on this mac.
    Symptoms are very similar to this post: https://discussions.apple.com/message/12245148?messageID=12245148&amp%3b#1224514 8 - however i understand that in OSX Lion - SMB was removed - so i cannot find this file to edit.
    I have tried bypassing additional hubs in the network by wiring direct cables to the switch that is connected to the file server, this made no difference.
    I have also tried disconnecting the ethernet cable, and running over wifi. This fixes the listing problem, but when editing HD content over a network drive, this connection is not fast enough to carry the data without interruption (some projects are linked to up to 900gb of hd video content!)
    Using ethernet, I have tried DHCP, DHCP with manual address, and manual mode. All reproduce this problem. i have tried using the windows workgroup, and tried without it.
    I have also followed this suggestion: https://discussions.apple.com/thread/2134936?threadID=2134936&tstart=45 and used OpenDNS. this did not fix the issue.
    For argument sake, I have also just tested a Macbook Pro running Snow Leopard to see if it was OS related. This reproduces the exact same problem, near instant directory listing on the wifi, a long and arduous wait on ethernet.
    I cannot work out why directory listing is instant over wifi, but not over ethernet on 2 different macs, running 2 different versions of OSX. I also do not understand why if the network is having trouble listing the directories - the data transfer speed is 300mbps when i copy files across the wired network from the file server to the mac.
    Does anyone have any other ideas as to what could be the problem here? We are about to start work on a very large project, where the content we are editing is spread out across around 200 different network folders (different shoots captured over the past 2 years). We really don't have the time to wait 60 seconds each time we need to access one of those directories to look for a file, and I am very close to pulling all my hair out!
    I really look forward to hearing from anyone who can offer any insight.

    If you are suspecting that the Windows update had something to do with your LAN going slow, then try the following:
    1.  Look for updates for your clients LAN NIC driver; or
    2.  Un-install the updates.

  • Internal Disk to Disk Data Transfer Speed Very Slow

    I have a G5 Xserve running Tiger with all updates applied that has recently started experiencing very slow Drive to Drive Data transfer speeds.
    When transferring data from one drive to another ( Internal to Internal, Internal to USB, Internal, Internal to FW, USB to USB or any other combination of the three ) we only are getting about 2GB / hr transfer speeds.
    I initially thought the internal drive was going bad. I tested the drive and found some minor header issues etc... that were able to be repaired so I replace the internal boot drive
    I tested and immediately got the same issue.
    I also tried booting from a FW drive and I got the same issue.
    If I connect to the server over the ethernet network, I get what I would expect to be typical data transfer rates of about 20GB+ / hr. Much higher than the internal rates and I am copying data from the same internal drives so I really don't think the drive is the issue.
    I called AppleCare and discussed the issue with them. They said it sounded like a controller issue so I purchased a replacement MLB from them. After replacing the drive data transfer speeds jumped back to normal for about a day maybe two.
    Now we are back to experiencing slow data transfer speeds internally ( 2GB / hr ) and normal transfer speeds ( 20GB+ / hr ) over the network.
    Any ideas on what might be causing the problem would be appreciated

    As suggested, do check for other I/O load on the spindles. And check for general system load.
    I don't know of a good GUI in-built I/O monitor here (and particularly for Tiger Server), though there is iopending and DTrace and Apple-provided [performance scripts|http://support.apple.com/kb/HT1992] with Leopard and Leopard Server. top would show you busy processes.
    Also look for memory errors and memory constraints and check for anything interesting in the contents of the system logs.
    The next spot after the controllers (and it's usually my first "hardware" stop for these sorts of cases, and usually before swapping the motherboard) are the disks that are involved, and whatever widgets are in the PCI slots. Loose cables, bad cables, and spindle-swaps. Yes, disks can sometimes slow down like this, and that's not usually a Good Thing. I know you think this isn't the disks, but that's one of the remaining common hardware factors. And don't presume any SMART disk monitoring has predictive value; SMART can miss a number of these cases.
    (Sometimes you have to use the classic "field service" technique of swapping parts and of shutting down software pieces until the problem goes away. Then work from there.)
    And the other question is around how much time and effort should be spent on this Xserve G5 box; whether you're now in the market for a replacement G5 box or a newer Intel Xserve box as a more cost-effective solution.
    (How current and how reliable is your disk archive?)

  • Oracle VM 2.2.2 - TCP/IP data transfer  is very slow

    Hi, i've encountered a disturbing problem with OVM 2.2.2.
    My dom0 network setup (4 identical servers):
    eth0/eth1 (ixbe 10gbit) -> bond0 (mode=1) -> xenbr0 -> domU vif's
    Besides bonding setup, it's default OVM 2.2.2 installation.
    Problem description:
    TCP/IP data dransfer speed:
    - between two dom0 hosts: 40-50MB/s
    - between two domU hosts within one dom0 host: 40-50MB/s
    - between dom0 and locally hosted domU: 40-50MB/s
    - between any single domU and anything outside it's dom0 host: 55KB/s -
    something is definitely wrong here.
    domU network config:
    vif = ['bridge=xenbr0,mac=00:16:3E:46:9D:F1,type=netfront']
    vif_other_config = []
    I have similar installation on Debian/Xen, and everything is running
    fine, e.g. i don't have any data transfer speed related issues.
    regards
    Robert

    There is also an issue with the ixgbe driver in the stock OVM2.2.2 kernel (bug:1297057 on MoS). We were getting abysmal results for receive traffic (measured in hundreds of kilobytes!!! per second at times) compared to transmit. It's not exactly the same as your problem, so don't blindly follow what I say below!!!
    ### "myserver01" is a PV domU on Oracle VM 2.2.2 server running stock kernel ###
    [root@myserver02 netperf]# ./netperf -l 60 -H myserver01 -t TCP_STREAM
    MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to myserver01.mycompany.co.nz (<IP>) port 0 AF_INET
    Recv Send Send
    Socket Socket Message Elapsed
    Size Size Size Time Throughput
    bytes bytes bytes secs. 10^6bits/sec
    87380 16384 16384 60.23 1.46
    ### Repeat the test in the opposite direction, to show TX is fine from "myserver01" ###
    [root@myserver01 netperf]# ./netperf -l 60 -H myserver02 -t TCP_STREAM
    MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to myserver02.mycompany.co.nz (<IP>) port 0 AF_INET
    Recv Send Send
    Socket Socket Message Elapsed
    Size Size Size Time Throughput
    bytes bytes bytes secs. 10^6bits/sec
    87380 16384 16384 60.01 2141.59
    In my case, a workaround as advised by Oracle Support is to run:
    ethtool -C eth0 rx-usecs 0
    ethtool -C eth1 rx-usecs 0
    against the slaves within your bond group. This will give you better performance (in my case, got up to ~1.2GBit/s), although there are some fixes coming out in the next kernel which get even better speeds (in my tests, ~2.2GBit/s):
    Edited by: user10786594 on 11/09/2011 02:22

  • Very high volumes of data transfer on ethernet.

    Since upgrading to Leopard the volume of network data transfer has gone through the roof! Enough to force me to go over my broadband limit and have to pay penalty charges. Just sitting here this morning for 4 hours the system clocked up 100MB out (Tx) and 300MB incoming (Rx).
    Does anyone know how to turn this off?

    As far as I can tell, there is nothing inherent in Leopard that makes it use more bandwidth than Tiger. You need to identify which applications are using the bandwidth and take appropriate action.
    Questions:
    1) Are you using a file syncing service such as DropBox or iDisk?
    2) Could it be iTunes?
    3) Did you download any software updates automatically?
    4) Do you have Mail set up with an IMAP account (like Gmail) with automatic polling?
    To identify which applications have a network connection established, open Terminal and enter:
    $ lsof | grep IPv | grep ESTABLISHED
    Don't enter the "$" - that represents the command prompt. THe command will list all "open files", using an Internet Protocol connection that is ESTABLISHED.
    Regards,
    Rodney

  • How to find the max data transfer rate(disk speed) supported by mobo?

    I plan on replacing my current HDD with a new and bigger HDD.
    For this I need to know the max data transfer rate(disk speed) that my mobo will support. However, dmidecode is not telling me that. Am I missing something?
    Here's dmidecode:
    # dmidecode 2.11
    SMBIOS 2.5 present.
    80 structures occupying 2858 bytes.
    Table at 0x000F0450.
    Handle 0xDA00, DMI type 218, 101 bytes
    OEM-specific Type
    Header and Data:
    DA 65 00 DA B2 00 17 4B 0E 38 00 00 80 00 80 01
    00 02 80 02 80 01 00 00 A0 00 A0 01 00 58 00 58
    00 01 00 59 00 59 00 01 00 75 01 75 01 01 00 76
    01 76 01 01 00 05 80 05 80 01 00 D1 01 19 00 01
    00 15 02 19 00 02 00 1B 00 19 00 03 00 19 00 19
    00 00 00 4A 02 4A 02 01 00 0C 80 0C 80 01 00 FF
    FF 00 00 00 00
    Handle 0xDA01, DMI type 218, 35 bytes
    OEM-specific Type
    Header and Data:
    DA 23 01 DA B2 00 17 4B 0E 38 00 10 F5 10 F5 00
    00 11 F5 11 F5 00 00 12 F5 12 F5 00 00 FF FF 00
    00 00 00
    Handle 0x0000, DMI type 0, 24 bytes
    BIOS Information
    Vendor: Dell Inc.
    Version: A17
    Release Date: 04/06/2010
    Address: 0xF0000
    Runtime Size: 64 kB
    ROM Size: 4096 kB
    Characteristics:
    PCI is supported
    PNP is supported
    APM is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    ESCD support is available
    Boot from CD is supported
    Selectable boot is supported
    EDD is supported
    Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    ACPI is supported
    USB legacy is supported
    BIOS boot specification is supported
    Function key-initiated network boot is supported
    Targeted content distribution is supported
    BIOS Revision: 17.0
    Handle 0x0100, DMI type 1, 27 bytes
    System Information
    Manufacturer: Dell Inc.
    Product Name: OptiPlex 755
    Version: Not Specified
    UUID: 44454C4C-5900-1050-8033-C4C04F434731
    Wake-up Type: Power Switch
    SKU Number: Not Specified
    Family: Not Specified
    Handle 0x0200, DMI type 2, 8 bytes
    Base Board Information
    Manufacturer: Dell Inc.
    Product Name: 0PU052
    Version:
    Handle 0x0300, DMI type 3, 13 bytes
    Chassis Information
    Manufacturer: Dell Inc.
    Type: Space-saving
    Lock: Not Present
    Version: Not Specified
    Asset Tag:
    Boot-up State: Safe
    Power Supply State: Safe
    Thermal State: Safe
    Security Status: None
    Handle 0x0400, DMI type 4, 40 bytes
    Processor Information
    Socket Designation: CPU
    Type: Central Processor
    Family: Xeon
    Manufacturer: Intel
    ID: 76 06 01 00 FF FB EB BF
    Signature: Type 0, Family 6, Model 23, Stepping 6
    Flags:
    FPU (Floating-point unit on-chip)
    VME (Virtual mode extension)
    DE (Debugging extension)
    PSE (Page size extension)
    TSC (Time stamp counter)
    MSR (Model specific registers)
    PAE (Physical address extension)
    MCE (Machine check exception)
    CX8 (CMPXCHG8 instruction supported)
    APIC (On-chip APIC hardware supported)
    SEP (Fast system call)
    MTRR (Memory type range registers)
    PGE (Page global enable)
    MCA (Machine check architecture)
    CMOV (Conditional move instruction supported)
    PAT (Page attribute table)
    PSE-36 (36-bit page size extension)
    CLFSH (CLFLUSH instruction supported)
    DS (Debug store)
    ACPI (ACPI supported)
    MMX (MMX technology supported)
    FXSR (FXSAVE and FXSTOR instructions supported)
    SSE (Streaming SIMD extensions)
    SSE2 (Streaming SIMD extensions 2)
    SS (Self-snoop)
    HTT (Multi-threading)
    TM (Thermal monitor supported)
    PBE (Pending break enabled)
    Version: Not Specified
    Voltage: 0.0 V
    External Clock: 1333 MHz
    Max Speed: 5200 MHz
    Current Speed: 2666 MHz
    Status: Populated, Enabled
    Upgrade: Socket LGA775
    L1 Cache Handle: 0x0700
    L2 Cache Handle: 0x0701
    L3 Cache Handle: Not Provided
    Serial Number: Not Specified
    Asset Tag: Not Specified
    Part Number: Not Specified
    Core Count: 2
    Core Enabled: 2
    Thread Count: 2
    Characteristics:
    64-bit capable
    Handle 0x0700, DMI type 7, 19 bytes
    Cache Information
    Socket Designation: Not Specified
    Configuration: Enabled, Not Socketed, Level 1
    Operational Mode: Write Back
    Location: Internal
    Installed Size: 32 kB
    Maximum Size: 32 kB
    Supported SRAM Types:
    Other
    Installed SRAM Type: Other
    Speed: Unknown
    Error Correction Type: None
    System Type: Data
    Associativity: 8-way Set-associative
    Handle 0x0701, DMI type 7, 19 bytes
    Cache Information
    Socket Designation: Not Specified
    Configuration: Enabled, Not Socketed, Level 2
    Operational Mode: Varies With Memory Address
    Location: Internal
    Installed Size: 6144 kB
    Maximum Size: 6144 kB
    Supported SRAM Types:
    Other
    Installed SRAM Type: Other
    Speed: Unknown
    Error Correction Type: Single-bit ECC
    System Type: Unified
    Associativity: <OUT OF SPEC>
    Handle 0x0800, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: PARALLEL
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: DB-25 female
    Port Type: Parallel Port PS/2
    Handle 0x0801, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: SERIAL1
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: DB-9 male
    Port Type: Serial Port 16550A Compatible
    Handle 0x0802, DMI type 126, 9 bytes
    Inactive
    Handle 0x0803, DMI type 126, 9 bytes
    Inactive
    Handle 0x0804, DMI type 126, 9 bytes
    Inactive
    Handle 0x0805, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: USB1
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: Access Bus (USB)
    Port Type: USB
    Handle 0x0806, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: USB2
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: Access Bus (USB)
    Port Type: USB
    Handle 0x0807, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: USB3
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: Access Bus (USB)
    Port Type: USB
    Handle 0x0808, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: USB4
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: Access Bus (USB)
    Port Type: USB
    Handle 0x0809, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: USB5
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: Access Bus (USB)
    Port Type: USB
    Handle 0x080A, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: USB6
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: Access Bus (USB)
    Port Type: USB
    Handle 0x080B, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: USB7
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: Access Bus (USB)
    Port Type: USB
    Handle 0x080C, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: USB8
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: Access Bus (USB)
    Port Type: USB
    Handle 0x080D, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: ENET
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: RJ-45
    Port Type: Network Port
    Handle 0x080E, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: MIC
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: Mini Jack (headphones)
    Port Type: Audio Port
    Handle 0x080F, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: LINE-OUT
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: Mini Jack (headphones)
    Port Type: Audio Port
    Handle 0x0810, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: LINE-IN
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: Mini Jack (headphones)
    Port Type: Audio Port
    Handle 0x0811, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: HP-OUT
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: Mini Jack (headphones)
    Port Type: Audio Port
    Handle 0x0812, DMI type 8, 9 bytes
    Port Connector Information
    Internal Reference Designator: MONITOR
    Internal Connector Type: None
    External Reference Designator: Not Specified
    External Connector Type: DB-15 female
    Port Type: Video Port
    Handle 0x090A, DMI type 9, 13 bytes
    System Slot Information
    Designation: SLOT1
    Type: x1 Proprietary
    Current Usage: In Use
    Length: Long
    Characteristics:
    PME signal is supported
    Handle 0x0901, DMI type 126, 13 bytes
    Inactive
    Handle 0x0902, DMI type 9, 13 bytes
    System Slot Information
    Designation: SLOT2
    Type: 32-bit PCI
    Current Usage: Available
    Length: Long
    ID: 2
    Characteristics:
    5.0 V is provided
    3.3 V is provided
    PME signal is supported
    Handle 0x0903, DMI type 126, 13 bytes
    Inactive
    Handle 0x0904, DMI type 126, 13 bytes
    Inactive
    Handle 0x0905, DMI type 126, 13 bytes
    Inactive
    Handle 0x0906, DMI type 126, 13 bytes
    Inactive
    Handle 0x0907, DMI type 126, 13 bytes
    Inactive
    Handle 0x0908, DMI type 126, 13 bytes
    Inactive
    Handle 0x0A00, DMI type 10, 6 bytes
    On Board Device Information
    Type: Video
    Status: Disabled
    Description: Intel Graphics Media Accelerator 950
    Handle 0x0A02, DMI type 10, 6 bytes
    On Board Device Information
    Type: Ethernet
    Status: Enabled
    Description: Intel Gigabit Ethernet Controller
    Handle 0x0A03, DMI type 10, 6 bytes
    On Board Device Information
    Type: Sound
    Status: Enabled
    Description: Intel(R) High Definition Audio Controller
    Handle 0x0B00, DMI type 11, 5 bytes
    OEM Strings
    String 1: www.dell.com
    Handle 0x0D00, DMI type 13, 22 bytes
    BIOS Language Information
    Language Description Format: Long
    Installable Languages: 1
    en|US|iso8859-1
    Currently Installed Language: en|US|iso8859-1
    Handle 0x0F00, DMI type 15, 29 bytes
    System Event Log
    Area Length: 2049 bytes
    Header Start Offset: 0x0000
    Header Length: 16 bytes
    Data Start Offset: 0x0010
    Access Method: Memory-mapped physical 32-bit address
    Access Address: 0xFFF01000
    Status: Valid, Not Full
    Change Token: 0x00000018
    Header Format: Type 1
    Supported Log Type Descriptors: 3
    Descriptor 1: POST error
    Data Format 1: POST results bitmap
    Descriptor 2: System limit exceeded
    Data Format 2: System management
    Descriptor 3: Log area reset/cleared
    Data Format 3: None
    Handle 0x1000, DMI type 16, 15 bytes
    Physical Memory Array
    Location: System Board Or Motherboard
    Use: System Memory
    Error Correction Type: None
    Maximum Capacity: 8 GB
    Error Information Handle: Not Provided
    Number Of Devices: 4
    Handle 0x1100, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x1000
    Error Information Handle: Not Provided
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 1024 MB
    Form Factor: DIMM
    Set: None
    Locator: DIMM_1
    Bank Locator: Not Specified
    Type: DDR2
    Type Detail: Synchronous
    Speed: 667 MHz
    Manufacturer: AD00000000000000
    Handle 0x1101, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x1000
    Error Information Handle: Not Provided
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 1024 MB
    Form Factor: DIMM
    Set: None
    Locator: DIMM_3
    Bank Locator: Not Specified
    Type: DDR2
    Type Detail: Synchronous
    Speed: 667 MHz
    Handle 0x1102, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x1000
    Error Information Handle: Not Provided
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 1024 MB
    Form Factor: DIMM
    Set: None
    Locator: DIMM_2
    Bank Locator: Not Specified
    Type: DDR2
    Type Detail: Synchronous
    Speed: 667 MHz
    Handle 0x1103, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x1000
    Error Information Handle: Not Provided
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 1024 MB
    Form Factor: DIMM
    Set: None
    Locator: DIMM_4
    Bank Locator: Not Specified
    Type: DDR2
    Type Detail: Synchronous
    Speed: 667 MHz
    Handle 0x1300, DMI type 19, 15 bytes
    Memory Array Mapped Address
    Starting Address: 0x00000000000
    Ending Address: 0x000FDFFFFFF
    Range Size: 4064 MB
    Physical Array Handle: 0x1000
    Partition Width: 1
    Handle 0x1400, DMI type 20, 19 bytes
    Memory Device Mapped Address
    Starting Address: 0x00000000000
    Ending Address: 0x0007FFFFFFF
    Range Size: 2 GB
    Physical Device Handle: 0x1100
    Memory Array Mapped Address Handle: 0x1300
    Partition Row Position: 1
    Interleave Position: 1
    Interleaved Data Depth: 1
    Handle 0x1401, DMI type 20, 19 bytes
    Memory Device Mapped Address
    Starting Address: 0x00080000000
    Ending Address: 0x000FDFFFFFF
    Range Size: 2016 MB
    Physical Device Handle: 0x1101
    Memory Array Mapped Address Handle: 0x1300
    Partition Row Position: 1
    Interleave Position: 1
    Interleaved Data Depth: 1
    Handle 0x1402, DMI type 20, 19 bytes
    Memory Device Mapped Address
    Starting Address: 0x00000000000
    Ending Address: 0x0007FFFFFFF
    Range Size: 2 GB
    Physical Device Handle: 0x1102
    Memory Array Mapped Address Handle: 0x1300
    Partition Row Position: 1
    Interleave Position: 2
    Interleaved Data Depth: 1
    Handle 0x1403, DMI type 20, 19 bytes
    Memory Device Mapped Address
    Starting Address: 0x00080000000
    Ending Address: 0x000FDFFFFFF
    Range Size: 2016 MB
    Physical Device Handle: 0x1103
    Memory Array Mapped Address Handle: 0x1300
    Partition Row Position: 1
    Interleave Position: 2
    Interleaved Data Depth: 1
    Handle 0x1410, DMI type 126, 19 bytes
    Inactive
    Handle 0x1800, DMI type 24, 5 bytes
    Hardware Security
    Power-On Password Status: Enabled
    Keyboard Password Status: Not Implemented
    Administrator Password Status: Enabled
    Front Panel Reset Status: Not Implemented
    Handle 0x1900, DMI type 25, 9 bytes
    System Power Controls
    Next Scheduled Power-on: *-* 00:00:00
    Handle 0x1B10, DMI type 27, 12 bytes
    Cooling Device
    Type: Fan
    Status: OK
    OEM-specific Information: 0x0000DD00
    Handle 0x1B11, DMI type 27, 12 bytes
    Cooling Device
    Type: Fan
    Status: OK
    OEM-specific Information: 0x0000DD01
    Handle 0x1B12, DMI type 126, 12 bytes
    Inactive
    Handle 0x1B13, DMI type 126, 12 bytes
    Inactive
    Handle 0x1B14, DMI type 126, 12 bytes
    Inactive
    Handle 0x2000, DMI type 32, 11 bytes
    System Boot Information
    Status: No errors detected
    Handle 0x8100, DMI type 129, 8 bytes
    OEM-specific Type
    Header and Data:
    81 08 00 81 01 01 02 01
    Strings:
    Intel_ASF
    Intel_ASF_001
    Handle 0x8200, DMI type 130, 20 bytes
    OEM-specific Type
    Header and Data:
    82 14 00 82 24 41 4D 54 01 01 00 00 01 A5 0B 02
    00 00 00 00
    Handle 0x8300, DMI type 131, 64 bytes
    OEM-specific Type
    Header and Data:
    83 40 00 83 14 00 00 00 00 00 C0 29 05 00 00 00
    F8 00 4E 24 00 00 00 00 0D 00 00 00 02 00 03 00
    19 04 14 00 01 00 01 02 C8 00 BD 10 00 00 00 00
    00 00 00 00 FF 00 00 00 00 00 00 00 00 00 00 00
    Handle 0x8800, DMI type 136, 6 bytes
    OEM-specific Type
    Header and Data:
    88 06 00 88 5A 5A
    Handle 0xD000, DMI type 208, 10 bytes
    OEM-specific Type
    Header and Data:
    D0 0A 00 D0 01 03 FE 00 11 02
    Handle 0xD100, DMI type 209, 12 bytes
    OEM-specific Type
    Header and Data:
    D1 0C 00 D1 78 03 07 03 04 0F 80 05
    Handle 0xD200, DMI type 210, 12 bytes
    OEM-specific Type
    Header and Data:
    D2 0C 00 D2 F8 03 04 03 06 80 04 05
    Handle 0xD201, DMI type 126, 12 bytes
    Inactive
    Handle 0xD400, DMI type 212, 242 bytes
    OEM-specific Type
    Header and Data:
    D4 F2 00 D4 70 00 71 00 00 10 2D 2E 42 00 11 FE
    01 43 00 11 FE 00 0F 00 25 FC 00 10 00 25 FC 01
    11 00 25 FC 02 12 00 25 FC 03 00 00 25 F3 00 00
    00 25 F3 04 00 00 25 F3 08 00 00 25 F3 0C 07 00
    23 8F 00 08 00 23 F3 00 09 00 23 F3 04 0A 00 23
    F3 08 0B 00 23 8F 10 0C 00 23 8F 20 0E 00 23 8F
    30 0D 00 23 8C 40 A6 00 23 8C 41 A7 00 23 8C 42
    05 01 22 FD 02 06 01 22 FD 00 8C 00 22 FE 00 8D
    00 22 FE 01 9B 00 25 3F 40 9C 00 25 3F 00 09 01
    25 3F 80 A1 00 26 F3 00 A2 00 26 F3 08 A3 00 26
    F3 04 9F 00 26 FD 02 A0 00 26 FD 00 9D 00 11 FB
    04 9E 00 11 FB 00 54 01 23 7F 00 55 01 23 7F 80
    5C 00 78 BF 40 5D 00 78 BF 00 04 80 78 F5 0A 01
    A0 78 F5 00 93 00 7B 7F 80 94 00 7B 7F 00 8A 00
    37 DF 20 8B 00 37 DF 00 03 C0 67 00 05 FF FF 00
    00 00
    Handle 0xD401, DMI type 212, 172 bytes
    OEM-specific Type
    Header and Data:
    D4 AC 01 D4 70 00 71 00 03 40 59 6D 2D 00 59 FC
    02 2E 00 59 FC 00 6E 00 59 FC 01 E0 01 59 FC 03
    28 00 59 3F 00 29 00 59 3F 40 2A 00 59 3F 80 2B
    00 5A 00 00 2C 00 5B 00 00 55 00 59 F3 00 6D 00
    59 F3 04 8E 00 59 F3 08 8F 00 59 F3 00 00 00 55
    FB 04 00 00 55 FB 00 23 00 55 7F 00 22 00 55 7F
    80 F5 00 58 BF 40 F6 00 58 BF 00 EB 00 55 FE 00
    EA 00 55 FE 01 40 01 54 EF 00 41 01 54 EF 10 ED
    00 54 F7 00 F0 00 54 F7 08 4A 01 53 DF 00 4B 01
    53 DF 20 4C 01 53 7F 00 4D 01 53 7F 80 68 01 56
    BF 00 69 01 56 BF 40 FF FF 00 00 00
    Handle 0xD402, DMI type 212, 152 bytes
    OEM-specific Type
    Header and Data:
    D4 98 02 D4 70 00 71 00 00 10 2D 2E 2D 01 21 FE
    01 2E 01 21 FE 00 97 00 22 FB 00 98 00 22 FB 04
    90 00 11 CF 00 91 00 11 CF 20 92 00 11 CF 10 E2
    00 27 7F 00 E3 00 27 7F 80 E4 00 27 BF 00 E5 00
    27 BF 40 D1 00 22 7F 80 D2 00 22 7F 00 45 01 22
    BF 40 44 01 22 BF 00 36 01 21 F1 06 37 01 21 F1
    02 38 01 21 F1 00 39 01 21 F1 04 2B 01 11 7F 80
    2C 01 11 7F 00 4E 01 65 CF 00 4F 01 65 CF 10 D4
    01 65 F3 00 D5 01 65 F3 04 D2 01 65 FC 00 D3 01
    65 FC 01 FF FF 00 00 00
    Handle 0xD403, DMI type 212, 157 bytes
    OEM-specific Type
    Header and Data:
    D4 9D 03 D4 70 00 71 00 03 40 59 6D 17 01 52 FE
    00 18 01 52 FE 01 19 01 52 FB 00 1A 01 52 FB 04
    1B 01 52 FD 00 1C 01 52 FD 02 1D 01 52 F7 00 1E
    01 52 F7 08 1F 01 52 EF 00 20 01 52 EF 10 21 01
    52 BF 00 22 01 52 BF 40 87 00 59 DF 20 88 00 59
    DF 00 E8 01 66 FD 00 E9 01 66 FD 02 02 02 53 BF
    00 03 02 53 BF 40 04 02 53 EF 00 05 02 53 EF 10
    06 02 66 DF 00 07 02 66 DF 20 08 02 66 EF 00 09
    02 66 EF 10 17 02 66 F7 00 18 02 66 F7 08 44 02
    52 BF 40 45 02 52 BF 00 FF FF 00 00 00
    Handle 0xD800, DMI type 126, 9 bytes
    Inactive
    Handle 0xDD00, DMI type 221, 19 bytes
    OEM-specific Type
    Header and Data:
    DD 13 00 DD 00 01 00 00 00 10 F5 00 00 00 00 00
    00 00 00
    Handle 0xDD01, DMI type 221, 19 bytes
    OEM-specific Type
    Header and Data:
    DD 13 01 DD 00 01 00 00 00 11 F5 00 00 00 00 00
    00 00 00
    Handle 0xDD02, DMI type 221, 19 bytes
    OEM-specific Type
    Header and Data:
    DD 13 02 DD 00 01 00 00 00 12 F5 00 00 00 00 00
    00 00 00
    Handle 0xDE00, DMI type 222, 16 bytes
    OEM-specific Type
    Header and Data:
    DE 10 00 DE C1 0B 00 00 10 05 19 21 01 00 00 01
    Handle 0x7F00, DMI type 127, 4 bytes
    End Of Table
    Hdparm also does not tell me the max data transfer rate (disk speed) of my current drive although this link : www.wdc.com/en/library/sata/2879-001146.pdf  says that it is 3.0Gb/s
    and here's hdparm -I /dev/sda
    /dev/sda:
    ATA device, with non-removable media
    Model Number: WDC WD800JD-75JNC0
    Firmware Revision: 06.01C06
    Standards:
    Supported: 6 5 4
    Likely used: 8
    Configuration:
    Logical max current
    cylinders 16383 16383
    heads 16 16
    sectors/track 63 63
    CHS current addressable sectors: 16514064
    LBA user addressable sectors: 156250000
    Logical/Physical Sector size: 512 bytes
    device size with M = 1024*1024: 76293 MBytes
    device size with M = 1000*1000: 80000 MBytes (80 GB)
    cache/buffer size = 8192 KBytes
    Capabilities:
    LBA, IORDY(can be disabled)
    Standby timer values: spec'd by Standard, with device specific minimum
    R/W multiple sector transfer: Max = 16 Current = 8
    Recommended acoustic management value: 128, current value: 254
    DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
    Cycle time: min=120ns recommended=120ns
    PIO: pio0 pio1 pio2 pio3 pio4
    Cycle time: no flow control=120ns IORDY flow control=120ns
    Commands/features:
    Enabled Supported:
    * SMART feature set
    Security Mode feature set
    * Power Management feature set
    * Write cache
    * Look-ahead
    * Host Protected Area feature set
    * WRITE_BUFFER command
    * READ_BUFFER command
    * DOWNLOAD_MICROCODE
    SET_MAX security extension
    Automatic Acoustic Management feature set
    * Device Configuration Overlay feature set
    * Mandatory FLUSH_CACHE
    * SMART error logging
    * SMART self-test
    * Gen1 signaling speed (1.5Gb/s)
    * Host-initiated interface power management
    * SMART Command Transport (SCT) feature set
    * SCT Long Sector Access (AC1)
    * SCT LBA Segment Access (AC2)
    * SCT Error Recovery Control (AC3)
    * SCT Features Control (AC4)
    * SCT Data Tables (AC5)
    Security:
    Master password revision code = 65534
    supported
    not enabled
    not locked
    frozen
    not expired: security count
    not supported: enhanced erase
    Checksum: correct
    Last edited by Inxsible (2011-03-27 04:40:49)

    I just checked my BIOS and my current setting is set at IDE although it also mentions that the default should be AHCI. Currently I have a dual boot of Windows 7 (need it for Tax software) and Arch
    So I guess, when I get the new HDD, I will first set it to AHCI and then install the OSes on it. See if NCQ helps any, and if not I will turn it back and re-install (if I have to). I am planning to have Windows only in virtualbox in the new drive.
    Anyhoo, while I was in the BIOS I found two things which I had questions about :
    1) Under Onboard Devices --> Integrated NIC , my setting is currently set at "On w/PXE" and it says the default should be just "On". Would it be ok to change it back to On since its a single machine and its not booting an OS on any server. I just don't want to have to re-install anything now since I will be doing that in the new HDD.
    2) How would I know whether my BIOS would support a 64 bit OS in Virtualbox? I checked some setting under Virtualization, but they weren't very clear.
    I will edit this post and let you know exactly what settings were present under the Virtualization sub-section.

  • Time Capsule only runs with 1,1Mbit up/down during data transfer, internet speed is ok, TC is used to extend an existing network

    Hello Everyone,
    I have a new 2TB Time Capsule running with a MacBook Air. I want to use the TC to access data (Aperture library, iTunes library, other Files) and to backup my MacBook Air via Time Machine. I set it up, integrated the TC in my Network (FritzBox) by choosing "extend existing network" and it works. BUT only with 1.1Mbit/second while writing or reading Data to/from it. Internet speed is very good, like it was before. While the 1.1Mbit/second seem to be ok with Aperture and iTunes (streaming music and movies) it is still painfully slow and I'm not realy happy with that
    I've read that:
    The 1.1Mbit problem is pretty common when Time Capsule is integrated and used to extend a network (bridge modus), it also looses all ethernet connectivity then (that woul explain why connecting it by ethernet didn't help during initial setup and data transfer)
    Is there a solution besides ditching the Fritzbox and using the TC to build the network? Because basicly I still need the Fritzbox for its DECT features.
    Thank you for any help in advance and have a nice day,
    Olli

    You have double hop wireless with this setup..
    You should bridge the TC.. that is router bridge not wireless bridge, and plug the TC into the Frizyboy by ethernet.
    Then you can setup the TC wireless to reinforce the fritzy..
    Same wireless name as SSID.
    Same security settings... really should be WPA2 AES or in TC personal.
    Same password..
    Just different wireless channel.
    Then you can use 5ghz on the TC if you are up close and personal.

  • Problems with Photoshop performance and data transfer speed on iMac

    Two months ago, I started noticing slow performances using Photoshop (above all using clone stamp tool) on my 27" iMac (late 2012). I did the AHT and I found that 8GB of 32GB RAM were broken.
    I removed them but the problem didn't disappered, I also noticed that data transfer speed (both copy and paste from/to internal HD and from CF card/external HD) was really slow.
    I tried many solutions suggested by Apple support, none of them worked out. At the end, I tried uninstalling and re-installing Photoshop: no more problems!!!
    10 days ago, I received a new 8GB RAM module and so I installed it back... suddenly, the problem came back, I tried re-installing again Photoshop but the problem, this time, still persist!
    Does anyone had the same experience? All other CC programs work well (LR, AE, Premiere...)

    yes, it does!
    what seems to be very strange to me is how data trasnfer speed could be affected!
    (just to say, I've already tried reset of SMC and PRAM, I've tried with different accounts and I've also re-installed the OS, next step would be formatting the disk and installing the OS from zero)

  • Error while executing Initialize with Data Transfer for 0FI_GL_10

    Hello All,
    Post Pre prod refresh, our timestamp for the datasource 0FI_GL_10 got reset. Due to which our deltas did not bring any records to the BW system.
    First we did an Initialize without data transfer for all the BW related datasources. The deltas were then set properly for all datasources except 0FI_GL_10.
    We then raised a message to SAP and they suggested to run the 'Initialize with data transfer' for 0FI_GL_10 so that the timestamp is set and accordingly the deltas are fixed.
    The issue now is we are getting the following error message while running INIT with data transfer.
    Job terminated in source system --> Request set to red
    Message no. RSM078
    We have copied the data till July 1st week of 2011.
    Please advice. The issue is very critical.
    Thanks & Regards
    Sneha

    Hi Arvind
    Thanks for your inputs.
    Please find below the details of the short dump.
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          09/07/2011 11:25:32
    Short text
         SQL error in the database when accessing a table.
    What can you do?
         Note which actions and input led to the error.
         For further help in handling the problem, contact your SAP administrator
         You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
    How to correct the error
         Database error text........: "ORA-01652: unable to extend temp segment by 128
          in tablespace PSAPTEMP"
         Internal call code.........: "[RSQL/FTCH/FAGLFLEXT ]"
         Please check the entries in the system log (Transaction SM21).
         If the error occures in a non-modified SAP program, you may be able to
         find an interim solution in an SAP Note.
         If you have access to SAP Notes, carry out a search with the following
         keywords:
         "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    Information on where terminated
        Termination occurred in the ABAP program "GP_GLX_FAGLFLEXT" - in
         "FETCH_TO_ISTRUCTURE".
        The main program was "SBIE0001 ".
        In the source code you have the termination point in line 903
        of the (Include) program "GP_GLX_FAGLFLEXT".
        The program "GP_GLX_FAGLFLEXT" was started as a background job.
        Job Name....... "BIREQU_4N3PZQ12IA0X0PYGEA85IG39S"
        Job Initiator.. "BIWREMOTE"
        Job Number..... 11203300
        The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
        procedure "FETCH_TO_ISTRUCTURE" "(FORM)", but it was neither handled locally
         nor declared
        in the RAISING clause of its signature.
        The procedure is in program "GP_GLX_FAGLFLEXT "; its source code begins in line
        840 of the (Include program "GP_GLX_FAGLFLEXT ".

  • Error 33172 occurred at Read & Write data transfer between two or more PF2010 controller

    Hi,i need to do data transfer between two or more FP2010 controller.e.g. FP2010(A) & FP2010(B).
    FP2010(A) need to transfer the measurement (from its I/O module) to FP2010(B) to do the data analysis.These data transfer should be synchronous btw two controller to prevent data lost.
    From the vi used in the attachment,i encountered some problems at:
    (1) Error 33172 occurred while publishing the data.Can i create and publish data under different item name?
    (2) How to synchronies the read & write btw contorller?
    All controller are communicating with each other directly without the need of a host computer to link them together
    Is there any other method to do fast data transfer betwe
    en controller?

    Hi YongNei,
    You were succesful in omiting enough information to make it very difficult to answer!
    Please post your example.
    Please tell us what version of LV-RT you are using.
    Please define what you concider "fast data transfer".
    Have you concidered mapping the FP tags of FP2010(A) to FP2010(B) and vise versa?
    WHat exactly has to be syncronized?
    If you have something that is close to working, share that.
    Well, that as far as I can go with the info you have provided. Depending on the details, what you are asking could be anything from trivial to impossible with the currently available technology. I just can't say.
    It would probably be a good idea to start over with a fresh question (sorry) because not many people are going to know what a a "
    PF2010" is and I can not guarentee that I will be able to get back to you personally until next week-end.
    Trying to help you get an answer,
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Rp-pppoe connected but no data transfer

    hi,
    i installed arch on 27th . Post installation i setup internet connection using rp-pppoe, which was a straight forward setup. I also got connected to net and downloaded data upon a system upgrade. Except this one instance, thereafter last two days if connected i am getting no data transfer after a connection is established.
    Upon ping of 8.8.8.8  i am getting this error of destination net unreachable & if you ping google.com i get the error unknown host.
    when i checked the pppoe status i get this message:
    link is up and running on interface ppp0 and no packet errors both RX and TX.
    The system upgrade did not happen on 27th due to the TZselec tconflicting files error.
    It is a fresh system.
    i am pasting below the lines from the messages.log of 27th when i got the data transfer happened for the first time and next of 29th with the same system but nothing happening except i am connected.
    27th:
    Jun 27 12:46:03 localhost kernel: [  117.794497] r8169 0000:02:00.0: eth0: link up
    Jun 27 12:46:06 localhost kernel: [  120.763326] eth0: no IPv6 routers present
    Jun 27 12:58:01 localhost kernel: [  835.641169] PPP generic driver version 2.4.2
    Jun 27 12:58:01 localhost pppd[888]: pppd 2.4.5 started by root, uid 0
    Jun 27 12:58:01 localhost pppd[888]: Using interface ppp0
    Jun 27 12:58:01 localhost pppd[888]: Connect: ppp0 <--> /dev/pts/0
    Jun 27 12:58:02 localhost pppoe[889]: PADS: Service-Name: ''
    Jun 27 12:58:02 localhost pppoe[889]: PPP session is 14295 (0x37d7)
    Jun 27 12:58:02 localhost pppd[888]: CHAP authentication succeeded: CHAP authentication success, unit 7436
    Jun 27 12:58:02 localhost pppd[888]: CHAP authentication succeeded
    Jun 27 12:58:02 localhost kernel: [  837.068606] PPP BSD Compression module registered
    Jun 27 12:58:03 localhost pppd[888]: Cannot determine ethernet address for proxy ARP
    Jun 27 12:58:03 localhost pppd[888]: local  IP address 117.204.173.123
    Jun 27 12:58:03 localhost pppd[888]: remote IP address 117.204.160.1
    Jun 27 12:58:03 localhost pppd[888]: primary   DNS address 218.248.255.212
    Jun 27 12:58:03 localhost pppd[888]: secondary DNS address 218.248.241.2
    Jun 27 13:01:01 localhost /USR/SBIN/CROND[934]: (root) CMD (run-parts /etc/cron.hourly)
    Jun 27 13:01:01 localhost anacron[938]: Anacron started on 2012-06-27
    Jun 27 13:01:01 localhost anacron[938]: Will run job `cron.daily' in 28 min.
    Jun 27 13:01:01 localhost anacron[938]: Will run job `cron.weekly' in 48 min.
    Jun 27 13:01:01 localhost anacron[938]: Will run job `cron.monthly' in 68 min.
    Jun 27 13:01:01 localhost anacron[938]: Jobs will be executed sequentially
    Jun 27 13:04:10 localhost -- MARK --
    Jun 27 13:16:48 localhost pppoe-stop: Killing pppd
    Jun 27 13:16:48 localhost pppd[888]: Terminating on signal 15
    Jun 27 13:16:48 localhost pppd[888]: Connect time 18.8 minutes.
    Jun 27 13:16:48 localhost pppd[888]: Sent 411268 bytes, received 16885685 bytes.
    29th :
    Jun 29 17:54:13 localhost kernel: [    5.019108] r8169 0000:02:00.0: eth0: link down
    Jun 29 17:54:14 localhost dhcpcd[675]: eth0: carrier acquired
    Jun 29 17:54:14 localhost kernel: [    6.632983] r8169 0000:02:00.0: eth0: link up
    Jun 29 17:54:14 localhost dhcpcd[675]: eth0: broadcasting for a lease
    Jun 29 17:54:15 localhost dhcpcd[675]: eth0: offered 192.168.1.2 from 192.168.1.1
    Jun 29 17:54:15 localhost dhcpcd[675]: eth0: acknowledged 192.168.1.2 from 192.168.1.1
    Jun 29 17:54:15 localhost dhcpcd[675]: eth0: checking for 192.168.1.2
    Jun 29 17:54:21 localhost dhcpcd[675]: eth0: leased 192.168.1.2 for 10080 seconds
    Jun 29 17:54:21 localhost dhcpcd[675]: forked to background, child pid 702
    Jun 29 17:54:21 localhost /usr/sbin/crond[751]: (CRON) STARTUP (1.4.8)
    Jun 29 17:54:21 localhost /usr/sbin/crond[751]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
    Jun 29 17:54:21 localhost /usr/sbin/crond[751]: (CRON) INFO (running with inotify support)
    Jun 29 17:54:47 localhost kernel: [   39.424170] NET: Registered protocol family 10
    Jun 29 17:54:47 localhost kernel: [   39.441086] NET: Registered protocol family 4
    Jun 29 17:54:47 localhost kernel: [   39.458946] NET: Registered protocol family 5
    Jun 29 17:54:47 localhost kernel: [   39.480053] PPP generic driver version 2.4.2
    Jun 29 17:54:47 localhost pppd[811]: pppd 2.4.5 started by root, uid 0
    Jun 29 17:54:47 localhost pppd[811]: Using interface ppp0
    Jun 29 17:54:47 localhost pppd[811]: Connect: ppp0 <--> /dev/pts/0
    Jun 29 17:54:48 localhost pppoe[812]: PADS: Service-Name: ''
    Jun 29 17:54:48 localhost pppoe[812]: PPP session is 2021 (0x7e5)
    Jun 29 17:54:48 localhost pppd[811]: CHAP authentication succeeded: CHAP authentication success, unit 4257
    Jun 29 17:54:48 localhost pppd[811]: CHAP authentication succeeded
    Jun 29 17:54:48 localhost kernel: [   40.866233] PPP BSD Compression module registered
    Jun 29 17:54:48 localhost pppd[811]: not replacing existing default route via 192.168.1.1
    Jun 29 17:54:48 localhost pppd[811]: Cannot determine ethernet address for proxy ARP
    Jun 29 17:54:48 localhost pppd[811]: local  IP address 117.204.161.173
    Jun 29 17:54:48 localhost pppd[811]: remote IP address 117.204.160.1
    Jun 29 17:54:48 localhost pppd[811]: primary   DNS address 218.248.255.212
    Jun 29 17:54:48 localhost pppd[811]: secondary DNS address 218.248.241.2
    Jun 29 17:54:57 localhost kernel: [   49.523342] eth0: no IPv6 routers present
    Jun 29 18:01:01 localhost /USR/SBIN/CROND[876]: (root) CMD (run-parts /etc/cron.hourly)
    Jun 29 18:01:01 localhost anacron[881]: Anacron started on 2012-06-29
    Jun 29 18:01:01 localhost anacron[881]: Will run job `cron.daily' in 29 min.
    Jun 29 18:01:01 localhost anacron[881]: Will run job `cron.weekly' in 49 min.
    Jun 29 18:01:01 localhost anacron[881]: Will run job `cron.monthly' in 69 min.
    Jun 29 18:01:01 localhost anacron[881]: Jobs will be executed sequentially
    Jun 29 18:04:04 localhost pppoe-stop: Killing pppd
    Jun 29 18:04:04 localhost pppd[811]: Terminating on signal 15
    Jun 29 18:04:04 localhost pppd[811]: Connect time 9.3 minutes.
    Jun 29 18:04:04 localhost pppd[811]: Sent 0 bytes, received 926 bytes.
    Now in both the cases i got connected but as i said before except twice on  27th i am not able to have data transfer of any type either through ping or pacman upgrade.
    Upon the same time i cross checked on my other systems, ubuntu and windows and i had no problems with the same, to confirm any issue with my isp. As of now i am typing one of those systems only.
    I have googled a lot, read the other options of pppd,etc, but upon similar queries by other users found no viable solution to this problem.
    My hostname is also proper in the config files. I also once used static ip for a change to see if things go working
    but nothing is sucessful so far.
    The only viable solution i read so far upon google search where there was a success was a fresh installation of arch by an user and he got the same working. But definitely i wont go with that. As i said above i got connected twice on the day of the installation and post that also i am now getting connected but with no data transfer.
    Pls suggest what to do to get the connection working.
    regards

    Upon a search on the forums yesterday
    i read one user query on this forums who was advised the same and he had the same problem like me and it did not got solved with either methodds.
    Last his query was still open. I did not save that link.
    So i did not give that method a try so far, waiting for a solution for this method without going for new developments thinking a search for a day or two might get some viable results.
    i guess you are mentioning the topic of this link
    https://wiki.archlinux.org/index.php/Pppd [This article explains how to set up a point-ti-point connections using pppd and the kernel PPPoE driver. ]
    Further in my case the connection is happening and also getting disconnected. You can very well see the same in the  log file which i pasted.
    Jun 27 13:16:48 localhost pppd[888]: Connect time 18.8 minutes.
    Jun 27 13:16:48 localhost pppd[888]: Sent 411268 bytes, received 16885685 bytes.
    Jun 29 18:04:04 localhost pppd[811]: Connect time 9.3 minutes.
    Jun 29 18:04:04 localhost pppd[811]: Sent 0 bytes, received 926 bytes.
    So same thing but different results on 2 different days. So what the problem really is i dont understand. Infact what the problem is the system is also not giving out, except that a connection happens, no data transfer takes place and the connection is cut and the stats are also show. Just diving to implement some new method or a reinstall, without resolving this which looks sensible yet senseless too, simply does not appeal here. If really there is some bug or issue with that rp-pppoe package then there is some point to jump to another method.
    This must be solvable some way or other.
    Last edited by beopen (2012-06-29 17:30:16)

  • MyRIO memory, data transfer and clock rate

    Hi
    I am trying to do some computations on a previously obtained file sampled at 100Msps using myRIO module. I have some doubts regarding the same. There are mainly two doubts, one regarding data transfer and other regarding clock rate. 
    1. Currently, I access my file (size 50 MB) from my development computer hard drive in FPGA through DMA FIFO, taking one block consisting of around 5500 points at a time. I have been running the VI in emulation mode for the time being. I was able to transfer through DMA from host, but it is very slow (i can see each point being transferred!!). The timer connected in while loop in FPGA says 2 ticks for each loop, but the data transfer is taking long. There could be two reasons for this, one being that the serial cable used is the problem, the DMA happens fast but the update as seen to the user is slower, the second being that the timer is not recording the time for data trasfer. Which one could be the reason?
    If I put the file in the myRIO module, I will have to compile it each and every time, but does it behave the same way as I did before with dev PC(will the DMA transfer be faster)? And here too, do I need to put the file in the USB stick? My MAX says that there is 293 MB of primary disk free space in the module. I am not able to see this space at all. If I put my file in this memory, will the data transfer be faster? That is, can I use any static memory in the board (>50MB) to put my file? or can I use any data transfer method other than FIFO? This forum (http://forums.ni.com/t5/Academic-Hardware-Products-ELVIS/myRIO-Compile-Error/td-p/2709721/highlight/... discusses this issue, but I would like to know the speed of the transfer too. 
    2. The data in the file is sampled at 100Msps. The filter blocks inside FPGA ask to specify the FPGA clock rate and sampling rate, i created a 200MHz derived clock and mentioned the same, gave sampling rate as 100Msps, but the filter is giving zero results. Do these blocks work with derived clock rates? or is it the property of SCTL alone?
    Thanks a lot
    Arya

    Hi Sam
    Thanks for the quick reply. I will keep the terminology in mind. I am trying analyse the data file (each of the 5500 samples corresponds to a single frame of data)  by doing some intensive signal processing algorithms on each frame, then average the results and disply it.
    I tried putting the file on the RT target, both using a USB stick and using the RT target internal memory. I thought I will write back the delay time for each loop after the transfer has occured completely, to a text tile in the system. I ran the code my making an exe for both the USB stick and RT target internal memory methods; and compiling using the FPGA emulater in the dev PC VI. (A screenshot of the last method is attached, the same is used for both the other methods with minor modifications. )To my surprise, all three of them gave 13 ms as the delay. I certainly expect the transfer from RT internal memory faster than USB and the one from the dev PC to be the slowest. I will work more on the same and try to figure out why this is happening so.
    When I transferred the data file (50MB) into the RT flash memory, the MAX shows 50MB decrease in the free physical memory but only 20MB decrease in the primary disk free space. Why is this so? Could you please tell me the differences between them? I did not get any useful online resources when I searched.
    Meanwhile, the other doubt still persists, is it possible to run filter blocks with the derived clock rates? Can we specify clock rates like 200MHz and sampling rates like 100Msps in the filter configuration window? I tried, but obtained zero results.
    Thanks and regards
    Arya
    Attachments:
    Dev PC VI.PNG ‏33 KB
    FPGA VI.PNG ‏16 KB
    Delay text file.PNG ‏4 KB

Maybe you are looking for