MATLAB IMAGE ACQUISITION TOOLBOX - RELEASE NOTES Betriebsanweisung Seite 330
- Seite / 574
- Inhaltsverzeichnis
- FEHLERBEHEBUNG
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
14 Using the VideoDevice System Object
14-2
VideoDevice System Object Overview
The Image Acquisition Toolbox introduces the VideoDevice System object™, which allows
single-frame image acquisition and code generation from MATLAB.
You use the imaq.VideoDevice function to create the System object. It supports the
same adaptors and hardware that the videoinput object supports; however, it has
different functions and properties associated with it. For example, the System object uses
the step function to acquire single frames.
- Image Acquisition Toolbox™ 1
- User's Guide 1
- How to Contact MathWorks 2
- Revision History 3
- Contents 5
- Using Events and Callbacks 10
- Using the Matrox Interface 13
- Troubleshooting 14
- Functions — Alphabetical List 16
- Block Reference 16
- Getting Started 17
- 1 Getting Started 18
- Product Overview 19
- Related Products 21
- Supported Hardware 21
- Image Acquisition Tool (GUI) 22
- Step 6: Acquire Image Data 33
- Step 7: Clean Up 37
- Introduction 39
- Toolbox Components Overview 40
- Toolbox Components 41
- 2 Introduction 42
- Supported Devices 43
- Setting Up Frame Grabbers 45
- Previewing Data 48
- Previewing Data 49
- Opening the Tool 60
- Parts of the Desktop 60
- Selecting a Device and Format 66
- Adding New Hardware 68
- Using a Camera File 68
- Setting Frames Per Trigger 70
- Setting the Color Space 71
- Logging Your Data 74
- Setting Up Triggering 77
- Setting a Region of Interest 80
- Restoring Default Parameters 85
- The Preview Window 86
- Acquiring Data 88
- About the Session Log 101
- Saving the Session Log 101
- Copying the Session Log 102
- Adaptors 111
- Connecting to Hardware 119
- Getting Hardware Information 120
- Determining the Device ID 121
- 5 Connecting to Hardware 122
- Getting Hardware Information 123
- Creating a Video Input Object 127
- Specifying the Video Format 129
- Using the save Command 145
- Using the obj2mfile Command 145
- Acquiring Image Data 149
- Data Logging 151
- 6 Acquiring Image Data 152
- Data Logging 153
- Specifying the Trigger Type 156
- Using an Immediate Trigger 157
- Using a Manual Trigger 159
- Specifying the Trigger Type 167
- Executing Multiple Triggers 181
- Managing Memory Usage 186
- Logging Image Data to Disk 190
- Logging Image Data to Disk 193
- Image Acquisition Overview 200
- Overview 201
- Understanding Image Data 209
- Specifying the Color Space 214
- Viewing Acquired Data 220
- Retrieving Timing Information 221
- 02-Mar-2007 13:00:24 222
- [data time] = getdata(vid); 222
- 8 Using Events and Callbacks 230
- Event Types 231
- Event Types 233
- Retrieving Event Information 234
- Retrieving Event Information 235
- Monitoring Memory Usage 243
- Simulink 247
- Using the imaqlib Command 249
- Using Code Generation 251
- Saving Video Data to a File 252
- Saving Video Data to a File 253
- Step 5: Connect the Blocks 255
- Step 7: Run the Simulation 257
- Types of Setups 260
- Windows Configuration 262
- Linux Configuration 263
- Mac Configuration 264
- The TCP/IP tab 266
- The DNS tab 267
- The Ethernet tab 268
- Software Configuration 269
- Setting Preferences 271
- Property Display 278
- Set GigE Properties 280
- Use GigE Commands 281
- Create the gigecam Object 283
- Using the Kinect for Windows 289
- Detecting the Kinect Devices 295
- Saturation = 1 298
- Sharpness = 0.5 298
- WhiteBalance = 2700 298
- Runtime from the list 316
- 13 Using the Matrox Interface 322
- L = isLocked(obj) 333
- Kinect for Windows Metadata 335
- <property_value> 338
- Using the codegen Function 342
- Shared Library Dependencies 342
- Adding Support for Additional 345
- Hardware 345
- Troubleshooting Overview 348
- DALSA Coreco IFC Hardware 349
- 16 Troubleshooting 350
- DALSA Coreco Sapera Hardware 351
- Data Translation Hardware 353
- Hamamatsu Hardware 361
- Matrox Hardware 362
- Matrox Hardware 363
- QImaging Hardware 364
- QImaging Hardware 365
- National Instruments Hardware 366
- Point Grey Hardware 368
- Point Grey Hardware 369
- Kinect for Windows Hardware 370
- Kinect for Windows Hardware 371
- GigE Vision Hardware 372
- GigE Vision Hardware 373
- [d t m]=getdata(vid,2); 377
- GenICam GenTL Hardware 380
- GenICam GenTL Hardware 381
- Windows Video Hardware 382
- Windows Video Hardware 383
- Linux Video Hardware 385
- Linux DCAM IEEE 1394 Hardware 387
- Macintosh Video Hardware 388
- Description 394
- Examples 396
- commands 397
- See Also 398
- executeCommand 403
- Input Arguments 404
- More About 420
- Properties 438
- imaq.VideoDevice 439
- Functions 440
- obj2mfile 455
- Custom Update Function 461
- BayerSensorAlignment 492
- Characteristics 493
- DeviceID 494
- DiskLogger 496
- DiskLoggerFrameCount 501
- ErrorFcn 502
- EventLog 503
- FrameGrabInterval 506
- FramesAcquired 508
- FramesAcquiredFcn 509
- FramesAcquiredFcnCount 510
- FramesAvailable 511
- FramesPerTrigger 512
- InitialTriggerTime 513
- LoggingMode 516
- NumberOfBands 520
- Previewing 523
- ReturnedColorSpace 524
- ROIPosition 526
- Selected 530
- SelectedSourceName 532
- SourceName 536
- StartFcn 537
- TimerFcn 541
- TimerPeriod 542
- TriggerCondition 543
- TriggerFcn 545
- TriggerFrameDelay 546
- TriggerRepeat 548
- TriggersExecuted 550
- TriggerSource 551
- TriggerType 553
- UserData 557
- VideoFormat 558
- VideoResolution 560
- From Video Device 562
- Code Generation 563
- Dialog Box 564
- From Video Device 565
- 19 Block Reference 566
- Video Input (Obsolete) 573
Verwandte Produkte und Handbücher für Software MATLAB IMAGE ACQUISITION TOOLBOX - RELEASE NOTES
Software MATLAB BUILDER JA 2 Betriebsanweisung
(292 Seiten)
(292 Seiten)
Software MATLAB BUILDER EX 1 Betriebsanweisung
(182 Seiten)
(182 Seiten)
© 2020, manymanuals.de. Alle Rechte vorbehalten. | 0.040 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern