Give some more details - in what circumstances do you get this error?
Posts by neighbour1
-
-
I usually power to the brake connector (you need to have the plug with cable) and then figure out what motor you have in case of brake. Usually a simple diode bridge and it works like you wanted
It's almost free of charge, because as pdl said brake release unit is a bit expensive.
-
Sometimes I do it, it works without any problems. But mind that there are differences in robot's behaviour according to those signals. If it's not a problem for you, feel free.
Do you have a modular (physical ) I/O? Configure it as the same signal (rack ,slot, start = the same for all of them) and then you save two more ins for other purpose. Sometime I also do it even with Profibus, Profinet, DvNet, etc., because I'm lazy
When needed I also "cross" 4 signals: IMSTP, Hold, SFSPD, Enable - they also could work together.
-
Notepad++, then Roboguide, then real robot.
Notepad++ (or any other text editor) is used to start the project and do the heavy lifting. Scratch, copy, paste, etc. I know Roboguide has an internal (and somewhat hidden) text editor, but I prefer N++ because it is faster.
With the raw program(s) written, is time to upload it to Roboguide and debug. Maybe teach some basic positions, etc.
With these more "mature" programs, is time to upload in the robot itself, touch up the rest of the path and make tests.
But this happens mostly on small projects with single/few robots. Big deployments normally have virtually commissioned OLP programs that in theory are plug and play.
Emphasis on "In theory"...
When using N++ what language coding do you use in order to get the best TP code visibility?
And second issue: which encoding do you use?
-
What is the controller type?/verion? I suppose R-J3iB, you could try to load IMG into Roboguide and then make AOA backup, also readable files (ASCII). Than you can compare things.
-
-
Who and how has changed you the language from Japanese to English?
-
To get the manual you should contact your local Fanuc representative, where you'd bought the robot.
There are two types of grease to this robot:
- Kyodo yushi VIGOGREASE RE0 to J1-J4 reducers,
- SHELL ALVANIA GREASE S2 to bearings.
All the greasing points and procedures are described in the manual.
-
I have no idea whether it was solved or not, but at least some of us uses search engine from the forum
I'd presonally check in Prog Select -> Production checks -> Single step. Look at the attached screens.
Hope this helps.
-
What version of M-410iC you have? I mean the subtype, according to payload: 185kg, 315kg, etc.?
-
Good to know, thanks a lot for help!
-
On which module do you have this "6" - servoamplifier?
If yes, then voltage supplied to the control circuit (+5 V) is too low.
Then manual says:
1. Check the phase voltage of the three phase input power (200 VAC in European version robot) to the servo amplifier. If it is 170VAC or lower, check the line voltage.
2. Replace the servo amplifier.
But mind that it doesn't always tell the truth - you have to serach...
What type of robot is it?
-
We also suspect this. How can we install software?
That's why I asked is it R-J2 or R-J3
In R-J3 it would be easier - from Image backup and using memory card.
In R-J2 it's more complicated. As pdl said: do you have any backups or the original system software?
-
We tried this too, but it didn't work.
If I understood properly you'd dismounted all components from the main CPU board and then placed it into another main CPU board, right? After replacing the main CPU board you've probably lost system software and this could be the problem with it.
-
And... is there anything on the TP scrren or is it blank?
What about TP status LEDs?
-
Is it R-J2 or R-J3 controller?
-
-
Maybe the button is broken? Have you checked it?
-
I've found the exact same thing with my 6.31 robot (and made a thread where some solutions were suggested but none of them fixed the problem for me, here); build buttons are grayed out in RG. I have no problems translating 6.40 karel programs for my other robot though.
Ha! So WinOLPC as I thought at the beginning was your sollution
Thanks a lot for helping hand!
BTW: do you know what happens when I compile my karel prog in RG cell using software 6.40 and then try to load it into the robot with 6.30? Have you also tried this?
-
Also "grey" -> not active