mattdc

Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • in reply to: Terminal Window Dialog Normal? #2715
    mattdc
    Participant

    Great, thanks for the tips. I’ve identified the problem. The computer itself (rescued it from the supply closet) is severely underpowered for the task, but the upgraded A+++ gpu was masking its shortcomings.

    Big help!

    Is documentation of the command line flags available online?

    Thanks again.

    in reply to: External button for rain/drain #2712
    mattdc
    Participant

    Great, thanks for the update. I went ahead and wired up an arduino and some buttons. It seems to be working perfectly fine without crashing anything.

    in reply to: External button for rain/drain #2702
    mattdc
    Participant

    I found the wayback machine post, and was wondering if anyone had a source for the specified code files: ScriptExecutorTool.h and ScriptExecutorTool.cpp

    https://shorturl.at/hjlAZ

    in reply to: Kinect USB Problems. #2541
    mattdc
    Participant

    New adapter is promising. Motor, Camera, Audio now display properly in the readout.

    Thanks.

    in reply to: Kinect USB Problems. #2533
    mattdc
    Participant

    Ah, I see. I misunderstood and thought so long as one of those items was showing everything was ok!

    I’ll get a new adapter and give that a whirl. Thanks.

    in reply to: Kinect USB Problems. #2530
    mattdc
    Participant

    Thanks for the reply.

    I installed everything “stock” following the detailed install instructions on an older PC with upgraded video card.

    mattdc@arsandbox:~$ lsusb
    Bus 002 Device 003: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
    Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 003 Device 019: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor
    Bus 003 Device 018: ID 0409:005a NEC Corp. HighSpeed Hub
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    mattdc@arsandbox:~$ lsb_release -dc
    Description: Linux Mint 19 Tara
    Codename: tara

    I’ve tried multiple Kinect units. 2@ v.1414 and 1@ v.1478. The 1414’s act the same. I think the 1478 is broken outright; It displays a red light when I plug it in. I guess it’s possible all are broken, or there is a problem with the AC adapter not supplying the correct voltage? I should probably try a second from a different vendor.

    I tried all the stock USB ports with the same results. Both Kinect 1414’s show as Microsoft Corp. Xbox NUI Motor

    I’ve also tried other newer Linux distros. All the software [eventually] installs and builds correctly, but I get hung up on step 6, which is making me think it’s something I’m missing in the instructions, or just incompatible hardware.

    The PC is some kind of ASUS with onboard everything.

    Thanks again.

    • This reply was modified 1 year, 3 months ago by mattdc.
    in reply to: Kinect USB Problems. #2526
    mattdc
    Participant

    I’ve been through the forum and tried other troubleshooting steps.

    I got the add on USB card recommended in a different post.
    Have tried multiple Kinects.
    Kinect shows when I list USB, lsusb

    I don’t have projector, yet so I haven’t connected that, but I can’t imagine that would be the cause. I note it here as a just incase since I’ve tried everything else I can think of.

    Next step is to try the 18.3 version of the software which was noted as a possible solution fr some hardware in a post on the forum.

    I’m probably just doing something dumb, but I can’t figure it out.

    Thanks.

    in reply to: Drain water in software #2512
    mattdc
    Participant

    Also trying to post, but am unable.

Viewing 8 posts - 1 through 8 (of 8 total)