Data Rate V Maximum data rate

Can anyone tell me if my speed will increase due to DLM if my max data rate continues to climb. I used to have 70meg downstream no problem, but after lots of attempts to get BT to resolve an issue left it (thought I would just let my contract expire) when it dropped to 57 max. Now the max data rate has increased from 65000 to the value below. As a result, my speeds have increased to upto 62 down again. There is however a big discrepancy between the two figures, does this mean my speed will continue to increase if it continues upwards accordingly? Why the big difference between the two?
Thanks in advance.

Within 10 days if the cause has been fixed, I'd say
If you found this post helpful, please click on the star on the left
If not, I'll try again

Similar Messages

Upload Maximum Date Rate Lower Than Upload Data Ra...

Hello there,
I have just brought up my BT Home Hub 5 stats and my upload data rate is higher than my upload maximum date rate. Is this normal? My upload noise margin has dropped to 4.9 - 5.1 dB. I've had BT Infinity just over 2 days and was wondering if this was normal for FTTC connections?
Many thanks,
William

normally the data rate will be lower than max data rate but yours is that close I would not bother unless it starts to affect your connection which is unlikely
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

Ipad 2 video data rate. Whats the maximum data rate it can play back?

I'm creating a video file I want to play in 1920 x 1080 on the ipad 2 and not sure what the maximum data rate should be.

Frankiedude wrote:
I'm creating a video file I want to play in 1920 x 1080 on the ipad 2 and not sure what the maximum data rate should be.
Depends upon the format of the video. See:
http://www.apple.com/ipad/specs/

Maximum data rate

Good Evening,
We recently had a VDSL connection installed to upgrade our speeds from 6mb to around 15mbps on a good day.
BT Wholesale says the IP Profile is 14.12mbps but the maximum data rate on the hub stats is much higher. Could someone help with this please.
And just to say its good to be back on the forums again.
Kind regards,
Dominic
Here are the stats:
5. VDSL uptime:
3 days, 13:25:37
6. Data rate:
1296 / 14583
7. Maximum data rate:
1629 / 23612
8. Noise margin:
6.2 / 6.2
9. Line attenuation:
0.0 / 31.4

dombullion wrote:
how do my stats look. could i be getting faster speeds?
VDSL uptime:
4 days, 07:07:57
6. Data rate:
1296 / 14583
7. Maximum data rate:
1691 / 23990
8. Noise margin:
6.4 / 6.3
9. Line attenuation:
0.0 / 31.4
10. Signal attenuation:
0.0 / 25.5
No it looks like you are getting the best speed, your Noise Margin is near 6db which is the minumum the connection likes to be at, it appears that DLM is doing its job right.

Maximum data rate RT host can handle (sbRIO 9602)

Hi all, i got a sbRIO 9602,
in my application FPGA reads data from custom module @ 1Mhz, just i'm wondering if
RT host has the capability to read data and visualize it on a graph without losing samples.
I just want to know this before look how to implement any Bufferized/Producer consumer/DMA transfer 'cause
if RT host can't simply manage this data rate i will have soon or later buffer overflow.
Until now what i've thought is to copy 1000 contiguous samples in a memory in a ONE SHOT way, reading this memory from RT Host and visualize it on a waveform Graph.
But again if there is the possibility to show acquired data continuously is obviously better.
Thanks in advance.

Hi, thank you all for your suggestions.
In my RT Host i read 10000 values in every cycle so data rate drops to 1Mhz/10000 ->100Hz i think.
What i want to do know is to detect peaks in my data and create an histogram of that peaks in RT.
I've placed a peak detector VI that takes as input my array of 10000 values and generate an array with only peaks but i don't understand how to use Histogram PtByPt VI. It works with single data value at a time so to generate a consistent histogram i should wait 10000 cycles and so it may not be as fast as 100Hz .
Previuously i've tried to detect peaks and generate Histogram directly on FPGA to be sure to be as fast as possible due to 1Mhz data acquiring, but now with 10000 values chunk i guess if i can realize this on RT host side .
Any suggestion will be really appreciated.

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.

How do I get a high data rate throughput from FPGA module to my PC running Labview app

Hi,
I am using a 7811R (Ni FPGA board) and a MXI-4 card in a PXI-1031DC chassis. I am trying to measure the maximum rate I can send data from the MXI-4 card to my PC and up into a labview windows application. The PC also has a MXI-4 card which is on the PCI bus. My PC is a 3.2 GHz with 2 gigs of ram. When I run the experiment to dump data to my labview application, I get a maximum speed of 728KB/s. I think this is too low. Has anyone been able to get a higher through put and if so how did you do it?

The source code is available and it doesn't have any real
dependencies on Flex
http://opensource.adobe.com/svn/opensource/flex/sdk/trunk/frameworks/projects/framework/sr c/mx/utils/UIDUtil.as

H.264 All-Intra Data Rates Significantly Higher

Does the built-in H.264 codec encode I-frame only files differently? I am trying to determine the optimal GOP length for high bitrate exports. Image quality seems to degrade, even in the I-frames, when using key frame distances greater than one.
After performing a series of tests to characterize the Adobe H.264 encoder, I discovered that exported files are significantly larger when key frame distance equals one frame (N=1). The average video data rate for a test file rendered with the Adobe H.264 encoder is as follows:
N=1 : 2.17 bpp : 24I
N=2 : 0.66 bpp : 12I + 12P
N=3 : 0.59 bpp : 8I + 8B + 8P
Note how the data rate drops 70% (from 2.17 to 0.66 bpp) even though 50% of the I-frames still exist when N=2. By comparison, here is the video data rate when exporting with QuickTime H.264:
N=1 : 0.89 bpp : 24I
N=2 : 0.70 bpp : 12I + 12P
N=3 : 0.64 bpp : 8I + 16P
The following chart shows data rates at key frame distances from 1-48 frames for Adobe H.264, QuickTime H.264 (via Adobe), QuickTime Pro, and Expression Encoder 4 Pro. Data rates are consistent among all encoders at GOP lengths greater than one. There is an anomoly with the Adobe H.264 codec compressing all-intra files.
The observed behavior occurs in all profiles, which were tested at Levels 4.1, 4.2, 5.0, and 5.1:
Image quality is better in the Adobe H.264 all-intraframe file, especially with respect to detail retention. The pictures below show sections of two consecutive frames magnified 400%. The file with N=2 is less accurate and contains noticeable blocking. Even the I-frames don't look as good in the files where N>1.
The test file was a seventeen second Premiere Pro sequence consisting of H.264, MPEG-2, and AE files with effects applied. Exports were rendered from the Premiere Pro timeline and from a V210 uncompressed 4:2:2 intermediate file of the sequence. The following settings were used:
Format: H.264
Width: 1280
Height: 720
Frame Rate: 24 fps
Field Order: Progressive
Aspect: Square Pixels (1.0)
TV Standard: NTSC
Profile: Baseline, Main, and High
Levels: 4.1, 4.2, 5.0, 5.1
Render at Maximum Bit Depth: Enabled
Bitrate Encoding: VBR, 2-Pass
Target Bitrate: Maximized for each Profile/Level
Maximum Bitrate: Maximized for each Profile/Level
Key Frame Distance: 1, 2, 3, 4, 5, 6, 7, 8, 12, 24, 48
Use Maximum Render Quality: Enabled
Multiplexer: MP4
Stream Capability: Standard
Software:
Adobe Media Encoder CS6 Creative Cloud v6.0.3.1 (64-bit)
Premiere Pro CS6 Creative Cloud v6.0.3
Windows 7 SP1
QuickTime Pro for Windows v7.6.9 (1680.9)
MediaInfo 0.7.62 (for GOP and data rate information)

I think the short answer is yes,
a h.264 encoder does I-frame only differently. I frames are complete expressions of a picture with no temporal compression information.
P frames use _P_redictive information. IE information from prior frames.
B frames use _B_i-directional predictive frame information.
h.264 gets the majority of it's bit saving from use of B and P frames. When you do I-frame only you only get the block compression and none of the advantages of P and B frames. Thus the GOP N=1 doesn't get very good bit's per pixel.
Having said all that I do find your comment...
Profitic wrote:
Note how the data rate drops 70% (from 2.17 to 0.66 bpp) even though 50% of the I-frames still exist when N=2. By comparison, here is the video data rate when exporting with QuickTime H.264:
... very interesting. Indeed, why is the datarate 70% less when it should at best be 50% for GOP N=2. 50% less should be the same I-frame information plus 0 bytes for the B frame between them. (GOP = I,B,I). Any more than that and it is throwing away bits from the I-frame. So, this seems to be to be a ratecontrol bug.
http://en.wikipedia.org/wiki/Group_of_pictures
"The GOP structure is often referred by two numbers, for example, M=3, N=12. The first number tells the distance between two anchor frames (I or P): it is the GOP size. The second one tells the distance between two full images (I-frames): it is the GOP length. For the example M=3, N=12, the GOP structure is IBBPBBPBBPBBI. Instead of the M parameter the maximal count of B-frames between two consecutive anchor frames can be used."

Airport Extreme Card Data Rate

I've just bought a MacBook Pro which has an Airport Extreme card.....
In order to achieve data rates of 54 Mbps do I have to use an Airport Extreme Base Station?
Or can I still achieve 54 Mbps with a third party 802.11g wireless base station?

You do not need an AEBS to achieve maximum throughput, any 802.11g compliant router will theoretically achieve that speed. Bear in mind that the theoretical speed is never reached in real-world applications. You will be lucky to get one-half that speed.

GPIB Data Transfer Rate

The maximum data rate in the original GPIB standard is about 1MByte/s. I have a microcontroller connected to a NAT9914 but I don't know what the transfer data rate is. For RS232 protocol, I could specify the baudrate, say 9600. Is it possible to specify the data rate for the NAT9914; say for example 500kByte/s? I read about the T1 delay, but not sure how to apply it if I need 500kByte/s data rate for example.
Any suggestion or comment would be greatly appreciated. Thank you.

Hello GPIB.user,
The speed of the data transfers will depend on two things.
1. The speed that the talker is placing data onto the bus.
2. The speed that the slowest listener is accepting data.
GPIB was made to be extremely robust. I'm sure you've read something about the handshaking lines (NRFD, DAV, NDAC) that make sure that all instruments get the data. These do not toggle until all listeners have entered the correct states. So if you have a very slow GPIB instrument on the bus that is actively listening (accepting data and toggling the listener handshaking lines NRFD and NDAC) it will slow down the entire communication process.
The T1 delay that you mentioned controls the minimum time that the talker will wait before placing data on the bus. Even if all listeners are ready for more data, it will wait T1 before sending another byte. However if one instrument is taking a long time to accept the data, the talker must wait until all instruments are ready for more data before sending another byte.
So, there is no way to specify the data rate except with the T1 delay, but it only controls part of the total picture.
I hope this helps,
Steven T.

Another Data Rate Too High Error Question

Hi all,
I have seen quite a few posts about pgc errors, but most of them deal with slideshows and not video; and I can't find anything with the REF=KApgc error.
I'm just putting all of my home movies onto an authored DVD, not rocket science. I'm using the 'Film Submenu' preset with only 5 main movies, things like Easter, Birthday, etc. My transition for each button is a slate (for lack of a better word) that says exactly what it is and when it happened, before each movie plays.
After I had everything set up, I realized I didn't have an ability to "play all" that would include these slates. Simple solution, make a 'play all' button that links to a timeline that has everything in it - the slate, then the movie, next slate, next movie and so on. (When I say movie - they are all .mov files rendered out from After Effects, even the slates)
My transcode settings are NTSC DV High Quality 7mb VBR 2 Pass and the "maximum quality" box is checked.
When I run the 'Check Disc' all is fine. Preview the disc, all is fine.
Build Disc: Hours of Transcoding then the error: Data Rate Too High at *timecode* REF=KApgc.
When this movie is by itself with a button click, it's fine. It's only in the "play all" timeline that it produces the error.
If the data rate isn't too high in one place, why is it too high in another? It's the same thing, just a longer timeline.
Please Help!
Thanks.

Thanks Jeff,
I feel kind of silly for not thinking of that as a solution to my play all dilemma. That's why you're the expert I guess.
A better solution would be to create a playlist of all of your other timelines; that way, only one copy of each gets burned to disc.
Hopefully the "data rate" error will go away with these changes.
-Jeff
Can I place my slates that are just assets (.mov) in the playlist or can I only put timelines in there?
Thanks again,
-Jim

Best strategies for reducing effective data collection rate?

Hi,
I'm writing a VI to collect data from cDAQ modules that have a minimum sampling rate of 1612Hz due to the master timebase (specifically 9237 and 9215 modules). I would like to log data (1D waveform with timestamps) at 100Hz for 12 hours and save this to file. THe data also needs to be displayed during this time, and data logging should be robust so there is minimal risk of data loss.
I've made one attempt at doing this previously - I used the Align and resample expressVI but this was fairly messy, and the problems I ran into were that I had errors about the maximum array size being reached, and also constant buffer overwrite errors.
I would like to basically start this VI again from scratch, and I'm wondering if there are any suggestions for an overall strategy for this? I'm not asking for any code to be written for me, just concrete shoves in the right direction regarding things like data file type, how to resample or downsample data, how to clear arrays, etc.
Thanks,
Claire.

Claire,
It appears that you are appending the resampled waveform to an empty array of waveforms and then writing the appended array to the file. What does appending to an empty array accomplish? Just write the decimated array directly to the file.
If you want to have an array of all the waveforms, then you need to use shift registers to pass the appended array to the next iteration of the consumer loop.
You do not need the sequence structure. Dataflow takes care of making things happen in order.
I do not see how the feedback node will ever change the file name as it only executes once. I am not sure what you intended, but you may want to move the file path creation inside the loop and put it into a case structure which executes when it is time to create a new file.
The attached image is an example of the way I was thinking of decimating your data.
In both my image and your program the use of build array in a loop is not a good practice it the array can get large due to memory allocation issues. Better is to initialize an array of the maximum size and use Replace Array Element to put the data into the array.
Lynn
Attachments:
Decimate waveform.png ‏83 KB

How to send data at large IQ rate, at regular intervals and avoid buffer underflow?

Hello,
I am using 2921's and I have a Tx that generates payload only once, feeds it to a loop and the loop sends the same packet over and over again at a high rate. Please see attachment for VI screen snapshot. I want to have transmissions at regular intervals of my choice, but it does not work. I tried introducing a wait [ms] module into the loop (not shown in the attached figure), but I am facing the underflow problem.
Can someone please advise me on how to achieve this? Right now, the packet transmission interval is decided by the USRP, as soon as it sends a packet it sends another one, and if I try to control the transmission interval by using wait [ms] model, I have underflow.
Here are some details that could help you help me:
*30, 60, 90 or 120 bytes of payload
*8/16 bits sample width
*8 samples per symbol
*IQ rate of 8 MS/s
I would like to send every 10 ms, whereas sending 30,60,90,120 bytes takes about 1,2,3,4 ms, respectively.
Thanks!
Filip
Attachments:
snapshot.jpg ‏178 KB

Here are some general tips to increase your Tx streaming throughput:
0) Don't use a continuous generation at all. For many applications you don't need to stream continuously- a finite transmission (and you can loop a finite transmission) will do and you will basically not underflow in that case if you provide all the data up front.
1) As you can see from the chart, the bigger the data buffer you provide in each Write call, the faster you can stream.
2) Write sizes in multiples of the maximum packet size seem to work well. That number is 363for the USRP-292x series (although that may change in future driver releases). Try sending bursts of 10890 samples.
3) If your application allows it, set a Start Trigger Time a little in the future. Then start writing data before the device starts transmitting. For example, set the Start Trigger Time to the (current device time + 1 second). Then start writing data and you will have a second to pre-fill the on-device buffers. This will substantially reduce the number of underflows.
4) Be sure to do your data processing out of your write loop, to keep the write loop filling the pipleline as quickly as possible.
For your specific application, a finite, timed generation may be the write pattern.

Reducing data rate written to a LVM file

I have a LabVIEW 7.1 question regarding data logging. I have designed a system that reads the pressure of 6 4-20Ma pressure transducers. This data is then filtered to remove any noise, and displayed to the user on the computer's screen.
I am currently reading the data at 1000HZ using the DAQ Assistant, which seems to give a clear picture of the pressure changes. My supervisor has asked me to allow the system to log the results for what may be 3 or 4 days. As you ca imagine, 48 hours at 1000 samples a second is a lot of data! I need some method to reduce the data rate written to the file. Ideally, I would like to take one second of data, find the highest reading, and then file a single entry and a timestamp interval of 1 second. So, for each hour, there would be 3600 rows with 7 columns (1 time stamp and 6 sensors). It would be nice if the 1 second average could be adjustable, so that if long term logging is to be done (a week, for example), the interval can be changed to 5 seconds or whatever.
I have tried reducing the data read rate as much as possible, but it seems that 100hz is the smallest that is possible. That is still too high... as the hard drive would fill up in no time.
Any help in this area would be appreciated. I have tried a few things, and all to no success. I have included a copy of the code for anyone to review.
Hardware:
- 1 X P3 Laptop running LabVIEW 7.1 data acquisition software
- 1 X NI DAQCard-6062E interface PCard
- 1 X NI SC-2345 data acquisition hardware with
- 3 X SCC-CI20 current input module
- 6 X Omega PX 0-600PSIA 4-20mA pressure transducer
thanks so much!
Andrew
Attachments:
Testing.vi ‏812 KB

You would have to talk with your supervisor first to determine what he intends to do with the log data and what degree of resolution he actually needs first. You probably want the 1000Hz Sampling rate so you can do decent filtering on the signal (hopefully your pressures aren't actually changing at a faster rate than that). I'm assuming you are returning a single result for those 1000 readings for each sensor. Specify some file logging duration of n-seconds (or minutes or whatever). Between file writes, pop each filtered measurement into an array (either 1 array of 6 dimensions or 6 1-dimension arrays). After n-seconds have passed, determine the min, avg, and max values from each sensor (array) and log those with your timestamp. So if you set your log timer for 1 minute, you would log a single min, max, and average reading of 60 readings for 6 sensors (this would only require 1 row with say a timestamp and 3x6 (18) columns for each sensor's min, max, average data). After a 24hour period you will have logged 1440 rows of data. In 3 days that would only be 4320 rows of data. All that is as easy as using a timer and a case structure around your logging function which would be triggered every n-seconds. Everything else you're doing would be the same. None of this really has much to do with labview as it is more of a logical explanation of how and when to acquire and log your data. What method are you using for storing your data? CSV, BIN, etc.. If you also want to display the data in a chart, I would recommend charting the same data you're logging, otherwise your chart will probably crash your system at 1000samps/second for 60 hours.. Once again, it depends on how your supervisor is analyzing the logged data. Make your log duration programmable and change it until he is happy. If he's(she's?) using Excel, your maximum log timer would be 9 seconds (Equates to ~6.67 Logs per Minute, ~400 Logs per Hour, ~9600 Logs Per Day, for a total of 28,800 Logs(rows) for 3 days -- Excel is limited to 32000 rows).

Transfer data rate

OK, so I have resolved an older problem only to have dropped frames all the time during playback. How do I find out the maximum transfer data rate my processor can handle? ANy suggestions on how to get around an issue like that? If I want clean crisp graphics, how can I avoid the DV codec - which I understand is awful for graphics- yet still be able to play my sequence back without dropped frames?

Hi Kristin,
If I read correctly, you moved everything off your internal drive to an external. This external drive - is it a SATA drive, or FireWire? You mentioned SATA before, so I'm inclined to think that's what it is. If it IS an external Serial ATA drive, when you got it, did you zero all data on the drive before using it?
Also, when you started using this new external, did you change your capture/render drive settings in your prefs in FCP? If not, they may still be set to your system drive, the default, instead of your new external hard drive. If this is the case, change it in FCP, save, and quit. TRASH the render files and move all the capture files from the system disk. re-open FCP, reconnect the moved capture files (if any), and of course, you'll have to re-render most of your timeline. when you do this, it'll render everything to the new hard drive (SATA, yes?), and you SHOULD be good to go.
Now, as for interfacing with a monitor or an external device - are you going throgh firewire to a camera or deck and then to your video monitor? If so, no matter what, you won't be able to view anything but a single frame at a time with uncompressed. The only other thing that I can think of is that your camera/deck/external video device is powered on while you're trying to do this. In order to monitor Uncompressed externally, you need a pretty spiffy video capture card like the Kona. But internally, you should have no issues. So, make sure any external device except a hard drive is turned OFF, and disconnected.
If none of this works, what you may want to do is change your sequence settings back to NTSC/DV for compression, and when you're totally done editing your project, you change them BACK to uncompressed, render, and export an uncompressed file to an external hard drive, take that drive to a video production company, have them slap it on a DigitalBeta tape as a master, and you're good to go.
Hope this helps...
-Kris

Data Rate V Maximum data rate

Similar Messages

Maybe you are looking for