Looking for some info on this lathe, good or bad. NON CNC
Thanks for any help,
Smitty
Looking for some info on this lathe, good or bad. NON CNC
Thanks for any help,
Smitty
Typically a very good lathe and trouble free. But anything can be abused.
George
(Note: The opinions expressed in this post are my own and are not necessarily those of CNCzone and its management)
I got a Bpt-Romi full CNC version witch is the PowerPath15 and I just love it, pretty well made and depandable.
Thanks for the info, that is what I was hoping for. With a little time, and money, I will be back among the CNC group.
SMitty
I have used The EZpath II and I own a EZpath S. Both are great machines. I would make sure you get one of the newer ones that have constant surface speed.
I think the Romi Lath are good. I have a few units too. But recently I have a unit which has the X axis belt replace. When the setting is done on the X axis that day it self is good, off the machine then you try to go back to the set position it differs a bit. Anybody could give some tips to help out.
thks
mcwmah
Show me another lathe on the market for tooling that will even compete with an EZ-Path features.
I have had similar repeatability problems about 6 years ago with our EZ-Path. It turned out to be the Z axis encoder failing. Still going strong!
DC
It is possible that the home switch and the marker pulse on the encoder are making at the same time (murphy's law). Loosen the belt and move the motor 180 degrees without moving the ball screw. See if that makes homing a lot more reliable.
George
(Note: The opinions expressed in this post are my own and are not necessarily those of CNCzone and its management)
ROMI EZPATH Z AXIS NOT HOME.
cAN YOU PLEASE SEND ME SOLUTION ON [email protected].
Regards,
ganesh
I am assuming that the Z axis is moving and that this is a first generation EZPATH with the SEM DC motors.
Possibilities: Home switch not working.
Cable to home switch not conducting correctly.
Encoder missing marker pulse used for homing.
Bad AXSBOB board.
Bad BMDC board.
Software issue.
George
(Note: The opinions expressed in this post are my own and are not necessarily those of CNCzone and its management)
Dear Sir,
Thanks for look forward to our issue.
After giving command to home axis, X axis get homed but Z axis moved till over travel even if S2 limit switch
trip. I had check S2 limit switch NO contact its working. Also the cable continuity till CN2 is ok.
My observation is as soon as S2 gets trip A3 (Z axis drive) alarm (red light) light glows up. Even if S2 trips
Z axis reading gets stepping actually there was no physical movement in Z axis.
Home switch working.
Cable to home switch conducting correctly.
Encoder missing marker pulse used for homing.
For above point how can we check the marker pulse is missing?
Is there any checking method for encoder?
Regards,
Ganesh
You can check the output of the encoder with a oscilloscope.
Or you can exchange the X and Z motor and see if the problem follows the motor. This only if it is the 1st generation EZPATH that has identical SEM motors on both X and Z axis.
George
(Note: The opinions expressed in this post are my own and are not necessarily those of CNCzone and its management)
i have exchange X & Z axis motor & homing problem is solved. but i dont
understand the root cause for this problem.
thank for replay sir problem solved
Now i have been face another issue of ROMI Ez path lathe. When we start program it run 2 block of program & stop after that doesent step further.
Please help me out to solve this issue..
You give me too much data!
Any error message?
Run the program in preview and see if there is a programming problem.
Then look if it stops at a feed rate. If so, is the spindle speed correct? It will not feed if the actual spindle RPM is 20 percent or more different from command.
If you are using a "path" (rough, finish, etc) is it ended?
George
(Note: The opinions expressed in this post are my own and are not necessarily those of CNCzone and its management)
Program is as follow
00 TLCHG I1 T01 01
01 SETCSS G1 C160.00 S600
02 AUXFUN M8
03 STARTPATH 1
04 RAPID ABS X28.0000 29.0000
05 LINE ABS X28.0000 20.0000 F0.0100
06 CHAMFER ABS X130.0000 20.0000 P1.0000 F0.0100
07 LINE ABS X130.0000 Z-23.0000 F0.0100
08 LINE ABS X133.0000 Z-23.0000 F0.0100
09 PATHSTOP
10
Machine has been work for first cut & when it start second cut it has stop.
When we reduce the feed to 10-15, machine get start. Once machine get start it will run on 100 % feed. I don know how issue get solved.
Do you have a programming manual?
There are examples to follow in the book.
After you define a path you have to call it up (rough or finish).
Also you have to finish the program.
George
(Note: The opinions expressed in this post are my own and are not necessarily those of CNCzone and its management)
Program is as follow
00 TLCHG I1 T01 01
01 SETCSS G1 C160.00 S600
02 AUXFUN M8
03 STARTPATH 1
04 RAPID ABS X28.0000 29.0000
05 LINE ABS X28.0000 20.0000 F0.0100
06 CHAMFER ABS X130.0000 20.0000 P1.0000 F0.0100
07 LINE ABS X130.0000 Z-23.0000 F0.0100
08 LINE ABS X133.0000 Z-23.0000 F0.0100
09 PATHSTOP
10 ROUGH1I1 X0.5000 Z0.0000 F0.2000 0.2000 0.2000 S0.6500 C1.0000W45.0000
11 RAPID ABS X140.0000 Z1.0000
12 PROFIL11 X0.0000 Z0.0000 F0.2000 C1.0000 E45.0000 W90.0000 U2 A1
13 RAPID ABS X140.0000 Z1.0000
14 AUXFUN M9
15 AUXFUN M2
Machine has been work for first cut & when it start second cut it has stop.
When we reduce the feed to 10-15, machine get start. Once machine get start it will run on 100 % feed. I don know how issue get solved. I observed other abnormal thing is when we move the X – Axis in Do event & manually system shows the alarm “Following error limit excess”
From the description of following error on the X axis, and running at 100% feed. This is starting to sound like a tach failure, but cannot recall if these even had a tach built into the motor on a CSS machine. At least investigate signal loss due to a broken wires on the tach or encoder cable.
Pay attention to what axis is expected on the next move and where it stops running. Possibly reset the Z position far away from the spindle and try to run the same program again. If it is a broken cable, it may be bending at that previous point and shorting or losing connection etc.
DC