Advanced Search

I agree with Rod, naming can and will cause issues as soon as more people start using this, so changing it sooner rather than later would be beneficial.
Also agree on calling it Grotius, for us who spend more time here on the forum it would obvious, and new user will have to learn whatever the name may become.
P.S.
I still have nightmares with Probe Basic and Basic Probe !!!
Naming it QtMill and QtLathe would help a lot... Sorry LCVette, i know you asked us for a name and we came up with nothing.
We already have QtDragon and QtPlasmaC, those should fit nicely in the naming scheme.

there is no "probe basic lathe" just probe basic and a lathe ui. if you install probe basic you should be able to open the lathe sim, start there to verify the installation is correct first.

I wonder if the scurve planner could not be renamed to say "stpmod.so" or even "grotius-tp.so" in the build process?
The trajectory planner is loaded in the ini file settings so the name can be anything.
Changing the name would allow it to coexist in a version of linuxcnc that also includes the default tpmod.so. This would be desirable long term.

Also do try just the add on card with

Yes,
yes,
yes,
...
no!

ATX PSU is OK for testing and running the machine, but will limit the speed.
X220 is the "no" up there, had 2 of those, absolutely not usable for LinuxCNC, but since you have it, get the ISO, burn to USB, boot the X220 from it and do some latency tests as follows
latency-histogram --nobase --sbinsize 1000 --show
Also had 2 of X240 (still have one) both were/are fine for running LinuxCNC.
If the latency turns bad, i can upload an image i use on all my production laptops and PC's with Mint 19.3 and LinuxCNC 2.8.4, but this needs to be installed to be able to test it.

Thanks for getting back to me. I feel like I have tried that but I will confirm later on today.

Also I apologise for the photo they were taken when I was starting to play with getting this going. They were not meant specifically for the forum post more just as a record that I could look up on my phone when I was editing the hal file so all I needed was the address.

Happy to provide further information and better photos. If anyone thinks it will help.

OK, so
Mesa 7i96s it is (should be worth it, since I can us that one for the big machine later)
3 of the TB6600
Leaves the PSU question. I think I have an old ATX PSU. Those deliver 2-4 lines of 12V and several 5V lines. Could that do for the small steppers?
And my Thinkpad x220.

I have some additions. When using the carousel component on some machines, a notification appears. It does not affect the work, the machine is working normally, it just needs to be closed constantly. Maybe someone knows a solution. In the photo is a lathe. LCNC 2.9.4

Looking good!

Hi Endian. 

The scurve planner uses :
libclothoid3d and libscurve
libclothoid3 depends on libceres.

the scurve planner is tpmod.so.
loaded by linuxcnc.

Do you only want to use libscurve to generate motion for servo motor?



 

I've been trying to install the Probe Basic lathe all afternoon without success.
I've followed all the steps just like I did with the mill.
Is there a specific configuration for installing the Probe Basic lathe?

Yeah, that's not a sine wave (more like a rectified sine wave)
This may be something wrong with how you are measuring this
differentially (scope setup). Measuring single ended as Hansu suggested
would eliminate this possibility.

Is this connected to the converter? According to Heidenhains docs
the 1V P-P signals need a 120 Ohm (across 1V+ and 1V-) termination


The fuzzyness is likely just noise.

I suspect a problem with the encoder if you don't get ~1V sine waves when properly terminated

Marking up where the parts will be placed.
 

Sorry, I did not want to upset anybody. It is my fault. Sorry.

Thanks for the quick reply — that already helped a lot!

I switched the scope channel to AC coupling and used a drill with an Allen bit to move the spindle. Now I can finally see a sine wave (kind of).

However, two things are still puzzling me:

1. The sine wave appears very thick on the screen. My guess is it’s some kind of electrical noise, but I’m not entirely sure.
2. The amplitude is only around 50 mV, which is way lower than the expected 1 Vpp.  
   

Any idea what could be causing the “thick” waveform, and why the amplitude is so low?