Advanced Search

Hello friend
You can use an oscilloscope on the pulse output of this board, use the test axis feature in the image below

 

I recommend leaving the drives activated at this point, as remote activation may not be enabled in this test.
I also recommend not using the board indicated in your link, as it is not reliable, it does not have electrical isolation, and when the system loads it activates the outputs by itself, making the machine move before the releases and safety.
I recommend using the 7i96s electronic board, which is very safe and high quality.

I put in the MAC-address for the new adapter into /etc/ethercat.conf, and restarted ethercat service.
There were no initial datagram UNMATCHED messages, so I use the plasma table for some minutes.
Even after a day there were no datagram UNMATCHED messages, so I call that a win.
I even went back from isolcpus=1,2,3 to no isolpcus, it works just fine without that.

 
 

The verdict is: it works.
The stiff cable is a problem. And overall making a nice package of this will be a challenge.

My first experiment was to add an M.2 to PCIE adapter, and put in an Intel I210 card I have.Here is what that looks like 

There is the small M.2 card that goes in the slot and then there is the rather stiff cable that connects to the PCIE slot. And I plugged in the I210 there.

The biggest problem with this setup is that relatively stiff cable. It runs right over the screw that secures the M.2 board in place. I had to bend the cable, it is quite stiff. The cable became sandwiched between the adapter board and the M.2 system disk that sits on top. I got it there in the end but not ideal. 
 

As for the function - brilliant! After startup, the I210 showed up as a PCIE network adapter, it showed up in the interfaces list. I did nothing, just started the mini-PC. 

Hello Mr. PCW, I would like to thank you very much for all the help I have received here on the forum. I am very happy with the quality of the Mesa boards and the countless possibilities for any type of project. Exceeding all expectations. I would like to thank the Mesa manufacturer team for all their support. I wish you much peace, health and prosperity.

My project has been completed and I can't wait to continue new projects using your technology.
I am very pleased to recommend this technology to everyone.
See you soon.

I didn't say I'd used it.

Okay, okay, I did! It's definitely more useful for looking at small sections of the HAL.
The whole thing is a little too much for the tool, but if there's a subset that you're trying to understand better, it's definitely useful.

Thanks for writing it -- I found it because I was setting out to do the exact same thing, also using graphviz, but decided I should look around to see what was already available. You saved me a bunch of work!

paul

For some time I have been setting up a plasma system using a N100 mini-PC and ethercat drives 3xECT60 and one of my own Metalmusing EaserCAT-7000 board for IO and torch height. It is working fine, but there is the occasional, sometimes more than occasional message in dmesg/journal, datagrams UNMATCHED

In this case it is not a catastrophe, the ethercat cards easily recovers.
It means that the EtherCAT server sends out a packet and expects a packet back. For some reason it doesn't come back in time (I think).

So the focus is on this mini-PC, a T8 Firebat pro plus. It has two network ports, both Realtek. It is small, draw around 10 W, three HDMI and three USB 3 ports. Had the network worker better it would have been good, but no.
 
The network ports areI have of course tested with the realtek dkms driver, and added boot options. It gets better with the dkms driver but there is still the occasional datagram UNMATCHED. I don't want them.

I have seen in the past that all Intel network adapter perform better than this. So I will add an Intel network adapter to this mini-PC.
What I have in mind is to replace the WiFi card with some kind of ethernet card. The WiFi is an M.2 card, size 2230.
That's the options I have. No PCIE, no mini-PCIE. Just a M.2 2230 E-key WiFi card position.


 

Hi Guys,

Thanks for feedback.

Now we added hal pins for jogging xyz in pause state.

The halui pins are unreachable from within the tpmod component.
Then tpmod has it's own hal pins for jog in pause.
 

For the one's who still want to do keyboard jogging in pause state, like plasma cnc's  :

• enable the jog keyboard hal pin.

This to prevent unwanted moves by accident.

Yes, it sound like the old firmware issue.

One known way to fix this is to reflash the firmware on a RPI4

Another possible fix is to temporarily short RPI GPIO8 to GPIO25 (40 pin pins 22 and 24)
or if that does not work, temporarily short RPI GPIO25 (40 pin header pin 22) to Gnd

Then remove the connection once the card has been re-flashed.

I bought a Mesa 7C80 from EUsurplus.com, on March 11.
I have read on mesanet.com that cards bought before 2025 would not be compatible with rpi5.
So this is supposed to be compatible as i understand it.
I have an unaltered installation from this image www.linuxcnc.org/iso/rpi-5-debian-bookwo...25-01-27-0140.img.xz

When i try to follow the write up in the Pi5 MESA 7c80 WORKING thread, i get the same error as the OP.

I do this command: sudo mesaflash --device 7c80 --addr /dev/spidev0.0 --spi --readhmid
I get this response :

Unexpected cookie at 0100..0110:
00000000 00000000 00000000
No 7C80 board found

Do i need to flash this card to make it compatible with rpi5?
Can i do that somehow from a rpi5?
If not, what might be wrong?
SPI is enabled.

Hi all,
Right now I am testing my first CNC machine. I can already toggle the machine power on and off on LinuxCNC to lock or unlock the motor of my machine. But when I press + on y-axis (the axis i am testing), there is still no response. I think it might be the motor driver problem. Can somebody help? Thanks a lot!

This is my motor driver.
www.amazon.ca/MECCANIXITY-Stepper-Driver...ps%2C135&sr=8-5&th=1

This is my motor.
ca.robotshop.com/products/nema-17-steppe...7-1684a-single-shaft

This is my bob.
www.amazon.ca/SainSmart-Breakout-Board-S...r%2Caps%2C134&sr=8-8

Thanks again

I’m at this stage noticing that I can’t change the velocity of y-axis (the one I’m testing). I think it might be the motor driver setting up problem.

ContinenteCNC wrote:

I would suggest these ones here. Do you have PCI slots available?

Moschip MCS9835CV-BA
www.amazon.ca/Startech-Com-PCI2S1P-Seria...s%2C189&sr=1-23&th=1

Sunix SUN 2212
www.amazon.ca/1-Port-RS-232-Parallel-PCI...tronics%2C208&sr=1-3

Moschip MCS9900CV-AA
www.amazon.ca/InLine-76625C-Parallel-PCI...7&xpid=zMzIe5Bgkwo7G

Sunix SUN1989
www.amazon.ca/StarTech-com-PCI1P2-1-Port...3&xpid=zMzIe5Bgkwo7G

Moschip MCS9901
www.amazon.ca/Parallel-Printer-Converter...0&xpid=zMzIe5Bgkwo7G

have a build-in parallel port PC now. Thanks!

setp stepgen.4.position-scale [JOINT_4]SCALE
setp stepgen.4.steplen 1
setp stepgen.4.stepspace 0
setp stepgen.4.dirhold 40000
setp stepgen.4.dirsetup 40000
setp stepgen.4.maxaccel [JOINT_3]STEPGEN_MAXACCEL
net zpos-cmd joint.4.motor-pos-cmd => stepgen.4.position-cmd
net zpos-fb stepgen.4.position-fb => joint.4.motor-pos-fb
net zstep <= stepgen.4.step
net zdir <= stepgen.4.dir
net zenable joint.3.amp-enable-out => stepgen.4.enable
net estop-out <= iocontrol.0.user-enable-out
net estop-out => iocontrol.0.emc-enable-in

The red text probably should be:
setp stepgen.4.maxaccel [JOINT_4]STEPGEN_MAXACCEL
net apos-cmd joint.4.motor-pos-cmd => stepgen.4.position-cmd
net apos-fb stepgen.4.position-fb => joint.4.motor-pos-fb
net astep <= stepgen.4.step
net adir <= stepgen.4.dir
net aenable joint.4.amp-enable-out => stepgen.4.enable

Note that you also need to connect the astep and adir signals to the appropriate
parallel port pins similar to this (z highlighted ):

setp parport.0.pin-01-out-invert 1
net estop-out => parport.0.pin-01-out
net xstep => parport.0.pin-02-out
setp parport.0.pin-02-out-reset 1
net xdir => parport.0.pin-03-out
net y0step => parport.0.pin-04-out
setp parport.0.pin-04-out-reset 1
net y0dir => parport.0.pin-05-out
net zstep => parport.0.pin-06-out
setp parport.0.pin-06-out-reset 1
net zdir => parport.0.pin-07-out
net y1step => parport.0.pin-08-out
setp parport.0.pin-08-out-reset 1
net y1dir => parport.0.pin-09-out
net spindle-cw => parport.0.pin-14-out
net spindle-pwm => parport.0.pin-16-out
net xenable => parport.0.pin-17-out
 

 

Here is the lower half of the report