search

jamesremuscat / avx

A system for controlling A/V devices such as video switchers via a networkable control device.
4 stars 1 forks source link

Trying to move blinds results in sound desk power being cut #39

Closed jamesremuscat closed 10 years ago

jamesremuscat commented 10 years ago

Via Jamie T:

"I’ve had a report of an issue with the touch screen so just wanted to flag it up..

Apparently when you want the blinds to go up or down it turns off the sound desk (it’s happened all of today Will said and it doesn’t do a soft shut down so all the amps pop..)"

jamesremuscat commented 10 years ago

Particularly dubious-looking lines from dmesg (actually /var/log/kern.log):

Jan 30 18:01:41 controller kernel: [4135668.918796] hub 1-1.2:1.0: port 3 disabled by hub (EMI?), re-enabling... Jan 30 18:01:41 controller kernel: [4135668.919217] usb 1-1.2.3: USB disconnect, device number 8 Jan 30 18:01:41 controller kernel: [4135668.936813] pl2303 ttyUSB5: pl2303 converter now disconnected from ttyUSB5 Jan 30 18:01:41 controller kernel: [4135668.936971] pl2303 1-1.2.3:1.0: device disconnected Jan 30 18:01:41 controller kernel: [4135669.177013] usb 1-1.2.3: new full-speed USB device number 17 using dwc_otg Jan 30 18:01:41 controller kernel: [4135669.278824] usb 1-1.2.3: New USB device found, idVendor=067b, idProduct=2303 Jan 30 18:01:41 controller kernel: [4135669.278856] usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jan 30 18:01:41 controller kernel: [4135669.278873] usb 1-1.2.3: Product: USB-Serial Controller Jan 30 18:01:41 controller kernel: [4135669.278888] usb 1-1.2.3: Manufacturer: Prolific Technology Inc. Jan 30 18:01:41 controller kernel: [4135669.285887] pl2303 1-1.2.3:1.0: pl2303 converter detected Jan 30 18:01:41 controller kernel: [4135669.293402] usb 1-1.2.3: pl2303 converter now attached to ttyUSB10

1-1.2.1 is the power/screens card, 1-1.2.3 is the Blinds B relay card. I suspect this might have been enough to confuse the controller process as to which device to send commands to... I restarted the controller process (after double-checking the 5V power supply to the four-way USB hub, which was my gut reaction - it clicked when I pressed it in tighter) and blinds, screens and power are behaving as they should.

As to what exactly happened at 18:01 to trigger this... is it possible someone tripped over a cable in the power room or nudged the USB hub? (I'm not really happy with how I've 'mounted' it, I need to look for a better solution at some point.) The relevant line in the Linux kernel suggests EM interference (the 'EMI' in the first message) so could just be random chance.

Things are working now, so closing this issue.