Now that you mention it, maybe I have one of those jobs with 2 LBs.. gonna check right away..
but that doesn't explain why I get "Pendant Disconnection" all the times
Posts by varda
-
-
Update
Tried the same thing on another controller (I have 3 identical DX200 w/MH180), I'm getting the same alarms.... Syntax errors aren't coming up
I create empty robot jobs, transfer them to USB, using NPP I edit and add the code, and then transfer back to the controller.. is there something I'm missing?
-
Hi people, hope anybody can make this clear..
As title says, I'm trying to load .jbi files (standard Robot Jobs) to the controller, so I mark the files I want to load, hit enter, hit yes, and the controller freezes for a couple of seconds, then I get "DX200 pendant disconnected" with the blue background, and hitting "OK" or doing nothing makes it reboot anyway; while it's booting again, I have two red LEDs lit solid near the rotary switch on the YIO21 board, and when boot is completed it outputs 3 alarms:
ALARM 0020 [50] - CPU COMMUNICATION ERROR
ALARM 1865 [105] - M-SAF I/O BOARD COMM ERROR
ALARM 1876 [102] - M-SAF I/O BOARD WATCHDOG ERRORAlarms occur only if I try to load again the same files, turning power off and on again restores the system but I'm stuck here.
Sub code of 1865 says it could be either a failure in YSF21 or YSF22, while sub code of 1876 says "An error in channel 1 of YSF22 board was detected by CPU1 of YSF21 board".I'm waiting for a response regarding the sub codes from Yaskawa, it's weird that transferring .jbi files triggers communication alarms.
I checked all cables and connections mentioned in the alarm list but I have no clue about what's happening.Any suggestion?
-
Hi Fabian,
of course they won't and that's why I'm asking and still waiting, even if this is a password that nobody will be able to use without a working copy of MotoVRC/MotoSim 2015. -
Hell yeah! 46 rocks
Back to important things, correct, in DX200 you MUST be in Yaskawa mode to load .PRM files, but also in MotoSim (tried right now in Management mode in a DX200 virtual cell, only Yaskawa mode will do the trick).
The password I have will work only with a virtual DX200.
From my experience I think I know why Yaskawa Mode has been locked into an hardware key (I think you can pay for one of those, lasts 6 months per licence file), there are sooooooooo many reasons for it and I'm sure you already know why there's no backdoor for a real controller...
About DX200's security, that could be an idea, but it's often better to keep your high card in the deck, usually when you need something that could really help your job, you end up buying if it's impossible or really hard to get for free.I'm still waiting for a "good to go" from any moderator/admin before posting anything, I like this forum and wouldn't like to get banned for a damn string.
-
Hi Too_fast_46,
I hope that 46 stands for Valentino Rossi
I'm not sure I fully understood your question, but from my experience I never had to boot to maintenance (both real/virtual controllers) to access Yaskawa Mode, that can be achieved just entering the Yaskawa code instead of the Maintenance PW (99999999); and yes, there are not so many things to do in maintenance mode in the "Option function" menu, all the other controller features are activated through knowledge of parameters.
The password I'm talking about applies only to Virtual controllers, but to me it's very useful because I can try any optional function just making a phone call to Yaskawa service to get the parameters and that's all.. -
Motouser,
as long as you use the speed override function "as is", you're not allowed to write (manually) a value over 100% (in the small box that comes up in the job window when switching to play/remote); since you cannot vary the speed directly modifying the box while the robot is running in play/remote, but instead you should HOLD or stop for a while, write the new value and press play again, you can manually do this holding down SHIFT and tapping UP or DOWN cursor keys, and that adds or subs 10% each time.
If you're using the speed override function which gets the speed value from the IG#(xx) you set (look at my first answer on this thread), yes, that can go up to 255% and be dead sure that VJ=255% will probabily lead to a servo tracking error or something worse (never tried to push that hard, I have no clue on what exactly a robot would do in this case).
But still, I can't say if speeding just a little (say 105-110%) could help the robot run faster in certain paths or if it's just a bad ideafluke,
give 'em a big hug and your ALL.PRM and they will do the trick hopefully, maybe there's something I'm missing -
Hi asgary64,
as Robodoc said, MotoSim EG-VRC 2015 (now running SP3) has a CAM function you could use for the purpose of generating the routes for shaving the workpiece.For doing this you need to setup your cell with your robot and the 3D model (preferrable an ACIS .SAT file because there's no scaling and it's the native lightest model to import, .STEP files still have problems in parsing/loading, better use .IGES or .SAT); once imported you can "teach" points on the surface you want to polish and use the CAM function to get the path calculated.
You could even use the PAINTING function which uses a "visual path editor" but I never used that, so I have no clue on how to set that thing up.
And Robodoc is right, if you have some kind of special grinding equipment (pretty sure you do) you will have to build your own piece of software to develop some kind of parametric polishing routines.
-
I'm aware that I shouldn't post Paid-Option-Parameters settings and Yaskawa Mode codes and whatever else; that being said, this Yaskawa developer password applies only to the virtual controllers in MotoSim/MotoVRC, and doesn't in any case let users acces to the magic-blue "Y mark" on the status bar (sadly, I tried by myself one nanosecond after getting this info, so no bothering with "does this work on real controllers dude?").
Enabling Yaskawa Mode on a virtual controller on first hand unlocks those protected parameters such as FD or S1D and so on...
But, again, there's a checksum generated with a Yaskawa algorithm on bottom of every protected parameter file, there's no way of doing thisIf someone needs the code or wants to try it, I just want to make sure the Moderators are ok with me posting this.
-
Hi Fabian, thank you
well, sometimes I even feel free to use SEARCH, open all results and CTRL+F any word I'm looking for
BTW awesome forum, keep it up guys
-
Hi everybody, I've been around this forum for more than one year before posting something.. for any question I had it was pretty easy to find an answer here because at least someone else had the same issues
Back to the topic, hi fluke, on DX200 the parameters should be
-S2C701=1 enables the speed override function
-S2C702=1 takes the speed softkey value in teach mode and stores it as the speed override value when switching to play or remote mode (L=1%, M=2%, H=10%)
-S2C709=1 this takes the previously set value (SO set to 50%, switch to teach and back again to play/remote, value remains 50%)Instead if you want to specify the value using an input group IG#(xx) you must set S4C287=[IG number you plan to use]
and be sure you set to 0 from S4C288 to S4C295.
Be very careful with this setting because on a DX100 I've been able to go over 100%, because filling with ones an IG#(xx) is 255%, and it's not a great idea as smurril73 already mentionedWell, the parameters are the same as on DX100, but if you can't find a solution I suggest you to send the ALL.PRM file to your local Yaskawa representative and they will unlock the function, or at least they will check if there's something else to setup.
Cheers