1. Home
    1. Dashboard
    2. Search
  2. Forum
    1. Unresolved Threads
    2. Members
      1. Recent Activities
      2. Users Online
      3. Team Members
      4. Search Members
      5. Trophys
  3. Articles
  4. Blog
  5. Videos
  6. Jobs
  7. Shop
    1. Orders
  • Login or register
  • Search
This Thread
  • Everywhere
  • This Thread
  • This Forum
  • Articles
  • Pages
  • Forum
  • Blog Articles
  • Products
  • More Options
  1. Robotforum - Support and discussion community for industrial robots and cobots
  2. Forum
  3. Industrial Robot Support and Discussion Center
  4. Fanuc Robot Forum
Your browser does not support videos RoboDK Software for simulation and programming
Visit our Mainsponsor
IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Sponsored Ads

Setting Up a Password System (with USB Keys)

  • Robo_Eng_13
  • July 6, 2018 at 7:06 PM
  • Thread is Resolved
  • Robo_Eng_13
    Reactions Received
    26
    Trophies
    4
    Posts
    432
    • July 6, 2018 at 7:06 PM
    • #1

    I have been collecting information from the forum, manuals, Fanuc Tech Support, and my own experimentation for about a year now, and i am now working on a document for setting up the Fanuc Password System from scratch with my lessons learned.

    Some things not yet addressed in the document.

    1. the UT1 port requires a special option J957 USB port on iPendant

    2. the UT1 port has some issues on different versions of the software. I had my first success with V8.30P/20, failed with V8.30P/13 and V8.30P/36, was told to upgrade to V8.30P/39, actually upgraded to V8.30P/40, and succeeded with that version.

    3. If you make a change to the password level config XML and reload it, the keys will no longer work and need to be re-flashed. Make sure you have your levels setup how you want them before rolling out.

    4. You must know the DCS password of the original robot and the new robot when transferring the syspass.sv file.

    5. Tip. I randomly generated my passwords, and realized halfway through the i was using both capitol i and lowercase L interchangeably, due to the font i had printed my notes in. I suggest just axing these two characters entirely. I had less issues with O and 0, but may not want those either.

    6. You CAN do the majority of the password setup in the background on a machine that is running production, which is very handy!

    7. I always take an image and AOA backup of every robot before i do anything to it, just in case something goes majorly wrong.

    8. There are emergency instructions in the HandlingTool manual for recovering if the Install User's information is lost, so your machine is not permanently bricked if someone runs off with that.

    9. It seems like larger capacity flash drives, and non FAT formatting will work at UD1, but not UT1.

    10. It seems like UT1 gets overwhelmed or something after a number of logins, and will become non-responsive to new plug ins. Cycling power corrects this. I have had no such issue on UD1.

    Files

    Password Setup Doc.pdf 746.8 kB – 232 Downloads
  • Online
    leos037
    Trophies
    3
    Posts
    7
    • August 13, 2018 at 12:54 AM
    • #2
    Quote from Robo_Eng_13


    I have been collecting information from the forum, manuals, Fanuc Tech Support, and my own experimentation for about a year now, and i am now working on a document for setting up the Fanuc Password System from scratch with my lessons learned.

    Some things not yet addressed in the document.

    1. the UT1 port requires a special option J957 USB port on iPendant

    2. the UT1 port has some issues on different versions of the software. I had my first success with V8.30P/20, failed with V8.30P/13 and V8.30P/36, was told to upgrade to V8.30P/39, actually upgraded to V8.30P/40, and succeeded with that version.

    3. If you make a change to the password level config XML and reload it, the keys will no longer work and need to be re-flashed. Make sure you have your levels setup how you want them before rolling out.

    4. You must know the DCS password of the original robot and the new robot when transferring the syspass.sv file.

    5. Tip. I randomly generated my passwords, and realized halfway through the i was using both capitol i and lowercase L interchangeably, due to the font i had printed my notes in. I suggest just axing these two characters entirely. I had less issues with O and 0, but may not want those either.

    6. You CAN do the majority of the password setup in the background on a machine that is running production, which is very handy!

    7. I always take an image and AOA backup of every robot before i do anything to it, just in case something goes majorly wrong.

    8. There are emergency instructions in the HandlingTool manual for recovering if the Install User's information is lost, so your machine is not permanently bricked if someone runs off with that.

    9. It seems like larger capacity flash drives, and non FAT formatting will work at UD1, but not UT1.

    10. It seems like UT1 gets overwhelmed or something after a number of logins, and will become non-responsive to new plug ins. Cycling power corrects this. I have had no such issue on UD1.

    Display More

    Im workin in a version8.3 of spot tool with a 16gb flash drive in the ut1, and i did'n have problem....sorry for my bad english.

    Enviado desde mi SM-G530H mediante Tapatalk

    Edited once, last by leos037 (August 13, 2018 at 12:56 AM).

  • JW_Basco
    Posts
    2
    • September 10, 2024 at 3:16 PM
    • #3
    Quote from Robo_Eng_13

    I have been collecting information from the forum, manuals, Fanuc Tech Support, and my own experimentation for about a year now, and i am now working on a document for setting up the Fanuc Password System from scratch with my lessons learned.

    Some things not yet addressed in the document.

    1. the UT1 port requires a special option J957 USB port on iPendant

    2. the UT1 port has some issues on different versions of the software. I had my first success with V8.30P/20, failed with V8.30P/13 and V8.30P/36, was told to upgrade to V8.30P/39, actually upgraded to V8.30P/40, and succeeded with that version.

    3. If you make a change to the password level config XML and reload it, the keys will no longer work and need to be re-flashed. Make sure you have your levels setup how you want them before rolling out.

    4. You must know the DCS password of the original robot and the new robot when transferring the syspass.sv file.

    5. Tip. I randomly generated my passwords, and realized halfway through the i was using both capitol i and lowercase L interchangeably, due to the font i had printed my notes in. I suggest just axing these two characters entirely. I had less issues with O and 0, but may not want those either.

    6. You CAN do the majority of the password setup in the background on a machine that is running production, which is very handy!

    7. I always take an image and AOA backup of every robot before i do anything to it, just in case something goes majorly wrong.

    8. There are emergency instructions in the HandlingTool manual for recovering if the Install User's information is lost, so your machine is not permanently bricked if someone runs off with that.

    9. It seems like larger capacity flash drives, and non FAT formatting will work at UD1, but not UT1.

    10. It seems like UT1 gets overwhelmed or something after a number of logins, and will become non-responsive to new plug ins. Cycling power corrects this. I have had no such issue on UD1.

    Display More

    Hello,

    Where are the appendices (A & B) that you reference in your PDF? Thanks

  • Robo_Eng_13
    Reactions Received
    26
    Trophies
    4
    Posts
    432
    • September 24, 2024 at 7:35 PM
    • #4
    Quote from JW_Basco

    Hello,

    Where are the appendices (A & B) that you reference in your PDF? Thanks

    After doing some digging in old files, attached is what i had put together on Screen IDs (Appendix A), but i never assembled anything more complete than what is available in the manual (MAROBHT8304141E REV C Section 5 Table 5-39 "Features".

    Files

    Appendix A.xlsx 22.72 kB – 22 Downloads
  • Zardlin
    Reactions Received
    1
    Posts
    18
    • December 17, 2024 at 1:33 PM
    • #5

    Robo_Eng_13 I've been looking through your old posts concerning password setup and all, do you happen to be remember what the major differences between all your levels were? I've pretty much figured out the xml portion, I'm just stuck on brainstorming how I want to set up my levels to use the granularity afforded at its fullest.
    Thanks in advance

  • warhound96
    Reactions Received
    2
    Posts
    44
    • December 18, 2024 at 12:30 PM
    • #6

    i would like to add one more question here. I followed your examples and did all these but i have another problem. If i set the type=0, even though "Select" is with full access and RW i can't find it in the menu and if i press the physical button i have access to the program but i cant get access to creating a program, i'll also upload my .xml file


    <?xml version="1.0"?>


    <PASSWORD>

    <!-- Define Level Names -->
    <LEVEL level="0" name="OPERATOR" />
    <!--LEVEL level="8" name="INSTALL" /-->

    <!-- Define Menu Type. Full=0, Quick=1 -->
    <DEFMENU level="0" type="0" />
    <!--DEFMENU level="8" type="0" /-->

    <!-- Define Default Screen For Log In -->
    <DEFSCREEN level="0" sp_id="18" scrn_id="1" />
    <!--DEFSCREEN level="8" sp_id="18" scrn_id="1" /-->

    <SCREEN level="0" sp_id="1631" scrn_id="1" access="0"/> <!--UTILITIES_Home-->
    <SCREEN level="0" sp_id="153" scrn_id="1" access="0"/> <!--UTILITIES_Hints-->
    <SCREEN level="0" sp_id="1463" scrn_id="1" access="0"/> <!--UTILITIES_iRCalibration-->
    <SCREEN level="0" sp_id="1196" scrn_id="4" access="0"/> <!--UTILITIES_Robot Condition-->
    <SCREEN level="0" sp_id="930" scrn_id="1" access="0"/> <!--UTILITIES_Prog adjust-->
    <SCREEN level="0" sp_id="151" scrn_id="1" access="0"/> <!--UTILITIES_Program Shift-->
    <SCREEN level="0" sp_id="150" scrn_id="1" access="0"/> <!--UTILITIES_Mirror Image Shif-->
    <SCREEN level="0" sp_id="155" scrn_id="1" access="0"/> <!--UTILITIES_Tool Offset-->
    <SCREEN level="0" sp_id="191" scrn_id="1" access="0"/> <!--UTILITIES_Frame Offset-->
    <SCREEN level="0" sp_id="254" scrn_id="1" access="0"/> <!--UTILITIES_Angle Entry Shift-->
    <SCREEN level="0" sp_id="1200" scrn_id="1" access="0"/> <!--UTILITIES_Group Exch-->
    <SCREEN level="0" sp_id="95" scrn_id="11" access="0"/> <!--TEST CYCLE_Arc weld-->
    <SCREEN level="0" sp_id="955" scrn_id="1" access="0"/> <!--I/O_Cell Interface-->
    <SCREEN level="0" sp_id="95" scrn_id="17" access="0"/> <!--I/O_Weld Ext DO-->
    <SCREEN level="0" sp_id="992" scrn_id="1" access="0"/> <!--I/O_Custom-->
    <SCREEN level="0" sp_id="97" scrn_id="1" access="0"/> <!--I/O_Analog-->
    <SCREEN level="0" sp_id="99" scrn_id="1" access="0"/> <!--I/O_Group-->
    <SCREEN level="0" sp_id="108" scrn_id="1" access="0"/> <!--I/O_UOP-->
    <SCREEN level="0" sp_id="157" scrn_id="1" access="0"/> <!--I/O_Interconnect-->
    <SCREEN level="0" sp_id="299" scrn_id="1" access="0"/> <!--I/O_Link Device-->
    <SCREEN level="0" sp_id="1111" scrn_id="1" access="0"/> <!--I/O_Flag-->
    <SCREEN level="0" sp_id="1062" scrn_id="1" access="0"/> <!--I/O_Ethernet/IP-->
    <SCREEN level="0" sp_id="166" scrn_id="1" access="0"/> <!--SETUP_Prog select-->
    <SCREEN level="0" sp_id="1383" scrn_id="4" access="0"/> <!--SETUP_Proccess Monitor-->
    <SCREEN level="0" sp_id="1985" scrn_id="1" access="0"/> <!--SETUP_ZDT Client-->
    <SCREEN level="0" sp_id="68" scrn_id="1" access="1" rw_access="1"/> <!--SETUP_General-->
    <SCREEN level="0" sp_id="1087" scrn_id="1" access="0"/> <!--SETUP_Coll Guard-->
    <SCREEN level="0" sp_id="154" scrn_id="1" access="0"/> <!--SETUP_Frames-->
    <SCREEN level="0" sp_id="140" scrn_id="1" access="0"/> <!--SETUP_Macro-->
    <SCREEN level="0" sp_id="147" scrn_id="1" access="0"/> <!--SETUP_Ref Position-->
    <SCREEN level="0" sp_id="163" scrn_id="1" access="0"/> <!--SETUP_Port Init-->
    <SCREEN level="0" sp_id="181" scrn_id="1" access="0"/> <!--SETUP_Ovrd Select-->
    <SCREEN level="0" sp_id="31" scrn_id="1" access="0"/> <!--SETUP_User Alarm-->
    <SCREEN level="0" sp_id="456" scrn_id="1" access="0"/> <!--SETUP_Error Table-->
    <SCREEN level="0" sp_id="1304" scrn_id="1" access="0"/> <!--SETUP_iPendant Setup-->
    <SCREEN level="0" sp_id="1111" scrn_id="6" access="0"/> <!--SETUP_BG Logic-->
    <SCREEN level="0" sp_id="1337" scrn_id="1" access="0"/> <!--SETUP_Resume Offset-->
    <SCREEN level="0" sp_id="420" scrn_id="1" access="0"/> <!--SETUP_Resume Tol-->
    <SCREEN level="0" sp_id="197" scrn_id="1" access="0"/> <!--SETUP_Stroke Limit-->
    <SCREEN level="0" sp_id="200" scrn_id="1" access="0"/> <!--SETUP_Space Fnct.-->
    <SCREEN level="0" sp_id="1163" scrn_id="1" access="0"/> <!--SETUP_Diag Interface-->
    <SCREEN level="0" sp_id="195" scrn_id="1" access="0"/> <!--SETUP_Host Comm-->
    <SCREEN level="0" sp_id="1216" scrn_id="1" access="0"/> <!--SETUP_ZDT EOAT Setup-->
    <SCREEN level="0" sp_id="935" scrn_id="1" access="0"/> <!--SETUP_Passwords-->
    <SCREEN level="0" sp_id="1296" scrn_id="1" access="0"/> <!--SETUP_EtherCAT-->
    <SCREEN level="0" sp_id="74" scrn_id="1" access="0"/> <!--FILE_File-->
    <SCREEN level="0" sp_id="253" scrn_id="1" access="0"/> <!--FILE_File Memory-->
    <SCREEN level="0" sp_id="1008" scrn_id="1" access="0"/> <!--FILE_Auto Backup-->
    <SCREEN level="0" sp_id="37" scrn_id="1" access="0"/> <!--USER-->
    <SCREEN level="0" sp_id="71" scrn_id="1" access="1" rw_access="1"/> <!--SELECT-->
    <SCREEN level="0" sp_id="148" scrn_id="2" access="0"/> <!--DATA_Position Reg-->
    <SCREEN level="0" sp_id="1471" scrn_id="3" access="0"/> <!--DATA_String Reg-->
    <SCREEN level="0" sp_id="34" scrn_id="2" access="0"/> <!--DATA_KAREL Vars-->
    <SCREEN level="0" sp_id="34" scrn_id="3" access="0"/> <!--DATA_KAREl Posns-->
    <SCREEN level="0" sp_id="1383" scrn_id="1" access="0"/> <!--STATUS_Proccess report-->
    <SCREEN level="0" sp_id="1383" scrn_id="2" access="0"/> <!--STATUS_Proccess Data-->
    <SCREEN level="0" sp_id="32" scrn_id="2" access="0"/> <!--STATUS_Axis-->
    <SCREEN level="0" sp_id="70" scrn_id="1" access="0"/> <!--STATUS_Version ID-->
    <SCREEN level="0" sp_id="1613" scrn_id="3" access="0"/> <!--STATUS_Production St-->
    <SCREEN level="0" sp_id="226" scrn_id="1" access="0"/> <!--STATUS_Exec-Hist-->
    <SCREEN level="0" sp_id="1196" scrn_id="2" access="0"/> <!--STATUS_Motion Profilier-->
    <SCREEN level="0" sp_id="1196" scrn_id="3" access="0"/> <!--STATUS_Robot Condition-->
    <SCREEN level="0" sp_id="1196" scrn_id="5" access="0"/> <!--STATUS_Servo off History-->
    <SCREEN level="0" sp_id="152" scrn_id="1" access="0"/> <!--STATUS_Prg Timer-->
    <SCREEN level="0" sp_id="152" scrn_id="2" access="0"/> <!--STATUS_Sys Timer-->
    <SCREEN level="0" sp_id="296" scrn_id="1" access="0"/> <!--STATUS_Condition-->
    <SCREEN level="0" sp_id="1827" scrn_id="1" access="0"/> <!--STATUS_Reminder-->
    <SCREEN level="0" sp_id="1711" scrn_id="1" access="0"/> <!--STATUS_Power Consuamption-->
    <SCREEN level="0" sp_id="1296" scrn_id="2" access="0"/> <!--STATUS_EtherCAT-->
    <SCREEN level="0" sp_id="1621" scrn_id="1" access="0"/> <!--STATUS_Notifications-->
    <SCREEN level="0" sp_id="1826" scrn_id="1" access="0"/> <!--STATUS_Customer Register-->
    <SCREEN level="0" sp_id="34" scrn_id="1" access="0"/> <!--SYSTEM_Variables-->
    <SCREEN level="0" sp_id="66" scrn_id="1" access="0"/> <!--SYSTEM_OT Release-->
    <SCREEN level="0" sp_id="162" scrn_id="1" access="0"/> <!--SYSTEM_Axis Limits-->
    <SCREEN level="0" sp_id="34" scrn_id="6" access="0"/> <!--SYSTEM_Config-->
    <SCREEN level="0" sp_id="290" scrn_id="1" access="0"/> <!--SYSTEM_Motion-->
    <SCREEN level="0" sp_id="1133" scrn_id="1" access="0"/> <!--SYSTEM_DCS-->
    <SCREEN level="0" sp_id="190" scrn_id="1" access="0"/> <!--USER2-->

    <!-- Global key -->

    <!-- PREV --> <GLABEL level="0" name="PREV" access="1"/>
    <!-- NEXT --> <GLABEL level="0" name="NEXT" access="1"/>
    <!-- EDIT --> <GLABEL level="0" name="EDIT" access="1"/>
    <!-- DETAIL --> <GLABEL level="0" name="DETAIL" access="1"/>
    <!-- TYPE --> <GLABEL level="0" name="[ TYPE ]" access="1"/>
    <!-- ALL --> <GLABEL level="0" name="ALL" access="1"/>
    <!-- OVERWRITE --> <GLABEL level="0" name="OVERWRITE" access="1"/>
    <!-- YES --> <GLABEL level="0" name="YES" access="1"/>
    <!-- NO --> <GLABEL level="0" name="NO" access="1"/>
    <!-- EXIT --> <GLABEL level="0" name="EXIT" access="1"/>


    <!-- Operators can use any of the editing keys on the Edit Screen -->
    <LLABEL level="0" name="TOUCHUP" sp_id="64" scrn_id="1" access="1" /> <!--Touchup in Edit screen for Creating Program-->
    <LLABEL level="0" name="POINT" sp_id="64" scrn_id="1" access="1" /> <!--Point-->
    <LLABEL level="0" name="[EDCMD]" sp_id="64" scrn_id="1" access="1" /> <!--EDCMD-->
    <LLABEL level="0" name="WELD_ST" sp_id="64" scrn_id="1" access="1" /> <!--WELD_ST-->
    <LLABEL level="0" name="WELD_PT" sp_id="64" scrn_id="1" access="1" /> <!--WELD_PT-->
    <LLABEL level="0" name="WELDEND" sp_id="64" scrn_id="1" access="1" /> <!--WELDEND-->

    <!--Based on the Edit screen you have to adjust the names as well to be fully operational-->


    </PASSWORD>

  • Zardlin
    Reactions Received
    1
    Posts
    18
    • December 18, 2024 at 1:45 PM
    • #7

    warhound96 I haven't encountered this issue, have you tried setting another level than level 0 with these settings? Maybe Level 0 has some basic restrictions that stay even after setting up the xml. I'm not 100% sure but my own xml i have no access for level 0-1-2 and even the physical button doesnt get the page to open, while 3 & 4 only have read, they can see the select tab but not go into the programs and the rest act as if no password restrictions applied (as intended).


    I've also noticed you do not have any settings for sp_id 64 screen_id 1 which is the Edit menu and could be behind why operator is unable to create a program.


    That is my guess but I'm new to robotics so take it with a grain of salt

  • warhound96
    Reactions Received
    2
    Posts
    44
    • December 18, 2024 at 1:57 PM
    • #8

    Zardlin i'll try doing that as well. it's just that i don't want him, for the operator to see that there are more options even though he won't be able to click or choose them and interact of course too. When i changed levels the other day, trying from 1 to 4 levels, even though i had everything in "0", meaning no access with the "Program" or "Setup" level etc, the operator had access again and even to change things

  • Zardlin
    Reactions Received
    1
    Posts
    18
    • December 18, 2024 at 3:57 PM
    • #9

    Try this and set it to level 4, this is one of the original tests i did to see what happened when everything is off, youll see on the tp that there isnt much the operator can do and he has to start programs from the HMI. To log back in as INSTALL go to the home page and there should be a blue box where you can enter the INSTALL user
    All you have to do is change the extension to xml.
    Let me know how it goes!

    Files

    password.txt 95.85 kB – 10 Downloads
  • warhound96
    Reactions Received
    2
    Posts
    44
    • December 18, 2024 at 4:03 PM
    • #10

    Zardlin I'll see what i can do, because i already have this file and many more like it! Thanks anyways though for your time!

Advertising from our partners

IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Advertise in Robotics
Advertise in Robotics

Job Postings

  • Anyware Robotics is hiring!

    yzhou377 February 23, 2025 at 4:54 AM
  • How to see your Job Posting (search or recruit) here in Robot-Forum.com

    Werner Hampel November 18, 2021 at 3:44 PM
Your browser does not support videos RoboDK Software for simulation and programming

Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Thread Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000
  1. Privacy Policy
  2. Legal Notice
Powered by WoltLab Suite™
As a registered Member:
* You will see no Google advertising
* You can translate posts into your local language
* You can ask questions or help the community with your knowledge
* You can thank the authors for their help
* You can receive notifications of replies or new topics on request
* We do not sell your data - we promise

JOIN OUR GREAT ROBOTICS COMMUNITY.
Don’t have an account yet? Register yourself now and be a part of our community!
Register Yourself Lost Password
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on Google Play
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on the App Store
Download