Advanced Search

I think we have all gone off track with how this should work.
Please refer to the template source code
github.com/LinuxCNC/linuxcnc/blob/master...s/homecomp.comp#L257Note that there is a condition here that decides if this joint should be custom homed or homed normally.
So this pin should be set to 1 if this joint is to be custom homed with setp

But if you look at tangentaudio's code, he (and every body else, me included) uses this pin to trigger homing in cia402 which is wrong!
So we should be creating a new pin start-homing to trigger the cic402.n.home pin.

Can you guys review this and see if you agree?

Thanks for sharing your success. I am about to start again for the third time. I keep trying  to add extra stuff in. The first time, my work was obsoleted as the homecomp template was massively changed. Before I started, I did work out that the cia402.comp would never work and at that time changes to homing.c were required.
The homecomp is a very simple but we keep trying to use cia402.comp that as written before custom homing was introduced and was based on drive that homed to index.

I did try building cia402.comp into the homecomp but that was the one that was obsoleted. I don't think it would work because the homing loop sits outside the lcec loop so it will be one step behind.

I think the  best architecture would be to rewrite cia402.comp so it did everything with the drive except homing (inside the lcec loop) and then everything to do with homing was done in the homecomp. 

Thanks.  The first issue is the output to control the spindle speed. I use a mesa 7i76e card with 0-10V as reference voltage on the spindle port TB4. The output won't go higher than +5V or for that matter, 50% of any reference voltage that I use.  The spindle also starts turning at 50% of the maximum spindle speed output setting when I use the slider in manual mode to control the spindle speed.  (The spindle only starts to run when the slider is in the middle.) The reason why I suspect that the issue is related to the qt_lathe gui is because when I do the exact same setup with pncconfig selecting AXIS as gui, the maximum output is the the same as the max+ reference voltage. 

The output is similar to "bipolar mode" as descibed in the 7i76e manual p15:as in the screenshot of the manual..     

I also noticed that the -5V to +5V (or 0-10V) output setting in the Spindle section of pncconfig for qtdragon has no influence on the output voltage of the spindle speed control. Whether the box is selected or not it makes no difference. 

My current goal is to get the lathe running with the correct axes and spindle control.  Once that is sorted I'll inform you of the other issues as I find them.

Remark:
The issue was resolved by changing the OUTPUT_SCALE parameter in the .ini file to a value of 1000.  As I read through the comments in the forum regarding the OUTPUT_SCALE value I realised that this is not an absolute value. 
 

Maybe you can check the pinout here attached.

I will do some further tests now- coming from 2.8... and a 7i77, this stuff is quite "all new" now with ct ect.

Thanks guys!

BR

Embed a Qtvcp camera panel (there is a sim example of this)

linuxcnc.org/docs/devel/html/gui/qtvcp-v...vcp:panels:cam-align
You can modify the panel to add buttons or add a pyvcp panel as well for native buttons

You can read HAL pins in python remaps

Hi all,
I'm about to read the instructions to install probe basic, but I thought I should ask if anyone has swapped to it without a fresh install of linuxcnc.
If anyone has switched to probe basic from another gui, what problems should be expected? Any tips for those switching?

Something like:
x = float(self.w.lineEdit_sensor_x.text())
y = float(self.w.lineEdit_sensor_y.text())

@RodW, edit your post and removed the phone number on request as he was getting spam calls.

BTW, that "override potentiometer" looks promising...

Mach3 is absolutely not usable for this or anything complicated, and so are most of "turn key" solutions, even Siemens will cause much more problems for you than LinuxCNC.
In short, there is no other viable option, especially there is nothing usable under 15-30K$.

try opening Linuxcnc Status (settings tab right hand side 'status')
Look under G5x offset.
I bet that linuxcnc is using the right offset but qtdragon is reporting wrong on the offset page.
I assume you are referencing the offset page entries?