Advanced Search

Sorry got distracted over the holidays.

So I made your recommended change to the glade file and it did not work. see screenshot

any more suggestions?

thank you as always
 

If you wish to test the inputs, disconnect all external devices from the inputs
and test each input by connecting it to field power (+24V in your case)
Note the touching the screw on the connector is not reliable unless the screw is tight

If the NPN limit switch outputs are not very close to ground in one state,
you still have a wiring error.

Hi Guys,

I must have an endless loop in this program, as LCNC hangs as soon as I load it. 
I have been through it twice, and can't see my error.

The first loop starts at X-4, and loops as it increments up in 8mm steps across to X52, while the second loop starts at Z30, and increments down in 6mm steps, until reaching Z0.

Without LCNC calling the error, may I please request you check this and let me know what I have screwed up, as I can't see it?
Thanks.
Mark
 

scsmith1451 wrote:

Also, what happened to my previous topics? Are they automatically purged with a new year? 

No they are not.
Do you recall the tittle or some exact part of the content or section of the forum or anything that might help find it?
Usually they can be restored, if not permanently deleted.

I rewired my psu input from psu > wagos > mesa input > field to psu > mesa > field > wagos but no change sadly.

Oddly enough, I can jump between gnd and input pins 13 and 12 and get a change of state using showpin, but nothing down to pin 8. And thats without a resistor on any input except for 8.

AFAIK, in pncconf a tandem axis simply duplicates the the primary axis
(with a different stepgen and joint position command) so any differences
(like a reversed direction) would need to be done by editing
the hal or ini file.

Cant try anything at the moment, but thats sweet. you have any examples of it in use? (even sims)

Hi All;

I finally have the second Y Axis installed on my machine and was trying to configure it.  I'm using a MESA i76u board. When I started pncconf, I selected to modify my existing single Y axis configuration since it worked beautifully. I increased the number of Step/Dir channels to 5 as my machine was currently configured for a 4th rotary axis.

On the Axis configuration page I set the 5th Step/Dir configuration to Y2 Tandem, and on the P3 pin configuration page I added the input for the Y2 Tandem Both Limit & Home. I moved through the X Motor config as it was already working correctly to the Y Motor configuration which I verified till worked as expected. I expected the Y2 Motor to be the next configuration page, however pncconf proceeded to the Z, then A axes with no page to configure Y2.

Did I miss something earlier in the config process that would generate a configuration for Y2? Perhaps I needed to set the machine configuration to xyyza or xyy2za or something akin to it? 

A little help would be greatly appreciated.

Also, what happened to my previous topics? Are they automatically purged with a new year? 

Regards and happy New Year

rodw wrote:

JT wrote:

Also note that there is no /etc/apt/sources.list.d/debian.sources in my Debian 13 after doing a full upgrade.

JT
yes the old format is retained on a full upgrade from Bookworm but it will nag you on an apt update to run sudo apt modernize-sources if I got the spelling right...

Debian says the old format will be removed in time.
 

This was an upgrade of Debian 13 not 12.

JT

Those voltage values indicate a wiring issue.

With NPN sensors, one state should be very close to GND  (<1V)
How high the voltage is in the other state depends on the pullup resistance
which may be infinite (no pullup) or some intermediate voltage depending on the
pullup resistance (some NPN proximity switches have built in weak pullups)

Because the low levels are not close to GND, it sounds like the the NPN proximity
switch common is not connected to the field power common.

 

Regarding the error “Unknown M code used: M130”:

I followed the official LinuxCNC documentation/tutorial for configuring user M-codes.
The INI file was configured according to the manual, including the correct use of [RS274NGC] USER_M_PATH, and the M130 file is executable.

Despite this, LinuxCNC still reports:

file .INI
[EMC]
MACHINE = eng-eth
DEBUG = 0
VERSION = 1.1

[DISPLAY]
DISPLAY = axis
EDITOR = geany
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
ARCDIVISION = 64
GRIDS = 10mm 20mm 50mm 100mm 1in 2in 5in 10in
MAX_FEED_OVERRIDE = 1.2
MIN_SPINDLE_OVERRIDE = 0.5
MAX_SPINDLE_OVERRIDE = 1

DEFAULT_LINEAR_VELOCITY = 10.0
MIN_LINEAR_VELOCITY = 0
MAX_LINEAR_VELOCITY = 42.0

DEFAULT_ANGULAR_VELOCITY = 15.00
MIN_ANGULAR_VELOCITY = 0
VELOCIDADE_ANGULAR_MÁXIMA = 100.0

PREFIXO_DO_PROGRAMA = /home/cnc/Área de trabalho/
GRÁFICO_DE_INTRODUÇÃO = linuxcnc.gif
TEMPO_DE_INTRODUÇÃO = 5
INCREMENTOS = .1mm .05mm
PYVCP = Probe_panel.xml

[KINS]
JUNTAS = 3
CINEMÁTICA = trivkins coordenadas=XYZ


[FILTRO]
EXTENSÃO_DO_PROGRAMA = .txt,.png,.gif,.jpg Imagem de Profundidade em Tons de Cinza
EXTENSÃO_DO_PROGRAMA = .py Script Python
png = imagem-para-gcode
gif = imagem-para-gcode
jpg = imagem-para-gcode
py = python

[TAREFA]
TAREFA = milltask
TEMPO_DE_CICLO = 0.010

[RS274NGC]
#REMAP=M6 grupo_modal=6 ngc=sonda # (ATIVAR SONDA)
ARQUIVO_DE_PARÂMETROS = linuxcnc.var
FEATURES = 12
SUBROUTINE_PATH = macros
ON_ABORT_COMMAND = O <on_abort> call
FEATURES = 12
RETAIN_G43 = 0
INI_VARS = 1
HAL_PIN_VARS = 1


[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
COMM_WAIT = 0.010
BASE_PERIOD = 0
SERVO_PERIOD = 600000



[HAL]
HALFILE = eng-eth.hal
HALUI = halui
TWOPASS = on
HALFILE = Probe_preload.hal
POSTGUI_HALFILE = Probe_postgui.hal

[HALUI]
MDI_COMMAND = G54
MDI_COMMAND = G55
MDI_COMMAND = G56
MDI_COMMAND = G57
MDI_COMMAND = G58
MDI_COMMAND = G59
MDI_COMMAND = G59.1
MDI_COMMAND = G59.2
MDI_COMMAND = G59.3

MDI_COMMAND = O <probe_toolchange> CALL [1]
MDI_COMMAND = O <probe_toolchange> CALL [2]
MDI_COMMAND = O <probe_toolchange> CALL [3]

MDI_COMMAND = O <probe_x_plus> CALL
MDI_COMMAND = O <probe_x_minus> CALL
MDI_COMMAND = O <probe_y_plus> CALL
MDI_COMMAND = O <probe_y_minus> CALL
MDI_COMMAND = O <probe_z_minus> CALL
MDI_COMMAND = O <probe_pocket> CALL
MDI_COMMAND = O <probe_operations> CALL [1]
MDI_COMMAND = O <probe_operations> CALL [2]
MDI_COMMAND = O <probe_operations> CALL [3]

MDI_COMMAND = O <probe_manual_set> CALL [0]
MDI_COMMAND = O <probe_manual_set> CALL [1]
MDI_COMMAND = O <probe_manual_set> CALL [2]
MDI_COMMAND = O <probe_manual_set> CALL [3]
MDI_COMMAND = O <probe_escape> CALL

MDI_COMMAND = O <probe_calibration> CALL

[TRAJ]
COORDINATES = XYZ
LINEAR_UNITS = mm
ANGULAR_UNITS = degree
CYCLE_TIME = 0.010
DEFAULT_LINEAR_VELOCITY = 42.0
VELOCIDADE_LINEAR_MÁXIMA = 42,0

[EMCIO]
EMCIO = io
TEMPO_DE_CICLO = 0,100
TABELA_DE_FERRAMENTAS = tool.tbl

#*** EIXO_X *******************************
[EIXO_X]
LIMITE_MÍNIMO = -5000
LIMITE_MÁXIMO = 5000

VELOCIDADE_MÁXIMA = 42,0
ACELERAÇÃO_MÁXIMA = 350,0


[JUNTA_0]
TIPO = LINEAR
HOME = 0

VELOCIDADE_MÁXIMA = 42
ACELERAÇÃO_MÁXIMA = 350,0
ACELERAÇÃO_MÁXIMA_MÁXIMA = 5000

LIMITE_MÍNIMO = -5000
LIMITE_MÁXIMO = 5000
ESCALA = 400
ERRO_FERROR = 1,0
ERRO_FERROR_MÍNIMO = 0,25
DESLOCAMENTO_HOME = 0,0

VELOCIDADE_DE_BUSCA_HOME = 0
VELOCIDADE_DE_TRAVA_HOME = 0
HOME_SEQUENCE = 1

DEADBAND = 0.002
P = 220
I = 0
D = 0
FF0 = 0
FF1 = 1
FF2 = 0
BIAS = 0
PGAIN = 220
PID_MAXOUTPUT = 250

#*** EIXO Y *******************************
[AXIS_Y]
MIN_LIMIT = -5000
MAX_LIMIT = 5000

MAX_VELOCITY = 42.0
MAX_ACCELERATION = 350.0


[JOINT_1]
TYPE = LINEAR
HOME = 0.0

MAX_VELOCITY = 42
MAX_ACCELERATION = 350.0
MAX_MAXACCEL = 5000

MIN_LIMIT = -5000
MAX_LIMIT = 5000
SCALE = 400
FERROR = 1.0
MIN_FERROR = 0.25
HOME_OFFSET = 0.0


HOME_SEARCH_VEL = 0
HOME_LATCH_VEL = 0
HOME_SEQUENCE = 2


DEADBAND = 0.002
P = 220
I = 0
D = 0
FF0 = 0
FF1 = 1
FF2 = 0
BIAS = 0
PGAIN = 220
PID_MAXOUTPUT = 250


#*** EIXO Z *******************************
[AXIS_Z]
MIN_LIMIT = -5000
MAX_LIMIT = 5000

MAX_VELOCITY = 15
MAX_ACCELERATION = 150.0

[JOINT_2]
TYPE = LINEAR
HOME = 0.0


MAX_VELOCITY = 15
ACELERAÇÃO_MÁXIMA = 150,0
ACELERAÇÃO_MÁXIMA_MÁXIMA = 5000

LIMITE_MÍNIMO = -5000
LIMITE_MÁXIMO = 5000 ESCALA
=
820,512
ERRO_FERROR = 1,0 ERRO_FERROR_MÍNIMO
= 0,25
DESLOCAMENTO_HOME
= 0,0 VELOCIDADE_DE_BUSCA_HOME = 0 VELOCIDADE_DE_TRAVAMENTO_HOME = 0 SEQUÊNCIA_HOME
= 0
BANDA MORTA = 0,002
P = 220
I = 0
D = 0
FF0 = 0
FF1 = 1
FF2 = 0
BIAS = 0
PGAIN = 220
PID_SAÍDA_MÁXIMA = 250
[SONDA]
# Defina até três números de ferramentas de sondas diferentes em sua tabela de ferramentas. Defina os números não utilizados como zero.
TOOL_NUMBER_1 = 99
TOOL_NUMBER_2 = 0
TOOL_NUMBER_3 = 0
# Curso máximo de segurança da sua sonda nas direções X/Y. O valor é fornecido pelo fabricante. Em caso de dúvida, defina para ~3 mm.
MAX_XY_DISTANCE = 3
# Distância que a sonda percorrerá após uma sondagem rápida. Valores recomendados entre 0,5 e 2 mm.
XY_CLEARANCE = 0,5
# Curso máximo de segurança da sua sonda na direção Z. O valor é fornecido pelo fabricante. Em caso de dúvida, defina para ~2 mm.
MAX_Z_DISTANCE = 2
# Distância que a sonda percorrerá após uma sondagem rápida. Valores recomendados entre 0,5 e 2 mm.
Z_CLEARANCE = 0,5
# Velocidade da sondagem rápida. Valores recomendados entre 50 e 500 mm por minuto.
# Observação: Todos os valores de velocidade definidos serão verificados. Os valores considerados são: ACELERAÇÃO_MÁXIMA (x, y e z), TEMPO_DE_DEBOUNCE e DISTÂNCIA_MÁXIMA_XY/Z.
VEL_RÁPIDA = 200
# Velocidade lenta da sonda. Este valor é importante para a precisão geral. Valores recomendados entre 10 e 50 mm por minuto.
VEL_LENTA = 20
# Velocidade rápida de avanço entre os movimentos da sonda de bolso sem sondagem real.
VEL_RÁPIDA = 2000
# Acionamentos adicionais da sonda levarão a uma melhor calibração. Valores entre 0 e 3 são recomendados.
ADICIONAR_ACIONAMENTOS_DA_SONDA = 2
# Atraso de tempo em ms para o debounce do interruptor da sonda. Tente manter o valor o mais baixo possível. Valores recomendados entre 2 e 20 ms.
TEMPO_DE_DEBOUNCE = 10
# Configure o interruptor da sua ferramenta de sonda. 0 = NA (normalmente aberto), 1 = NF (normalmente fechado)
# Observação: O LED de sinal da sonda deve mudar de verde para vermelho quando você tocar a ponta da sonda.
INTERRUPTOR_DA_SONDA = 0

Had the same issue, double check your wiring of the orange block. If it's wrong it won't power up and you'll get the issue your are seeing.

Gentelmen, I am not an expert of C hard code for this big performance irons... I have coding just embedded stuff (day of 8bits stuff) and from this I am little bit bended to optimsing everything over readable coding ... because of lack everything 

therefore it was just my opinion ... I am open to learn new stuff and let my habits behind 

Luca do you think about the look ahead position control? PositionCommand(t+1) as I said before please? For run the ethernet and ethercat servo packs in CSP control? This will change the lagging and cycle ferror during movement...

I have coded my own component which is solving it by it is not accurate during the accellerations change ... 

Sorry, just for info: the encoder is a separately mounted encoder just for thread cutting, so it has not really to do with the spindle control itsself, though would be nice if positioning the spindle would be possible later on...

rodw wrote:

I don't think it makes sense to manually optimise for execution speed in this day and age. Instead use GCC compiler options -03 or -0fast and possibly native optimisations march=native and possibly mtune=native. This may increase code size and possibly memory usage but I don't see that current hardware has constraints in this area. Gone are the days of massaging code to save every byte to fit in a 64k terminal! I did find using the C ternary operator was more efficient than if-else during that exercise.
 

I disagree. Compilers can do great things, but writing code with performance in mind can make a HUGE difference. I haven't looked at this code to know if there's low-hanging fruit here or not. As an illustrative example, I recently got the PeanutGB emulator running on an nRF54L microcontroller. Various low-hanging-fruit optimizations (pulling branches out of loops, handling 16-bit numbers natively instead of as 2x 8 bit integers, etc.) brought that from running at not even full speed to running at 130~150% speed.

There's certainly an argument for writing readable code over the most optimized- the above changes varied from neutral in readability to highly detrimental to readability.

Any loops are a good place to start looking at optimization- pulling out any branches, unrolling them, and/or reducing calculations that are done in the loop. Basically Amdahl's Law- look at optimizing the parts of the code that take the most execution time.