Advanced Search

Nice, glad you have such reasons, i've been out of commission for exactly 3 weeks now due to sticking my finger where it does not belong, it is astonishing how a messed up finger tip can limit the ability to work... or just brush teeth. This brushing teeth with left hand was absolutely hilarious for several days as i was shaking my whole body doing it! Got used to it though.
BTW, 3 weeks and still can not remove stitches as the swelling has not subsided sufficiently.

spincycle wrote:

Thank you kindly PCW for your reply.

This might be a very stupid question, but how do I implement the link you provided into MesaCT?

Do Just download the last hostmot2.c and mesaflash.c files and swap them into the mesa flash-master folder?

Excuse my ignorance!

j
 

github.com/LinuxCNC/mesaflash there is a quickstart instructions at the bottom of that page to build and install mesaflash.

MesaCT uses whatever version of mesaflash that is installed.

JT

Ja auf jeden Fall. Kein Laptop.

Thinkcentre tinys, Fujitsu esprimos, einiege Intel NUCs und wie erwähnt Raspberries sind geeignet.

Je nach gui reicht nen 4er raspi nicht mehr so richtig und es sollte ein 5er sein.

Ethercat oder nicht ist für die hardware (leistungsmäßig) quasi egal. Jitter ist bei 1ms Servothread gut in den Griff zu kriegen mit allen genannten obigen Rechnern. Man muss aber schon wissen was man macht.

Netzwerkgeschwindigkeit wie sonst für Mesakarten ist dir ja in deiner Konfiguration egal. Ich bin bei ethercat nicht fit, aber Guido hat in seinem Git was online was läuft...

github.com/GuiHue/EtherCAT-CNC-HMI

I was completing and testing my new parameter subroutine for helical inside or outside contour ramp, adjustable stepover and x/y/z allowance finishing cut. Took the whole night to iron out some misbehaviour

 

if I can take any two inputs and turn them into an MPG encoder in the HAL then could I just take two inputs from the EtherCat side?

I was thinking I would need to be running on an realtime thread to do encoder counting due to some timing issues between "listening" to A and B ticks.. But if the Pi GPIO can run on the Servo thread and 1ms is fast enougn, then it should be fast enough for the ethercat IO too right??