Advanced Search

spumco wrote:

Lcvette wrote:

Are you changing back to manual mode to enable jogging? When it doesnt complete a subroutine it will be in auto mode.

Maybe not Probe Basic specific... but is there a way to force manual mode via the 'on_abort' process?  So if any of the subroutines (probe, ATC, etc.) fails the machine jumps to manual mode.

If there is a way, that might be a nice-to-have addition to the PB config(s)... don't leave the machine hanging in an aborted auto mode.
 

That would be a great addition to Probe Basic.

If you have a 7I97T you need to have the latest mesaflash

The LinuxCNC ISO includes  version is 3.4.9 which does
not support the 7I97T

github.com/LinuxCNC/mesaflash
 (build instructions on bottom of page)

That means the host computer has a latency issue of some kind

Common causes:

Power management/speed-step/Turbo modes/C states >C1 enabled in BIOS

Network hardware issues with Ethernet connected cards

With Intel MACs you need to disable IRQ coalescing (man hm2_eth)

With Realtek MACs and the LinuxCNC buster release you may need to install
the DKMS RTK8168 driver as the driver included with the shipped kernel is broken
 

I don't know why those modes aren't shown in my version. I just downloaded it, followed the installation instructions and it looked like this. 


How can I add them?

Todd wrote:

There are no "special" parts there that I want or are worth much on their own. It is all of the time I put into building it that I hate to see go for naught. (There is a lot of "me" in that machine.)

Gut-punch understood.

Ismacr63 wrote:

Lcvette wrote:

Are you changing back to manual mode to enable jogging? When it doesnt complete a subroutine it will be in auto mode.

jog mode is activated.

"JOG" is not a mode.  Even if the on-screen jog button is highlighted, LCNC can still be in MDI or Auto mode.

It looks like your screen has been edited to remove the mode indicator-buttons... or you've got a different version.

I've circled the mode buttons in the attached pic.  You can also open halshow, and under 'halui' add the various mode indicators to the watch list to see what mode LCNC is in.

If, after a subroutine is aborted, LCNC is in Auto mode, you won't be able to jog regardless if the GUI's 'jog' button appears active.

 

There are no "special" parts there that I want or are worth much on their own. It is all of the time I put into building it that I hate to see go for naught. (There is a lot of "me" in that machine.)

Lcvette wrote:

Are you changing back to manual mode to enable jogging? When it doesnt complete a subroutine it will be in auto mode.

jog mode is activated.

   I keep getting the following error message on startup of Linuxcnc.Is there something I need to change on the configuration?

thanks for the answers, I'll start by saying that I'm not very good at configuring linuxcnc and what I came up with is the result of the guided procedure and many tests to make everything work. I do it as a hobby even though I am a milling machine by profession. I don't know if it is possible to move the motors via software but I don't think so, but mechanically everything runs well and everything is lubricated. I also tried inverting the axis motors and even loading the parameters of other axes but nothing changed. I add my .ini file configuration of the x and y axis but I don't see huge differences, but the x and z axis are perfect, the x gives me problems. I have a printnc that I upgraded myself with aluminum components that has a dual motor y-axis and all cables shielded. I attach the ini file and the hal file so you can see what I configured so you can tell me if I'm wrong. If I made a mistake, please tell me in detail what I did wrong so I can understand where to correct it. you wrote to me to try to put 2000 on the direction setting and holding times, but I don't really know which string you are referring to. thanks for your help.

Losing/gaining a fixed amount per reversal may indicate a a step timing issue
with direction (or inverted step polarity).

You can easily check this by setting long direction setup and hold times
(say 20000 ns) and seeing if the issue goes away.

Also in general unless it limits your maximum step rates I would set the
step time to double the manufacturers minimum step pulse width.

will try tomorrow thx

Lcvette wrote:

Are you changing back to manual mode to enable jogging? When it doesnt complete a subroutine it will be in auto mode.

Maybe not Probe Basic specific... but is there a way to force manual mode via the 'on_abort' process?  So if any of the subroutines (probe, ATC, etc.) fails the machine jumps to manual mode.

If there is a way, that might be a nice-to-have addition to the PB config(s)... don't leave the machine hanging in an aborted auto mode.

Todd wrote:

most likely dump it at a dispersal auction after they take possession of the property

Buy it at auction and strip out the good parts?  You know nobody else will bid on it.

Or make an offer to the existing owner to purchase the components out of the machine before the deal is finalized.

Sorry to hear about the job and situation.

ich danke dir das ist genau das was ich gesucht habe. da gibts sogar noch die 2.8.4. warum mit der alten version alles geht udn mit der 2.9.3 nicht ich habe keine Ahnung dazu bin ich zu wenig computer nerd