Advanced Search

Oh wow... I've been racking my brain because of a spelling mistake...

thanks tommy, gonna give that a try. i have some old parts lying around and i think i will stretch some cables and give it a dry run this afternoon out in the shop. when this is done, there will be 4 machines all with mesa cards and if this works out it will make life alot easier with just one station to control all of them. ill post after i run some tests...

oh and usb 1.1? thats some old stuff from the "plug and pray" days!

There should be no Base Period in use for Mesa boars, only if using a parallel port together with them.

Ini file, axis y / joint 2 section still says AXIS Z
Andit is miss spelled, should be COORDINATES

Easy, you have the hardware, connect stuff and test by running some gcode in "air cutting" mode, see if it drops the connection.
As for throughput, i have a very old USB to LAN adapter that i am pretty sure is USB 1.1 and it works fine for Mesa directly connected to it.
I also tested laptop to Mesa through a gigabit switch and had no issues but those were the only things attached to the switch.
And i would venture a guess that any access point will fail miserably and drop connections even if PC and Mesa are using LAN, not WiFi, at any point any request from WiFi goes to PC or Mesa and vice versa.

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.