Think you also should plug in TB1, the upper left connector. There is included the power supply for the logic.
Posts by hermann
-
-
You absolutely should have setup the tcp (user tool in Fanuc speach) at the tip of the grinder. Otherwise you won't get any good result.
-
It seems that you didn't describe the problem exact enough.
It's normal that the motors are going off when you switch to manual mode.
Any messages on the TP?
-
This highly depends on the actual path.
If you decrease all values of $acc_axis[] and one of the axis has only a very small way to move, then the complete movement is affected very much.
If you need the exact stop at position B I don't see a different possibility to make the movement smoother. If the motion will continue to position C use approximation parameter like c_dis or c_vel.
-
... 0.1 resolution in space range 4x3х2м. ...
0.1m or 0.1 mm?
For the mm: think you will not find a sensor with resolution of 0.1mm for a range of 2m (at least not for low cost).
So will have to make small partial scans and 'glue' them together.
-
... But if an operator stops the production line when the robot program runs between line 4 and 10 sometimes we receive the error. . .
So the fault only occurs when the robot is stopped?
How does the operator stop the line? Or how is the robot stopped, by which signal?
-
.. Also is it possible to change the operating mode of the robot from the PLC. . .
No.
The other question I don't understand complete. What's the exact circumstances when you get the message?
-
In sum with your other post https://www.robot-forum.com/robotforum/use…8980-music-man/ you should search for an integrator company with knowledge in paint applications.
Think your questions/problems can't be solved on this forum.
-
When you setup a tcp with 4 point method, how big is the mean error in the tcp calculation screen?
Robot model?
Controller model?
What is the text to error 50050?
-
Full ack to panic_mode and Skyefire.
And:
- Don't use the INI Fold in ISR.
- use Brake command in ISR, to stop actual movement of the robot.
- in ISR disable corresponding Interrupt.
-.... ..
-
The error shows that the interrupt is triggered. The problem is not the declaration of the interrupt, but the code in the interrupt routine.
So show the interrupt routines. But please no screenshots, send the code as attachment or copy paste him into the thread
-
Is it really possible that the parts are machined with a hand grinder after casting?
Yes.
-
.. the robot can go to a position with axis 4 flipped over 180 degrees from the thought position which caused the position to be out by approx. 20mm. .
If this happens the calibration of the robot or tool definition is wrong. Flipping axis 4,5,6 shouldn't cause an an error of 20mm.
Easiest way to check calibration is to setup a tcp (sharp tool tip) with standard 4 position method. The mean error shouldn't be more than 0.5 mm.
-
First thing I would do is:
Write in a program with the line
ptp_rel {E1 1000}
Then measure the distance of the movement. Making shure the distance is 1000mm.
If it is not 1000mm, adjust $rat_mot_ax[7].
-
Common problem, the robot shows in the i/O status screen 0/1 where 0 is FALSE and 1 is TRUE.
That leads to confusion.
-
For upload, download I can remember an option NFS client for the robots. If they have that option and a network card you can setup a NFS server on your laptop, and load programs over this NFS connection. But setting up the NFS server isn't that easy.
For s4c+, may be a ftp server on the robot was standard.
-
You should change R,W,P for one of the two tools.
You shouldn't use external links for pictures, use upload function of the forum.
-
Use correct project for the actual controller, don't use projects from different controller.
-
Orange is the new white 😁
-
Why?
Do you send packets through the internet to the robot? (Then use VPN).
Do you have secret messages to send?
Do you fear agents in your factory?