RDM Responder Tests is not detecting ENTTEC DMXUSB pro

[Glavan Fernandez]

Hi All,

I am trying to test my RDM device using ENTTEC DMXUSB pro with open lighting RDM Responder Tests in Ubuntu. I have followed the getting started guide and installed OLA, ola-rdm-tests. Linux is detecting ENTTEX DMXUSB pro, I have verified using ola_dev_info command. Device information is like this.

 port 4, IN /dmx/universe/%d, priority 100
Device 9: KiNet Device
Device 10: Enttec Usb Pro Device
  port 0, IN Serial #: 02243655, firmware 2.4, priority 100
  port 0, OUT Serial #: 02243655, firmware 2.4, patched to universe 1, RDM supported
Device 11: StageProfi Device
  port 0, OUT /dev/ttyUSB0

But, RDM Responder is not detecting the device. I have attached a screenshot for the same.Can any one let me know that If am missing any steps here to detect this device here.

Regards,

Glavan Fernandez

[Peter Newman]

For anyone following along at home it's a PNG file.

Glavan, I was going to say you need to select the universe in the dropdown, but I'm guessing you'll tell me that's empty?

How did you install the RDM tests, which guide? With apt or via git and compiling?

It sounds like it could be this bug if it's apt:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790886

Either way, can we see the web browser's console logs, and the RDM test server log please?

Could you try the CLI test tool instead:

http://docs.openlighting.org/ola/man/man1/rdm_responder_test.py.1.html

P.S. Are you also http://www.rdmprotocol.org/forums/showthread.php?p=3180 which will save me answering that question too? And apologies for not replying their sooner if you are.

[Glavan Fernandez]

hey peter,

i installed RDM tests using Open lighting Architecture(OLA)

http://opendmx.net/index.php/OLA_Debian_/_Ubuntu

i followed the steps as per their guide, and arrived at this stage too

 port 4, IN /dmx/universe/%d, priority 100
Device 9: KiNet Device
Device 10: Enttec Usb Pro Device
  port 0, IN Serial #: 02243655, firmware 2.4, priority 100
  port 0, OUT Serial #: 02243655, firmware 2.4, patched to universe 1, RDM supported
Device 11: StageProfi Device
  port 0, OUT /dev/ttyUSB0

it looks like the system has detected the ENTTEC tester, but the web view is unable to do so.

I have attached the screenshot of my terminal logs.

and yes

 http://www.google.com/url?q=http%3A%2F%2Fwww.rdmprotocol.org%2Fforums%2Fshowthread.php%3Fp%3D3180&sa=D&sntz=1&usg=AFQjCNGgidFH5zihV51lq7SDgQmmvERzEA

the above link is my question on that forum.

Regards,

Glavan Fernandez

[Peter Newman]

Hi Glavan,

Can we see the output of "dpkg -l | grep -i ola" please?

That error is a bit odd, it's suggesting it's having comms problems with the Python code, but talking to localhost, not one I've seen before.

However the screenshot also confirms it's the Debian bug I linked to.

Can you do an "ls -al /usr/share/ola/rdm-server/". I think the symlinks will be broken, so should be made like so:

ln -s /usr/share/ola/rdm-server/jquery.min.js /usr/share/javascript/jquery/jquery.min.js

ln -s /usr/share/ola/rdm-server/jquery-ui.min.js /usr/share/javascript/jquery-ui/jquery-ui.min.js

ln -s /usr/share/ola/rdm-server/jquery-ui.css /usr/share/javascript/jquery-ui/themes/base/jquery-ui.css

Did you want to try rdm_responder_test.py as a temporary alternative?

[Glavan Fernandez]

Hi peter,

I have attached a screenshot of "dpkg -l | grep -i ola"

I tried the commands

Can you do an "ls -al /usr/share/ola/rdm-server/". I think the symlinks will be broken, so should be made like so:

ln -s /usr/share/ola/rdm-server/jquery.min.js /usr/share/javascript/jquery/jquery.min.js

ln -s /usr/share/ola/rdm-server/jquery-ui.min.js /usr/share/javascript/jquery-ui/jquery-ui.min.js

ln -s /usr/share/ola/rdm-server/jquery-ui.css /usr/share/javascript/jquery-ui/themes/base/jquery-ui.css

But it says the file already exists.

i tried those

[Peter Newman]

Oops, that will be me getting the syntax of ln wrong yet again, try this instead:

ln -s /usr/share/ola/rdm-server/jquery-1.7.2.min.js /usr/share/ola/rdm-server/jquery.min.js

ln -s /usr/share/ola/rdm-server/jquery-ui-1.8.21.min.js /usr/share/ola/rdm-server/jquery-ui.min.js

That should get that working. Alternatively, you may want to try this PPA, which has a more recent version of OLA in it (May 2016, compared to Sept 2015):

https://launchpad.net/~voltvisionfrenchy/+archive/ubuntu/ola?field.series_filter=xenial

Or git, which is newer still, but needs compiling...

[Glavan Fernandez]

hi peter,

It worked according to the procedure you told me.

Thanks a lot.

I'll keep you posted if i come across any other shortcomings.

Regards

Glavan Fernandez

[Peter Newman]

Great, glad you've sorted it.

As mentioned, getting through the git build may be worth the challenge for our latest and greatest set of RDM tests, instructions here:

https://www.openlighting.org/ola/linuxinstall/#Debian_Ubuntu

Just "sudo apt-get remove ola" first, so the deb package and git aren't fighting each other.

If you're on a VM you could snapshot so you could easily roll back if you needed to.

[Glavan Fernandez]

hi peter ,

i had kept the rdm testing aside due to other works on my plate, right now i am facing another issue , 

My Enttec DMXUSB pro device is physically not able to send any rdm commands, but from the UI it says test passed,

i am stuck at this point , is there a possibility that i have to purchase the license for RDM commands support or is there an alternative way 

to test without the RDM dongle (which enttec provides for entire functionality) 

[Peter Newman]

Hi Glavan,

Sorry for the slow reply.

What do you mean by physically not able to send them?

You don't need the Enttec USB licence stick, as long as the Enttec has the RDM capable firmware on, it should just work fine.

Does DMX work from your DMXUSB?

[Glavan Fernandez]

Dmx is working perfectly fine. When I gotta test a particular command say GetDeviceInfo().... Typically it should send me a start code i.e. 0xCC.... followed by the RDM command packet....neither am I able to see the start code nor the packet frame. I also tried to sniff the packets coming out of the dmxusb pro using a picoscope.... But I wasn't able to see any signal, 

Question,

Shouldn't we be running dmx in the background?

--

---
You received this message because you are subscribed to the Google Groups "RDM Testing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdm-testing...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Peter Newman]

Ah, you mean your device doesn't see the RDM packets? To clarify, do you mean that DMX is working fine from OLA using the same dongle?

Does discovery complete successfully? Can you use the device via OLA's web UI (or the CLI tools), rather than the RDM tests? I assume you've selected and added a number of tests, and selected the correct universe? If you run DMX in the background too, does that get to your device at least?

Can we have some olad -l 4 logs:

https://www.openlighting.org/ola/get-help/ola-faq/#How_do_I_get_olad_-l_4_logs

Whether you run DMX in the background or not shouldn't matter, it's just an option to be a more realistic test environment.

On Thursday, 17 January 2019 01:53:38 UTC, Glavan Fernandez wrote:

Dmx is working perfectly fine. When I gotta test a particular command say GetDeviceInfo().... Typically it should send me a start code i.e. 0xCC.... followed by the RDM command packet....neither am I able to see the start code nor the packet frame. I also tried to sniff the packets coming out of the dmxusb pro using a picoscope.... But I wasn't able to see any signal, 

Question,

Shouldn't we be running dmx in the background?

On Wed 16 Jan, 2019, 11:45 PM Peter Newman, <peterjnewman> wrote:

Hi Glavan,

Sorry for the slow reply.

What do you mean by physically not able to send them?

You don't need the Enttec USB licence stick, as long as the Enttec has the RDM capable firmware on, it should just work fine.

Does DMX work from your DMXUSB?

On Thursday, 10 January 2019 07:08:04 UTC, Glavan Fernandez wrote:

hi peter ,

i had kept the rdm testing aside due to other works on my plate, right now i am facing another issue , 

My Enttec DMXUSB pro device is physically not able to send any rdm commands, but from the UI it says test passed,

i am stuck at this point , is there a possibility that i have to purchase the license for RDM commands support or is there an alternative way 

to test without the RDM dongle (which enttec provides for entire functionality) 

--

---
You received this message because you are subscribed to the Google Groups "RDM Testing" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rdm-testing+unsubscribe@googlegroups.com.

[Glavan Fernandez]

hi peter ,

DMX commands are working perfectly.

i am currently using this URL which i came across while traversing through OLA test -up

http://localhost:9090/ola.html .

WEB UI looks like this.

Here i am able to run only the RDM discovery command.

But i am currently facing this issue.

I am a newbie to Linux platform so i am not able to rectify this issue.

is there a fix for this issue

"socket error...Already in use".

currently i am using the WEBUI from OLA

and the tests i run from this UI ... i am not able to see RDM packets in my DUT.

Can you please guide me on how to use the CLI tool?

i have enclosed a copy of olad -l 4

To unsubscribe from this group and stop receiving emails from it, send an email to rdm-testing...@googlegroups.com.

[Peter Newman]

On Thursday, 17 January 2019 10:14:00 UTC, Glavan Fernandez wrote:

hi peter ,

DMX commands are working perfectly.

i am currently using this URL which i came across while traversing through OLA test -up

http://localhost:9090/ola.html .

WEB UI looks like this.

Here i am able to run only the RDM discovery command.

So does it discover your fixture?

But i am currently facing this issue.

I'm not clear exactly which issue you're referring to, or do you just generally mean it's not working?

I am a newbie to Linux platform so i am not able to rectify this issue.

is there a fix for this issue

"socket error...Already in use".

Where do you get the socket error, can we see the surrounding log please.

currently i am using the WEBUI from OLA

and the tests i run from this UI ... i am not able to see RDM packets in my DUT.

Did you click the discovery button in the RDM test webpage, then add some tests, then click run tests?

Can you please guide me on how to use the CLI tool?

i have enclosed a copy of olad -l 4

Unfortunately lots more interesting stuff happens after that. Can you copy and paste all the text from that window up until after the point that it fails please.

[Glavan Fernandez]

 when i connect the enttec dmxusb pro to the scope i am able to see break and the start code generated, but that does not discover my device on the UI.

that's one thing.

when i try to run rdm_test_server.py from terminal it says socket error address already in use.

i did run OLA discovery command from the UI , i am able to select my universe but i am not getting any options from the drop down menu for RDM responders even though my DUT is connected.

 i will attach the full log below for olad -l 4

user@BLRMIESPC-981:~$ olad -l 4
olad/Olad.cpp:94: OLA Daemon version 0.10.2
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 5, events 2001, descriptor: 0xf2ce90
olad/OlaDaemon.cpp:121: Using configs in /home/user/.ola
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 8, events 2001, descriptor: 0xf2d4e0
common/thread/Thread.cpp:193: Thread pref-saver, policy SCHED_OTHER, priority 0
common/rdm/PidStoreLoader.cpp:251: Loading DISC_UNIQUE_BRANCH
common/rdm/PidStoreLoader.cpp:251: Loading DISC_MUTE
common/rdm/PidStoreLoader.cpp:251: Loading DISC_UN_MUTE
common/rdm/PidStoreLoader.cpp:251: Loading PROXIED_DEVICES
common/rdm/PidStoreLoader.cpp:251: Loading PROXIED_DEVICE_COUNT
common/rdm/PidStoreLoader.cpp:251: Loading COMMS_STATUS
common/rdm/PidStoreLoader.cpp:251: Loading QUEUED_MESSAGE
common/rdm/PidStoreLoader.cpp:251: Loading STATUS_MESSAGES
common/rdm/PidStoreLoader.cpp:251: Loading STATUS_ID_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading CLEAR_STATUS_ID
common/rdm/PidStoreLoader.cpp:251: Loading SUB_DEVICE_STATUS_REPORT_THRESHOLD
common/rdm/PidStoreLoader.cpp:251: Loading SUPPORTED_PARAMETERS
common/rdm/PidStoreLoader.cpp:251: Loading PARAMETER_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading DEVICE_INFO
common/rdm/PidStoreLoader.cpp:251: Loading PRODUCT_DETAIL_ID_LIST
common/rdm/PidStoreLoader.cpp:251: Loading DEVICE_MODEL_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading MANUFACTURER_LABEL
common/rdm/PidStoreLoader.cpp:251: Loading DEVICE_LABEL
common/rdm/PidStoreLoader.cpp:251: Loading FACTORY_DEFAULTS
common/rdm/PidStoreLoader.cpp:251: Loading LANGUAGE_CAPABILITIES
common/rdm/PidStoreLoader.cpp:251: Loading LANGUAGE
common/rdm/PidStoreLoader.cpp:251: Loading SOFTWARE_VERSION_LABEL
common/rdm/PidStoreLoader.cpp:251: Loading BOOT_SOFTWARE_VERSION_ID
common/rdm/PidStoreLoader.cpp:251: Loading BOOT_SOFTWARE_VERSION_LABEL
common/rdm/PidStoreLoader.cpp:251: Loading DMX_PERSONALITY
common/rdm/PidStoreLoader.cpp:251: Loading DMX_PERSONALITY_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading DMX_START_ADDRESS
common/rdm/PidStoreLoader.cpp:251: Loading SLOT_INFO
common/rdm/PidStoreLoader.cpp:251: Loading SLOT_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading DEFAULT_SLOT_VALUE
common/rdm/PidStoreLoader.cpp:251: Loading DMX_BLOCK_ADDRESS
common/rdm/PidStoreLoader.cpp:251: Loading DMX_FAIL_MODE
common/rdm/PidStoreLoader.cpp:251: Loading DMX_STARTUP_MODE
common/rdm/PidStoreLoader.cpp:251: Loading SENSOR_DEFINITION
common/rdm/PidStoreLoader.cpp:251: Loading SENSOR_VALUE
common/rdm/PidStoreLoader.cpp:251: Loading RECORD_SENSORS
common/rdm/PidStoreLoader.cpp:251: Loading DIMMER_INFO
common/rdm/PidStoreLoader.cpp:251: Loading MINIMUM_LEVEL
common/rdm/PidStoreLoader.cpp:251: Loading MAXIMUM_LEVEL
common/rdm/PidStoreLoader.cpp:251: Loading CURVE
common/rdm/PidStoreLoader.cpp:251: Loading CURVE_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading OUTPUT_RESPONSE_TIME
common/rdm/PidStoreLoader.cpp:251: Loading OUTPUT_RESPONSE_TIME_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading MODULATION_FREQUENCY
common/rdm/PidStoreLoader.cpp:251: Loading MODULATION_FREQUENCY_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading DEVICE_HOURS
common/rdm/PidStoreLoader.cpp:251: Loading LAMP_HOURS
common/rdm/PidStoreLoader.cpp:251: Loading LAMP_STRIKES
common/rdm/PidStoreLoader.cpp:251: Loading LAMP_STATE
common/rdm/PidStoreLoader.cpp:251: Loading LAMP_ON_MODE
common/rdm/PidStoreLoader.cpp:251: Loading DEVICE_POWER_CYCLES
common/rdm/PidStoreLoader.cpp:251: Loading BURN_IN
common/rdm/PidStoreLoader.cpp:251: Loading DISPLAY_INVERT
common/rdm/PidStoreLoader.cpp:251: Loading DISPLAY_LEVEL
common/rdm/PidStoreLoader.cpp:251: Loading PAN_INVERT
common/rdm/PidStoreLoader.cpp:251: Loading TILT_INVERT
common/rdm/PidStoreLoader.cpp:251: Loading PAN_TILT_SWAP
common/rdm/PidStoreLoader.cpp:251: Loading REAL_TIME_CLOCK
common/rdm/PidStoreLoader.cpp:251: Loading LOCK_PIN
common/rdm/PidStoreLoader.cpp:251: Loading LOCK_STATE
common/rdm/PidStoreLoader.cpp:251: Loading LOCK_STATE_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading LIST_INTERFACES
common/rdm/PidStoreLoader.cpp:251: Loading INTERFACE_LABEL
common/rdm/PidStoreLoader.cpp:251: Loading INTERFACE_HARDWARE_ADDRESS_TYPE1
common/rdm/PidStoreLoader.cpp:251: Loading IPV4_DHCP_MODE
common/rdm/PidStoreLoader.cpp:251: Loading IPV4_ZEROCONF_MODE
common/rdm/PidStoreLoader.cpp:251: Loading IPV4_CURRENT_ADDRESS
common/rdm/PidStoreLoader.cpp:251: Loading IPV4_STATIC_ADDRESS
common/rdm/PidStoreLoader.cpp:251: Loading INTERFACE_RENEW_DHCP
common/rdm/PidStoreLoader.cpp:251: Loading INTERFACE_RELEASE_DHCP
common/rdm/PidStoreLoader.cpp:251: Loading INTERFACE_APPLY_CONFIGURATION
common/rdm/PidStoreLoader.cpp:251: Loading IPV4_DEFAULT_ROUTE
common/rdm/PidStoreLoader.cpp:251: Loading DNS_IPV4_NAME_SERVER
common/rdm/PidStoreLoader.cpp:251: Loading DNS_HOSTNAME
common/rdm/PidStoreLoader.cpp:251: Loading DNS_DOMAIN_NAME
common/rdm/PidStoreLoader.cpp:251: Loading IDENTIFY_DEVICE
common/rdm/PidStoreLoader.cpp:251: Loading RESET_DEVICE
common/rdm/PidStoreLoader.cpp:251: Loading POWER_STATE
common/rdm/PidStoreLoader.cpp:251: Loading PERFORM_SELFTEST
common/rdm/PidStoreLoader.cpp:251: Loading SELF_TEST_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading CAPTURE_PRESET
common/rdm/PidStoreLoader.cpp:251: Loading PRESET_PLAYBACK
common/rdm/PidStoreLoader.cpp:251: Loading IDENTIFY_MODE
common/rdm/PidStoreLoader.cpp:251: Loading PRESET_INFO
common/rdm/PidStoreLoader.cpp:251: Loading PRESET_STATUS
common/rdm/PidStoreLoader.cpp:251: Loading PRESET_MERGEMODE
common/rdm/PidStoreLoader.cpp:251: Loading POWER_ON_SELF_TEST
common/rdm/PidStoreLoader.cpp:251: Loading BACKGROUND_QUEUED_STATUS_POLICY
common/rdm/PidStoreLoader.cpp:251: Loading BACKGROUND_QUEUED_STATUS_POLICY_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading BACKGROUND_STATUS_TYPE
common/rdm/PidStoreLoader.cpp:251: Loading QUEUED_STATUS_ENDPOINT_COLLECTION
common/rdm/PidStoreLoader.cpp:251: Loading QUEUED_STATUS_UID_COLLECTION
common/rdm/PidStoreLoader.cpp:251: Loading ENDPOINT_LIST
common/rdm/PidStoreLoader.cpp:251: Loading ENDPOINT_TO_UNIVERSE
common/rdm/PidStoreLoader.cpp:251: Loading RDM_TRAFFIC_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading ENDPOINT_MODE
common/rdm/PidStoreLoader.cpp:251: Loading ENDPOINT_LABEL
common/rdm/PidStoreLoader.cpp:251: Loading DISCOVERY_STATE
common/rdm/PidStoreLoader.cpp:251: Loading ENDPOINT_TIMING
common/rdm/PidStoreLoader.cpp:251: Loading ENDPOINT_TIMING_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading BINDING_CONTROL_FIELDS
common/rdm/PidStoreLoader.cpp:251: Loading ENDPOINT_IDENTIFY
common/rdm/PidStoreLoader.cpp:251: Loading BACKGROUND_DISCOVERY
common/rdm/PidStoreLoader.cpp:251: Loading ENDPOINT_DEVICE_LIST_CHANGE
common/rdm/PidStoreLoader.cpp:251: Loading ENDPOINT_DEVICES
common/rdm/PidStoreLoader.cpp:251: Loading TCP_COMMS_STATUS
common/rdm/PidStoreLoader.cpp:251: Loading ENDPOINT_LIST_CHANGE
common/rdm/PidStoreLoader.cpp:251: Loading DEVICE_MODE
common/rdm/PidStoreLoader.cpp:251: Loading SERIAL_NUMBER
common/rdm/PidStoreLoader.cpp:251: Loading FAN_MODE
common/rdm/PidStoreLoader.cpp:251: Loading STATUS_LEDS
common/rdm/PidStoreLoader.cpp:251: Loading CCT_ADJUST
common/rdm/PidStoreLoader.cpp:251: Loading GN_ADJUST
common/rdm/PidStoreLoader.cpp:251: Loading DMX_SIGNAL_LOSS_MODE
common/rdm/PidStoreLoader.cpp:251: Loading MODEL_ID
common/rdm/PidStoreLoader.cpp:251: Loading MODEL_ID_LIST
common/rdm/PidStoreLoader.cpp:251: Loading PIXEL_TYPE
common/rdm/PidStoreLoader.cpp:251: Loading PIXEL_COUNT
common/rdm/PidStoreLoader.cpp:251: Loading DIMMER_MODE
common/rdm/PidStoreLoader.cpp:251: Loading LIGHT_MODE
common/rdm/PidStoreLoader.cpp:251: Loading CONSTANT_COLOR_MODES
common/rdm/PidStoreLoader.cpp:251: Loading CP_DISPLAYON
common/rdm/PidStoreLoader.cpp:251: Loading CP_FIXTID
common/rdm/PidStoreLoader.cpp:251: Loading CP_EVAN_RGBCMY
common/rdm/PidStoreLoader.cpp:251: Loading CP_FIXWHEELSC
common/rdm/PidStoreLoader.cpp:251: Loading CP_LAMPONDMX
common/rdm/PidStoreLoader.cpp:251: Loading CP_ENCPT
common/rdm/PidStoreLoader.cpp:251: Loading CP_PTSPEEDMODE
common/rdm/PidStoreLoader.cpp:251: Loading CP_DIMMERCURVE
common/rdm/PidStoreLoader.cpp:251: Loading CP_SILENTMODE
common/rdm/PidStoreLoader.cpp:251: Loading CP_SHUTTERONERR
common/rdm/PidStoreLoader.cpp:251: Loading CP_DIMMONSHUTTER
common/rdm/PidStoreLoader.cpp:251: Loading CP_POWERFANSMODE
common/rdm/PidStoreLoader.cpp:251: Loading CP_ARTNET_MODE
common/rdm/PidStoreLoader.cpp:251: Loading CP_NETREPEATDMX
common/rdm/PidStoreLoader.cpp:251: Loading CP_UNIVERSE
common/rdm/PidStoreLoader.cpp:251: Loading CP_AFAUTOSCALEOFF
common/rdm/PidStoreLoader.cpp:251: Loading CP_MCOLORADJUST
common/rdm/PidStoreLoader.cpp:251: Loading CP_MEFFRANDID
common/rdm/PidStoreLoader.cpp:251: Loading CP_MEFFDISTRIB
common/rdm/PidStoreLoader.cpp:251: Loading CP_EVANCURVEMODE
common/rdm/PidStoreLoader.cpp:251: Loading CP_PT_HOMING_SPEC
common/rdm/PidStoreLoader.cpp:251: Loading CP_PAN_HOME_ANGLE
common/rdm/PidStoreLoader.cpp:251: Loading CP_TILT_HOME_ANGLE
common/rdm/PidStoreLoader.cpp:251: Loading CP_CWHEEL_LINEAR
common/rdm/PidStoreLoader.cpp:251: Loading CP_ANTI_BLIND
common/rdm/PidStoreLoader.cpp:251: Loading CP_PIXELS_UNIVERSE
common/rdm/PidStoreLoader.cpp:251: Loading CP_RPTONDMX_UNIVERSE
common/rdm/PidStoreLoader.cpp:251: Loading CP_CHNLMODE_PIXELS
common/rdm/PidStoreLoader.cpp:251: Loading SHOW_ID
common/rdm/PidStoreLoader.cpp:251: Loading OUTPUT_POWER
common/rdm/PidStoreLoader.cpp:251: Loading HOP_PATTERN
common/rdm/PidStoreLoader.cpp:251: Loading BANDWIDTH
common/rdm/PidStoreLoader.cpp:251: Loading NUM_OF_CHANNELS
common/rdm/PidStoreLoader.cpp:251: Loading LEVEL_TEST
common/rdm/PidStoreLoader.cpp:251: Loading CURVE
common/rdm/PidStoreLoader.cpp:251: Loading BUMP_ENABLED
common/rdm/PidStoreLoader.cpp:251: Loading DATA_LOSS_TIMEOUT
common/rdm/PidStoreLoader.cpp:251: Loading BACKLIGHT_TIMEOUT
common/rdm/PidStoreLoader.cpp:251: Loading RDM_PROXY_ENABLED
common/rdm/PidStoreLoader.cpp:251: Loading INPUT_FORMAT
common/rdm/PidStoreLoader.cpp:251: Loading IP_ADDRESS
common/rdm/PidStoreLoader.cpp:251: Loading IP_SUBNET_MASK
common/rdm/PidStoreLoader.cpp:251: Loading IP_GATEWAY
common/rdm/PidStoreLoader.cpp:251: Loading DHCP_MODE
common/rdm/PidStoreLoader.cpp:251: Loading MAC_ADDRESS
common/rdm/PidStoreLoader.cpp:251: Loading SET_UID
common/rdm/PidStoreLoader.cpp:251: Loading DMX_OUTPUT_STANDARD
common/rdm/PidStoreLoader.cpp:251: Loading ADD_DISCOVERY
common/rdm/PidStoreLoader.cpp:251: Loading DMX_INTERSLOT_TIME
common/rdm/PidStoreLoader.cpp:251: Loading LATENCY
common/rdm/PidStoreLoader.cpp:251: Loading FACTORY_SETTINGS_LOCK
common/rdm/PidStoreLoader.cpp:251: Loading DMX_RDM_INTERLEAVE
common/rdm/PidStoreLoader.cpp:251: Loading PROXIED_DEVICES_ENHANCED
common/rdm/PidStoreLoader.cpp:251: Loading ADAPTIVE_ON_OFF
common/rdm/PidStoreLoader.cpp:251: Loading PWRUP_TEST
common/rdm/PidStoreLoader.cpp:251: Loading INTERNAL_STATS
common/rdm/PidStoreLoader.cpp:251: Loading NE_FAULT_DETECT_MODE
common/rdm/PidStoreLoader.cpp:251: Loading DMX_PROTECT_MODE
common/rdm/PidStoreLoader.cpp:251: Loading DMX_LOSS_MODE
common/rdm/PidStoreLoader.cpp:251: Loading PREHEAT_LEVEL
common/rdm/PidStoreLoader.cpp:251: Loading OUTPUT_CAP_VALUE
common/rdm/PidStoreLoader.cpp:251: Loading DMX_TERM_MODE
common/rdm/PidStoreLoader.cpp:251: Loading FULL_DISCOVERY
common/rdm/PidStoreLoader.cpp:251: Loading OUTPUT_DEFAULT_VALUE
common/rdm/PidStoreLoader.cpp:251: Loading DALI_FADE_TIME
common/rdm/PidStoreLoader.cpp:251: Loading INCREMENTAL_DISCOVERY_INTERVAL
common/rdm/PidStoreLoader.cpp:251: Loading ACK_TIMER_FACTOR
common/rdm/PidStoreLoader.cpp:251: Loading MDG_NETWORK_UNIVERSE_NUMBER
common/rdm/PidStoreLoader.cpp:251: Loading MDG_NETWORK_UNIVERSE_NAME
common/rdm/PidStoreLoader.cpp:251: Loading MDG_GENERATOR_STATE
common/rdm/PidStoreLoader.cpp:251: Loading DMX_LAMP_OFF_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading DMX_RESET_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading MCX_LAMP_OFF_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading FIXTURE_ID
common/rdm/PidStoreLoader.cpp:251: Loading STAND_ALONE_OPERATION_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading SYNCHRONIZED
common/rdm/PidStoreLoader.cpp:251: Loading AUTO_PROGRAM_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading ENABLE_TIMERS
common/rdm/PidStoreLoader.cpp:251: Loading TIMER1_START_TIME
common/rdm/PidStoreLoader.cpp:251: Loading TIMER1_END_TIME
common/rdm/PidStoreLoader.cpp:251: Loading TIMER2_START_TIME
common/rdm/PidStoreLoader.cpp:251: Loading TIMER2_END_TIME
common/rdm/PidStoreLoader.cpp:251: Loading LIGHTSENSOR_LEVEL_TRIGGER_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading CAPTURE_CURRENT_SENSOR_VALUE
common/rdm/PidStoreLoader.cpp:251: Loading LIGHTSENSOR_TRIGGER_LEVEL
common/rdm/PidStoreLoader.cpp:251: Loading ADD_SCENE
common/rdm/PidStoreLoader.cpp:251: Loading INSERT_SCENE
common/rdm/PidStoreLoader.cpp:251: Loading STORE_SCENE
common/rdm/PidStoreLoader.cpp:251: Loading DELETE_SCENE
common/rdm/PidStoreLoader.cpp:251: Loading DELETE_ALL_SCENES
common/rdm/PidStoreLoader.cpp:251: Loading NEXT_SCENE
common/rdm/PidStoreLoader.cpp:251: Loading PREVIOUS_SCENE
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_SETTINGS
common/rdm/PidStoreLoader.cpp:251: Loading RUN_PROGRAM
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_NUMBER
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_WAIT_TIME
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_FADE_TIME
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_INTENSITY
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_CYAN
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_MAGENTA
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_YELLOW
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_RED
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_GREEN
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_BLUE
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_AMBER
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_WHITE
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_ZOOM
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_FOCUS
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_RANDOM_COLOR
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_COLOR_WHEEL
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_GOBO_SELECTION
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_GOBO_INDEXING
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_ANIMATION_POSITION
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_ANIMATION_INDEXING
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_GET_DMX
common/rdm/PidStoreLoader.cpp:251: Loading SCENE_FROST_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading AUTO_SHUTTER_BO_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading EFFECT_SPEED
common/rdm/PidStoreLoader.cpp:251: Loading EFFECT_SHORTCUTS_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading EFFECT_FEEDBACK_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading LAMP_HOUR_WARNING_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading LAMP_HOUR_WARNING_HOURS
common/rdm/PidStoreLoader.cpp:251: Loading AIR_FILTER_HOUR
common/rdm/PidStoreLoader.cpp:251: Loading AIR_FILTER_HOUR_WARNING_HOURS
common/rdm/PidStoreLoader.cpp:251: Loading DISPLAY_ERRORS_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading LAMP_ERROR_TEST_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading SAVE_CUSTOM_CONFIGURATION
common/rdm/PidStoreLoader.cpp:251: Loading LOAD_CUSTOM_CONFIGURATION
common/rdm/PidStoreLoader.cpp:251: Loading BARNDOOR_SOFTWARE_VERSION
common/rdm/PidStoreLoader.cpp:251: Loading CMY_BLACKOUT_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading TRACKING_MODE
common/rdm/PidStoreLoader.cpp:251: Loading TRACKING_CAL
common/rdm/PidStoreLoader.cpp:251: Loading DIMMER_CURVE
common/rdm/PidStoreLoader.cpp:251: Loading FOCUS_TRACKING
common/rdm/PidStoreLoader.cpp:251: Loading DISPLAY_AUTO_OFF
common/rdm/PidStoreLoader.cpp:251: Loading LAMP_PREHEAT_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading LAMP_PREHEAT_VALUE
common/rdm/PidStoreLoader.cpp:251: Loading LAMP_POWER_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading LAMP_POWER_VALUE
common/rdm/PidStoreLoader.cpp:251: Loading IRIS_BLACKOUT_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading COLOR_WHEEL_BLACKOUT_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading STUDIO_MODE
common/rdm/PidStoreLoader.cpp:251: Loading BLOCK_TEMP_SETTING
common/rdm/PidStoreLoader.cpp:251: Loading GOBO3_ANIMATION_START
common/rdm/PidStoreLoader.cpp:251: Loading GOBO3_ANIMATION_END
common/rdm/PidStoreLoader.cpp:251: Loading PAN_TILT_SPEED
common/rdm/PidStoreLoader.cpp:251: Loading PAN_TILT_MOVE_ON_RESET_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading PAN_TILT_LIMITATION_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading PAN_LIMITATION_MINIMUM
common/rdm/PidStoreLoader.cpp:251: Loading PAN_LIMITATION_MAXIMUM
common/rdm/PidStoreLoader.cpp:251: Loading TILT_LIMITATION_MINIMUM
common/rdm/PidStoreLoader.cpp:251: Loading TILT_LIMITATION_MAXIMUM
common/rdm/PidStoreLoader.cpp:251: Loading PAN_TILT_LIMITATION_AREA
common/rdm/PidStoreLoader.cpp:251: Loading FOLLOW_SPOT_MODE_ENABLE
common/rdm/PidStoreLoader.cpp:251: Loading FOLLOW_SPOT_MODE_LOCK_TOGGLE
common/rdm/PidStoreLoader.cpp:251: Loading FOLLOW_SPOT_MODE_LOCK_PAN
common/rdm/PidStoreLoader.cpp:251: Loading FOLLOW_SPOT_MODE_LOCK_TILT
common/rdm/PidStoreLoader.cpp:251: Loading REGULATE_LAMP_FAN
common/rdm/PidStoreLoader.cpp:251: Loading REGULATE_GOBO_FAN
common/rdm/PidStoreLoader.cpp:251: Loading LAMP_COOLING
common/rdm/PidStoreLoader.cpp:251: Loading FAN_CLEAN
common/rdm/PidStoreLoader.cpp:251: Loading FAN_MODE
common/rdm/PidStoreLoader.cpp:251: Loading SERIAL_NUMBER
common/rdm/PidStoreLoader.cpp:251: Loading EVENT_LOG_USER_EVENT_TRIGGER
common/rdm/PidStoreLoader.cpp:251: Loading FAN_ERROR_STATUS
common/rdm/PidStoreLoader.cpp:251: Loading MAX_LAMP_POWER
common/rdm/PidStoreLoader.cpp:251: Loading LAMP_FADE_ON_COMM_LOSS
common/rdm/PidStoreLoader.cpp:251: Loading LOCK_PAN
common/rdm/PidStoreLoader.cpp:251: Loading LOCK_TILT
common/rdm/PidStoreLoader.cpp:251: Loading PAN_TILT_FREE_MOTION
common/rdm/PidStoreLoader.cpp:251: Loading FOLLOW_SPOT_CONTROLLER_MODE
common/rdm/PidStoreLoader.cpp:251: Loading ZOOM_TYPE
common/rdm/PidStoreLoader.cpp:251: Loading FOLLOW_SPOT_ZOOM
common/rdm/PidStoreLoader.cpp:251: Loading ZERO_GOBO_WHEELS
common/rdm/PidStoreLoader.cpp:251: Loading CLEAR_LOG
common/rdm/PidStoreLoader.cpp:251: Loading DISABLE_MECHS
common/rdm/PidStoreLoader.cpp:251: Loading DMX_INPUT
common/rdm/PidStoreLoader.cpp:251: Loading WIRELESS_UNLINK
common/rdm/PidStoreLoader.cpp:251: Loading SCREENSAVER_DELAY
common/rdm/PidStoreLoader.cpp:251: Loading DMX_HOLD_MODE
common/rdm/PidStoreLoader.cpp:251: Loading SLOT_LABELS
common/rdm/PidStoreLoader.cpp:251: Loading MODIFY_SENSOR_DEFINITION
common/rdm/PidStoreLoader.cpp:251: Loading NETWORK_ADDRESS
common/rdm/PidStoreLoader.cpp:251: Loading NETWORK_MASK
common/rdm/PidStoreLoader.cpp:251: Loading GATEWAY_ADDRESS
common/rdm/PidStoreLoader.cpp:251: Loading DNS_ADDRESS
common/rdm/PidStoreLoader.cpp:251: Loading DC_OFFSET
common/rdm/PidStoreLoader.cpp:251: Loading DC_FADER_OFFSET
common/rdm/PidStoreLoader.cpp:251: Loading DC_CALIBRATION
common/rdm/PidStoreLoader.cpp:251: Loading CURVE_DEFINITION
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_LOGIN
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_LOGOUT
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_RADIO_POWER_24
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_RADIO_POWER_58
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_MASK_24
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_MASK_58
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_RADIO_MODE
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_RADIO_AHFSS
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_AFHSS_MASK_24
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_AFHSS_MASK_54
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_SIGNAL_STRENGTH
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_DMX_TO_RDM_RATIO
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_DOWNSTREAM_RDM
common/rdm/PidStoreLoader.cpp:251: Loading WDMX_IDENTIFY_PROXIES
common/rdm/PidStoreLoader.cpp:251: Loading ETC_LED_CURVE
common/rdm/PidStoreLoader.cpp:251: Loading ETC_LED_CURVE_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading ETC_LED_STROBE
common/rdm/PidStoreLoader.cpp:251: Loading ETC_LED_OUTPUT_MODE
common/rdm/PidStoreLoader.cpp:251: Loading ETC_LED_OUTPUT_MODE_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading ETC_LED_RED_SHIFT
common/rdm/PidStoreLoader.cpp:251: Loading ETC_LED_WHITE_POINT
common/rdm/PidStoreLoader.cpp:251: Loading ETC_LED_WHITE_POINT_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading ETC_LED_FREQUENCY
common/rdm/PidStoreLoader.cpp:251: Loading ETC_DMX_LOSS_BEHAVIOR
common/rdm/PidStoreLoader.cpp:251: Loading ETC_DMX_LOSS_BEHAVIOR_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading ETC_LED_PLUS_SEVEN
common/rdm/PidStoreLoader.cpp:251: Loading ETC_BACKLIGHT_BRIGHTNESS
common/rdm/PidStoreLoader.cpp:251: Loading ETC_BACKLIGHT_TIMEOUT
common/rdm/PidStoreLoader.cpp:251: Loading ETC_STATUS_INDICATORS
common/rdm/PidStoreLoader.cpp:251: Loading ETC_RECALIBRATE_FIXTURE
common/rdm/PidStoreLoader.cpp:251: Loading ETC_OVER_TEMP_MODE
common/rdm/PidStoreLoader.cpp:251: Loading ETC_SIMPLE_SETUP_MODE
common/rdm/PidStoreLoader.cpp:251: Loading ETC_LED_STROBE_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading ETC_LED_RED_SHIFT_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading ETC_LED_PLUS_SEVEN_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading ETC_BACKLIGHT_TIMEOUT_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading ETC_SIMPLE_SETUP_MODE_DESCRIPTION
common/rdm/PidStoreLoader.cpp:251: Loading ETC_PREPARE_FOR_SOFTWARE_DOWNLOAD
common/rdm/PidStoreLoader.cpp:251: Loading SERIAL_NUMBER
common/rdm/PidStoreLoader.cpp:251: Loading CODE_VERSION
common/rdm/PidStoreLoader.cpp:251: Loading MODEL_ID
common/rdm/PidStoreLoader.cpp:251: Loading MODEL_ID_LIST
common/rdm/PidStoreLoader.cpp:251: Loading PIXEL_TYPE
common/rdm/PidStoreLoader.cpp:251: Loading PIXEL_COUNT
common/rdm/PidStoreLoader.cpp:190: Load Complete
common/network/PosixInterfacePicker.cpp:161: Skipping lo because it's a loopback
common/network/PosixInterfacePicker.cpp:244: Found: enp0s25, 10.7.231.221, d4:be:d9:99:7d:48
common/network/InterfacePicker.cpp:92: Using interface enp0s25 (10.7.231.221)
olad/OlaServer.cpp:194: Server UID is 7a70:dde7070a
olad/OlaServer.cpp:206: Server instance name is OLA Server
common/network/TCPSocket.cpp:235: bind to 127.0.0.1:9010 failed, Address already in use
common/rpc/RpcServer.cpp:102: Could not listen on the RPC port 9010, you probably have another instance of running.
olad/OlaServer.cpp:252: Failed to init RPC server
common/io/EPoller.cpp:306: ss process time was 0.000000
common/thread/Thread.cpp:193: Thread signal-thread, policy SCHED_OTHER, priority 0

[Peter Newman]

On Friday, 18 January 2019 06:58:15 UTC, Glavan Fernandez wrote:

 when i connect the enttec dmxusb pro to the scope i am able to see break and the start code generated, but that does not discover my device on the UI.

that's one thing.

when i try to run rdm_test_server.py from terminal it says socket error address already in use.

That's just telling you it's already running on the machine, running sudo /etc/init.d/rdm_test_server stop and then running from the terminal would fix it, however it won't log anything particularly exciting for your current error.

i did run OLA discovery command from the UI , i am able to select my universe but i am not getting any options from the drop down menu for RDM responders even though my DUT is connected.

Okay, that definitely sounds like a discovery error somewhere.

As the message says, OLA is already running, so this log doesn't have any of the juicy stuff in it. Please ensure you've followed all the steps here: https://www.openlighting.org/ola/get-help/ola-faq/#How_do_I_get_olad_-l_4_logs

If you have, the log will just keep going and going, so just copy it all after it's run discovery once via the RDM server (or ola_rdm_discover -u <universe>).