Advanced Search

and the result of

1 more PWM added (this is Efinix for 7I92T)

 

 

ok. so i found that there was no line for the A-axis in the main HAL file.. Added that one, and now that input shows up as well.
However, still no movement.

You have "loadrt HM2_ETH " twice in the hal file, there can be only one ... (insert HighLander movie quote here)

Lower MAX_VELOCITY in the ini file, both in the display section and TRAJ section.
Those numbers should be in mm/s, so 100 means 100mm/s or 6M/minute.

Did some more studying and read the info on FERROR and MIN_FERROR. In looking at the check list I noticed that Base period could be the problem so I changed mine 1000000 and now i can move the axis. got some more study and tuning to do bu slowly making progress.

Hey,
I'm working with a Pi 5 running LinuxCNC 2.9.4 on a Mesa 7i95T.
After installing Mesact i used it to create a baseconfig for my XYYZ machine.
After adding the second Y axis nothing worked anymore.

Would you please take some time to help me out. Thank you.

It gives me following error:

Debug file information:
Can not find -sec TRAJ -var COORDINATES -num 1
Note: Using POSIX realtime
Missing [TRAJ]COORDINATES
6052
6099
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

attached are my .ini and .hal
 

ok that is the piece that i was missing! i was focused on throughput and thinking that there couldnt be that much data transfered to overload a network. forgot about latency.

how about an unmanaged switch or a hub? i know hubs arent great for congestion, but i would be only using one machine at a time so broadcast wouldnt be an issue. im just looking for a way here to simplify my wiring and reduce my physical footprint so any suggestions would be greatly welcome!

Hi Aciera,

What would be the loadrt and addf lines for the debounce?

As for the jog pins. They are lighting up in the halshow. However, axis A doesn't.
Counts value changes. The scale is another thing. At 1x it shows 1e-6. At 10x it shows 1e-5. And finally at 100x it shows as 0.0001. At 100x the count changes per 1000 pulses/counts.
As stated in the earlier, edited, posts the feed and spindle values do change in the interface.

Yes this is something I noticed when comparing files generated by mesact and pncconf. So changed all occurrences in the pncconf xx.hal file. Linuxcnc now comes up with QTplasmac but none of the motors work. Did the same trying the Axis GUI and same results. I get an hm2_7i95.0:error finishing read iter=(number varies from 17 to several hundred) when the GUI starts. When I push a jog x+ I get a joint 0 following error. In both cases the motors do nothing and can't see anything on halscope.

Hola, publico aquí en el foro en el español para ver si alguien a pasado por lo mismo... 

He estado usando 7i96S en con LINUXCNC 2.8.4 sin problemas. Ahora decidí usar la misma pc para diagramar una mesa de Plasma, donde quiero combinar Ethercat junto con Mesa 7i96S. Tengo dos puertos LAN, he visto que es posible la configuración. Al iniciar linuxcnc todo funciona perfecto hasta que aparecen lo que muestro en las imágenes. Seguro es problema de latencia, pero no entiendo si esta latencia puede estar generada por usar Ethercat + 7i96S o por haber cambiado de versión de linuxcnc. 

Desde ya muchas gracias!! 

PD: Me olvidado mencionar que también he probando usando SERVO_PERIOD = 2000000



     

You seem to be missing 'loadrt' and 'addf' lines for the 'debounce' component.
Once the config is running you can use the 'Halconfiguration' tool by going to the settings page in gmoccapy and clicking on the button on the bottom right corner.
Then you can change to the Watch tab and select the pins 'axis.L.jog-enable', 'axis.L.jog-counts', 'axis.L.jog-scale' from the selector tab on the left ('L' being the axis letter you are testing). Confirm that '-enable' is true, '-counts' are changing when you turn the wheel on the pendant and that '-scale' is set to a sensible value.

OK. Here are the config files.
Anything in them that would hinder the jog wheel from working?
Edit1: Looking into the toolheight setter not ' responding' I found the HalShow button. Here the jog count is changing as I rotate it. so the signals are received by LinuxCNC. It's just not used or something. (BTW had the input pin for the probe wrong it was set to 31 but wired to pin 21...)
Edit2: the jog wheel works for the spindle and feed rate. But not on any of the 4 axis.

Also the debounce issue in the xhc-hb04.hal? "./xhc-hb04.hal:47: parameter or pin 'debounce.0.delay' not found"

I'm currently running the gmoccapy 3.4.9 GUI for LinuxCNC.
btw. any tips for a touchscreen interface (not Touchy)?

Yeah, this was it...
"inmux.00.input-00" is the correct pin...
I'll make sure to be talking to the correct pin next time, before i ask another stupid question

Comment out the error on line 53 (probably need to do this a few times) until it starts, then open halshow and work out the correct spelling