-
-
Notifications
You must be signed in to change notification settings - Fork 391
Open
Labels
1. Device support2. Needs informationsNeeds additional informationsNeeds additional informations5. GigeIssue in the GigEVision implementationIssue in the GigEVision implementation
Description
Describe the bug
Multiple acquisition and single acquisition tests fail for the ContrasTech Mars 800-200gc camera. Errors indicate GigEVision write_memory error (invalid-parameter) and missing timestamp information.
Example output from arv-camera-test-0.10:
Looking for the first available camera
vendor name = ContrasTech
model name = Mars 800-200gc
device serial number = 3C04215PAK00002
image width = 800
image height = 600
exposure = 4000 µs
gain = 1 dB
payload = 480000 bytes
gv n_stream channels = 1
gv current channel = 0
gv packet delay = 0 ns
** (arv-camera-test-0.10:13510): CRITICAL **: arv_gc_integer_get_value: assertion 'error == NULL || *error == NULL' failed
gv packet size = 0 bytes
Can't create stream thread: [ArvGevSCPSPacketSize] [ArvGevSCPSPacketSizeReg] GigEVision write_memory error (invalid-parameter)
To Reproduce
Steps to reproduce the behavior:
- Run the test:
arv-camera-test-0.10- Or run your own program (
main2.cpp) using Aravis:
./main2
Using camera: ContrasTech-Mars 800-200gc-3C04215PAK00002
Can't create stream: [ArvGevSCPSPacketSize] [ArvGevSCPSPacketSizeReg] GigEVision write_memory error (invalid-parameter)Expected behavior
- Stream thread should be created successfully.
- Packet size should not be 0 bytes.
- Multiple and single acquisition tests should pass.
Camera description:
- Manufacturer: ContrasTech
- Model: Mars 800-200gc
- Interface: GigE Vision
Platform description:
- Aravis version: 0.9.1 (also tested 0.8.35)
- OS: Ubuntu 20.04
- Hardware: x86_64
Additional context
- Camera works with MVViewer.
- Failures occur during
ArvGevSCPSPacketSizewrites.
main2.cpp code:
main2.cpp
Metadata
Metadata
Assignees
Labels
1. Device support2. Needs informationsNeeds additional informationsNeeds additional informations5. GigeIssue in the GigEVision implementationIssue in the GigEVision implementation