Artnet DMX module

Begonnen von zevnik, 17 Januar 2014, 00:54:32

Vorheriges Thema - Nächstes Thema

Elektron

Hi Zeldi,

Today i've done some more test.
After some Wireshark and tcpdump analysis I've got it work but only when OLA and FHEM are not on the same Device!
When OLA and FHEM are running on the same Device (RaspberryPi in my Case) i get the Error Message.
Independet on what IP-Address I use. (127.0.0.1 or the "real" IP)

Any sugestions how I could get it work?
I think FHEM and OLA on the same Device with a simple FTDI-RS485 Interface should be a cheap solution...

With kind regards
Michael

zevnik

Hi,

artnet client by default opens UDP socket on local port 6454 (which is supposed to be in standard), but I can change it, so you can test it (or you can change it in line 324).

Elektron

Hi,

you are right, when i woke up this morning i thought the Problem is that source- an destination-Port are the same.
And the destination-Port as allready used by the olad.

Thank you for your Support!
Michael

Elektron

Hi,

I've changed the Source-Port in Line 324 and now it works fine.
With the usage of OLAD the FHEM-ARTNET-Module is compatible with nearly all DMX-Interfaces including simple FTDI-Interfaces.
If I find some time I'll write an Wiki-Artikle...

Thank you for your Help!
Mochael

zevnik

Hi,

can you just clarify: OLA daemon's purpose is controlling the lights via DMX. DMX are sent over RS485, which connected locally on the machine? And it's feed is artnet, that's why you are using my ARTNET module? Great to hear that.

So you are connecting to localhost OLA listener? I'll make a change in the code, to find next available port if 6454 is busy.

Can you just please describe your usage scenario? Because I have a plan of dividing the module into virtula/physical part, so you could define multiple autonomous lights (fixtures) which are then controlled be the same artnet physical interface. Which means you can use standard RGB or white dimmer options available already in FHEM.

But since, I don't need that option that much, development is ofcourse very slow:)

Elektron

Hi Zeldi,

Im using olad www.opendmx.net to send DMX-Telegrams over a simple FTDI-Based USB-RS485-Adapter.
OLA supports many different DMX Interfaces an use Artnet as Input...
FHEM and OLAD are running on an RaspberryPI.
Via DMX I control 2 LED-Par64 spots. 6-Channel (RGB, brightnes, strobe).

I also want to control later some WS2801 via the SPI-Interface of the Raspberry-PI

Michael

macmattes

Hi Zeldi

i have added the Universe Option
as already said i use different artnet->ws2801 modules each with an other ip and different universes,

i have one request. i use > 100 channels , therefore it will be good to disable the channelstate string in the webview

oldicke

Hi,

please can help one?
when it comes to German

oldicke

define ArtNet0 ARTNET 1.0.0.200 0

geht leider bei mir nicht,bekomme immer die meldung

wrong syntax: define <name> ARTNET ip[:port] universe comma_separated_channels

was mach ich falsch?

ext23

Da fehlen doch noch die Kanäle...
HM, KNX, FS20, 1-Wire, PanStamp, AVR-NET-IO, EM1000EM, PCA301, EC3000, HM-LAN, CUL868, RFXtrx433, LGW, DMX @Ubuntu-Server (Hauptsystem) & Raspberry Pi (Satellit)

zevnik

Zitat von: oldicke am 05 Mai 2015, 14:13:03
define ArtNet0 ARTNET 1.0.0.200 0

geht leider bei mir nicht,bekomme immer die meldung

wrong syntax: define <name> ARTNET ip[:port] universe comma_separated_channels

was mach ich falsch?


define ArtNet0 ARTNET 1.0.0.200 0  1,2,3,4

für die aktive Kanäle die du brauchst.

zevnik

Zitat von: macmattes am 29 November 2014, 21:27:57
Hi Zeldi

i have added the Universe Option
as already said i use different artnet->ws2801 modules each with an other ip and different universes,

i have one request. i use > 100 channels , therefore it will be good to disable the channelstate string in the webview

Maybe I finally find some time to improve the module. And also take your suggestion into account.

oldicke

#72
Zitat von: zeldi am 06 Mai 2015, 12:00:39

define ArtNet0 ARTNET 1.0.0.200 0  1,2,3,4

für die aktive Kanäle die du brauchst.

habe denn noch die meldung

wrong syntax: define <name> ARTNET ip[:port] universe comma_separated_channels

omg

jetzt geht es mit: define ArtNet ARTNET 192.168.178.13:6454 0 1,2,3

muss ich für jede Universe ein "defin ArtNet" anlegen?
und wie kann ich 150 leds gleich zeitig steuern?  :-\ (ws2812) strips

zevnik

Ich denke ich weiss wo liegt ein problem:
meine originäle version hat ein Syntax von:  define ArtNet ARTNET 192.168.178.13:6454 1,2,3 (ohne universe)
patch von @macmates Syntax ist: define ArtNet ARTNET 192.168.178.13 0 1,2,3 (mit universe)

Wie 100 artnet Modules steuren? Hm..., Artnet module ist zurzeit ein 1:1 interface zum Artnet device.
Kan ws2812 LEDs auf eine Broadcastaddresse zuhören?

Ich denke diese Kombination könnte funktionieren:
led1:universe=0:channel=1,2,3
led2:unverse=0:channel=4,5,6
led3:universe=0:channel=7,8,9
define ArtNet ARTNET 192.168.178.255 1,2,3,4,5,6,7,8,9

oldicke

#74
Hallo,

habe eine andere Lösung gefunden.

ich habe 4 led rgb streifen. für jeden rgb streifen eine Universe, da meine ArtNet-box nicht RGB macht habe ich sie
in GRB angeben müssen.

define initialUsbCheck notify global:INITIALIZED usb create
define ArtNet1 ARTNET 192.168.178.13:6454 1 1,0,2
define ArtNet2 ARTNET 192.168.178.13:6454 2 1,0,2
define ArtNet3 ARTNET 192.168.178.13:6454 3 1,0,2
define ArtNet0 ARTNET 192.168.178.13:6454 0 1,0,2


so kann ich jeden Streifen einzeln ansteuern. (ws2812b) aber immer nur ein Kanal (0,1,2)= 1 led.
jede weitere led ein Kanal mit z.B. (3,4,5). Ist sehr aufwendig. :(

gibt es eine andere Lösung ?