AR logo.png

ANNIN ROBOTICS

0
  • HOME

  • TUTORIALS

  • DOWNLOADS

  • THIRD-PARTY SOFTWARE

  • ROBOT KITS

  • FORUM

  • BLOG

  • CONTACT

  • More

    Use tab to navigate through the menu items.
    To see this working, head to your live site.
    • Categories
    • All Posts
    • My Posts
    Sert Engineering
    Mar 05, 2021

    (PermissionError(13, 'The device does not recognize the command.', None, 22))

    in Questions

    - I successfully installed teensy and Arduino sketches.

    - Connection established and I see yellow sign on ARCS software


    Problem: Every time w

    hen I try to jog axis' I get collision error or out of calibration for all axis' and I read permission error on that black screen (see attached photos)


    Can I anyone take a look this please?


    Thank you

    Sert




    5 answers0 replies
    0
    1
    Sert Engineering
    Mar 05, 2021

    UPDATE: I disabled encoders and axis' started moving. But this time when I jog J4, J1 moves :) I know it s bad wiring. I believe switching connection cables would solve this issue without rewiring.

    1
    Chris Annin
    Mar 07, 2021

    thank you for the update on the J1 and J4 wiring issues. let me know what you find after getting J1 and J4 resolved. I believe the encoder or collision error will be resolved when J1 and J4 are looking at the correct encoders.

    1
    Kstan Simit
    Mar 15, 2021

    Sert, you may tweak abit at Teensy-to-stepper driver there if you sure the enclosure-to-robot arm J1-J6 cable is correct.

    1
    xtblue
    Apr 27, 2021

    Check your 5v going to the limit switches, I had mine reversed and every axis gave me the fault when trying to jog. It will also cause homing to fail on all axis if you have it reversed.

    1
    annonuser2
    May 22, 2021

    If you haven't found a solution to your permission error, please take a look at the link below. I had the same com port permission error and was able to resolve it.

    https://www.anninrobotics.com/forum/questions/ar2-software-troubleshooting-com-port-permission-error

    5 comments