Advanced Search

For the cross slide I oredered a 12mm ballscrew. If I can find room I will mount the ball nut under the cross slide table. If not, the screw I bought is long enough that I could mount the ballscrew on the back side of the cross slide table.

I'll be going out of town for a couple weeks, but when I get back I think I will do some examining for the encoder situation.

I saw a video of somone doing threading on linuxCNC using a missing tooth scheme. I may look into this more when I bored in my hotel room next week.

Thanks again for the comments
 

Leave them at default 5000 till you have everything working properly, then you can decide if you need to mess with timings. Usually there is no need.

www.aliexpress.us/item/3256805790238823.html

I am waiting for the manual from the seller, will add when i receive it.

 

No., unless you need a new component to provide the pins.
(which is not the case here)

If you are learning, I would definitely poke around a bit with halshow
(in axis it's: Machine --> Show Hal Configuration)

 

Greg,

Right now, you have a machine in good mechanical state. The only problem you have with this machine is the controller. My advice, do not remove or dismantle any component at this stage. 

1-Gather the manuals wiring diagrams and any information you can find. 

2-Study the servo drive CONTROL METHOD (analog, digital, industrial communication bus etc …) 

3- Study existing wiring diagrams and determine the number and type of IO’s (sourcing/sinking) 

4- study the type of controller you will need, the type of daughter boards needed and type of PC (pci/pcie/ethernet/Mitsubishi bus communication bus … etc 

5- Modify the existing wiring diagrams to reflect the changes required. Keep in mind that the machine was designed and assembled by highly skilled craftsmen, at this stage you will focus on keeping the modifications to existing components to a strict minimum. 

6- With all the above knowledge and mods you will be ready to configure the controller and choose GUI 


Note: machine integration requires patience especially if you have not done it before on a machine such as vmc. (Bounding, grounding, shielding can be nightmare, modifying the safety control system can become a liability and changing from sourcing/sinking io can be laborious, etc …), keep it simple stupid (KISS) is the answer to a successful project.

Thanks for your reply . Just curios if we need to loadrt something in hal before putting the new command.

Hi
G10 L20 P1 z0 doesnt work if the below program is stopped midway and rerun. Random z values come up and cut gets all wrong. Please guide as what is incorrect.
G10 L20 P1 x0 z0
G01 Z0.5
G01 Z-0.1 F5 ; cut here
G10 L20 P1  z0
Code here
M2

This very quickly is going to turn into a how to destroy some Fanuc encoders thread so stay tuned for that   

I've decided to replace the encoders... this is probably not the answer that future readers are going to want to read, but its the least expensive and most straight-forward approach I can come up with. Either I have a digital problem or a mechanical problem to solve, and the latter is much more manageable with my skill set. 

I'm trying to get better at knowing when to take a different path to the finish line. I once spent months trying to design a DC motor driver (90v 200amps) that ran on 600v 3phase for a Hardinge CHNC lathe based on open source electric vehicle schematics. Long story short, I didn't succeed and blew up a lot of expensive components along the way    Once I finally decided to swap the motor for an AC one and add a VFD, the whole thing was turning in in 2 days! 

More to come! 

timo wrote:

Unfortunately hollow shaft encoders are much more expensive than the required parts

 

One option might be an engine crank encoder:

Do not buy RPI5
www.youtube.com/shorts/qN-1nPGbS3I

If you end up doing ~91 full turns (@65536 counts per degree and 360 degrees per turn)
the 32 bit signed position number used in intermediate encoder calculations will wrap, I suspect
this may be whats happening. Are 91 turns possible?

running version 2.9.2

reason for a high count on C is because its tool path with just continues +C axis moves in it to form a swarf move in a hole,

in the ini for the c axis i have
MIN_LIMIT = -1e99
MAX_LIMIT = 1e99

ENCODER_SCALE = 65536
#1/5 first gear , 1/72 worm 2nd gear
#16384*4= 65536 pp/r
#gears 1/5+1/72=1/360
#65536*360/360=65536

One option would be a stmbl v5: github.com/freakontrol/stmbl
There is also a thread on the forum.
I have it running with smaller Mistubishi Motors, your encoders should be supported. The HA103 Motor is on the upper power limit, but it should be fine. It can run the 200V motors direct from mains voltage without a transformer.

i use M68 to control my rc-servo gripper's
so i can control it by gcode and for the gui i use mdi commands and a vcp gui with buttons to set some fixed positions

[HALUI]
MDI_COMMAND = M68 E0 Q-100
MDI_COMMAND = M68 E0 Q-75
MDI_COMMAND = M68 E0 Q0
MDI_COMMAND = M68 E0 Q75
MDI_COMMAND = M68 E0 Q100

www.youtube.com/shorts/Tp3savo-MGs

Very well prepared