22:00 EST UPDATE:
Up and running! Phew!
Had to insert "
boblightd -f" into /etc/rc.local so that the daemon activates before the XBMC Boblight add-on starts up.
Found this out by enabling/disabling the add-on after XBMC had started up and it subsequently working.
For those having issues, you may also need to insert a "sleep #" (e.g. sleep 10) into rc.local to ensure the daemon starts up before the client starts up. Else it'll fail to connect.
That's why the test commands (boblight-constant) were working but it wasn't actually capturing any video for processing.
Unfortunately, the calculator is offline (
https://sanya.tarhelyszolgaltato.eu) so I can't modify my existing (working) setup (for now).
-------------------------------------------------------------
21:30 EST (2013-04-01, 12:43)Memphiz Wrote: add --without-v4l
Thanks! After playing around with the various switches (--without-v4l actually gave an error [
configure: WARNING: unrecognized options: --without-v41], finally got it to compile and build without issue. Verified that libboblight.a, libboblight.so.0.0.0 and other files were created properly in /usr/lib/.
Alas, still running into issues:
Installed the XBMC Boblight add-on and set it up for 127.0.0.1:19333 and it connects properly.
Downloaded a standard 150 LED
boblight.conf and used sudo to put it in
/etc/:
Code:
[global]
interface 127.0.0.1
port 19333
[device]
name ambilight
type momo
output /dev/ttyACM0
channels 450
prefix 41 64 61 00 95 C0
interval 10000
rate 115200
debug off #turn this on to see what it's doing with the serial port
delayafteropen 1000000
However, after rebooting, it doesn't activate the lights during playback.
Verified using
dmesg | tail that the Arduino is detected:
Quote:xbmc@XBMC:~$ dmesg | tail
[ 2160.107646] cdc_acm 2-6:1.0: ttyACM0: USB ACM device
[ 3395.213761] usb 2-6: USB disconnect, device number 5
[ 3398.232126] usb 2-6: new full-speed USB device number 6 using ohci_hcd
[ 3398.456440] usb 2-6: New USB device found, idVendor=16c0, idProduct=0483
[ 3398.456451] usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3398.456458] usb 2-6: Product: USB Serial
[ 3398.456465] usb 2-6: Manufacturer: Teensyduino
[ 3398.456471] usb 2-6: SerialNumber: 12345
[ 3398.459632] cdc_acm 2-6:1.0: This device cannot do calls on its own. It is not a modem.
[ 3398.459702] cdc_acm 2-6:1.0: ttyACM0: USB ACM device
Running
boblightd is successful:
Quote:xbmc@XBMC:~$ boblightd
(InitLog) start of log /home/xbmc/.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:rocess) opening listening socket on 127.0.0.1:19333
(CDevice:rocess) ambilight: starting with output "/dev/ttyACM0"
(CDevice:rocess) ambilight: setting up
(CDevice:rocess) ambilight: setup succeeded
And using
boblight-constant in another PuTTY window is successful with testing commands such as
boblight-constant FF0000:
Quote:xbmc@XBMC:~/Downloads$ boblight-constant FF00FF
Connecting to boblightd
Connection to boblightd opened
Corresponding response from
boblightd:
Quote:(CClientsHandler::RemoveClient) removing 127.0.0.1:41430
(CClientsHandler:rocess) 127.0.0.1:41432 connected
(CClientsHandler:arseMessage) 127.0.0.1:41432 said hello
(CClientsHandler:arseSet) 127.0.0.1:41432 priority set to 128
Is there something that could be missing? Any other ways to debug this?
Also, is it required to put
boblightd -f into rc.local for automatic startup?