Posts by KyleW

    Set the system variable $RMT_MASTER to 0.

    I originally set the system config to remote but that didn't help after changing that to 0 it worked. Don't know why the remote setting in the config didn't fix it? Either way. Thanks a bunch!!

    I do not have that setting.

    Edit: Added the setting. I can toggle the RSR1 bit now. Getting SYST-007 fault currently. Will update when I get it fixed.

    Have others had the issue of running PNS programs in roboguide? I have the UOP Signals mapped to flags, the config set for pns/remote, and a bg logic program turning the signals on at the rights times but for some reason the PNS1 signal for the life of me won't turn on, same with PNS Strobe. They are the only signals mapped in the controller so not double mapped and even when i stop the bg program i can't manually turn the signals on either.

    Any thoughts?

    HawkME I saw you had commented on a different post that it should work, but not sure what I'm missing.


    I tried mapping the UI signals to DO and it's same thing. Seems the UI are the driving signals even though they're inputs, not being driven by the DO. This seems like a roboguide bug?

    I spoke with Fanuc, for verifying a core media they said:

    "One of the files that make up the core software is, apverify.bat. Run this as administrator. It will open and run in a Windows CMD screen, and it will verify each file in the core. If it's successful the window will close, but if it finds an error the CMD window will remain open with a message."

    Fanuc Technical Support

    Did you fill out a PAC request form? All the information they need is on there and I'm surprised if you haven't turned in one already.

    We got the robot from an integrator, they ordered the original pac code and they ordered it incorrectly. I sent Fanuc a picture of the version screen so they could send us the correct pac code and it authorized so I know its right but it wouldn't install. Now that I'm going through the core (that was also given to us from the integrator) I don't think it's actually a core media at all...

    I may have high standards for speed. I've been talking with them for about a week now regarding the whole situation. I told them on friday that I was unable to load the option and was hoping they would transfer me to technical support (because I was talking with spare parts to get the PAC code) but only this morning I received the email that they will be sending me to technical support. So I may get an answer later today but I originally told them about the issue friday.

    Hello all,

    I have a PAC code from fanuc and it authorizes, but won't install. I reached out to them and they asked me to check the version of the core media that I have. But I don't know how to do that.

    To fix this option not loading, I was thinking I need to do a software update. Is that correct? Fanuc is just too slow to answer me. Hoping someone here can verify my suspicions.


    <!-- Block Access to Skipping Lines of Code -->

    <PWD level="0" const="24" access="0"/>

    <PWD level="2" const="24" access="1"/>

    <PWD level="3" const="24" access="0"/>

    <PWD level="4" const="24" access="0"/>

    Does anyone have a description for each const? There are 24 total, and I only know what 20 and 24 do now.

    Hope this helps whoever else.


    I'm not sure exactly which one, I will figure it out and then update this post but I just added and disabled all of the constants to the password file. One of them disables being able to answer the "start from different line prompt"

    <PWD level="4" const="1" access="0"/>

    There are const 1-24, I disabled access to all of them for level 4.

    Does anyone have a description for each const? Otherwise I'll only be able to figure out which one affects this line skip prompt.

    How are you starting the robot? If you are using UOP, then simply don't provide the operators with a resume button. If they turn the teach pendant on and off then you can force them to start the program over from the beginning.

    It's a weird UOP/SOP combo. It's UOP signals controlled through flags so it can auto start after fence open/faults but if you press the sop start it will also pulse the start signal. But I don't want it to restart at the beginning because it's in the middle of loading a furnace and waiting for the signal drop the ingot, but they skip it and it loads the furnace anyway.

    It pops up with a prompt but they are intentionally skipping the line so they say yes. Currently I'm trying to figure out if I can disable the FWD/BWD buttons in the password xml file. I know it's a setting in the function menu but it would be nice to just have it tied to our logins instead.

    Anyone know the key Id for the FWD/BWD buttons? And/or where to find Key IDs in either the manual or variables? I have had no luck so far


    We have operators and others that have found if the robot is waiting for a signal that if they turn the TP on and go down a line, and turn the TP off and start the robot it starts from this new line. What options do I have for stopping this? We have passwords. Is there a system variable or something I'm misisng?


    I understand where you're coming from, I'm just trying to make a level for my automation team that has access to absolutely everything without giving the ability to disable passwords. Not that they would disable them but if someone got a hold of their login. Want to keep the install password off the floor for peaking eyes.


    I have added passwords to all of my robots and it's all working great, but I found that I can still simulate I/O even at the lowest level (but not when logged out). Does anyone know a line in XML that I can add to lock out this sim function?


    Is this a single pass or multiple? Are you conventional milling or climb? Conventional is recommended if you lack rigidity.

    It's a 3mm thickness part, doing multiple pass of .6mm each. After getting all the way through I do a final clean up cut that takes .4mm off of each side. And doing conventional milling

    Interesting enough I just milled the mirror image part and both the vertical and the angle piece came out really clean.

    The 3rd one is the bumpy one, you may be able to see in image, all others are a clean cut edge.

    HawkME, If I have an opportunity to move the fixture I will, and definitely plan to get the 2 flute bit.

    Haha, yeah I know this is very not ideal. I'm working with a lot of spare parts trying to do the best I can. :winking_face_with_tongue:
    I got a 1/4" carbide 4 flute bit (extends about 3/4" past collar), 25,000rpm air spindle (self regulating so i cant adjust its RPM), moving at 8mm/s. The fixture is about 7ft away from the robot so not max reach but not very close.

    I'm about to get a 2 flute 1/4" carbide bit though.

Advertising from our partners