Menu

#3 Crashes when using Define Foot Pedal Codes

1.0
closed
Rolf
None
2016-07-24
2016-07-10
No

I'm using the Microdia foot pedal, and installed the package with gdebi on my Linux Mint 17.3 machine, no problem. However, assignments I'm making for the pedals via Define Pedal Sets aren't doing anything. When I try to verify or set up the pedal using Define Foot Pedal Codes, it crashes. In fact, as soon as I click on one of the boxes (labeled Left Pedal, etc), the program freezes, I can't even x out. Eventually, an error notice comes up, "FootController is not responding. You may choose to wait a short while for it to continue or force the application to quit entirely." Waiting does nothing, so I have to Force Quit.

Please help. Thanks!

Related

Tickets: #3

Discussion

  • Rolf

    Rolf - 2016-07-11
    1. Define foot pedal codes is a tricky beast, as it is only listening to the device that you have nominated as your pedal (/dev/input/event3 for example), so once you have clicked into the 'Left Pedal' box you must only press the foot pedals. Any mouse clicking or keyboard entry just messes up, as the program is only reading the pedal device.
    2. evtest (in the documentation)
      If you don't currently have the 'evtest' package installed, install it and then run:
      sudo evtest
      on the command line.
      It will allow you to identify the /dev/input/event(x) which belongs to your pedal.
      Select the correct option:
      Once the initial flurry of output is done, start pressing the pedals and see what codes are being transmitted by your pedal.
      Also check that you have the correct /dev/input/event(n) set in the HID device in footcontroller Tools->Configure.
      Let me know, how you get on.
      N.B. the documentation is reasonably exhaustive with respect to defining the foot pedal and issues you may come across.
     

    Last edit: Rolf 2016-07-11
    • james israel

      james israel - 2016-07-14

      Okay, was able to do it using the remapping instructions and creating the
      .hwdb file.

      I would like to set one of the pedals to Page Down, but I'm not sure
      exactly how to type that. Using your list under "Keymap List when
      re-mapping keys for a foot pedal", it says you can use 'pagedown', but when
      I try that (using 'key' as the type), I get an error message saying, "No
      such keyname, ignoring it."

      How can I find out what signifies 'page down' and other keys?

      Thanks for your help.

      James

      On Mon, Jul 11, 2016 at 2:26 AM, Rolf rolfofsaxony@users.sf.net wrote:

      1. Define foot pedal codes is a tricky beast, as it is only listening
        to the device that you have nominated as your pedal (/dev/input/event3 for
        example), so once you have clicked into the 'Left Pedal' box you must only
        press the foot pedals. Any mouse clicking or keyboard entry just messes up,
        as the program is only reading the pedal device.
      2. evtest (in the documentation)
        If you don't currently have the 'evtest' package installed, install it
        and then run:
        sudo evtest
        on the command line.
        It will allow you to identify the /dev/input/event(x) which belongs to
        your pedal.
        Select the correct option:
        Once the initial flurry of output is done, start pressing the pedals
        and see what codes are being transmitted by your pedal.
        Also check that you have the correct /dev/input/event(n) set in the
        HID device in footcontroller Tools->Configure.
        Let me now, how you get on.
        N.B. the documentation is reasonably exhaustive with respect to
        defining the foot pedal and issues you may come across.

      Status: open
      Milestone: 1.0
      Created: Sun Jul 10, 2016 08:37 PM UTC by james israel
      Last Updated: Sun Jul 10, 2016 08:37 PM UTC
      Owner: nobody

      I'm using the Microdia foot pedal, and installed the package with gdebi on
      my Linux Mint 17.3 machine, no problem. However, assignments I'm making for
      the pedals via Define Pedal Sets aren't doing anything. When I try to
      verify or set up the pedal using Define Foot Pedal Codes, it crashes. In
      fact, as soon as I click on one of the boxes (labeled Left Pedal, etc), the
      program freezes, I can't even x out. Eventually, an error notice comes up,
      "FootController is not responding. You may choose to wait a short while for
      it to continue or force the application to quit entirely." Waiting does
      nothing, so I have to Force Quit.

      Please help. Thanks!

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/footcontroller/tickets/3/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Tickets: #3

      • james israel

        james israel - 2016-07-14

        Okay, I found it under 'Key names available in X11', it should be entered
        as 'Page_Down' ...

        Thanks again.

        James

        On Thu, Jul 14, 2016 at 2:51 PM, Jammin' James jamminjames1@gmail.com
        wrote:

        Okay, was able to do it using the remapping instructions and creating the
        .hwdb file.

        I would like to set one of the pedals to Page Down, but I'm not sure
        exactly how to type that. Using your list under "Keymap List when
        re-mapping keys for a foot pedal", it says you can use 'pagedown', but when
        I try that (using 'key' as the type), I get an error message saying, "No
        such keyname, ignoring it."

        How can I find out what signifies 'page down' and other keys?

        Thanks for your help.

        James

        On Mon, Jul 11, 2016 at 2:26 AM, Rolf rolfofsaxony@users.sf.net wrote:

        1. Define foot pedal codes is a tricky beast, as it is only listening
          to the device that you have nominated as your pedal (/dev/input/event3 for
          example), so once you have clicked into the 'Left Pedal' box you must only
          press the foot pedals. Any mouse clicking or keyboard entry just messes up,
          as the program is only reading the pedal device.
        2. evtest (in the documentation)
          If you don't currently have the 'evtest' package installed, install
          it and then run:
          sudo evtest
          on the command line.
          It will allow you to identify the /dev/input/event(x) which belongs
          to your pedal.
          Select the correct option:
          Once the initial flurry of output is done, start pressing the pedals
          and see what codes are being transmitted by your pedal.
          Also check that you have the correct /dev/input/event(n) set in the
          HID device in footcontroller Tools->Configure.
          Let me now, how you get on.
          N.B. the documentation is reasonably exhaustive with respect to
          defining the foot pedal and issues you may come across.

        Status: open
        Milestone: 1.0
        Created: Sun Jul 10, 2016 08:37 PM UTC by james israel
        Last Updated: Sun Jul 10, 2016 08:37 PM UTC
        Owner: nobody

        I'm using the Microdia foot pedal, and installed the package with gdebi
        on my Linux Mint 17.3 machine, no problem. However, assignments I'm making
        for the pedals via Define Pedal Sets aren't doing anything. When I try to
        verify or set up the pedal using Define Foot Pedal Codes, it crashes. In
        fact, as soon as I click on one of the boxes (labeled Left Pedal, etc), the
        program freezes, I can't even x out. Eventually, an error notice comes up,
        "FootController is not responding. You may choose to wait a short while for
        it to continue or force the application to quit entirely." Waiting does
        nothing, so I have to Force Quit.

        Please help. Thanks!

        Sent from sourceforge.net because you indicated interest in
        https://sourceforge.net/p/footcontroller/tickets/3/

        To unsubscribe from further messages, please visit
        https://sourceforge.net/auth/subscriptions/

         

        Related

        Tickets: #3

        • Rolf

          Rolf - 2016-07-15

          Hi James
          can I assume that you now have it up and running?
          If that is the case, I can close this ticket and for you the real fun starts, as you attempt to master the intricacies of xdotool.
          A whole new viper's nest! ;)
          I recommend that you start on the command line, which will provide you with error messages galore, until you have what you want and then transfer that into footswitch.

           
  • Rolf

    Rolf - 2016-07-12
    • assigned_to: Rolf
     
  • Rolf

    Rolf - 2016-07-24
    • status: open --> closed
     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.