Advanced Search

Hello, can you show me how to read the S command and what you changed.   

Thanks, Andy, you steered me in the right direction.

GPIO13 would not work at all, continuing to research that.

GPIO25, once pullup=GPIO25 was added, works.

I only have 1 limit switch setup, so I'm fully functional with the official image, Byte2Bot board, and my old Probotix motor driver setup.  Attached are the .hal and .ini files that worked, and my config.txt

 

Yes ethercat OP state is one thing, cia402 enable state is another thing (on top of OP state)
Linuxcnc need to go through every step to enable the drive. Skipping steps or shortcuts are not allowed.
But I have never worried about that, the cia402 component does that automatically.

almost forgot about the job buttons, those are now also dynamically set to display the new options for xyzbc as well as the offsets page ui bits as can be seen in the image below.

just waiting on a tester and need to update the docs once everything tests out and I will push the update out to the apt develop version of PB for install and updating.

 

 

Have to thank you for all your help. I finally got this running very well following my above plan. Freecad is great for many things but not so sure it is the best for programs with subroutines.
Again, thanks for your patience.

Routerworks

ok so i spent the morning and afternoon updating some things with dro display, it is completely modular now in probe basic in the test branch, it includes preconfigured dro displays for the following:

xyz
xyza
xyzab
xyzac
xyabc
user (predefined with xyzabc)

this should allow users to configure however they need to for a multitude of configurations.

it will be activated in the ini section with the addition of the following two lines:

USER_DROS_PATH = user_dro_display/
DRO_DISPLAY = xyzac 

(xyz, xyza, xyzab, xyzac, xyzbc, user) these will be the available options with "user" being editable and stored in the config folder same as usertabs/buttons etc.

it is completed but i need a tester to pull the "dro_display_dynamic_loading" branch and just verify all works on a diferent pc than mine before i send it live as an update.  it will require users to update their config if they want to run anything besides xyz which it will default to if no ini entry is used.

thoughts/help testing?

Thanks,

Chris

 

Thank you, appreciate the confirmation.

Yes, step/dir spindle control is possible and supported.
You may have to do some minor hal file editing depending
on which configuration utility you use.

Where it gets more complex is when you have a combined
spindle/C axis.

Hey folks, I'm on the verge of replacing the Masso G3 running my 3 axis mill with LinuxCNC likely paired with a Mesa 7i92S board.
It's a basic machine X, Y, Z axis configuration with DMM DC servos and DYN2 drivers for the axis. Three inductive limit switches, a tool setter and a 3D probe. The one possible wrinkle is that the spindle motor is a Bergerda servo motor currently controlled by step and direction. I think it can also be controlled via 0-10v but I'd prefer to retain the step and direction control.
Is LinuxCNC configurable such that spindle control can remain step and direction?

I tried using RoseKins, and it does not work to drive the 2nd spindle either.

Thanks that worked perfectly

I was using the following which does not work for my purposes.

    if self.task == 0: # ignore the preview interpreter
        yield INTERP_EXECUTE_FINISH

After removing (if self.task == 0: ), it works.

 

you can use



NOTE: No 'self.execute(..)' command can be used after this.

 

linuxcnc.org/docs/html/remap/remap.html

 

correct, this is explained int he instructions to remove the comments or you will receive errors.

 

Gave the new axis-like UI a spin this morning. Looks and feels good. I noticed the buttons (e-stop and machine-on, in particular) don't have the 3D "I'm pushed" look when they're pushed released. A small thing, but there's no other visual way to tell the state.

I need to come up to speed on modifying these UIs, so I can make changes and flesh it out. (I know, I know... watch the videos. ) The big missing piece for me right now is a probing/touch-off screen. My current probing setup is pyvcp, so clearly it will need to be redone. But I'll bet you already have fully functional probe screens just waiting to be dropped in.

cmorley wrote:

There is a slowly developing version for qt screens:
github.com/LinuxCNC/linuxcnc/commits/qt_ncam/

 

To install NativeCAM from that site, should I download or clone all the linuxcnc package of files?

Regards
Giovanni