Home automation with openHAB using RPI2, OLA and a DMX controller … solution?

[m...@psyron.com]

Hello guys,

(watch this video for a desciption of my problem: https://youtu.be/dQrUNlLq4Us)

I have almost successfully completed my home automation setup using
- RPI2
- openHAB
- OLA
- UART native DMX interface
- 30 channel DMX controller

OLA is working, but when changing colors from within openHAB there is always a delay of 30 seconds or so. Messages are sent/received immediately to/from OLA but it seems like OLA is not sending the commands to the DMX controller - only after a while.
This is a very strange behavior and i am not very familiar with OLA/DMX.
Can someone give me a hint how to solve this problem?

[Peter Newman]

For anyone who doesn't want to watch Markus' video, a summary of the issue:

OLA old web UI control works fine. With old web UI open, control from OpenHAB is instantaneous, but he gets blackouts after about 30s.
With OLA old web UI on DMX monitor page, control is very laggy from OpenHAB, taking tens of seconds to respond to the change on OpenHAB.

In terms of your issue Markus, with the faders open, the blackouts are expected behaviour, OLA is merging the two data streams (you can configure LTP or HTP), essentially the two systems (the web UI and OpenHAB) are fighting for control.

With the old web UI on the DMX monitor page it should all work fine in theory.

Can you try a few things, firstly close all tabs that have the old web UI open, does that fix the issue? If not, run ola_dmxmonitor, the command line tool and see if the updates are instantaneous on there from OpenHAB.

Can you confirm who makes the UART interface board (it looks like the BitWizard one), also which OLA plugin are you using to drive it?

Can we also have a log from olad -l 4 when the issue is occurring (you'll need to stop the other olad instance if you're running it as a service).

Is the delay always consistent between changing OpenHAB and seeing it change in real life, or does it vary?

[Markus Stoehr]

Thanks so much for taking time!!

Am Dienstag, 29. März 2016 01:40:35 UTC+2 schrieb Peter Newman:

For anyone who doesn't want to watch Markus' video, a summary of the issue:

OLA old web UI control works fine. With old web UI open, control from OpenHAB is instantaneous, but he gets blackouts after about 30s.
With OLA old web UI on DMX monitor page, control is very laggy from OpenHAB, taking tens of seconds to respond to the change on OpenHAB.

In terms of your issue Markus, with the faders open, the blackouts are expected behaviour, OLA is merging the two data streams (you can configure LTP or HTP), essentially the two systems (the web UI and OpenHAB) are fighting for control.

With the old web UI on the DMX monitor page it should all work fine in theory.

Can you try a few things, firstly close all tabs that have the old web UI open, does that fix the issue?

No, still get that delay of 2 - 60 seconds, mostly around 40 seconds, but vary a lot.
 

If not, run ola_dmxmonitor, the command line tool and see if the updates are instantaneous on there from OpenHAB.

The changes in dmxmonitor appear instantaneous, but that suddenly appears a message "Data Loss!"

Can you confirm who makes the UART interface board (it looks like the BitWizard one), also which OLA plugin are you using to drive it?

Yes, it's BitWizard, i use the "UART native DMX"-interface. To install and make it work i used the following instructions:
http://opendmx.net/index.php/OLA_Device_Specific_Configuration#Raspberry_Pi

Can we also have a log from olad -l 4 when the issue is occurring (you'll need to stop the other olad instance if you're running it as a service).

Ok, stopped olad with: sudo /etc/init.d/olad stop
Then starting "olad -l 4"

I have here a different universe than when starting the service and i am able to select all other plugins, which shouldn't be i guess because when using UART native DMX all other plugins should be disabled, right?  Is this already the problem?
Is it possible that i have multiple installations of ola? Where should be the default installation path, "/usr/bin/" right?
Or is it possible that i have multiple configuration files? Where should the right one be located?

[Markus Stoehr]

Can we also have a log from olad -l 4 when the issue is occurring (you'll need to stop the other olad instance if you're running it as a service).

Here are the last messages i get:

common/io/SelectPoller.cpp:233: ss process time was 0.000196
common/io/EPoller.cpp:306: ss process time was 0.000010
common/io/SelectPoller.cpp:233: ss process time was 0.001712
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000046
common/io/SelectPoller.cpp:233: ss process time was 0.000085
common/io/SelectPoller.cpp:233: ss process time was 0.000326
common/io/SelectPoller.cpp:233: ss process time was 0.000418
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/SelectPoller.cpp:233: ss process time was 0.002426
common/io/SelectPoller.cpp:233: ss process time was 0.000077
common/io/SelectPoller.cpp:233: ss process time was 0.000418
olad/OlaServer.cpp:385: Garbage collecting
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/EPoller.cpp:306: ss process time was 0.000004
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/EPoller.cpp:306: ss process time was 0.000003
plugins/usbdmx/AsyncPluginImpl.cpp:362: Scanning USB devices....
plugins/usbdmx/AsyncPluginImpl.cpp:368: Got 6 devices
common/io/EPoller.cpp:306: ss process time was 0.000004
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/EPoller.cpp:306: ss process time was 0.000004
common/io/EPoller.cpp:306: ss process time was 0.000008
plugins/sandnet/SandNetDevice.cpp:151: Sending Sandnet advertisement
common/io/EPoller.cpp:306: ss process time was 0.000005
common/io/SelectPoller.cpp:233: ss process time was 0.000408
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/SelectPoller.cpp:233: ss process time was 0.002000
common/io/SelectPoller.cpp:233: ss process time was 0.000089
common/io/SelectPoller.cpp:233: ss process time was 0.000287
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000882
common/io/SelectPoller.cpp:233: ss process time was 0.000089
common/io/SelectPoller.cpp:233: ss process time was 0.000307
common/io/EPoller.cpp:306: ss process time was 0.000012
plugins/pathport/PathportDevice.cpp:144: Sending pathport arp reply
common/io/EPoller.cpp:306: ss process time was 0.000005
plugins/sandnet/SandNetDevice.cpp:151: Sending Sandnet advertisement
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000886
common/io/SelectPoller.cpp:233: ss process time was 0.000091
common/io/SelectPoller.cpp:233: ss process time was 0.000292
common/io/SelectPoller.cpp:233: ss process time was 0.000465
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000094
common/io/SelectPoller.cpp:233: ss process time was 0.000305
plugins/sandnet/SandNetDevice.cpp:151: Sending Sandnet advertisement
common/io/EPoller.cpp:306: ss process time was 0.000011
common/io/SelectPoller.cpp:233: ss process time was 0.000419
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000040
common/io/EPoller.cpp:306: ss process time was 0.000004
common/io/SelectPoller.cpp:233: ss process time was 0.000097
common/io/SelectPoller.cpp:233: ss process time was 0.000415
common/io/EPoller.cpp:306: ss process time was 0.000007
plugins/usbdmx/AsyncPluginImpl.cpp:362: Scanning USB devices....
plugins/usbdmx/AsyncPluginImpl.cpp:368: Got 6 devices
common/io/EPoller.cpp:306: ss process time was 0.000005
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/SelectPoller.cpp:233: ss process time was 0.000853
common/io/SelectPoller.cpp:233: ss process time was 0.000086
common/io/SelectPoller.cpp:233: ss process time was 0.000288
common/io/EPoller.cpp:306: ss process time was 0.000009
plugins/sandnet/SandNetDevice.cpp:151: Sending Sandnet advertisement
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.001304
common/io/SelectPoller.cpp:233: ss process time was 0.000080
common/io/SelectPoller.cpp:233: ss process time was 0.000277
common/io/EPoller.cpp:306: ss process time was 0.000008
common/io/EPoller.cpp:306: ss process time was 0.000009
common/io/SelectPoller.cpp:233: ss process time was 0.000911
common/io/SelectPoller.cpp:233: ss process time was 0.000093
common/io/SelectPoller.cpp:233: ss process time was 0.000302
common/io/EPoller.cpp:306: ss process time was 0.000009
common/io/EPoller.cpp:306: ss process time was 0.000011
plugins/pathport/PathportDevice.cpp:144: Sending pathport arp reply
common/io/EPoller.cpp:306: ss process time was 0.000005
common/io/EPoller.cpp:306: ss process time was 0.000006
plugins/sandnet/SandNetDevice.cpp:151: Sending Sandnet advertisement
common/io/EPoller.cpp:306: ss process time was 0.000005
common/io/EPoller.cpp:306: ss process time was 0.000008
common/io/EPoller.cpp:306: ss process time was 0.000010
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000864
common/io/SelectPoller.cpp:233: ss process time was 0.000088
common/io/SelectPoller.cpp:233: ss process time was 0.000278
olad/OlaServer.cpp:385: Garbage collecting
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/EPoller.cpp:306: ss process time was 0.000003
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/EPoller.cpp:306: ss process time was 0.000003
common/io/EPoller.cpp:306: ss process time was 0.000005
plugins/usbdmx/AsyncPluginImpl.cpp:362: Scanning USB devices....
plugins/usbdmx/AsyncPluginImpl.cpp:368: Got 6 devices
common/io/EPoller.cpp:306: ss process time was 0.000004
common/io/EPoller.cpp:306: ss process time was 0.000007
plugins/sandnet/SandNetDevice.cpp:151: Sending Sandnet advertisement
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000432
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000041
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/SelectPoller.cpp:233: ss process time was 0.000096
common/io/SelectPoller.cpp:233: ss process time was 0.000404
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.001270
common/io/SelectPoller.cpp:233: ss process time was 0.000077
common/io/SelectPoller.cpp:233: ss process time was 0.000259
common/io/SelectPoller.cpp:233: ss process time was 0.000441
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/SelectPoller.cpp:233: ss process time was 0.000091
common/io/SelectPoller.cpp:233: ss process time was 0.000317
plugins/sandnet/SandNetDevice.cpp:151: Sending Sandnet advertisement
common/io/EPoller.cpp:306: ss process time was 0.000008
common/io/SelectPoller.cpp:233: ss process time was 0.000442
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000095
common/io/SelectPoller.cpp:233: ss process time was 0.000246
plugins/pathport/PathportDevice.cpp:144: Sending pathport arp reply
common/io/EPoller.cpp:306: ss process time was 0.000009
common/io/SelectPoller.cpp:233: ss process time was 0.000417
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000088
common/io/SelectPoller.cpp:233: ss process time was 0.000258
plugins/sandnet/SandNetDevice.cpp:151: Sending Sandnet advertisement
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/EPoller.cpp:306: ss process time was 0.000007
plugins/usbdmx/AsyncPluginImpl.cpp:362: Scanning USB devices....
plugins/usbdmx/AsyncPluginImpl.cpp:368: Got 6 devices
common/io/EPoller.cpp:306: ss process time was 0.000004
common/io/SelectPoller.cpp:233: ss process time was 0.000425
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/SelectPoller.cpp:233: ss process time was 0.000091
common/io/SelectPoller.cpp:233: ss process time was 0.000378
common/io/SelectPoller.cpp:233: ss process time was 0.000402
common/io/EPoller.cpp:306: ss process time was 0.000009
common/io/EPoller.cpp:306: ss process time was 0.000005
common/io/SelectPoller.cpp:233: ss process time was 0.000046
common/io/SelectPoller.cpp:233: ss process time was 0.000093
common/io/SelectPoller.cpp:233: ss process time was 0.000321
plugins/sandnet/SandNetDevice.cpp:151: Sending Sandnet advertisement
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000863
common/io/SelectPoller.cpp:233: ss process time was 0.000094
common/io/SelectPoller.cpp:233: ss process time was 0.000280
common/io/SelectPoller.cpp:233: ss process time was 0.000437
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000108
common/io/SelectPoller.cpp:233: ss process time was 0.000306
plugins/sandnet/SandNetDevice.cpp:151: Sending Sandnet advertisement
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000432
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/SelectPoller.cpp:233: ss process time was 0.000090
common/io/SelectPoller.cpp:233: ss process time was 0.000280
olad/OlaServer.cpp:385: Garbage collecting
olad/Universe.cpp:423: Removed Stale Client
olad/Universe.cpp:423: Removed Stale Client
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/EPoller.cpp:306: ss process time was 0.000008
common/io/EPoller.cpp:306: ss process time was 0.000004
common/io/EPoller.cpp:306: ss process time was 0.000010
common/io/EPoller.cpp:306: ss process time was 0.000004
common/io/SelectPoller.cpp:233: ss process time was 0.000422
common/io/EPoller.cpp:306: ss process time was 0.000005
common/io/SelectPoller.cpp:233: ss process time was 0.000085
common/io/SelectPoller.cpp:233: ss process time was 0.000263
plugins/usbdmx/AsyncPluginImpl.cpp:362: Scanning USB devices....
plugins/usbdmx/AsyncPluginImpl.cpp:368: Got 6 devices
common/io/EPoller.cpp:306: ss process time was 0.000005
common/io/EPoller.cpp:306: ss process time was 0.000006
plugins/pathport/PathportDevice.cpp:144: Sending pathport arp reply
common/io/EPoller.cpp:306: ss process time was 0.000005
common/io/EPoller.cpp:306: ss process time was 0.000006
plugins/sandnet/SandNetDevice.cpp:151: Sending Sandnet advertisement
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/EPoller.cpp:306: ss process time was 0.000008
common/io/SelectPoller.cpp:233: ss process time was 0.001149
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/SelectPoller.cpp:233: ss process time was 0.000037
common/io/SelectPoller.cpp:233: ss process time was 0.000094
common/io/SelectPoller.cpp:233: ss process time was 0.000419
common/io/SelectPoller.cpp:233: ss process time was 0.000428
common/io/EPoller.cpp:306: ss process time was 0.000005
common/io/SelectPoller.cpp:233: ss process time was 0.000092
common/io/SelectPoller.cpp:233: ss process time was 0.000345
common/io/EPoller.cpp:306: ss process time was 0.000011
plugins/sandnet/SandNetDevice.cpp:151: Sending Sandnet advertisement
common/io/EPoller.cpp:306: ss process time was 0.000004
common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/SelectPoller.cpp:233: ss process time was 0.000966
common/io/SelectPoller.cpp:233: ss process time was 0.000086
common/io/SelectPoller.cpp:233: ss process time was 0.000395
common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.001003
common/io/SelectPoller.cpp:233: ss process time was 0.000091
common/io/SelectPoller.cpp:233: ss process time was 0.000420
plugins/sandnet/SandNetDevice.cpp:151: Sending Sandnet advertisement
common/io/EPoller.cpp:306: ss process time was 0.000049
^Ccommon/thread/SignalThread.cpp:105: Received signal: Interrupt
common/http/HTTPServer.cpp:523: Notifying HTTP server thread to stop
common/http/HTTPServer.cpp:525: Waiting for HTTP server thread to exit
common/http/HTTPServer.cpp:527: HTTP server thread exited
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 47
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 14
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 10
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 24
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 26
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 27
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 29
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 28
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 30
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 31
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 40
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 41
common/io/EPoller.cpp:306: ss process time was 0.000013
common/io/EPoller.cpp:306: ss process time was 0.000012
 

[Markus Stoehr]

And when i stop and restart ola with "/usr/bin/olad -l 4" i get this again:

So it seems that all other plugins are in again. But this doesn't happen when starting as service.

[Markus Stoehr]

When starting as service i get this:



But in both cases i get the same problems with openHAB.

[Arjan van Vught]

Hi Markus,

Different configurations files are used when starting as a service or starting from an user account.

For example :

pi@openlighting-3 ~/.ola $ pwd
/home/pi/.ola

and

pi@openlighting-3 /etc/init.d $ pwd
/etc/init.d
pi@openlighting-3 /etc/init.d $ grep CONFIG olad
CONFIG_DIR="/var/lib/ola/conf"


- Arjan
http://www.raspberrypi-dmx.com/

Op 29-3-2016 om 20:06 schreef Markus Stoehr:

And when i stop and restart ola with "/usr/bin/olad -l 4" i get this again:

So it seems that all other plugins are in again. But this doesn't happen when starting as service.

--
The Open Lighting Project: open-l...@googlegroups.com, #openlighting (irc.freenode.org)
To unsubscribe from this group, send email to open-lightin...@googlegroups.com
For more options, visit https://groups.google.com/groups/opt_out?hl=en

[Peter Newman]

What Arjan said; you can also use the -c option to use the same config directory in both cases, see http://docs.openlighting.org/ola/man/man1/olad.1.html for more.

We'll need a full log of olad -l 4 when it's generating the problem, not just the last bit of it. Can you also share ola-uartdmx.conf from whichever config folder your using when you have the issue.

Do the lights behave if you use ola-dmxconsole instead of the web UI? My gut feeling is this is an issue with DMX data rates and your receiver and the UART generation. Have you got any other DMX kit, or just that one item?

On Tuesday, 29 March 2016 19:13:44 UTC+1, Arjan van Vught wrote:

Hi Markus,

Different configurations files are used when starting as a service or starting from an user account.

For example :

pi@openlighting-3 ~/.ola $ pwd
/home/pi/.ola

and

pi@openlighting-3 /etc/init.d $ pwd
/etc/init.d
pi@openlighting-3 /etc/init.d $ grep CONFIG olad
CONFIG_DIR="/var/lib/ola/conf"


- Arjan
http://www.raspberrypi-dmx.com/

Op 29-3-2016 om 20:06 schreef Markus Stoehr:

And when i stop and restart ola with "/usr/bin/olad -l 4" i get this again:

So it seems that all other plugins are in again. But this doesn't happen when starting as service.

--
The Open Lighting Project: open-l...@googlegroups.com, #openlighting (irc.freenode.org)

To unsubscribe from this group, send email to open-lighting+unsubscribe@googlegroups.com

[Markus Stoehr]

Hi Peter, Hi Arjen,

thanks for the support, i am starting to understand more of OLA/DMX, helps a lot to feel the support!

I now understand the difference between LTI/HTP and i tried both.
- when having set HTP and having OLA console open the little green led of my DMX controller is blinking very fast
- in this state when i switch colors in openHAB i got the aboved results that lights are switching immediately, but turn off again after 1-2 seconds.
- when closing the OLA console i got the other results, that the little green led of my DMX controller stops blinking and after changing color in openHAB it takes about 30 seconds, then the little green led blinks once and the color switches and stays lik this

Here my UART native DMX config file (ola-uartdmx.conf):
/dev/ttyAMA0-break = 100
/dev/ttyAMA0-malf = 100
device = /dev/ttyAMA0
enabled = true

Other UART related configurations i had to made (/boot/config.txt):
# For more options and information see
# http://www.raspberrypi.org/documentation/configuration/config-txt.md
# Some settings may impact device functionality. See link above for details
init_uart_clock=16000000

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on
^M
# NOOBS Auto-generated Settings:^M
hdmi_force_hotplug=1^M
config_hdmi_boost=4^M
overscan_left=24^M
overscan_right=24^M
overscan_top=16^M
overscan_bottom=16^M
disable_overscan=0^M


I also have followed those instructions for the UART:
http://elinux.org/RPi_Serial_Connection#Preventing_Linux_using_the_serial_port

Here the fresh /var/log/syslog file after calling "/usr/bin $ olad -l 4" and testing the second case:
pi@raspberrypi:~ $ olad -l 4
olad/Olad.cpp:94: OLA Daemon version 0.9.8
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 5, events 2001, descriptor: 0x1f9e820
olad/OlaDaemon.cpp:121: Using configs in /home/pi/.ola
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 8, events 2001, descriptor: 0x1f98328
common/thread/Thread.cpp:192: 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 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 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:160: skipping lo because it's a loopback
common/network/PosixInterfacePicker.cpp:243: Found: wlan0, 192.168.2.200, 74:da:38:55:a5:43
common/network/PosixInterfacePicker.cpp:243: Found: wlan0, 192.168.2.105, 74:da:38:55:a5:43
common/network/PosixInterfacePicker.cpp:243: Found: tun0, 10.8.0.1, 00:00:00:00:00:00
common/network/InterfacePicker.cpp:92: Using interface wlan0 (192.168.2.200)
olad/OlaServer.cpp:194: Server UID is 7a70:c802a8c0
olad/OlaServer.cpp:206: Server instance name is OLA Server
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 10, events 2001, descriptor: 0x2017a40
olad/AvahiDiscoveryAgent.cpp:201: Client state changed to AVAHI_CLIENT_S_RUNNING
common/thread/Thread.cpp:192: Thread http, policy SCHED_OTHER, priority 0
common/http/HTTPServer.cpp:496: HTTP Server started on port 9090
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 14, events 2001, descriptor: 0x1fe62c0
olad/AvahiDiscoveryAgent.cpp:236: State for OLA Server._http._tcp,_ola, group 0x1ff03a8 changed to AVAHI_ENTRY_GROUP_UNCOMMITED
olad/AvahiDiscoveryAgent.cpp:334: Adding _ola._sub._http._tcp
olad/AvahiDiscoveryAgent.cpp:342: Failed to add _ola._sub._http._tcp
olad/OlaServer.cpp:481: Updated PID definitions.
olad/OlaServer.cpp:489: PID store is at 0x202aa68
olad/AvahiDiscoveryAgent.cpp:236: State for OLA Server._http._tcp,_ola, group 0x1ff03a8 changed to AVAHI_ENTRY_GROUP_REGISTERING
common/thread/Thread.cpp:192: Thread signal-thread, policy SCHED_OTHER, priority 0
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 22, events 2001, descriptor: 0x1fe4c28
olad/PluginManager.cpp:73: Skipping ArtNet because it was disabled
olad/PluginManager.cpp:73: Skipping Dummy because it was disabled
olad/PluginManager.cpp:73: Skipping E1.31 (sACN) because it was disabled
olad/PluginManager.cpp:73: Skipping ESP Net because it was disabled
olad/PluginManager.cpp:73: Skipping GPIO because it was disabled
olad/PluginManager.cpp:73: Skipping KarateLight because it was disabled
olad/PluginManager.cpp:73: Skipping KiNET because it was disabled
olad/PluginManager.cpp:73: Skipping Milford Instruments because it was disabled

common/io/EPoller.cpp:306: ss process time was 0.000008

olad/PluginManager.cpp:73: Skipping Enttec Open DMX because it was disabled
olad/PluginManager.cpp:73: Skipping Open Pixel Control because it was disabled

common/io/EPoller.cpp:306: ss process time was 0.000006

olad/PluginManager.cpp:73: Skipping OSC because it was disabled
olad/PluginManager.cpp:73: Skipping Renard because it was disabled
olad/PluginManager.cpp:73: Skipping SandNet because it was disabled
olad/PluginManager.cpp:73: Skipping ShowNet because it was disabled

common/io/EPoller.cpp:306: ss process time was 0.000006

olad/PluginManager.cpp:73: Skipping SPI because it was disabled
olad/PluginManager.cpp:73: Skipping StageProfi because it was disabled
olad/PluginManager.cpp:73: Skipping Serial USB because it was disabled
olad/PluginManager.cpp:73: Skipping USB because it was disabled
olad/PluginManager.cpp:73: Skipping Pathport because it was disabled
olad/PluginManager.cpp:73: Skipping FTDI USB DMX because it was disabled
olad/PluginManager.cpp:195: Trying to start UART native DMX
plugins/uartdmx/UartDmxPlugin.cpp:67: Trying to open UART device /dev/ttyAMA0
plugins/uartdmx/UartWidget.cpp:68: Opening serial port /dev/ttyAMA0
plugins/uartdmx/UartWidget.cpp:74: Opened serial port /dev/ttyAMA0
common/io/ExtendedSerial.cpp:69: Port speeds for 24 are 250000 in and 250000 out
common/thread/Thread.cpp:192: Thread , policy SCHED_OTHER, priority 0
plugins/uartdmx/UartDmxPlugin.cpp:92: Started UartDmxDevice /dev/ttyAMA0
olad/DeviceManager.cpp:105: Installed device: UART native DMX:20-/dev/ttyAMA0
olad/PortManager.cpp:119: Patched 20-/dev/ttyAMA0-O-0 to universe 0
olad/PluginManager.cpp:200: Started UART native DMX

common/io/EPoller.cpp:306: ss process time was 0.000010

plugins/uartdmx/UartDmxThread.cpp:136: Granularity for UART thread is GOOD
olad/AvahiDiscoveryAgent.cpp:236: State for OLA Server._http._tcp,_ola, group 0x1ff03a8 changed to AVAHI_ENTRY_GROUP_ESTABLISHED

common/io/SelectPoller.cpp:233: ss process time was 0.000288

common/io/SelectPoller.cpp:233: ss process time was 0.012910

common/io/EPoller.cpp:306: ss process time was 0.000008

common/io/EPoller.cpp:306: ss process time was 0.000007

common/io/SelectPoller.cpp:233: ss process time was 0.000057
common/io/SelectPoller.cpp:233: ss process time was 0.000126
common/io/SelectPoller.cpp:233: ss process time was 0.000607

common/io/SelectPoller.cpp:233: ss process time was 0.000258

common/io/SelectPoller.cpp:233: ss process time was 0.000277
common/io/SelectPoller.cpp:233: ss process time was 0.000531

common/io/EPoller.cpp:306: ss process time was 0.000006

common/io/SelectPoller.cpp:233: ss process time was 0.000115
common/io/SelectPoller.cpp:233: ss process time was 0.000487

olad/OlaServer.cpp:385: Garbage collecting
common/io/EPoller.cpp:306: ss process time was 0.000007

common/io/SelectPoller.cpp:233: ss process time was 0.000238
common/io/SelectPoller.cpp:233: ss process time was 0.000452

common/io/EPoller.cpp:306: ss process time was 0.000008

common/io/SelectPoller.cpp:233: ss process time was 0.000060

common/io/EPoller.cpp:306: ss process time was 0.000006
common/io/SelectPoller.cpp:233: ss process time was 0.000096

common/io/SelectPoller.cpp:233: ss process time was 0.000698
olad/Universe.cpp:278: Added source client, 0x1ff3628 to universe 0

common/io/EPoller.cpp:306: ss process time was 0.000009

common/io/SelectPoller.cpp:233: ss process time was 0.008620
common/io/SelectPoller.cpp:233: ss process time was 0.000087
common/io/SelectPoller.cpp:233: ss process time was 0.000526

common/io/SelectPoller.cpp:233: ss process time was 0.000439

common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000046

common/io/EPoller.cpp:306: ss process time was 0.000004

common/io/SelectPoller.cpp:233: ss process time was 0.000090

common/io/SelectPoller.cpp:233: ss process time was 0.000599

olad/OlaServer.cpp:385: Garbage collecting
common/io/EPoller.cpp:306: ss process time was 0.000007

common/io/SelectPoller.cpp:233: ss process time was 0.000451

common/io/SelectPoller.cpp:233: ss process time was 0.000095

common/io/SelectPoller.cpp:233: ss process time was 0.000435
common/io/EPoller.cpp:306: ss process time was 0.000061
common/io/SelectPoller.cpp:233: ss process time was 0.000435

common/io/EPoller.cpp:306: ss process time was 0.000008

common/io/EPoller.cpp:306: ss process time was 0.000005

common/io/SelectPoller.cpp:233: ss process time was 0.000051

common/io/SelectPoller.cpp:233: ss process time was 0.000092

common/io/SelectPoller.cpp:233: ss process time was 0.000692
common/io/SelectPoller.cpp:233: ss process time was 0.000492

common/io/EPoller.cpp:306: ss process time was 0.000007

common/io/SelectPoller.cpp:233: ss process time was 0.000157
common/io/SelectPoller.cpp:233: ss process time was 0.000353
common/io/SelectPoller.cpp:233: ss process time was 0.000715

common/io/EPoller.cpp:306: ss process time was 0.000008

common/io/SelectPoller.cpp:233: ss process time was 0.000052

common/io/EPoller.cpp:306: ss process time was 0.000005

common/io/SelectPoller.cpp:233: ss process time was 0.000097

common/io/SelectPoller.cpp:233: ss process time was 0.000390

common/io/SelectPoller.cpp:233: ss process time was 0.000432
common/io/EPoller.cpp:306: ss process time was 0.000006

common/io/SelectPoller.cpp:233: ss process time was 0.000095

common/io/SelectPoller.cpp:233: ss process time was 0.000313
common/io/SelectPoller.cpp:233: ss process time was 0.000447
common/io/SelectPoller.cpp:233: ss process time was 0.000116

common/io/EPoller.cpp:306: ss process time was 0.000007

common/io/SelectPoller.cpp:233: ss process time was 0.000326
common/io/EPoller.cpp:82: EPOLL_CTL_ADD 29, events 2001, descriptor: 0x1feeac8

common/io/EPoller.cpp:306: ss process time was 0.000009
common/io/EPoller.cpp:306: ss process time was 0.000009

common/io/EPoller.cpp:306: ss process time was 0.000010
olad/Universe.cpp:278: Added source client, 0x1ff1438 to universe 0

common/io/EPoller.cpp:306: ss process time was 0.000008

common/io/SelectPoller.cpp:233: ss process time was 0.000462
common/io/SelectPoller.cpp:233: ss process time was 0.000047

common/io/EPoller.cpp:306: ss process time was 0.000006

common/io/EPoller.cpp:306: ss process time was 0.000005

common/io/SelectPoller.cpp:233: ss process time was 0.000110
common/io/SelectPoller.cpp:233: ss process time was 0.000340
common/io/SelectPoller.cpp:233: ss process time was 0.000551

common/io/EPoller.cpp:306: ss process time was 0.000007

common/io/SelectPoller.cpp:233: ss process time was 0.000138
common/io/SelectPoller.cpp:233: ss process time was 0.000493

olad/OlaServer.cpp:385: Garbage collecting
olad/Universe.cpp:423: Removed Stale Client

common/io/EPoller.cpp:306: ss process time was 0.000007

common/io/SelectPoller.cpp:233: ss process time was 0.000528

common/io/EPoller.cpp:306: ss process time was 0.000007
common/io/SelectPoller.cpp:233: ss process time was 0.000127

common/io/SelectPoller.cpp:233: ss process time was 0.000387
common/io/SelectPoller.cpp:233: ss process time was 0.000550

common/io/EPoller.cpp:306: ss process time was 0.000007

common/io/SelectPoller.cpp:233: ss process time was 0.000126
common/io/SelectPoller.cpp:233: ss process time was 0.000387
common/io/SelectPoller.cpp:233: ss process time was 0.000512

common/io/EPoller.cpp:306: ss process time was 0.000008

common/io/SelectPoller.cpp:233: ss process time was 0.000052

common/io/EPoller.cpp:306: ss process time was 0.000005

common/io/SelectPoller.cpp:233: ss process time was 0.000098
common/io/SelectPoller.cpp:233: ss process time was 0.000397

common/io/EPoller.cpp:306: ss process time was 0.000009

common/io/SelectPoller.cpp:233: ss process time was 0.001548

common/io/SelectPoller.cpp:233: ss process time was 0.000093

common/io/SelectPoller.cpp:233: ss process time was 0.000249
common/io/SelectPoller.cpp:233: ss process time was 0.000427

common/io/EPoller.cpp:306: ss process time was 0.000008

common/io/SelectPoller.cpp:233: ss process time was 0.000100

common/io/SelectPoller.cpp:233: ss process time was 0.000254

common/io/SelectPoller.cpp:233: ss process time was 0.000457

common/io/SelectPoller.cpp:233: ss process time was 0.000094

common/io/SelectPoller.cpp:233: ss process time was 0.000237

common/io/EPoller.cpp:306: ss process time was 0.000008

olad/OlaServer.cpp:385: Garbage collecting
olad/Universe.cpp:423: Removed Stale Client

common/io/EPoller.cpp:306: ss process time was 0.000006

common/io/SelectPoller.cpp:233: ss process time was 0.000410

common/io/EPoller.cpp:306: ss process time was 0.000006

common/io/SelectPoller.cpp:233: ss process time was 0.000048

common/io/EPoller.cpp:306: ss process time was 0.000004

common/io/SelectPoller.cpp:233: ss process time was 0.000095

common/io/SelectPoller.cpp:233: ss process time was 0.000371

common/io/EPoller.cpp:306: ss process time was 0.000008

common/io/SelectPoller.cpp:233: ss process time was 0.000944

common/io/SelectPoller.cpp:233: ss process time was 0.000102

common/io/SelectPoller.cpp:233: ss process time was 0.000307

common/io/EPoller.cpp:306: ss process time was 0.000008

common/io/SelectPoller.cpp:233: ss process time was 0.000926
common/io/SelectPoller.cpp:233: ss process time was 0.000105
common/io/SelectPoller.cpp:233: ss process time was 0.000310

common/io/EPoller.cpp:306: ss process time was 0.000008

common/io/SelectPoller.cpp:233: ss process time was 0.000909
common/io/SelectPoller.cpp:233: ss process time was 0.000105
common/io/SelectPoller.cpp:233: ss process time was 0.000303

common/io/EPoller.cpp:306: ss process time was 0.000013

common/io/SelectPoller.cpp:233: ss process time was 0.001196

common/io/EPoller.cpp:306: ss process time was 0.000004

common/io/SelectPoller.cpp:233: ss process time was 0.000044
common/io/SelectPoller.cpp:233: ss process time was 0.000106
common/io/SelectPoller.cpp:233: ss process time was 0.000427
common/io/SelectPoller.cpp:233: ss process time was 0.000451

common/io/EPoller.cpp:306: ss process time was 0.000007

common/io/SelectPoller.cpp:233: ss process time was 0.000124
common/io/SelectPoller.cpp:233: ss process time was 0.000355
common/io/SelectPoller.cpp:233: ss process time was 0.000499

common/io/EPoller.cpp:306: ss process time was 0.000007

common/io/SelectPoller.cpp:233: ss process time was 0.000106
common/io/SelectPoller.cpp:233: ss process time was 0.000421
common/io/SelectPoller.cpp:233: ss process time was 0.000467

common/io/EPoller.cpp:306: ss process time was 0.000007

common/io/SelectPoller.cpp:233: ss process time was 0.000100
common/io/SelectPoller.cpp:233: ss process time was 0.000383

common/io/EPoller.cpp:306: ss process time was 0.000009

olad/OlaServer.cpp:385: Garbage collecting
common/io/EPoller.cpp:306: ss process time was 0.000004

^Ccommon/thread/SignalThread.cpp:105: Received signal: Interrupt
common/http/HTTPServer.cpp:523: Notifying HTTP server thread to stop
common/http/HTTPServer.cpp:525: Waiting for HTTP server thread to exit
common/http/HTTPServer.cpp:527: HTTP server thread exited

common/io/EPoller.cpp:116: EPOLL_CTL_DEL 29

common/io/EPoller.cpp:116: EPOLL_CTL_DEL 14
common/io/EPoller.cpp:116: EPOLL_CTL_DEL 10

common/io/EPoller.cpp:306: ss process time was 0.000009

common/io/EPoller.cpp:306: ss process time was 0.000010

I have no other DMX kit to test right now.
But it looks like i am so close to get it work. Is it maybe a problem with the UART buffer or something like this? Unfortunately i am also not an expert with linux.

[Markus Stoehr]

I have just seen the following message in the log:

Port speeds for 24 are 250000 in and 250000 out

Does that mean the UART is not running with

init_uart_clock=16000000 as required? What did i do wrong then?

[Markus Stoehr]

But it looks the same as described here:
http://www.raspberrypi-dmx.com/raspberry-pi-ola-dmx512-sender

I am confused. So then where is the problem?

[Richard Ash]

No, that is absolutely correct. The Port speeds are the Baud rate (bits
per second), which always has to be less than the UART clock (typically
at least 4 times less, depends on hardware).

Those log messages look fine for the UART output plug-in.

Unfortunately there doesn't seem to be a schematic for your interface
board on the website, so I don't know what has to happen for the green
LED to light up. Or am I confused and the green LED is on your DMX
controlled device?

The UART DMX output plugin is designed to continually output data over
the DMX line, repeating itself if nothing is changing. This sounds like
it is happening when the OLA console is open (I presume you mean the
web interface?).
I will admit I did most of the testing with the web interface closed,
and using the ola_dmxconsole console program in an SSH session into my
Raspberry Pi. This way, you don't have the added complexity of the web
interface and it's time delays going on.

Unless I have missed something, have you tried just controlling your
DMX device from OLA, with the rest of the system (OpenHAB etc.) turned
off? That way merging doesn't complicate matters (I'm pretty sure a lot
of what you see is sources fighting each other for control), and we
will find out if changes in the universe state are getting passed
through to the DMX device or not. My preference would be to use the
command line tools (ola_dmxconsole and ola_dmxmonitor), because I know
they reliably update 10 times a second, where as the web interface is
more complex (if prettier). I would expect an instant response from
ola_dmxconsole to the lights, but would be interested to know what the
green LED shows when this is going on.

Richard

[Markus Stoehr]

Hi Richard,

yes the green led sits on the 30channel DMX controller and i guess that it blinks every time he got a new message from the UART DMX interface. So i think the problem must be with OLA not sending a message immediately to the UART DMX interface. Is there a way to check signals towards the serial port? I really can not imagine that the signal gets delayed by the interface or the dmx controller.

 

Yes, when using the OLA web ui everything works fine, the little green led is blinking very rapidely and all changes are immediately sent to the dmx controller (and visible). But when not using the OLA web, OLA seems not to send signals to the dmx controller immediately (receiving immediately form openHAB but not sending to the controller i guess). The green led is off and only after 30 seconds or so it blinks shortly and the changes are then visible.

Is there a way to force OLA to send the last incoming messages to the interface immediatly and permanently?

[Markus Stoehr]

At thi point in time i am quite sure the problems lies inside OLA since all messages are sent/received immediately to/by OLA. It must be OLA which is delaying and not sending the signals to the serial port.

So what are my next steps? Is OLA opensource? Can i check the code myself or can i pay money to get my problem fixed? I guess at this point i need some developers to answer my questions. I really need to get this setup to work, otherwise my whole home automation system is doomed. :(

[Arjan van Vught]

Hi Markus,

Using the OLA server with the on-board UART is not the most reliable
option.

Alternatively you can use the Raspberry Pi Zero with the BitWizard "DMX
interface for Raspberry Pi with USB (FT245RL)" board and the "Raspberry
Pi DMX USB Pro" open source application from here
http://www.raspberrypi-dmx.com/raspberry-pi-rdm-controller

- Arjan

[Markus Stoehr]

Hi Arjan,
so if i understand corretly you are the man who helped to develop those devices? Wow, i feel honored!

So at the moment i am using this device:
http://www.bitwizard.nl/shop/raspberry-pi?product_id=153

And you think using the FT245RL version will maybe solve my problems? If so i will of course order that other board.

Thanks a lot for this information! :)

[Richard Ash]

On Thu, 31 Mar 2016 04:47:50 -0700 (PDT)
Markus Stoehr <m...@psyron.com> wrote:
> yes the green led sits on the 30channel DMX controller and i guess
> that it blinks every time he got a new message from the UART DMX
> interface. So i think the problem must be with OLA not sending a
> message immediately to the UART DMX interface.

Or, the message from OpenHAB might not be getting to OLA in a timely
manner? Or, the OpenHAB input plugin might be blocking the operation
of the OLA core, so that data is not being passed on.

> Is there a way to check signals towards the serial port?

Not particularly easily. You would probably need to add some debugging
to the write thread method:
https://github.com/OpenLightingProject/ola/blob/master/plugins/uartdmx/UartDmxThread.cpp#L74

> I really can not imagine that
> the signal gets delayed by the interface or the dmx controller.

I agree that these are unlikely to be the problem.

> Yes, when using the OLA web ui everything works fine, the little
> green led is blinking very rapidely and all changes are immediately
> sent to the dmx controller (and visible). But when not using the OLA
> web, OLA seems not to send signals to the dmx controller immediately
> (receiving immediately form openHAB but not sending to the controller
> i guess). The green led is off and only after 30 seconds or so it
> blinks shortly and the changes are then visible.

What if neither the OLA web interface nor openHAB are running? The UART
output plugin will still be sending under these conditions (because the
thread doesn't stop). Obviously, nothing will change, but I would
expect that the little green LED would keep blinking.

What was the CPU usage when you were doing these tests? The UART output
plugin shouldn't use too much, but will be somewhat sensitive to other
programs using a lot of CPU (because the thread keeps getting kicked
off the CPU by others).

> Is there a way to force OLA to send the last incoming messages to the
> interface immediatly and permanently?

I'm convinced that this isn't your problem. Are you sure that the
messages are getting through to the OLA core correctly (ola_dmxmonitor
will show this, without the web interfacing getting in the way).

How does openHAB communicate with OLA? Is it sending traffic over the
network?

Richard

[Simon Newton]

Looks at the counters on /debug

--
The Open Lighting Project: open-l...@googlegroups.com, #openlighting (irc.freenode.org)

To unsubscribe from this group, send email to open-lightin...@googlegroups.com

[Markus Stoehr]

Hi Simon, counters? What do you mean?
Here what i get from /debug:

binary: olad
clients-connected: 2
cmd-line: -l 4 
config-dir: /home/pi/.ola
fd-limit: 65536
gid: 1000
group: pi
http_data_dir: /usr/share/olad/www
rpc-port: 9010
rpc-received: 9591
rpc-received-type: map:type request:9591
rpc-send-errors: 0
rpc-sent: 9346
server-instance-name: OLA Server
server-uid: 7a70:c802a8c0
ss-connected-descriptors: 3
ss-loop-count: 35413
ss-loop-time: 262535
ss-read-descriptors: 1
ss-timers: 1
ss-write-descriptor: 0
uid: 1000
universe-dmx-frames: map:universe 0:1370
universe-input-ports: map:universe 0:0
universe-mode: map:universe 0:"htp"
universe-name: map:universe 0:"myUniverse"
universe-output-ports: map:universe 0:1
universe-rdm-requests: map: 0:0
universe-sink-clients: map:universe 0:0
universe-source-clients: map:universe 0:2
universe-uids: map:universe 0:0
uptime-in-ms: 212570854
user: pi
using-epoll: 1

[Markus Stoehr]

Am Freitag, 1. April 2016 22:22:48 UTC+2 schrieb Richard Ash:

On Thu, 31 Mar 2016 04:47:50 -0700 (PDT)
Markus Stoehr <m...@psyron.com> wrote:
> yes the green led sits on the 30channel DMX controller and i guess
> that it blinks every time he got a new message from the UART DMX
> interface. So i think the problem must be with OLA not sending a
> message immediately to the UART DMX interface.
Or, the message from OpenHAB might not be getting to OLA in a timely
manner? Or, the OpenHAB input plugin might be blocking the operation
of the OLA core, so that data is not being passed on.

I have checked the messages from openHAB to OLA, they are sent/received immediately - no time delay
.

> Is there a way to check signals towards the serial port?
Not particularly easily. You would probably need to add some debugging
to the write thread method:
https://github.com/OpenLightingProject/ola/blob/master/plugins/uartdmx/UartDmxThread.cpp#L74

Will have to check this out ...

> I really can not imagine that
> the signal gets delayed by the interface or the dmx controller.
I agree that these are unlikely to be the problem.

Maybe OLA has a problem with DMX interfaces without own chips? Now i have ordered this interface to check whether it's working with it:
http://www.bitwizard.nl/shop/raspberry-pi?product_id=154

> Yes, when using the OLA web ui everything works fine, the little
> green led is blinking very rapidely and all changes are immediately
> sent to the dmx controller (and visible). But when not using the OLA
> web, OLA seems not to send signals to the dmx controller immediately
> (receiving immediately form openHAB but not sending to the controller
> i guess). The green led is off and only after 30 seconds or so it
> blinks shortly and the changes are then visible.
What if neither the OLA web interface nor openHAB are running? The UART
output plugin will still be sending under these conditions (because the
thread doesn't stop). Obviously, nothing will change, but I would
expect that the little green LED would keep blinking.

When i open the OLA web interface (console) then the green light starts blinking.
When i then close the OLA web interface the green light continue to blink but the moment i am sending a command from openHAB the light stop blinking and only after abotu 30 seconds the green light blinks once at the the color change takes place.

What was the CPU usage when you were doing these tests? The UART output
plugin shouldn't use too much, but will be somewhat sensitive to other
programs using a lot of CPU (because the thread keeps getting kicked
off the CPU by others).
 

Here the CPU usage while changing colors:

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
 1926 root      20   0  384532 119724  17480 S  12.9 12.6 813:58.18 java
 4089 pi        20   0   62996  11824   9268 S   1.3  1.2 538:18.92 olad
16874 pi        20   0    5092   2476   2124 R   1.0  0.3   0:00.49 top
    7 root      20   0       0      0      0 S   0.3  0.0   2:28.00 rcu_preempt
  709 root      20   0   23188  11440   6672 S   0.3  1.2   4:04.22 Xorg
  906 pi        20   0   88852  21876  18588 S   0.3  2.3  22:18.19 lxpanel
14721 root      20   0       0      0      0 S   0.3  0.0   0:01.60 kworker/1:0
    1 root      20   0    5404   3884   2704 S   0.0  0.4   0:21.59 systemd
    2 root      20   0       0      0      0 S   0.0  0.0   0:00.38 kthreadd
    3 root      20   0       0      0      0 S   0.0  0.0   0:44.95 ksoftirqd/0

 

> Is there a way to force OLA to send the last incoming messages to the
> interface immediatly and permanently?
I'm convinced that this isn't your problem. Are you sure that the
messages are getting through to the OLA core correctly (ola_dmxmonitor
will show this, without the web interfacing getting in the way).

I can see the changes i am doing in openHAB immediately in the ola dmx monitor, but somehow the dmx controller gets the message only after a delay of ~20/30 seconds

How does openHAB communicate with OLA? Is it sending traffic over the
network?

Not quite sure about this.

I remember reading a post with someone saying something about problems because of too much logging going on in the background?
But the cpu usage seems to be fine so i can't imagine this is the problem.

On my DMX UART interface there are some jumpers:
http://www.bitwizard.nl/shop/raspberry-pi?product_id=153
What are they for? Would a change help?

Markus

[Markus Stoehr]

Oh and what does "RDM" in the OLA web UI stands for?
Because here i can see a lot of values:
http://www.bitwizard.nl/shop/raspberry-pi?product_id=153

But in my case it's completely empty:

[Arjan van Vught]

Hi Markus,

Herewith some background information :

• https://en.wikipedia.org/wiki/RDM_%28lighting%29
• http://www.rdmprotocol.org/what-is-it/

You can not do RDM with the native UART interface.

When you use an DMX/RDM USB interface with a processor then you are able to do RDM.

However, this http://www.bitwizard.nl/shop/raspberry-pi?product_id=153 can be a RDM Responder --> http://www.raspberrypi-dmx.com/raspberry-pi-rdm-responder
It is also a DMX slave for controlling SPI devices (http://www.raspberrypi-dmx.com/raspberry-pi-rdm-responder/built-in-supported-spi-devices).

- Arjan


Op 2-4-2016 om 10:39 schreef Markus Stoehr:

[Markus Stoehr]

Hi Arjan,

thanks for your help, but i don't understand how this solves my problem:
- Does this mean that my problems with this product (http://www.bitwizard.nl/shop/raspberry-pi?product_id=153) will be the same when i will change it with this produkt( http://www.bitwizard.nl/shop/raspberry-pi?product_id=154) ?

And if yes, what is the solution to my problems then? Are what should be my next steps to get closer to a solution?

Markus

[Arjan van Vught]

Hi Markus,

With http://www.bitwizard.nl/shop/raspberry-pi?product_id=154 or any other USB device with a processor, the DMX timing is handled outside the host.
The external processor controls the DMX512 timing.

- Arjan

Op 2-4-2016 om 17:30 schreef Markus Stoehr:

[Richard Ash]

On Sat, 2 Apr 2016 01:32:18 -0700 (PDT)
Markus Stoehr <m...@psyron.com> wrote:

> Am Freitag, 1. April 2016 22:22:48 UTC+2 schrieb Richard Ash:
> > Or, the message from OpenHAB might not be getting to OLA in a
> > timely manner? Or, the OpenHAB input plugin might be blocking the
> > operation of the OLA core, so that data is not being passed on.
>
> I have checked the messages from openHAB to OLA, they are
> sent/received immediately - no time delay

How did you check this? I don't doubt you did, but where you saw the
changes coming through might matter.

> > What if neither the OLA web interface nor openHAB are running? The
> > UART output plugin will still be sending under these conditions
> > (because the thread doesn't stop). Obviously, nothing will change,
> > but I would expect that the little green LED would keep blinking.
>
> When i open the OLA web interface (console) then the green light
> starts blinking.
> When i then close the OLA web interface the green light continue to
> blink but the moment i am sending a command from openHAB the light
> stop blinking and only after abotu 30 seconds the green light blinks
> once at the the color change takes place.

This confirms what I was thinking - that when openHAB tries to send a
colour change, it does something which breaks the normal operation of
OLA (which stops the green light blinking). It's this, not the eventual
delivery of the change which you need to focus on.

> > What was the CPU usage when you were doing these tests? The UART
> > output plugin shouldn't use too much, but will be somewhat
> > sensitive to other programs using a lot of CPU (because the thread
> > keeps getting kicked off the CPU by others).
> >
> >
> Here the CPU usage while changing colors:
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
> COMMAND 1926 root 20 0 384532 119724 17480 S 12.9 12.6
> 813:58.18 java 4089 pi 20 0 62996 11824 9268 S 1.3
> 1.2 538:18.92 olad 16874 pi 20 0 5092 2476 2124 R
> 1.0 0.3 0:00.49 top 7 root 20 0 0 0 0 S
> 0.3 0.0 2:28.00 rcu_preempt

I presume openHAB is what is running java, and using most of the
resources in your shot. However, it isn't using so much that I would
expect ola to stop working. I can't find anything on
http://www.openhab.org/features/supported-technologies.html
which directs me to connecting openHAB to OLA. What plug-in are you
using to get from openHAB to OLA?

Richard

[Peter Newman]

The OLA binding for OpenHAB seems to be mentioned here:

https://github.com/openhab/openhab/wiki/DMX-Binding

Markus, as Richard says, if DMX output/the flashing green light is reliable from ola_dmxconsole, the OLA web UI all the time until OpenHAB gets involved, then it's highly likely you'll have similar issues regardless of which interface you're using. Yes as Arjan says, any of the OLA plugins/interfaces that don't have a local microcontroller onboard will be more susceptible to timing issues (e.g. the UART interface or an Enttec OpenDMX USB), but depending on exactly what is going wrong, you may have similar issues with a more expensive interface.

Do you have an oscilloscope available, or can you build one of these DMX testers http://www.bigclive.com/dmxtest.htm . It should help to narrow down if the UART is stopping transmitting entirely, or just that the timing/frames its transmitting aren't within the tolerances of your DMX receiver.

We are indeed open source, all the code is available here:

https://github.com/OpenLightingProject/ola

You can ignore the RDM stuff, I can't see exactly which image you're referring to, but I suspect they just happens to have our dummy RDM responders patched to the same interface too.

[Dale]

is it possible that the dmx console sends consistent dmx packets regardless of change (green light blinking), once closed and a serial update comes along, the dmx stream stops. some seconds later the serial fifo flushes and you get your one update (or similar)?
I had similar problem when trying to send dmx from an android device. If I changed values constantly on the andrioid, lights woud work, but when I stopped, the stream stopped and the lights went out. Never solved the problem.

On Monday, March 28, 2016 at 9:59:33 AM UTC-7, Markus Stoehr wrote:

Hello guys,

(watch this video for a desciption of my problem: https://youtu.be/dQrUNlLq4Us)

I have almost successfully completed my home automation setup using
- RPI2
- openHAB
- OLA
- UART native DMX interface
- 30 channel DMX controller

OLA is working, but when changing colors from within openHAB there is always a delay of 30 seconds or so. Messages are sent/received immediately to/from OLA but it seems like OLA is not sending the commands to the DMX controller - only after a while.
This is a very strange behavior and i am not very familiar with OLA/DMX.
Can someone give me a hint how to solve this problem?

[Markus Stoehr]

Hi Peter,

problem source found!

As some have guessed it was the 30 channel DMX controller which might have some problems.

I was able to get a usb DMX interface and a simple DMX light from a friend and tested both:

- with my friend's usb DMX interface using my 30 channel DMX controller i got the same problems

- using my friend's DMX light both interaces work perfectly.

 

Ok, so now that i know that there is a problem with my 30 channel DMX controller - is there a way to fix this or do i simply have to send it back and buy other ones?

 

Thanks again for all your supports. I feel sorry for all that drama because of a corrupt dmx controller but i didn't know much about dmx and also didn't know that it's sometimes possible that dmx hardware could be so buggy. I even bought 2 of those 30 channel dmx controller and i had the same problems with both of them.

 

Ok, now i will buy other controllers and hope that everything works fine then.

Thanks again a lot,

Markus

[Markus Stoehr]

Hi Dale,

i suppose you had similar problems like me then. And as i now know, it's my controller which is buggy. So i guess that the controller receives some of the signals but not all. Therefore if you change colors constantly the chances are higher that the controllers get some of the messages. But if you only change the color once it's very likely that this single message get lost.

So try another controller and check if you then still get the same problem.

(Though i am still quite not sure how and when signals are send in this chain of openHAB / ola / interface / controller:

- Is it correct that once the dmx controller gets a message it changes its state and stay like this until he gets a new message?

- And the dmx interface does not cache any messages but always send messages directly from ola to the controller?

- And OLA also does not cache messages?

- If so i guess my problem was that openHAB send messages only once per second or so and those few messages got lost then because of my corrupt controller)

 

Markus

[Markus Stoehr]

Summary:
Please avoid using this 30 channel DMX controller as it's likely to be very buggy:
http://de.aliexpress.com/item/30CHANNEL-27CH-EASY-DMX-LED-controller-DMX-decoder-driver-RGB-led-controller/32387978299.html

[Arjan van Vught]

Hi Markus,

When you have a DMX-RDM/USB interface, then it is worthwhile to do a test with your current DMX board and http://www.raspberrypi-dmx.com/raspberry-pi-rdm-responder
There are several options available for SPI-> buffered output.

- Arjan

Op 3-4-2016 om 11:55 schreef Markus Stoehr:

--

[Markus Stoehr]

Hi Arjan,

 

so you mean using this interface with a chip that can buffer messages (http://www.bitwizard.nl/shop/raspberry-pi?product_id=154) may also solve my problems?

I have aleady ordered it so i will see since i am curious to know.

I will report once i have tested it.

 

Markus

[Arjan van Vught]

Hi Markus,

A DMX-RDM-USB interface with a processor is not just for buffering messages. It is also responsible for a precise DMX transport timing, and precise RDM message timing.

You can use your current board as a replacement for http://de.aliexpress.com/item/30CHANNEL-27CH-EASY-DMX-LED-controller-DMX-decoder-driver-RGB-led-controller/32387978299.html
You current board has 2 SPI connectors which can be used for driving SPI expansion boards for controlling devices at different voltage level.

- Arjan

Op 3-4-2016 om 12:17 schreef Markus Stoehr:

[Markus Stoehr]

Hi Arjan,

You can use your current board as a replacement for http://de.aliexpress.com/item/30CHANNEL-27CH-EASY-DMX-LED-controller-DMX-decoder-driver-RGB-led-controller/32387978299.html

 I do not understand what you mean with this sentence. Can you please elaborate what you mean?

You current board has 2 SPI connectors which can be used for driving SPI expansion boards for controlling devices at different voltage level.

 Sorry, I also don't understand this.

Markus