Data log rate of Counter Period acquisition
I'm measuring and recording the period of a digital input pulse train (input to NI9421 card on a 'C' series DAQ chassis and recorded via LabVIEW SignalExpress 2009). The 'Counter Period' acquisition step is configured to use '1 Counter' measurement method.
In order to record the data I have to use '1 Sample (On Demand)' Acquisition mode.
When I review the recorded data, how can I determine:
a) the sample frequency of the recorded data points ?
b) the absolute timestamp of any data point ?
The log file has no information regarding the recording frequency, and from my experiments this seems to change based on the measured period of the input.
Any ideas??
Solved!
Go to Solution.
Hi a.yearsley,
The counters on the 1st generation cDAQ chassis (9172) do not support sample-clocked period measurements. I'm assuming you are using this chassis since you mentioned that you have the module in slot 5 or 6.
Your edge count workaround is very similar to the High Frequency 2 counter method. In either case, you specify a time duration and count the edges of your external signal during this time. The 2nd counter is used to generate the gate signal for the specified time duration. Your measurement error with this method is up to 1 period of the external signal, so it is more commonly used with higher frequency signals (I'm not sure what the frequency of your signal is).
The standard 1 counter method counts the number of ticks of an internal timebase (80 MHz) during one period of your input signal. Since the signal itself is what is gating the measurement, the sample is latched into the buffer on the edge of the signal and is not clocked independently. If desired, you could configure Implicit Timing, which would give you a period measured for every edge of the input signal.
Taking the above idea one step further, you could just configure an edge count task with the 80 MHz timebase as the source. Use the external signal as a sample clock. The only difference between this and using the standard period measurement with implicit timing is that the counter is not reset after every sample. This might make it easier to keep track if you want to log a sample every x seconds (i.e. once the total count passes a certain value). You can find the period by subtracting consecutive counts and multiplying by the period of the timebase (12.5 ns). The counter would rollover after about 53.69 seconds, but if you read the count as U32 there won't be any problem with the subtraction (0000 - FFFF = 1 if the numbers are U32).
If you are on a 2nd generation cDAQ chassis (e.g. 9174, 9178, 9188), then you actually do have support for a sample-clocked period measurement. You can choose whether or not to enable averaging. The 9178/9174 user manual has diagrams showing the sample-clocked frequency measurement which is essentially the same thing (the driver inverts the period measurement to obtain frequency). You must guarantee at least 1 edge of your external signal between sample clocks if using this method. The clock can come from a number of sources--I would probably recommend using another counter to generate it.
Best Regards,
John Passiak
Similar Messages
-
How can I save first data before data logging in a regular period?
Hi,
I need some help to see what's wrong with my VI. I want to save the first data when I launch my VI until reach the first minute, after I want save data minute by minute, but in this fisrt period my VI does't save this data in the .lvm file.
Could someone help me?
Thanks.
Attachments:
savefirstdata.vi 76 KBThanks MoReese, but I can't open again. Well, I think I figured out what you have said last post and it worked fine, I will attach the new VI. So, I got another question right now. Why when data acquisiton has start collecting data with timestamp after some time it's incremented 1 second in the time stamp inside the lvm file or same in txt file? I'll attach the file to exemplify.
Thanks for the responses.
Diego
Attachments:
savefirstdata3.vi 53 KB
incrementsecond.png 19 KB -
How do I control a data log session with period and sample time?
I need a data logging system where the operator can select 2 logging parameters: Log Period and Sample Time. I also need a START and STOP button to control the logging session. For example, set the log period for 1 hour and the sampling time for 1 second. (I may be using the wrong jargon here.) In this case when the START button is clicked, the system starts logging for 1 second. An hour later, it logs data for another second, and so on until the operator clicks the STOP button. (I will also include a time limit so the logging session will automatically stop after a certain amount of time has elapsed.)
It’s important that when the STOP button is clicked, that the system promptly stops logging. I cannot have the operator wait for up to an hour.
Note that a logging session could last for several days. The application here involves a ship towing a barge at sea where they want to monitor and data log tow line tension. While the system is logging, I need the graph X-axis (autoscaled) to show the date and time. (I’m having trouble getting the graph to show the correct date and time.) For this application, I also need the system to promptly start data logging at a continuous high rate during alarm conditions.
Of course I need to archive the data and retrieve it later for analysis. I think this part I can handle.
Please make a recommendation for program control and provide sample code if you can. It’s the program control concepts that I think I mostly need help here. I also wish to use the Strip Chart Update Mode so the operator can easily view the entire logging session.
DAQ Hardware: Not Selected Yet
LabVIEW Version: 6.1 (Feel free to recommend a v7 solution because I need to soon get it anyway.)
Operating System: Win 2000
In summary:
How do I control a graphing (data log) session for both period and sample time?
How do I stop the session without having to wait for the period to end?
How do I automatically interrupt and control a session during alarm conditions?
Does it make a difference if there is more than one graph (or chart) involved where there are variable sample rates?
Thanks,
DaveHello Dave,
Sounds like you have quite the system to set up here. It doesn�t look like you are doing anything terribly complicated. You should be able to modify different examples for the different parts of your application. Examples are always the best place to start.
For analog input, the �Cont Acq&Chart (buffered).vi� example is a great place to start. You can set the scan rate (scans/second) and how many different input channels you want to acquire. This example has its own stop button; it should be a simple matter to add a manual start button. To manually set how long the application runs, you could add a 100 ms delay to each iteration of the while loop (recommended anyway to allow processor to multi-task) and add a control that sets the number
of iterations of the while loop.
For logging data, a great example is the �Cont Acq to File (binary).vi� example.
For different sample rate for different input lines, you could use two parallel loops both running the first example mentioned above. The data would not be able to be displayed on the same graph, however.
If you have more specific questions about any of the different parts of your application, let me know and I�ll b happy to look further into it.
Have a nice day!
Robert M
Applications Engineer
National Instruments
Robert Mortensen
Software Engineer
National Instruments -
Log an analog channel and counter period channel to hard disk simultaneously
We are in a rush, and need to log one analog channel and one counter period measurement to disk simultaneoulsy using card controlled timing and set # of samples. Should be easy, but can't figure it out. Labview 6.1 we have & DAQ 6013E we just bought.
Greetings,
With regards to logging analog input data to file, I would suggest that you examine the examples available in the following location:
Examples >> Hardware Input and Output >> DAQ >> Analog Input >> Stream to Disk
Because you are interested in a finite number of samples, you should look at Acq N Scans to File (wdt).vi.
With regards to logging period measurement data to file, I would suggest that you examine the following example:
Examples >> Hardware Input and Output >> DAQ >> Counters >> DAQ-STC >> Measure Buffered Period (DAQ-STC).vi
This example does not log to file, but it does demonstrate how to program a buffered period measurement. You will need to add the logging functionality to this VI as demonstrated in Analog Input >> Stre
am to Disk.
Good luck with your application.
Spencer S. -
Pulsewidth data logging with counter channel
Hello everyone.
i have query with data logging of pulse duration measured with counter input into .lvm file
pulse signal contain frequency of 100 hz with pulse duration vary from 2 to 8 ms
i want to log pulse duration in .lvm file.
when running vi(below screen shot) i find data logg with duplicate instance of time.
i want to log pulse duration data with every ridging or falling edge of pulse.
so if i run vi for 20 sec i sould have 2000 reading of pulse duration in my.lvm file with appropriate time in time column
Attachments:
pulsewidth using counter.jpg 659 KBHello Karthik,
I can think of two ways I would approach this. One would use software timing, and the other would use hardware timing.
1. Software timing: This might be the easiest approach. The idea is you would use your example much as it is written, then use a loop with a delay as the "Time between samples" to call your counting code over and over. In this case, I have a few suggestions for your code. First, instead of the loop, you could start the counter, use a delay in a sequence structure (use "Wait (ms)", not "Wait Until Next ms Multiple")for your "Sampling time", then read the counter and stop. After the stop you'll need another "Wait (ms)" in a sequence structure for your "Time between samples". Finally, wrap a loop around all of this to r
epeat it. One advantage of this approach is the user can change the between time on the fly.
2. Hardware timing: The idea behind this would be to use two counters. The first would count, the output of the second would be wired to the gate of the first to control when the first counts. The second counter would be programmed to output a pulse train where the positive portion of the pulse would be your "Sampling time" and the negative portion would be your "Time between samples". The creative part for this approach would be figuring out when to read the count. One way to do this would be to also connect the gate of the second counter to an analog input, then read the count whenever the input goes low (say, below 1 volt). This approach might be the more accurate of the two. However, you would always be getting a total count, so you would have to subract the previous count each time. Also, you would not be able to change your sampling time or between time once you start.
Finally
I'd suggest looking at some examples - you can usually find code to help you.
Best Regards,
Doug Norman -
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. -
Help please: DAQWare or data logging software (multichannel data capture) questions
I am writing regarding DAQWare, data logging software, and the PC-LPM-16
board, which a group of us a trying to come to grips with. This is rather
lengthy, I'm afraid...
We are a group of college students in a computer programmer/analyst
program. We have a course that involves doing a project to go through the
software development lifecycle (or as much of it as can be done in a term).
For our project we teamed up with a group in the industrial hygiene
program; they have a computer (standalone) with a PC-LPM-16 (PnP) DAQ board
and the NI-DAQ software (all of this has been around for a few years, but
has not been used much), and our goal was to capture the data they are
measuring (atmospheric pollutants) to an Microsoft Access database.
We are not familiar with DAQ systems, but were shown the software they had
installed. This included DAQWare (appears to be version 2.0). We thought
we could use DAQWare to log data to a text file, which we then would import
into the Access database. We came up with VBA code to parse the ASCII text
file created, but have run into one problem: DAQWare does not timestamp
each sample, but only puts a single timestamp in the header information.
Now we could extrapolate the time for each line based on the sample rate,
except that sometimes it seems to put in 8 values per sample, sometimes 12
values. For instance, in the sample of a text file below, the capture was
run for 1 minute at a sample rate of 60, and there were 480 measurements in
the file, or 8 lines of measurements per sample. (At a sample rate of 100,
we got 800 measurements in the file etc.) This was two weeks ago. Today,
we returned to capture more data, and DAQWare was logging 12 measurements
per sample (so at a sample rate of 100, we ended up with 1200 lines of
measurements). We do not know where this factor of 8 or 12 is coming from
or how it got changed in the two weeks between captures. We would like to
be able to have them just run DAQWare, for days on end if they wanted,
capture the data to file, then use our code to parse the text file into the
database, but if we cannot put timestamps on the readings, there seems no
point.
*** Example of a capture below... ***
DAQWare File
Version: 2.0
Number of Lines in Header: 10
Comment:
Date: 10-18-1999 Time: 10:01:39
Sample Rate: 60.0
Scan Rate: 0.0
File Format: 1
Samples per Channel: 480.0
Number of Channels: 5
O3 SO2 NOX NO2 NO
4 3 2 1 0
1 1 1 1 1
0.537 0.276 0.259 -0.017 0.015
0.537 0.273 0.261 -0.022 0.012
0.537 0.276 0.259 -0.037 0.012
0.537 0.276 0.264 -0.007 0.015
*** and so on... ***
Regarding this attempt to use DAQWare:
1. Can you tell us where this factor (8 or 12 or however many more readings
than we would expect) means, where it is read from or set?
2. Is there an updated version of DAQWare that we should download that
would be better?
3. Is there some other existing software that we can download to use to
perform basic logging of multichannel analog input to a text file (with
timestamp)?
I realise that the software comes with tools (DLL functions) that one can
use to create custom software to interface with the DAQ board, but in the
limited amount of time we have we are not sure we can learn enough about
these functions to write our own datalogging software.
However, to see if I could grasp the basics, I have looked through the
examples for Visual Basic and think that a program would run something like
this:
1. at the beginning, use LPM16_Calibrate to reset the board
2. configure acquisition with DAQ_Config
3. start acquisition with Lab_ISCAN_Start
4. loop to check is acquisition done with Lab_ISCAN_Check
5. once sampling done, write data out to file
6. loop back up to 3 to get next lot of samples
Unfortunately, a sample app using Access and VBA I created came back with
an error telling me it could not find nidaq.dll (even though this is in the
Windows system directory); probably it is not a good idea to try to do this
in Access in the first place. I am going to have a go using Delphi, which
I know a bit better.
One thing I am unsure of is what the numbers will be coming out of
Lab_ISCAN; the reference file seems to indicate they will be binary
readings, not voltages, and I wonder how to correlate these with instrument
measurements (the instrumentation people we going to set it up so that
1mV=1ppm).
Any help you can give to point us in the right direction would be
appreciated.
Sincerely, Marc Bell ([email protected])I am writing regarding DAQWare, data logging software, and the PC-LPM-16
board, which a group of us a trying to come to grips with. This is rather
lengthy, I'm afraid...
We are a group of college students in a computer programmer/analyst
program. We have a course that involves doing a project to go through the
software development lifecycle (or as much of it as can be done in a term).
For our project we teamed up with a group in the industrial hygiene
program; they have a computer (standalone) with a PC-LPM-16 (PnP) DAQ board
and the NI-DAQ software (all of this has been around for a few years, but
has not been used much), and our goal was to capture the data they are
measuring (atmospheric pollutants) to an Microsoft Access database.
We are not familiar with DAQ systems, but were shown the software they had
installed. This included DAQWare (appears to be version 2.0). We thought
we could use DAQWare to log data to a text file, which we then would import
into the Access database. We came up with VBA code to parse the ASCII text
file created, but have run into one problem: DAQWare does not timestamp
each sample, but only puts a single timestamp in the header information.
Now we could extrapolate the time for each line based on the sample rate,
except that sometimes it seems to put in 8 values per sample, sometimes 12
values. For instance, in the sample of a text file below, the capture was
run for 1 minute at a sample rate of 60, and there were 480 measurements in
the file, or 8 lines of measurements per sample. (At a sample rate of 100,
we got 800 measurements in the file etc.) This was two weeks ago. Today,
we returned to capture more data, and DAQWare was logging 12 measurements
per sample (so at a sample rate of 100, we ended up with 1200 lines of
measurements). We do not know where this factor of 8 or 12 is coming from
or how it got changed in the two weeks between captures. We would like to
be able to have them just run DAQWare, for days on end if they wanted,
capture the data to file, then use our code to parse the text file into the
database, but if we cannot put timestamps on the readings, there seems no
point.
*** Example of a capture below... ***
DAQWare File
Version: 2.0
Number of Lines in Header: 10
Comment:
Date: 10-18-1999 Time: 10:01:39
Sample Rate: 60.0
Scan Rate: 0.0
File Format: 1
Samples per Channel: 480.0
Number of Channels: 5
O3 SO2 NOX NO2 NO
4 3 2 1 0
1 1 1 1 1
0.537 0.276 0.259 -0.017 0.015
0.537 0.273 0.261 -0.022 0.012
0.537 0.276 0.259 -0.037 0.012
0.537 0.276 0.264 -0.007 0.015
*** and so on... ***
Regarding this attempt to use DAQWare:
1. Can you tell us where this factor (8 or 12 or however many more readings
than we would expect) means, where it is read from or set?
2. Is there an updated version of DAQWare that we should download that
would be better?
3. Is there some other existing software that we can download to use to
perform basic logging of multichannel analog input to a text file (with
timestamp)?
I realise that the software comes with tools (DLL functions) that one can
use to create custom software to interface with the DAQ board, but in the
limited amount of time we have we are not sure we can learn enough about
these functions to write our own datalogging software.
However, to see if I could grasp the basics, I have looked through the
examples for Visual Basic and think that a program would run something like
this:
1. at the beginning, use LPM16_Calibrate to reset the board
2. configure acquisition with DAQ_Config
3. start acquisition with Lab_ISCAN_Start
4. loop to check is acquisition done with Lab_ISCAN_Check
5. once sampling done, write data out to file
6. loop back up to 3 to get next lot of samples
Unfortunately, a sample app using Access and VBA I created came back with
an error telling me it could not find nidaq.dll (even though this is in the
Windows system directory); probably it is not a good idea to try to do this
in Access in the first place. I am going to have a go using Delphi, which
I know a bit better.
One thing I am unsure of is what the numbers will be coming out of
Lab_ISCAN; the reference file seems to indicate they will be binary
readings, not voltages, and I wonder how to correlate these with instrument
measurements (the instrumentation people we going to set it up so that
1mV=1ppm).
Any help you can give to point us in the right direction would be
appreciated.
Sincerely, Marc Bell ([email protected]) -
Which is the best structure for start/stop data logging?
Hi everybody,
hope I can explain my problem good enough that anyone can help me:
I have a VI which continuely shows on a graph the voltage of a Analog Input of a DAQ device. Now I want to allow the user to start/stop with a click on a button data logging. Means that a second loop writes to a selected path every ms the data to a spreadsheet file.
At the moment my VI works like this:
You run the VI and Labview asks you one time for the file path, then you can start and stop the data logging. But you can do it only one time. If you want to log a certain time later another file, you have to close and open the whole VI again which is not very professional...
My target is:
It is onlyl necessary to start the VI one time. Then you can select a new file path, log data, select another file path, logging data again....and so on...
Which programm structure is necessary, can anyone help me as a labview beginner with that issue? I attached the VI if someone just wants to edit that...
Thank you for your help!! Markus
Attachments:
Logging voltage.vi 93 KB
screenshot.JPG 98 KB@NaruF1 and GerdW
you are right, there is a mistake, both loop rates should be the same (10 ms) :-)
@NaruF1
yes you understood correctly that the file dialog should appear every time the user wants to start writing a new log-file. The voltage we measure is a analog signal, so there will be several interesting periods we want to save for a later analysis in Excel.
To your 2nd point: if it works with a array it will be fine. But it must be possible to log data for lets say 5 minutes, so the array won´t be too large? (5 min @ 10 ms loop rate will be 30000 rows..
attached is the VI, saved as LV2009..
Thanx a lot!
@GerdW
..you ask why I didn´t create a structure like you recommended with notifiers or queues? The simple answer would be that I am not familiar with all this.. just began to write my first Labview programm. I will have al look to the LV help with all that stuff... Thank you a lot
Attachments:
Logging voltage.vi 80 KB -
Data logging optimization function in LabVIEW and SignalExpress
Hello, everyone! I and a colleague have assembled the attached VI,
which is used to control a plant growth chamber, and I could use some advice.
I would like to add data logging capabilities, ideally to note (1)
environmental conditions, such as temp and CO2 level and (2) when certain
situations occur, such as high CO2 or low pressure (which results in a change
to the “Case Structure for CO2 and Pressure”).
The chamber runs for weeks at a time, though, so I have a constraint.
Instead of continuously logging all the environmental data (which would yield
giant file sizes), I want to be able to take “snapshots”, say every 5 minutes,
so I can examine the chamber’s condition over a long period of time.
I attempted to use the Time Delay function to control the Write Measurements
function (as in LabVIEW’s Cycle Analysis example, which I’ve also attached),
but Time Delay halted my entire program.
I also tried the Wait (ms) function, but had no success.
I recently discovered the powerful data review and reporting tools that
SignalExpress has to offer. Ideally, I
would like to use a SignalExpress express VI to record the measurements instead of the more primative Write Measurements, but, I’m not sure how to implement this in my VI. For example, would I make a data acquisition VI in SignalExpress for all my sensors, export to LabVIEW, and use that to replace the current DAQ structure in my VI? (Because the chamber VI is interactive, I'm pretty sure that porting the LabVIEW VI to SignalExpress wouldn't work out well.) And I’m
still not sure how to control how often it records measurements.
Any advice would be much appreciated!
Attachments:
Chamber VI.vi 789 KB
Cycle Analysis.vi 300 KBHi, Sarah. Yes I definitely plan to use LabVIEW for the majority of my data acquisition and logging. I apologize, I think I probably should have broken my post into two separate posts for clarity, as my major concern is being able to set how often LabVIEW logs the environmental data (viewing the logged data in SignalExpress would be nice, but not a requirement).
As I explained before, I'd really like to be able to set up a system that records the environmental condtions at regular time intervals, say every 30 minutes, or if my "Case Structure for CO2 and Pressure" status changes (such as from "Normal Conditions" to "High CO2".
As an example, attached is a boolean structure (TimedWritedMeasurements.vi) that I came up with to record a simulated signal every 5 seconds (5000 ms). Once I can get it to work, I would connect the boolean to my environmental sensor outputs and CO2 and Pressure case structure in my Chamber VI.vi that I attached in my first post.
My problem is I can't seem to get the Trigger and Gate function to work the way I'd like. I'd like the Wait (ms) function to trigger the Trigger and Gate function every 5 seconds to change the case structure in the TimedWriteMeasurements.vi to "True", thereby causing the Write Measurement function to record the environmental conditions. Then I'd like the case structure reset to false, until it's triggered to true in another five seconds. Can anyone point me in the right direction?
Attachments:
TimedWriteMeasurements.vi 84 KB -
Hi,
I am using a cRio 9074 in scan mode and I have a fairly simple timed loop that should run at 5-10mSec periods to operate a pwm control. I also need to do some data logging and save two input signals (at approx. 1kS/sec). However, when I use write to spreadsheet, the loop speed drops and my timed loop period goes up to 50mSec. How can I speed this up, and what is the efficient way to save data in scan mode.
Thanks.
Solved!
Go to Solution.The single best way to improve determinism is to divide your acquisition/logging into two distinct producer/consumer loops as VTHokie says. Next best improvement would probably be using a binary format file structure rather than Write to Spreadsheet, which converts all data to ASCII representation prior to writing to file. Writing to ASCII files rather than binary files degrades performance in four ways:
CPU must be used to do the number to text conversion
ASCII represented numbers lose precision and don't exactly convert back to original data
The filesize is larger
When you go to read the file, it's slower for the above three reasons
On the other hand, an ASCII file is more portable - e.g., you can easily import into a third-party spreadsheet analysis program. But who in their right mind would export data OUTSIDE of LabVIEW when it offers best-in-industry analysis tools?
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;} -
Independen​t Sample and log rates
I would like to log data at 0.5 second intervals while the daq assistant acquires data at 1KHz,
I tried using the write to measurement file express vi but couldn't separate the sampling and logging rates.
Any suggestions with code is always appreciated.
Thanks !!
Attachments:
logger rates.vi 87 KBYour VI is saved in LabvIEW 2013, hence I can't open, either save it in previous version and upload or share the snapshot of block diagram.
Well, have you tried running two parallel loops one for acquisition and other for data logging.
Refer to these:
1. Application Design Patterns: Producer/Consumer
2. Data Acquisition Reference Design for LabVIEW
I am not allergic to Kudos, in fact I love Kudos.
Make your LabVIEW experience more CONVENIENT. -
No data in IT0007 during the period 05.05.2010 - 31.05.2010
Hi experts,
When i am running PY simulation for a particular employee who has joined as trainee a year before and was confirmed on 05.05.2011 I am getting error in log saying No data in IT0007 during the period 05.05.2010 to 31.05.2010. Pls brief me to overcome this issue ASAP.
Thanks in advance
UpensapPlease go to PA30 select the IT0007 and go for overview
check the start date of the records, check if there is data for the mentioned period in the error?
if not maintain it .
from which date the employees payroll is going to start? -
Determining Data transfer rate through modem in java
Hi,
I want to write an application in java which will communicate with
connected modem of the system and it will detect the data transfer rate.
I want to know how much data is transferring(upload/download)through modem and in a specific time how much data is transferred.
I will give some max upload/downloading limit for a specific time and if data transfer exceeds that limit,it will show message.
e.g if i fix max upload/download data transfer limit by the modem is say 10GB/20GB for a specific time span say for 15 days.Then my program automatically will start when the Modem will be connected and keep a log of data transfer(upload/download)and if data transfer goes beyond limit then it will show message.Also i would be able to see how much data is transferred for any specific day.
I want to know this type of application is possible in java.If yes then
which API's i need to use.
If this type of program is available in some site in other language then also i will be helpful.Pl give the links.
byeeeeeeee
PradiptoHi,
i want to do it in java only to explore the power of
java.I agree with Abuse, Java is not designed for such applications. I'm not even sure if you can solve your problems with Java. -
Configuring syslog and generating logs for a particular period.
Hi...
I have configured syslog server and the loggin enabled on ASA device... I want to generate the complete logs for a particular period of time. How can I generate this report.. Please help meHello,
I have an idea how it might work, but it is not certainly the best solution so if you will not find any other, this might work for you.
Enable sending logs to syslog server:
logging source-interface loopback
logging
configure EEM script to run "show log" periodicaly:
event manager applet test
event timer watchdog name test_name time 60 ! in seconds -> every minute
action 1.0 cli command "show log"
Best Regards
Please rate all helpful posts and close solved questions -
Data Log File Refnum Type Def Bug??
Hello,
I just found some quirky behaviour (LV 7.1.1):
1. In the attached LLB, open "RefnumVI.vi"
2. Select the Data Log File Refnum control and open it for editing (Edit - Customize Control ... from the menu)
3. Close "RefnumVI.vi" but leave "Refnum.ctl" open
4. Select the enum inside the refnum container, and open it
5. Select File - Save As ... and save the enum as "RefnumEnum2.ctl"
6. Close the enum
7. Save "Refnum.ctl", and close it
8. Reopen "RefnumVI.vi" and display its hierarchy (Browse - Show VI Hierarchy from the menu)
Notice that "RefnumVI.vi" still has a link to "RefnumEnum.ctl", even though we saved this as "RefnumEnum2.ctl" earlier.
If you go back to the VI, right click on the refnum, and replace it with itself (i.e. select "Refnum.ctl"), the link disappears.
This behaviour does not happen if I use a Cluster instead of a Data Log File Refnum. I imagine the difference is that the calling VI needs to know about the structure of the data log file in ways it doesn't need to know about the structure of a cluster, but this still is very counter-intuitive behaviour. Is this really expected? Or is it a bug? Is there any other way to remove the link?
Cheers,
Jaegen
Attachments:
RefnumEnumBug.llb 22 KBNathan,
Thanks for your response - I have 8.2 and am in the process of evaluating how/when to upgrade.
Does this mean that the compiler/linker is behaving differently depending on where you open a type def from? The reason I'm asking is that I've seen similar behavior when editing a hierarchy of type defs; depending on how I open the low-level type def I'm actually editing, changes will or won't get propagated to other instances properly.
Regarding this actual problem, the issue I had is that the data log file refnum type def exists on many VIs, and thus the incorrect link now exists on many VIs, and I don't see any way of correcting the problem without manually replacing the type def with itself in every location (given there's no "Replace All" feature in LV 7.1.1 ). However, the hierarchy I'm dealing with was only created for testing, so I don't actually need to fix it . I'll just know to avoid causing this problem in the first place in the future.
Jaegen
Maybe you are looking for
-
Palm Pre will not sync with EAS on Exchange 2010
I looked through the large EAS thread with the error "Unable to validate incoming server settings." Tried all of these issues and none have worked for me. Exchange version is Exchange 2010 running on Server 2008 R2; Tried without domain and it giv
-
It happened again!!! iPhoto stops deleting photos!
It happened again! As I reported in other threads in this forum, I have been experiencing deletion problems with iPhoto. This problem has been reported by many other users in different threads. To my knowledge, there has been no official fix / answer
-
How I work with MS-SQL function in oracle
I'm working in oracle now but I don't know how can I use following function in oracle. convert, dateadd, datediff, fetch_status, isnumeric, reverse, str and stuff
-
Web module generator: conditional formatting
Hi, I'm trying to generate the following behaviour in a web module. There is a status code in the table and I want it to be colored red when status = 'error' and green when status = 'running' else standard color. The item property "Formatting" can't
-
SCOM CI Connector is stuck in runnig state
Hello, I have problem with SCOM CI Connector in SCSM. It is stuck in running and 5%. I have tried to disable and re-enable but without success. I can't see any workflow related to this connector in workflow status. Is there any possibility how to sto