Comments (4)
samkearney
commented on June 3, 2024
Hey @vanvught,
Weird. I'm assuming this is from the latest installer version 0.2.0.7 downloaded from Bintray?
Can you find out the executable's exit code, using
> echo %ERRORLEVEL%
from rdmnet.
vanvught
commented on June 3, 2024
Hi Sam,
Yes, I am using the latest download. I have just written a dummy device for learning/debugging the LLRP protocol. I am eager to give it a proper test. - Arjan
C:\Program Files\ETC\RDMnet\bin>dir
Volume in drive C has no label.
Volume Serial Number is D289-73C5
Directory of C:\Program Files\ETC\RDMnet\bin
07-09-2019 16:20 <DIR> .
07-09-2019 16:20 <DIR> ..
11-04-2019 20:18 37.888 dnssd.dll
29-05-2019 23:09 90.112 llrp_manager_example.exe
29-05-2019 23:09 190.464 rdmnet_broker_example.exe
29-05-2019 23:09 97.792 rdmnet_device_example.exe
4 File(s) 416.256 bytes
2 Dir(s) 239.131.758.592 bytes free
C:\Program Files\ETC\RDMnet\bin>llrp_manager_example.exe
C:\Program Files\ETC\RDMnet\bin>echo %ERRORLEVEL%
-1073741819
from rdmnet.
samkearney
commented on June 3, 2024
I successfully reproduced this issue using the RDMnet binary package version 0.2.0.7.
I then tried and failed to reproduce it using the latest HEAD sources... so this got inadvertently fixed somewhere along the way.
I just made a new pre-release build, version 0.3.0.1: https://bintray.com/etclabs/rdmnet_bin/latest/0.3.0.1
The LLRP manager example should be working in this one.
This build also contains a ✨ brand new ✨ macOS native binary package! So, you're welcome to try that out as well.
from rdmnet.
vanvught
commented on June 3, 2024
@bootress
The Window version is working now.
C:\Program Files\ETC\RDMnet\bin>llrp_manager_example.exe
2019-09-10 14:33:14.723+02:00 RDMnet: Initializing network interfaces for LLRP...
2019-09-10 14:33:14.723+02:00 RDMnet: Set up LLRP network interface 127.0.0.1 for listening.
2019-09-10 14:33:14.723+02:00 RDMnet: Set up LLRP network interface ::1 for listening.
2019-09-10 14:33:14.723+02:00 RDMnet: Set up LLRP network interface fe80::b546:c256:1120:6ade for listening.
2019-09-10 14:33:14.723+02:00 RDMnet: Set up LLRP network interface 192.168.2.110 for listening.
2019-09-10 14:33:14.723+02:00 RDMnet: Set up LLRP network interface fe80::100:7f:fffe for listening.
2019-09-10 14:33:14.723+02:00 RDMnet: Set up LLRP network interface fe80::f59d:5459:1feb:d475 for listening.
2019-09-10 14:33:14.723+02:00 RDMnet: Set up LLRP network interface 169.254.212.117 for listening.
2019-09-10 14:33:14.723+02:00 RDMnet: Set up LLRP network interface fe80::5efe:192.168.2.110 for listening.
2019-09-10 14:33:14.723+02:00 RDMnet: Set up LLRP network interface fe80::5efe:169.254.160.92 for listening.
2019-09-10 14:33:14.723+02:00 RDMnet: Set up LLRP network interface fe80::cc8b:275b:e4b2:a05c for listening.
2019-09-10 14:33:14.723+02:00 RDMnet: Set up LLRP network interface 169.254.160.92 for listening.
Discovered network interfaces:
Handle Address MAC Name
0 127.0.0.1 00:00:00:00:00:00 Loopback Pseudo-Interface 1
1 ::1 00:00:00:00:00:00 Loopback Pseudo-Interface 1
2 fe80::b546:c256:1120:6ade xx:yy:e3:bc:e8:ef LAN-verbinding
3 192.168.2.110 xx:yy:e3:bc:e8:ef LAN-verbinding
4 fe80::100:7f:fffe 00:00:00:00:00:00 Teredo Tunneling Pseudo-Interface
5 fe80::f59d:5459:1feb:d475 00:ff:d8:02:5b:96 LAN-verbinding 3
6 169.254.212.117 00:ff:d8:02:5b:96 LAN-verbinding 3
7 fe80::5efe:192.168.2.110 00:00:00:00:00:00 isatap.{56AC8581-4A5A-4C89-82B3-24A78C3928EE}
8 fe80::5efe:169.254.160.92 00:00:00:00:00:00 isatap.{B0C6FC33-9AC3-4AFC-A9F0-9C167383FBAD}
9 fe80::cc8b:275b:e4b2:a05c 02:00:4c:4f:4f:50 Npcap Loopback Adapter
10 169.254.160.92 02:00:4c:4f:4f:50 Npcap Loopback Adapter
LLRP Manager Commands:
?: Print commands
d <netint_handle>: Perform LLRP discovery on network interface indicated by
netint_handle
pt: Print discovered LLRP Targets
pi: Print network interfaces
i <target_handle>: Get DEVICE_INFO from Target <target_handle>
l <target_handle>: Get DEVICE_LABEL from Target <target_handle>
si <target_handle>: Toggle IDENTIFY_DEVICE on/off on Target <target_handle>
sl <target_handle> <label>: Set DEVICE_LABEL to <label> on Target
<target_handle>
m <target_handle>: Get MANUFACTURER_LABEL from Target <target_handle>
c <target_handle>: Get DEVICE_MODEL_DESCRIPTION from Target <target_handle>
s <target_handle> <scope_slot>: Get COMPONENT_SCOPE for Scope Slot
<scope_slot> from Target <target_handle>
ss <target_handle> <scope_slot> <scope> [ip:port]: Set COMPONENT_SCOPE to
<scope> for Scope Slot <scope_slot> on Target <target_handle> with
optional static Broker address ip:port
q: Quit
d 3
Starting LLRP discovery...
Adding LLRP Target, UID 7ff0:3064d9e5, with handle 0
LLRP Discovery finished.
pt
Handle UID CID Type Hardware ID
0 7ff0:3064d9e5 9183911e-6986-40e8-a6e7-159f7cfd6251 RPT Device xx:yy:30:64:d9:e5
Also the macOS example is working - thank you!
MacBook-Air:~ arjanvanvught$ llrp_manager_example
2019-09-10 14:56:16.000+02:00 RDMnet: Initializing network interfaces for LLRP...
2019-09-10 14:56:16.000+02:00 RDMnet: Set up LLRP network interface 127.0.0.1 for listening.
2019-09-10 14:56:16.000+02:00 RDMnet: Set up LLRP network interface ::1 for listening.
2019-09-10 14:56:16.000+02:00 RDMnet: Set up LLRP network interface fe80::1 for listening.
2019-09-10 14:56:16.000+02:00 RDMnet: Set up LLRP network interface fe80::109f:c65c:9109:534b for listening.
2019-09-10 14:56:16.000+02:00 RDMnet: Set up LLRP network interface 192.168.2.133 for listening.
2019-09-10 14:56:16.000+02:00 RDMnet: Set up LLRP network interface fe80::d0f1:51ff:fe94:64d1 for listening.
2019-09-10 14:56:16.000+02:00 RDMnet: Set up LLRP network interface fe80::5dbd:3047:9370:985a for listening.
Warning: couldn't create LLRP Manager on network interface fe80::1 (error: 'Address already in use').
Discovered network interfaces:
Handle Address MAC Name
0 127.0.0.1 00:00:00:00:00:00 lo0
1 ::1 00:00:00:00:00:00 lo0
3 fe80::109f:c65c:9109:534b xx:yy:bb:d3:6f:b0 en0
4 192.168.2.133 xx:yy:bb:d3:6f:b0 en0
5 fe80::d0f1:51ff:fe94:64d1 d2:f1:51:94:64:d1 awdl0
6 fe80::5dbd:3047:9370:985a 00:00:00:00:00:00 utun0
LLRP Manager Commands:
?: Print commands
d <netint_handle>: Perform LLRP discovery on network interface indicated by
netint_handle
pt: Print discovered LLRP Targets
pi: Print network interfaces
i <target_handle>: Get DEVICE_INFO from Target <target_handle>
l <target_handle>: Get DEVICE_LABEL from Target <target_handle>
si <target_handle>: Toggle IDENTIFY_DEVICE on/off on Target <target_handle>
sl <target_handle> <label>: Set DEVICE_LABEL to <label> on Target
<target_handle>
m <target_handle>: Get MANUFACTURER_LABEL from Target <target_handle>
c <target_handle>: Get DEVICE_MODEL_DESCRIPTION from Target <target_handle>
s <target_handle> <scope_slot>: Get COMPONENT_SCOPE for Scope Slot
<scope_slot> from Target <target_handle>
ss <target_handle> <scope_slot> <scope> [ip:port]: Set COMPONENT_SCOPE to
<scope> for Scope Slot <scope_slot> on Target <target_handle> with
optional static Broker address ip:port
q: Quit
d 4
Starting LLRP discovery...
Adding LLRP Target, UID 7ff0:3064d9e5, with handle 0
pt
LLRP Discovery finished.
Handle UID CID Type Hardware ID
0 7ff0:3064d9e5 9183911e-6986-40e8-a6e7-159f7cfd6251 RPT Device xx:yy:30:64:d9:e5
from rdmnet.
Related Issues (13)
- Binary packages for Mac OS and Linux HOT 4
- llrp_manager_example : DMX512 Personality: 257 [> 255] HOT 1
- llrp_manager_example: Wrong output for Device info -> Product Category HOT 2
- llrp_manager_example: kLlrpCompNonRdmnet defined but not used HOT 1
- Library does not build on Linux HOT 3
- llrp_manager_example segfaults when there are > 200 targets on Linux HOT 6
- llrp_manager_example: Enhancement request: New LLRP Manager Commands HOT 7
- Download link binary packages is broken HOT 2
- llrp_manager_example: Hangs on discovery HOT 21
- [Question] Support for Android? HOT 3
- LLRP_Manager Hangs Discovery is fixed but IP issue HOT 9
- Lack of VECTOR_RPT_STATUS_BROADCAST_COMPLETE handling for NULL_ENDPOINT devices (but probably applies to all devices HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rdmnet.