Advanced Search

I was trying to have this automatically set so that upon login/startup, it is set.

However, Im good with your solution. Only thought would be if I can activate with a button on screen as well. Or better yet, connected to one of the existing buttons like Probing screen. What would be the best way to achieve this? Would that be via User buttons, and if so, how is thee M101 called for use in a User button?

If it is just "settings" I just hope they're better than the compatibility layer that the rpios uses.

Thank you PCW for your unconditional support.

is that just on acceleration, or is that lag on a straight line?
what is is the acceleration?

20 microns if its only on high acceleration and speed is "a good starting point' i think. shows much promise.

for comparative reference

My JMC ihsv57's were tuned to about 6 or 8 microns, at 0.3g and 1800rpm (as fast as they would go)

My omron ethercat servos are now tuned to like 4 microns in in acceleration moves at 1G and 1 micron during constant speed.

Made suggested change...another issue.  The provided line was in the file from the conversion script and I totally missed it as I was preparing INI and HAL files base in Imperial values rather than metric.    However, another issue arose: program could not find variable INPUT_SCALE.  I believe this is the updated name for the old (2.7.14) STEP_SCALE.  I changed the INI to reflect this and tried again.  Still an issue.

Notably as I have been working on this configuration conversion.  I have encountered several apparent variable name changes between 2.7.14 and 2.9.4,  Unfortunately I did not create a list which at this point would have been helpful.

In any event here is the set of documents for my latest attempt:

The "Z" signals are needed if you want to home to index.
(for more accurate homing)

Yes, normally you would connect the encoder ground at both the
drive and 7I97T end.

Dont know if this help but I managed to tune the following error to around 20 micron at 3000mm/min. The drive is non ethercat, just regular step+dir. Tuning it was quite trivial. Turning speed forward gain to 100% should reduce the following error significantly

Good on you for saving another 400E,
Mark

Yes, i checked the files twice but could not find anything strange, so try using the "show hal configuration" from the "machine" menu to watch the charge pump pin if it gets active when you enable LinuxCNC.

unknown wrote:

Another thing to think of, what happens when X11 support is dropped in favour of Wayland ?
The GUIs that rely on X11 libs.

Tho it received no interest apart from 2 forum members I managed to build a Devuan ARM image, no systemd and their CoC is fair to all, basically just don't be a dick to anyone.

The devs are aware of this. There are some Wayland settings to work around it.

emcPT wrote:

I did some research about the uspace and the general information is: uspace is not intended to control real machines, but used for simulation.

This is still true? Because if it is, I cannot use it as the intention is to really control the machine that was previously working.
Thank you

The Debian linuxcnc-uspace package includes the PREEMPT_RT kernel as a dependency so there should be no need to install anything else.
These new distros can be  a bit problematic. my notes here should solve any latency issues.
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing

 

Please see this post:
forum.linuxcnc.org/9-installing-linuxcnc...-4-5?start=40#323701

Wifi setup is by running

Be sure to edit to choose option 5 "Edit wpa_supplicant" with your country code, ssid & password.

To setup network for a mesa fpga Ethernet card, choose option 6 "Edit interface" and modify eth0 to match post above if you have jumpered the board for "FIXED FROM EEPROM"
If you have jumpered for "FIXED 192.168.1.121" replace 10.10.10.100 with 192.168.1.100.

If your home wifi network is on the 192.168.1 network, use the 10.10.10 network for your Mesa card, refer to you card's manual for jumpers to change.

After config reboot
To check the network type in a terminal
Taken from 7i92 Manual

A final note, there is no network notification applet for the desktop, so you will not get any notifications when the network connects, disconnects or reconnects.

in your hal:
change this line
to: