Der fehlende usbserial erscheint leider immer noch.
[Boblight SupportThread] Update: 11-02-2014, Boblight 0.8R6
-
-
Zitat
Original von Bschaar
wiki lesen: http://wiki.blue-panel.com/ind…BCr_lokale_Installationendanke für den hinweis
ist das jetzt so zu verstehen, dass boblight auf einer dm800hd nicht funktioniert, weil es keine nf.ipk dafür gibt?
-
Hallo,
rambodieschen:
für die DM8000HD ist die mips32el die richtige !!
Allerdings gibt es anscheinend mit der 8000er (und nur mit der !) auch noch andere Probleme, egal ob Boblight oder Atmolight - Plugin...Digital
-
Hm was für Probleme?
Ich habe jetzt alles neu geflasht/installiert (OE2 anstatt ICVS). Nun kann ich zwar Boblight installieren, nur stürzt ständig das Plugin mit Greenscreen ab.
Welche Lightpack muss ich auswählen und mit welchen Einstellungen?
Wenn ich das Lightpack am PC anschliesse steht da komischerweise Firmware 0.0.
Komischerweise finde ich so gut wie nichts im Internet über Dreambox und Lightpack. -
Hi Speedy,
thanks for the last version (r6).
It works nearly perfect - there are only two problems:
1) still flashlights
2) since r6: GS with live-color-adjustment -
Kann mir jemand bitte helfen?
Zur Hardware
DM800se clone oe 2.0
Image : edit by marco777
Plugin: Boblight
enigma2-plugin-extensions-boblight-enigma2_0.8r6_mips32el.ipkArdurio UNO
LED Strip mit 64 (leds)habe ich das Board erfolgreich und unter Win 7 + XBMC
getestet.http://www.boblightenigma2.net…-make-your-own-ambilight/
Bin nach der Anleitung vorgegangen
nur funktioniert das ganze leider nicht an meiner DM
Verschiedene boblight.conf probiert
auch mit dem Plugin selber erstelltKann mir jemand helfen?
Was ihr bei der Konfiguration eingegeben habt:
Schnittstelle.... Type usw.Vielen Dank schonmal
-
Nein dir wird hier niemand helfen!
Bei uns gibt es keinen Support für Cloneboxen!
Bye
-
Hallo zusammen,
ich bin neu hier und habe seit 1 Woche nun eine Dreambox DM500HD V2 DVB/C Version.
Ich besitze das Lightpack. Habe nun Boblight die neuste Version installiert.
Ich habe das Boblight an die Service Schnittstelle angeschlossen (Mini USB) indem ich einen Adapter von USB auf mini USB angeschlossen habe.
Allerdings leuchtet nicht einmal die Box vom Lighpack. Wenn ich eine Boblight Config abspeichern will, bekomme ich den greenscreen mit Fehlermeldung und die Box startet neu. Jetzt ist meine Frage, wo muss ich das Lightpack anschließen, und funktioniert das überhaupt direkt an die Dreambox angeschlossen?Vielen Dank schonmal für eine Antwort.
-
das ist der service connector - zum flashe/ seriell loggen
die 500HD hatt kein USB anschluss vom werk aus,
da must du dich um ein ESB-mod kümmern -
-
is it possible to use this plugin with phillips ambx lights??
-
Hello,
I have 2 Lightpack item (firmware >= 6.3).
1st Lightpack comfig is:
Code
Alles anzeigen#[global] #interface 127.0.0.1 #port 19333 [device] name ambilight_1st type lightpack channels 30 interval 20000 serial A4830363935351708161 #1_st #rate 57600 #debug off [color] name red rgb FF0000 #gamma 0.91 #adjust 1.0 #blacklevel 0.0 [color] name green rgb 00FF00 #gamma 0.86 #adjust 0.96 #blacklevel 0.0 [color] name blue rgb 0000FF #gamma 0.95 #adjust 0.80 #blacklevel 0.0 [light] #left name 1XX color red ambilight_1st 1 color green ambilight_1st 2 color blue ambilight_1st 3 hscan 0 15 vscan 66.67 100.0 [light] #left name 2XX color red ambilight_1st 4 color green ambilight_1st 5 color blue ambilight_1st 6 hscan 0 15 vscan 33.33 66.67 [light] #left name 3XX color red ambilight_1st 7 color green ambilight_1st 8 color blue ambilight_1st 9 hscan 0 15 vscan 0.0 33.33 [light] #top name 4XX color red ambilight_1st 10 color green ambilight_1st 11 color blue ambilight_1st 12 hscan 0.0 25.0 vscan 0 15 [light] #top name 5XX color red ambilight_1st 13 color green ambilight_1st 14 color blue ambilight_1st 15 hscan 25.0 50.0 vscan 0 15 [light] #top name 6XX color red ambilight_1st 16 color green ambilight_1st 17 color blue ambilight_1st 18 hscan 50.0 75.0 vscan 0 15 [light] #top name 7XX color red ambilight_1st 19 color green ambilight_1st 20 color blue ambilight_1st 21 hscan 75.0 100.0 vscan 0 15 [light] #right name 8XX color red ambilight_1st 22 color green ambilight_1st 23 color blue ambilight_1st 24 hscan 85.0 100 vscan 0.0 33.33 [light] #right name 9XX color red ambilight_1st 25 color green ambilight_1st 26 color blue ambilight_1st 27 hscan 85.0 100 vscan 33.33 66.67 [light] #right name 10X color red ambilight_1st 28 color green ambilight_1st 29 color blue ambilight_1st 30 hscan 85.0 100 vscan 66.67 100.0
2nd Lightpack condig is:
Code
Alles anzeigen#[global] #interface 127.0.0.1 #port 19333 [device] name ambilight type lightpack channels 30 interval 20000 serial A48393431343513101E0 #2_nd #rate 57600 #debug off [color] name red rgb FF0000 #gamma 0.91 #adjust 1.0 #blacklevel 0.0 [color] name green rgb 00FF00 #gamma 0.86 #adjust 0.96 #blacklevel 0.0 [color] name blue rgb 0000FF #gamma 0.95 #adjust 0.80 #blacklevel 0.0 [light] #left name 1XX color red ambilight 1 color green ambilight 2 color blue ambilight 3 hscan 0 15 vscan 66.67 100.0 [light] #left name 2XX color red ambilight 4 color green ambilight 5 color blue ambilight 6 hscan 0 15 vscan 33.33 66.67 [light] #left name 3XX color red ambilight 7 color green ambilight 8 color blue ambilight 9 hscan 0 15 vscan 0.0 33.33 [light] #top name 4XX color red ambilight 10 color green ambilight 11 color blue ambilight 12 hscan 0.0 25.0 vscan 0 15 [light] #top name 5XX color red ambilight 13 color green ambilight 14 color blue ambilight 15 hscan 25.0 50.0 vscan 0 15 [light] #top name 6XX color red ambilight 16 color green ambilight 17 color blue ambilight 18 hscan 50.0 75.0 vscan 0 15 [light] #top name 7XX color red ambilight 19 color green ambilight 20 color blue ambilight 21 hscan 75.0 100.0 vscan 0 15 [light] #right name 8XX color red ambilight 22 color green ambilight 23 color blue ambilight 24 hscan 85.0 100 vscan 0.0 33.33 [light] #right name 9XX color red ambilight 25 color green ambilight 26 color blue ambilight 27 hscan 85.0 100 vscan 33.33 66.67 [light] #right name 10X color red ambilight 28 color green ambilight 29 color blue ambilight 30 hscan 85.0 100 vscan 66.67 100.0
I had tested them alone as a 1 item connected to Dreambox DM7020 and they work correctly.
Than I combined configs in one (copy past operationa) and only 1 Lightpack shined.
Also there was some boblight error:Code
Alles anzeigen16:24:43.359199 (InitLog) start of log /home/root/.boblight/boblightd.log 16:24:43.360530 (PrintFlags) starting boblightd /etc/boblight.conf 16:24:43.360909 (CConfig::LoadConfigFromFile) opening /etc/boblight.conf 16:24:43.377990 (CConfig::CheckConfig) checking config lines 16:24:43.403773 (CConfig::CheckConfig) config lines valid 16:24:43.404187 (CConfig::BuildConfig) building config 16:24:43.443375 (CConfig::BuildConfig) built config successfully 16:24:43.443974 (main) Starting devices 16:24:43.445545 (CDevice::Process) ambilight: starting 16:24:43.446570 (CDevice::Process) ambilight: setting up 16:24:43.447419 (CDevice::Process) ambilight_1st: starting 16:24:43.449251 (CDevice::Process) ambilight_1st: setting up 16:24:43.453056 (CClientsHandler::Process) opening listening socket on *:19333 16:24:43.486678 (CDeviceLightpack::SetupDevice) ambilight_1st: found Lightpack at bus 4 address 5, serial is A48393431343513101E0 16:24:43.490375 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 4 address 5, serial is A48393431343513101E0 16:24:43.492591 (CDeviceLightpack::SetupDevice) ambilight_1st: found Lightpack at bus 3 address 26, serial is A4830363935351708161 16:24:43.493260 (CDeviceLightpack::SetupDevice) ERROR: ambilight_1st: error detaching interface 0, error:-5 16:24:43.496476 (CDevice::Process) ERROR: ambilight_1st: setting up failed, retrying in 10 seconds 16:24:43.500416 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 4 device address 5 16:24:43.505467 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 26, serial is A4830363935351708161 16:24:43.505724 (CDevice::Process) ambilight: setup succeeded 16:24:49.024478 (CClientsHandler::Process) 127.0.0.1:56354 connected 16:24:49.029375 (CClientsHandler::ParseMessage) 127.0.0.1:56354 said hello 16:24:49.057926 (CClientsHandler::ParseSet) 127.0.0.1:56354 priority set to 128 16:24:53.499415 (CDevice::Process) ambilight_1st: setting up 16:24:53.516366 (CDeviceLightpack::SetupDevice) ambilight_1st: found Lightpack at bus 4 address 5. Couldn't get serial. 16:24:53.524518 (CDeviceLightpack::SetupDevice) ambilight_1st: found Lightpack at bus 3 address 26, serial is A4830363935351708161 16:24:53.525167 (CDeviceLightpack::SetupDevice) ERROR: ambilight_1st: error detaching interface 0, error:-5 16:24:53.525560 (CDevice::Process) ERROR: ambilight_1st: setting up failed, retrying in 10 seconds 16:24:55.672361 (CDevice::Process) ambilight: closed 16:24:55.677742 (CDevice::Process) ambilight: setting up 16:24:55.698354 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 4 address 5, serial is A48393431343513101E0 16:24:55.705484 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 4 device address 5 16:24:55.711447 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 26, serial is A4830363935351708161 16:24:55.711693 (CDevice::Process) ambilight: setup succeeded 16:24:57.670174 (CDevice::Process) ambilight: closed 16:24:57.672468 (CDevice::Process) ambilight: setting up 16:24:57.696321 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 4 address 5, serial is A48393431343513101E0 16:24:57.704846 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 4 device address 5 16:24:57.710469 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 26, serial is A4830363935351708161 16:24:57.711629 (CDevice::Process) ambilight: setup succeeded 16:25:00.873707 (CDevice::Process) ambilight: closed 16:25:00.874422 (CDevice::Process) ambilight: setting up 16:25:00.896319 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 4 address 5, serial is A48393431343513101E0 16:25:00.905684 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 4 device address 5 16:25:00.913372 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 26, serial is A4830363935351708161 16:25:00.914362 (CDevice::Process) ambilight: setup succeeded 16:25:01.893896 (CDevice::Process) ambilight: closed 16:25:01.895494 (CDevice::Process) ambilight: setting up 16:25:01.916353 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 4 address 5, serial is A48393431343513101E0 16:25:01.930395 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 4 device address 5 16:25:01.935495 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 26, serial is A4830363935351708161 16:25:01.936010 (CDevice::Process) ambilight: setup succeeded 16:25:03.526007 (CDevice::Process) ambilight_1st: setting up 16:25:03.545328 (CDeviceLightpack::SetupDevice) ambilight_1st: found Lightpack at bus 4 address 5. Couldn't get serial. 16:25:03.551371 (CDeviceLightpack::SetupDevice) ambilight_1st: found Lightpack at bus 3 address 26, serial is A4830363935351708161 16:25:03.552486 (CDeviceLightpack::SetupDevice) ERROR: ambilight_1st: error detaching interface 0, error:-5 16:25:03.553382 (CDevice::Process) ERROR: ambilight_1st: setting up failed, retrying in 10 seconds 16:25:10.871372 (CDevice::Process) ambilight: closed 16:25:10.873352 (CDevice::Process) ambilight: setting up 16:25:10.896318 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 4 address 5, serial is A48393431343513101E0 16:25:10.903954 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 4 device address 5 16:25:10.909540 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 26, serial is A4830363935351708161 16:25:10.910331 (CDevice::Process) ambilight: setup succeeded 16:25:11.897552 (CDevice::Process) ambilight: closed 16:25:11.897965 (CDevice::Process) ambilight: setting up 16:25:11.916319 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 4 address 5, serial is A48393431343513101E0 16:25:11.930558 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 4 device address 5 16:25:11.936373 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 26, serial is A4830363935351708161 16:25:11.937289 (CDevice::Process) ambilight: setup succeeded 16:25:13.554456 (CDevice::Process) ambilight_1st: setting up
Then once again I have tested Lightpack alone and what is more strange 1st Lightpack works correctly but 2nd Lightpack works (Leds shines) but boblight config shows that the device is connectiong and disconecting all the time. Also Enigma2 GUI gives me message one by one that new USB device is connected.
Code
Alles anzeigen10:15:57.792603 (InitLog) start of log /home/root/.boblight/boblightd.log 10:15:57.794013 (PrintFlags) starting boblightd /etc/boblight.conf 10:15:57.794476 (CConfig::LoadConfigFromFile) opening /etc/boblight.conf 10:15:57.804254 (CConfig::CheckConfig) checking config lines 10:15:57.817189 (CConfig::CheckConfig) config lines valid 10:15:57.817518 (CConfig::BuildConfig) building config 10:15:57.837094 (CConfig::BuildConfig) built config successfully 10:15:57.837578 (main) Starting devices 10:15:57.838564 (CClientsHandler::Process) opening listening socket on *:19333 10:15:57.840724 (CDevice::Process) ambilight: starting 10:15:57.841649 (CDevice::Process) ambilight: setting up 10:15:57.862454 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 6, serial is A4830363935351B022F0 10:15:57.862965 (CDeviceLightpack::SetupDevice) ERROR: ambilight: error detaching interface 0, error:-5 10:15:57.863426 (CDevice::Process) ERROR: ambilight: setting up failed, retrying in 10 seconds 10:16:07.863873 (CDevice::Process) ambilight: setting up 10:16:07.879399 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 6, serial is A4830363935351B022F0 10:16:07.879874 (CDeviceLightpack::SetupDevice) ERROR: ambilight: error detaching interface 0, error:-5 10:16:07.880308 (CDevice::Process) ERROR: ambilight: setting up failed, retrying in 10 seconds 10:16:17.880713 (CDevice::Process) ambilight: setting up 10:16:17.895505 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 6, serial is A4830363935351B022F0 10:16:17.895991 (CDeviceLightpack::SetupDevice) ERROR: ambilight: error detaching interface 0, error:-5 10:16:17.896434 (CDevice::Process) ERROR: ambilight: setting up failed, retrying in 10 seconds 10:16:27.896849 (CDevice::Process) ambilight: setting up 10:16:27.905781 (CDeviceLightpack::SetupDevice) ERROR: ambilight: no Lightpack device with serial number A4830363935351B022F0 found 10:16:27.906293 (CDevice::Process) ERROR: ambilight: setting up failed, retrying in 10 seconds 10:16:37.906761 (CDevice::Process) ambilight: setting up 10:16:37.923439 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 8, serial is A4830363935351B022F0 10:16:37.932496 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 3 device address 8 10:16:37.932793 (CDevice::Process) ambilight: setup succeeded 10:17:06.749894 (CClientsHandler::Process) 127.0.0.1:47035 connected 10:17:06.751677 (CClientsHandler::ParseMessage) 127.0.0.1:47035 said hello 10:17:06.765286 (CClientsHandler::ParseSet) 127.0.0.1:47035 priority set to 128 10:17:17.946720 (CDevice::Process) ambilight: closed 10:17:17.948696 (CDevice::Process) ambilight: setting up 10:17:17.964916 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 8, serial is A4830363935351B022F0 10:17:17.972461 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 3 device address 8 10:17:17.974285 (CDevice::Process) ambilight: setup succeeded 10:17:18.968746 (CDevice::Process) ambilight: closed 10:17:18.969039 (CDevice::Process) ambilight: setting up 10:17:18.996406 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 8, serial is A4830363935351B022F0 10:17:19.008673 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 3 device address 8 10:17:19.009044 (CDevice::Process) ambilight: setup succeeded 10:17:20.143427 (CDevice::Process) ambilight: closed 10:17:20.144229 (CDevice::Process) ambilight: setting up 10:17:20.164849 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 8, serial is A4830363935351B022F0 10:17:20.174681 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 3 device address 8 10:17:20.177049 (CDevice::Process) ambilight: setup succeeded 10:17:21.257668 (CDevice::Process) ambilight: closed 10:17:21.257936 (CDevice::Process) ambilight: setting up 10:17:21.281474 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 8, serial is A4830363935351B022F0 10:17:21.297832 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 3 device address 8 10:17:21.303981 (CDevice::Process) ambilight: setup succeeded 10:17:22.274703 (CDevice::Process) ambilight: closed 10:17:22.276684 (CDevice::Process) ambilight: setting up 10:17:22.308441 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 8, serial is A4830363935351B022F0 10:17:22.317668 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 3 device address 8 10:17:22.318045 (CDevice::Process) ambilight: setup succeeded 10:17:36.346416 (CDevice::Process) ambilight: closed 10:17:36.348428 (CDevice::Process) ambilight: setting up 10:17:36.363432 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 8, serial is A4830363935351B022F0 10:17:36.370981 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 3 device address 8 10:17:36.377845 (CDevice::Process) ambilight: setup succeeded 10:17:42.741897 (CDevice::Process) ambilight: closed 10:17:42.743525 (CDevice::Process) ambilight: setting up 10:17:42.762402 (CDeviceLightpack::SetupDevice) ambilight: found Lightpack at bus 3 address 8, serial is A4830363935351B022F0 10:17:42.771418 (CDeviceLightpack::SetupDevice) ambilight: Lightpack is initialized, bus 3 device address 8 10:17:42.773484 (CDevice::Process) ambilight: setup succeeded 10:17:44.836031 (CDevice::Process) ambilight: closed
I thought that there is something wrong with this 2nd Lightpack so I have upload firmware once again and Lightpack is still in USB device connecting loop.
I thought that maybe Lightpack 2nd is brokes so I havce soldered 3rd Lightpack and the history was repeated.
BTW The Lightpack 2nd and 3rd works correctly with Windows and Prismatic.I have 2 questions:
1) Is it correct that for 2 devices I had created config by combining 2 configs (copy paste)?
2) Why Enigma2 discovers 2nd/3rd Lightpack in some loop? - strange because I do not disconnect the devise, usb cable is good, other thinks are good. (But it is only with Lighpack 2nd and 3rd. The Lightpacj 1st works correctly. -
1) 1st proflem is off the names for all devices should be unique.
2) But 2nd problem still exists. Eny ideas?? -
Hallo Experten,
habe mir die Boblight 0.8R6 auf meine Dreambox 8000 installiert, Sedu Firmware 3.0 und LED Stripes verbunden, boblight.conf mit dem BoblightConfigTool erstellt, aber nichts passiert.
In Boblight wird angezeigt, dass es nicht gestartet ist, wenn ich ein Reload mit Taste "Gelb" mache wird "keine boblight.conf in /etc gefunden" obwohl definitiv diese datei dort gespeichert ist.Wo liegt mein Fehler?
Danke für Eure Hilfe.
-
Manchmal erzeugt der ConfigCreator ne falsche conf. Was sagt denn "boblightd" per telnet?
-
also folgendes ist zu sehen
root@dm8000:~# boblightd
Boblight Daemon - for enigma2 0.8r6 (c) 2012-2013 Speedy1985 and Oktay Oeztuete
)
(InitLog) start of log /home/root/.boblight/boblightd.log
(PrintFlags) starting boblightd
(CConfig::LoadConfigFromFile) opening /etc/boblight.conf
(CConfig::CheckConfig) checking config lines
(CConfig::CheckConfig) config lines valid
(CConfig::BuildConfig) building config
(CConfig::BuildConfig) built config successfully
(main) Starting devices
(CClientsHandler::Process) opening listening socket on *:19333
(CDevice::Process) ambilight: starting with output "/dev/ttyUSB0"
(CDevice::Process) ambilight: setting up
(CDevice::Process) ambilight: setup succeeded -
das sieht ja schon mal gut aus. Jetzt könnten es noch spezielle Einträge in der config sein, die man für das SEDU braucht. Must mal ein wenig hier lesen. Hab ein KL16, deshalb kann ich hier leider nicht mehr weiterhelfen.
-
Danke soweit. Nur noch zwei abschließende Frage.
Die Anzeige in Hauptmenu "Boblight ist inaktiv" verwirrt mich.
1. Wird Boblight erst als "aktiv" gezeigt wenn eine funtionierende boblight.conf vorhanden ist oder kann bei mir irgendwas verstellt sein, das boblight gar nicht erst auf die boblight.conf zugreift?2. Wenn ich eine boblight.conf für Sedu im Boblight-Plugin erstelle und speichere bekomme ich immer einen Greenscreen. Kommt das bei Dir oder anderen auch vor?
-
Zitat
Original von direktor2000
1. Wird Boblight erst als "aktiv" gezeigt wenn eine funtionierende boblight.conf vorhanden ist oder kann bei mir irgendwas verstellt sein, das boblight gar nicht erst auf die boblight.conf zugreift?2. Wenn ich eine boblight.conf für Sedu im Boblight-Plugin erstelle und speichere bekomme ich immer einen Greenscreen. Kommt das bei Dir oder anderen auch vor?
zu1. Wenn die config fehlerhaft ist, bleibt die meldung "nicht aktiv" stehen.
zu2. wie gesagt habe ich ein Karatelight16. Es gibt noch ein Tool mit dem man auch eine config erstellen kann. Stand irgendwo ein paar Seiten voher. Das Sedu kann man, glaube ich, auch an den PC anschließen (zum Testen/Firmware). -
danke,
hab die leds mit boblight zum leuchten bekommen. mußte in der sedu-box noch den jumper auf 500k baud umstecken, sieht extrem gut aus.
es funktioniert allerdings nur, wenn ich mich über telnet mit der dreambox verbinde und "boblightd" aufrufe.
sobald telnet aus ist, wirds dunkel.aus eigener kraft macht boblight nichts hell, meckert weiter, dass die boblight.conf nicht vorhanden ist.
muss ich noch ein script basteln was "boblightd" beim start direkt von der dreambox ausgeführt wird?
was ist "boblightd" eigentlich genau? eine monitoring-option oder ein essentieller befehl, ohne den nichts zum laufen kommt?
danke noch mal für die bis dato sehr hilfreichen gedankenantöße.