Advanced Search

Also, UTF-8 locale is used by LinuxCNC, i think, but i never checked, i just set all my computer to en_US and UTF-8 and never have issues.

Looks like pncconf will not work with your locale setting
You may have to temporarily set the locale to en_US to work
around this issue.

thank you andy for this idea
i tried to make python script that reads the 2 hal pins but the problem is that due to the higher speed of changing the values in the hal pins the python script wasnt able to read all the values correctly there are some data missing and i tried cmorley idea to switch manual with simple python script and it did work

Hello,
unfortunately I ran into the next problem .
I was tuning my servos, in the calibration tab and saved the settings. The Machine behaved as expected. when i restartet LCNC the movements of the machine were jerky and ended up in positioning errors. So I set the the values back to something that just moves and repeated the process. Saved the settings and even checked the .ini if the values have been stored correctly. no problem. But as soon as i restart LCNC same problem. The values of the second tuning process ended up being more or less the same as the first time.
Am I missing something here?

EDIT:
The problem was me... i messed up something in the ini Seems to work now.

MPG wheel connection - fixed

MPG ENCODER INPUTS

Standard 7I95T firmware provides 4 quadrature MPG encoder inputs on isolated inputs 0 through 7.
Since the input threshold on isolated inputs is about 3V, its best to use sinking inputs (with the input common terminal tied to +5V) with TTL output level MPGs.

INPUT ENCODER 
0     QUADA-0      MPG 0
1     QUADB-0 
 
2     QUADA-1      MPG 1
3     QUADB-1 
 
4     QUADA-2      MPG 2
5     QUADB-2

6     QUADA-3      MPG 3
7     QUADB-3

 


The problem for me is that the MPG hand wheel function for inputs IN 00-07 cannot be selected from the submenu in the PNCONFG menu.
I don't know how to manually edit HAL.

Hello All,

I am trying to connect a Mesa 7i96s on a new installation.
I do not have much experience with Linux.
Running 6.1.0-40-rt-amd64
This error comes popping up, can any one give me a reason why this is happening?

Thank you,

Antony Manuel.

 

I think something is wrong with these 2 cfg files
turning.cfg
tool-change.cfg
both don't work, the rest seems ok

File "/usr/lib/python3/dist-packages/ncam.py", line 1914, in from_src
exec(self.attr["init"])
File "<string>", line 2, in <module>   <<<<<<<<<<<<<<<<<<<<< Which module??
NameError: name 'parent' is not defined. Did you mean: 'reparent'?

Only in this files, "parent" is used.
I deleted these blocks with "parent" as a test, and it worked. However, I don't know what the potential effects might be; I'm not familiar with this.



 

Sorry, but to test I would need to know the actual encoder/step counts that were being fed into the component at the point of failure.

But, I am sure that the code linked above is very wrong, and is likely to be the problem.

Can you:
1) Make sure that you have the linuxcnc-uspace-dev package installed.
2) Download the attached carousel.comp file
3) From the folder where you saved the file
And see if the problem is fixed?

No change needed to linuxcnc rt functions.
There is already the functionality needed to modify the call to nanosleep.
There is now closed issue at github where I look at that github.com/LinuxCNC/linuxcnc/issues/3564

What is new is that the option is made an explicit option syncToRefClock.
The old way to invoking the functionality, which works already now, is to
set a negative refSyncClockCycles value. The "-" triggers the function to be on.
This continues to work in linuxcnc spirit, and is now made clear with
both documentation of the function and an explicit option.
 

iocontrol.0.emc-enable-in probably needs to be true to release the e-stop condition. Is that happening?

From that example/template I linked to before, you needin the hal file.
That should allow it to start I think.
That example/template is a working example. You have a bit different naming due to two motors per drive, but other than that it should work.

I think that you need to control the tool changer to use the iocontrol.0.tool-prep-pocket number rather than the tool number.
Then you need to set up the tool table to say which tool is in which pocket.

Does this require changes in LinuxCNC or was the facility already there?

updated and works again! Thank You!

Yes, I am confident that LinuxCNC can do this.

You might prefer to control the machine with a Python script linked to a GUI, but using G-code is also possible.

Adaptive G-code could handle the different punch maps, but Python (which would send G-codes using MDI, probably) might work better.

An example of a GUI that calls adaptive G-code is my lathe macros, here is a link to one of the G-code routines:
github.com/andypugh/LatheMacros/blob/Py3_GTK3/turning.ngc
The subroutine is called with #1, #2 ... #6 specifying various parameters of the actions to be taken.

3) I don't really know the answer. It would probably be automatic at the end of the cycle?

4) The maximum length is much longer than the known universe. (10^308 units) but is practically limited to 15 significant digits, so using mm and 1 micron basic precision it would be approximately 10,000km.