Advanced Search

thanks for the hint!

that would be basically that what is done at that step (in homing.c in comp file from your link i did not find that part yet)?


BR
Dominik
edit (april10th): that got me a big step further, but besideds mapping pos_fb to pos_cmd (which worked for most of the sequence), i also had to change the ferror_limit in some steps as there may be abrupt changes due to position-values reset to home or zero  position.

not yet finished but i think i can solve it that way -> thanks again

Hello,
I'm a bit new to 4-axis machining and I've been machining features on axles. These axles were mounted on the A-axis. Fine.
But now I've clamped my ER32 collet block at 90° to the A-axis, with the nut facing upwards to secure my stock.
But I can't know his exact position until I lock it in the ER32 block because it moves downward when I tighten it. So I have to probe it.
I then need to use this measured value to set the part's origin in the CAD software to create the milling path. This is tedious and must be repeated every time I place a stock in the ER32 block.
Is there a way to avoid having to generate the program from the measured value?

jenkinson8 post=325911 userid=42861Teraz som späť doma. Príkaz, ktorý hľadáte, je:

[code]pip3 install tftpy --break-system-packages

Then rerun the upload_config.py command again.
 
 Its okay. Thanks

[/code]

timo wrote:

A not properly crimped plug or semitight srew termnial might cause a problem as well?
 

Yes.

timo wrote:

Or does the damage only occur when all four wires are disconnected at same time?
 

Any motor wire.

timo wrote:

I would guess the system does not know if I did it or it just happened.
 

What system? The drive will know, motors are inductors and disconnecting powered inductors cause huge spikes that very often end in dead equipment.

i just measured the bearing OD and the housing bore diameter, and the housing is a good .002 larger than the bearing OD. the shaft is either pressed into the ID or it got that way when it broke? the bearing feels like it is spinning just fine so i don't think the bearing was the root cause. the break was right at the shoulder where the bearing would ride and seat on the shaft. no wave washer on the front side and it does not feel like it has one on the other end either.

OP - That's a nice harmonic drive you've got there, especially with the big through-bore.

If you still need some mounting inspiration, Andy Pugh did a fantastic job of documenting his 4th axis build based on similar reducer.

machinedude wrote:

the only other clue i can offer up at this point would be the fact that the bearing was not pressed in the motor housing. it came right out so maybe a poor press fit added to this?

Bearings are quite often an interference fit on the shaft but close sliding (or transitional) fit in housing.  Makes assembly easier, especially in production environments.  Interference fits on both the shaft and housing make assembly a nightmare.

Frequently for smaller motors a spring/wave/Belleville washer is used inside one housing end to permit the bearing to move axially as the rotor shaft grows (from heat).  That spring preload also tends to keep the bearing outer races from spinning in the housing bore.

If the bearing was a fairly sloppy fit in the housing there was very little resistance to shaft bending and all the movement would have been concentrated at the shaft bearing seat shoulder.

Andy's suspicion about a fatigue crack from shaft misalignment is looking pretty darn persuasive to me.

Hi,

I've built an CNC router with MESA7I96 controller. I use an Pi5 for running linuxcnc and it works fine. Until this time I used Fusion360 for CAM, but I'm thinking on to try Vectric Pro.

Vectric has any metric post processor for linuxcnc? If yes, which one you use?

It's always fun to poke fun at the Septics, tho they seem to encourage it when some of the louder ones don't realise that other countries do things their own way and will argue the point.

A not properly crimped plug or semitight srew termnial might cause a problem as well?
Or does the damage only occur when all four wires are disconnected at same time?
I would guess the system does not know if I did it or it just happened.
 

Glad you waded into the live build environment. Wait till I get you going on the raspberry Pi 
Sorry it failed for you.. I had plenty of that. The biggest issue I had was getting apt configured and installing the gpt keys.
Bjarne from Etherlab was a big help there.

I think Linuxcnc builds all of the Debs in the one go.
There was a really interesting pull request from Stefan Moller that has yet to be committed which installed the dependencies the Debian way (eg. Just using one command. It would have been nice to see it in the code by now.

Hey guys, letting you all know that I found the problem. Looking back a few pages found that the repo has different nvem config files. Uploaded this one and it now works: github.com/scottalford75/Remora-RT1052-c...xCNC/nvem-rt1052.txt

I'm back home now. The command you're after is:
[/code]

Then rerun the upload_config.py command again.
 

sajurcaju wrote:

When I started halscope, the trigger level slider worked as expected. For some reason it has become non-functional. The slider is gray, no green, no way to adjust it. I've tried restarting halscope and changing trigger channel. It doesn't matter if I'm in Red Light Green Light Normal or Auto trigger.

Thanks,
Steve

Did you make any adjustments to the settings before the trigger level slider became greyed out?

tommylight wrote:

Anyone against deleting this topic?
I failed to raise hell...
P.S.
I still maintain that calling silicium "silicon" is not smart, by any stretch of imagination. Sue me !
 

Well I mean, if you're looking for a fight......

I noticed quite a few jabs taken at us 'Mericans over here......I could oblige. I also noticed some strange replies that are missing the post they must have been replying to, wonder what that's about.....

I rarely click the "recent topics" button, so I missed the fun.