Hog 4 Playback wing Touchscreen issues

jxgriffijxgriffi Registered User, DL Beta, Hog Beta
We just upgraded to 3.4.0 and, with a new rig, have been building an entirely new show file (not an upgraded show file). During a programming session...somehow we lost the Wing touchscreen (not on a reboot...DURING programming). Mouse presses work fine, but the touch screen no longer operates. I have tried reboots (different orders...console first, wing second...wing first, console second). I have tried booting with no DVI/USB cables attached and plugged them all back in. I have tried swapping USB ports. And still nothing.

I even went so far as to reinstall the full console ISO hoping it would "trick" the touchscreen into working. Still nothing.

Any thoughts on what may have happened?
Anything I can check inside the wing or console?
I'm at a loss.

Roadhog 4
Hog 4 Playback Wing
USB Keyboard
USB Trackball

Comments

  • jxgriffijxgriffi Registered User, DL Beta, Hog Beta
    Update:
    Ok...I did another full console ISO...HOWEVER...this time I kept all USB devices (keyboard, wing, mouse) plugged in (against the suggestion of the install instructions).

    This time it took the driver...and all is back to normal. Very odd though that it didn't work the first time and I used the exact same ISO.
  • rolfwenzelrolfwenzel Registered User, Hog Beta
    edited July 2016
    Hey All, I can second this Problem. Hog 4 with Fader Wing 4 attached. The Touchscreen of the Wing responses without any Problem in Calibration Mode! When in show mode the touches refer to the right Monitor of the Hog itself and nothing happens on the Wing (Fader Wing is attached to external Mon 2) Software Version 3.4.0

    Show is programmed new on 3.40, no old conversion

    In the middle of a tour, so no way to reinstall without real need...

    Best

    Rolf
  • jxgriffijxgriffi Registered User, DL Beta, Hog Beta
    And I just had this happen again today...
    Show started up fine...
    Middle of the show, no longer have touch control on the wing...console window is fine.

    Reboot...still same issue...reboot...still same issue. At this point, I still haven't been able to get my wing screen to respond to touch yet.

    RH4
    Fader Wing
    No other USB devices
  • jxgriffijxgriffi Registered User, DL Beta, Hog Beta
    Anyone have any thoughts on this??? It's getting VERY frustrating to randomly lose the touchscreen during shows. If I can't rely on the screen and have no way to fix it, why do I even have it????
  • dkayserdkayser Registered User, HES Staff
    Hi,

    Sorry no one has responded. I will try to help you narrow this down.

    Even though you have rebooted with and without USB plugged in, this looks like the most likely area to have a problem. Is the connection at the H4 Wing loose in any way? Could there be a problem anywhere with the connection?

    Also, when you plug in the USB of the touchscreen to a different port it will lose calibration information and a reboot is required, so try not to do that for the time being. Let's narrow this down without losing calibration.

    There is a syslogger available as part of the Log (pig-open-1), it is on the Launcher tab. The debug box is not checked by default, check the debug box to turn it on. This will allow us to monitor if the USB connection is coming and going or other system errors.

    I know you cannot during a show stop, but if it occurs at a time that is convenient, then first try to re-calibrate; the point being to establish that we can communicate directly to the input subsystem. If those presses are working, the the data is getting to the system correctly and we probably have a problem with X configuration in some way.

    There is also the Touchscreen Test application. This will test that X is receiving presses correctly. I would like you to try this if possible also. If this test succeeds then we can start looking at Hog4 application and it's libraries.

    Again, sorry for the delay, I hope we can narrow the answer down soon.

    donald
  • jxgriffijxgriffi Registered User, DL Beta, Hog Beta
    Thanks Donald...

    We are a permanent install, so nothing is getting plugged in/out regularly. It is all fully setup in the booth.

    The part that is weird is that I don't lose the wing...only the touchscreen. And it's all the same USB connection.

    When the touchscreen has failed, we have indeed tried to re-calibrate and the system does not respond to touches at all on the screen (again, the wing faders still work). The only way I can get anything to work on the screen is via mouse button presses. And there are times this state will stay for several reboots and then magically work again (without unplugging or doing anything).

    At first, I thought it was related to turn on sequence...but that doesn't seem to matter. I've tried wing first, then console. I've tried console then wing...sometimes it works...sometimes it doesn't. Currently we have resorted to having a new "view" that moves everything around in case the wing touchscreen doesn't work.

    We'll keep an eye out and see how we can troubleshoot this more.
  • dkayserdkayser Registered User, HES Staff
    Since the calibration is not finding the device and the Faders still work, it seems that the USB connections and HUBs are fine. This points to the USB touch screen controller; if it works 'early' in the day, but fails 'later' in the day, it might be related to some component of the touch screen controller that has started failing intermittently. At least that is where the evidence points. If you are able to monitor the syslogger that could confirm it's a lost connection.

    If you happen to have another wing you can try it and I would hope the problem goes away. That would confirm it.
  • jxgriffijxgriffi Registered User, DL Beta, Hog Beta
    Interesting...I'll definitely keep an eye on it. Is the touch screen controller a "user serviceable" part or would it have to be returned? I'll definitely keep an eye on the syslogger.

    Unfortunately, we don't have another fader wing.
  • dkayserdkayser Registered User, HES Staff
    I don't know if it is "user servicecable", but support should be able to answer. I would let them know.
  • jxgriffijxgriffi Registered User, DL Beta, Hog Beta
    So delving deeper into this...I have started seeing some "connections" but haven't pinpointed it yet.

    It "magically" returned to being usable.
    Had a very programming intensive day...and lost it sometime, but didn't notice till late in the evening.
    Next day, still no touch screen (wing continues to work)
    Theater dark for 2 days
    Came back and touch screen was fine.
    Did 4 shows...basic playback...no issues.
    Today...a very programming intensive day...and lose the wing touch screen sometime during the day. Because we don't use the touch screen on the wing a lot, I haven't pinpointed "when" it happens. But it seems to happen on programming heavy days.

    I'm trying to go back deep into the syslogger to see if I can pinpoint anything strange that has happened. Also I couldn't find the Touchscreen Test (I KNOW it's there...but couldn't remember how to find it).

    I have attached two screen shots from the Debug lines to see if any of it makes sense to you.

    Picture 1
    Picture 2

    (let me know if the links don't work!)


  • dkayserdkayser Registered User, HES Staff
    The logger has Source Config options that are available from a right-click on the Log Window's the title bar. Each process has a tab in Source Config. The Syslogger option in the log pane is part of the Launcher tab. Scroll down under the Launcher until you see the syslogger entry and click the Debug box.

    Let it run. Filter out unwanted messages by right-clicking the message and choosing disable. This will cut down on unwanted log traffic. I you have syslogger turned on and the failure occurs, save the log file so I can look at it.

  • jxgriffijxgriffi Registered User, DL Beta, Hog Beta
    Perfect!

    I did this today.

    Console start up...everything working perfectly.

    Knowing it was going to be a heavy programming day, I cleared the log window as soon as I booted the console. Added the Syslogger option.

    About 20 minutes in...have lost the touchscreen again.

    I exported the log and will email it to you. Let me know where to send it.

    J
  • dkayserdkayser Registered User, HES Staff
    Okay, donald.kayser@barco.com.

    d
  • dkayserdkayser Registered User, HES Staff
    Pulled from log at about 18 minutes after show load.

    105 Sep 16 14:15:18 hog4 kernel: [ 1391.222361] hub 2-1.2:1.0: unable to enumerate USB device on port 5
    105 Sep 16 14:15:18 hog4 kernel: [ 1391.222204] usb 2-1.2.5: device not accepting address 14, error -32
    105 Sep 16 14:15:18 hog4 kernel: [ 1390.815030] usb 2-1.2.5: new full speed USB device number 14 using ehci_hcd
    105 Sep 16 14:15:18 hog4 kernel: [ 1390.727111] usb 2-1.2.5: device not accepting address 13, error -32
    105 Sep 16 14:15:17 hog4 kernel: [ 1390.320754] usb 2-1.2.5: new full speed USB device number 13 using ehci_hcd
    105 Sep 16 14:15:17 hog4 kernel: [ 1389.937292] usb 2-1.2.5: device descriptor read/64, error -32
    105 Sep 16 14:15:17 hog4 kernel: [ 1389.849528] usb 2-1.2.5: new full speed USB device number 12 using ehci_hcd
    105 Sep 16 14:15:17 hog4 kernel: [ 1389.466464] usb 2-1.2.5: device descriptor read/64, error -32
    105 Sep 16 14:15:17 hog4 kernel: [ 1389.378712] usb 2-1.2.5: new full speed USB device number 11 using ehci_hcd
    105 Sep 16 14:15:16 hog4 halevt: Running: halevt-umount -u /org/freedesktop/Hal/devices/usb_device_62a_710d_noserial; halevt-umount -s
    105 Sep 16 14:15:16 hog4 halevt: Running: halevt-umount -u /org/freedesktop/Hal/devices/usb_device_62a_710d_noserial_if0_hiddev; halevt-umount -s
    105 Sep 16 14:15:16 hog4 halevt: Running: halevt-umount -u /org/freedesktop/Hal/devices/usb_device_62a_710d_noserial_if0_logicaldev_input; halevt-umount -s
    105 Sep 16 14:15:16 hog4 kernel: [ 1389.255564] usb 2-1.2.5: USB disconnect, device number 9
    105 Sep 16 14:15:16 hog4 kernel: [ 1389.254955] usb 2-1.2.5: device not accepting address 9, error -32
    105 Sep 16 14:15:16 hog4 kernel: [ 1388.848096] usb 2-1.2.5: reset full speed USB device number 9 using ehci_hcd
    105 Sep 16 14:15:16 hog4 kernel: [ 1388.760172] usb 2-1.2.5: device not accepting address 9, error -32
    105 Sep 16 14:15:16 hog4 kernel: [ 1388.353367] usb 2-1.2.5: reset full speed USB device number 9 using ehci_hcd
    105 Sep 16 14:15:15 hog4 kernel: [ 1387.970356] usb 2-1.2.5: device descriptor read/64, error -32
    105 Sep 16 14:15:15 hog4 kernel: [ 1387.882544] usb 2-1.2.5: reset full speed USB device number 9 using ehci_hcd
    105 Sep 16 14:15:15 hog4 kernel: [ 1387.499521] usb 2-1.2.5: device descriptor read/64, error -32
    105 Sep 16 14:15:15 hog4 kernel: [ 1387.411804] usb 2-1.2.5: reset full speed USB device number 9 using ehci_hcd
  • dkayserdkayser Registered User, HES Staff
    Device 710d is the touchscreen. It is failing at a level where the kernel loses it. This usually indicates a hardware failure. It can be as simple as a loose or degenerated connection or cable; it can be due to electrical component failure.

    You can take off the outside panel of the wing and inspect the internal wires - powered OFF. Once open you can tilt the screen and you will see three sets of cables: power, video, USB - check them for damage, looseness, corrosion. Make sure the connections at the back of the chassis are also fine. Replace the external cable with a new one.

    If these fail, then it will need service. Call them and they can get you going.

    good luck, donald
  • jxgriffijxgriffi Registered User, DL Beta, Hog Beta
    Thanks for the update Donald.

    I'll let you know what i find.

  • jxgriffijxgriffi Registered User, DL Beta, Hog Beta
    Thanks for all of the help Donald...

    I pulled apart the wing and re-seated everything. It seems to be working well right now. If it acts up again, I'll reach out to support for the controller info.
Sign In or Register to comment.