Advanced Search

Good morning,    i have most of my hardware.   i have been able to get a very basic 1 x Clearpath SD 2321s servo to run on the linuxCNC  jog.

My question Every time i shut down the system, my Stepconfig  saved configuration disappears, and i have to re run stepconfig to get back where i started.     The stepconfig program is set to save , so i get a shortcut for the files and a shortcut to open linuxCnc with that config.    

i am guessing but is the failure to save the configuration due to the linuxCnc being run from a thumbdrive image?

How can i get the config to save thru a power cycle?

I am ready to move my little test setup to the actual machine to see if the new servos are going to be strong enough to get my mill table moving.
The old servos were SEM MT304,,,   weighed 15 Lbs.   
The new servos are tiny tiny in comparison and weigh about 2 lbs or less

thanks
 

You still need to connect OUT4 and OUT5 to the appropriate 
spindle pins in hal (via the TB3 tab in pncconf)

What version of LinuxCNC do you have?

I was testing with the current release (2.9.4)

I also noticed that you need to check the "Show Advanced Option Pages"
checkbox on the pncconf start page

Maybe pass the position-command through a limit3 HAL component to limit velocity and acceleration?

The VFD on my high-speed spindle feels a bit like this, it starts sluggishly then seems to nearly get stuck, but in my case it then accelerates away to commanded speed.

Make sure that you really are getting 10V (or whatever) on the analogue voltage input to the VFD using a multimeter. (Also check the polarity...)

You could try operating the VFD with a potentiometer in the conventional way to check if the behaviour is the same.

I was wondering if a conformal coating would help, and found this thread, which may have some relevant ideas:
electronics.stackexchange.com/questions/...nd-will-this-prevent

If you are using CSS then this might be more complicated than it first seems.
The PP would need to calculate the spindle speed at the start and end of the sequence of feed moves and choose a spindle gear appropriately.

My own lathe handles this in HAL, but certainly not optimally. It will often do a gear change at the end of a facing cut, then change back at the start of the next cut, which isn't ideal.

Rather than preventing motion altogether, you could simply put a message on the screen when the probe fault output is set, using the "message" HAL component.

That said, how much of an issue is it if the toolsetter is disabled when the probe has a fault?

If the probe has a specific tool number, you could potentially add that to your logic.

Is the "3D plotter" specific to ProbeBasic?
If so, you might get better answers on the ProbeBasic part of the forum.

If "call" is the "unknown word beginning with "C"" then I think that this must be a ProbeBasic thing, as I have never seen the other UIs (which mainly share a previewer) have a problem with subroutine calls.

I am not entirely clear what problem you are seeing, but you should just be able to set the F-ERROR limits for the X axis very high, and then no errors will be raised.
If the problem isn't following-error trips, then I think we need more info.

Thank you Erick, i just talked to them and everything is OK, the left side angled not unloading is a safety feature as i thought, so the idea of leaving a straight cut in front of it with small tabs worked like a charm.
And we do have a pallet of manuals, mostly in Italian language and mostly not exactly for this machine as the pictures show the old version of the software, but still they did help a lot initially.
Again, thank you very much, i do appreciate the offer.

Main menu > preferences > appearance , chose a white theme, close and start LinuxCNC.
On my monitor i can see and read everything easily, but on most VA or TN monitors it might be very hard to read.
Try setting the brightness and contrast on the monitor, see if that improves things.

PS: Auf meinem Bildschirm ist das Fenster nur ein Viertel in der Größe!

Moin,

ich habe ein ziemlich triviales Problem: Wenn ich "halshow" (und div. andere Programme) aufrufe, kann man fast nichts erkennen, weil die Farben alle extrem dunkel sind  (s.u.). Ich finde nicht heraus, wie man das ändern kann. An dem verwendeten Theme liegt es anscheinend nicht! Kann mir jemand einen Tipp geben, wo man da hin greifen muss?

 

Vielen Dank im Vorraus
Chris

hallo michael,

info zu flatpak über terminal... 


weiter bun ich noch nicht gekommen