Advanced Search

I wonder, is there a Raspberry HAT that can direct interface with a stepper driver ?

Thanks
Jonh.

I'm using a Raspberry Pi 4 to drive a Mesa 7i96.   For unknown (as yet) reasons, I can't reliably run without errors unless I bump SERVO_PERIOD to 2000000 (i.e., 2ms).

What affect will this have on machine operation?  I sort of understand what's scheduled to run in the base thread, which of course is largely (completely?) irrelevant now that I have the Mesa.  But I don't have a good mental model for what runs in the servo thread, so I don't have a good understanding of what happens to operation/performance if it only runs half as often as usual.  Where would the difference show up?

Until recently my mill maxed out at about 40ipm, so absolute performance wasn't really a consideration.  I've upgraded to a machine capable of at least 80ipm using Grbl, and initial tests with LinuxCNC and the Mesa card indicate 100ipm may be fine.  So now I'm wondering if I need to start worrying more about that servo thread.

paul

Yes, it seems like some encoder option is not set correctly.
Clearing the count on every index really makes no sense for
general encoder use.

I don't really know but it seems to be set in the ini file:

 

It works. Thank you.

Thanks, PCW for this example! I try this out the next days. 
or2 is not used actually. 3D is NO and WZL is NC, otherwise I would have put them both in series.
I will see if I have to delete the -not for the 3D switch.
Thanks a lot and have a nice weekend!
Hanno

I've installed everything.

Also:
sudo apt update
sudo apt --fix-broken install
sudo apt install python3-qtpyvcp
sudo apt install python3-probe-basic

cd ~
mkdir dev
cd dev
git clone github.com/Lcvette/qtpyvcp-bookworm-installer.git
cd qtpyvcp-bookworm-installer
./install_for_qtpyvcp.sh
./updater.sh

And yet I still get this error:

Traceback (most recent call last):
File "/usr/bin/probe_basic", line 8, in <module>
sys.exit(main())
^^^^^^
File "/usr/lib/python3/dist-packages/probe_basic/__init__.py", line 20, in main
qtpyvcp.run_vcp(opts, VCP_CONFIG_FILE)
File "/usr/lib/python3/dist-packages/qtpyvcp/__init__.py", line 26, in run_vcp
run(*args, **kwargs)
File "/usr/lib/python3/dist-packages/qtpyvcp/app/__init__.py", line 129, in run
launch_application(opts, config)
File "/usr/lib/python3/dist-packages/qtpyvcp/app/launcher.py", line 78, in launch_application
loadWindows(config)
File "/usr/lib/python3/dist-packages/qtpyvcp/app/launcher.py", line 230, in loadWindows
window = _initialize_object_from_dict(window_dict)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/qtpyvcp/app/launcher.py", line 210, in _initialize_object_from_dict
return obj(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/probe_basic/probe_basic.py", line 53, in __init__
self.load_user_tabs()
File "/usr/lib/python3/dist-packages/probe_basic/probe_basic.py", line 87, in load_user_tabs
user_tab_folders = os.listdir(user_tabs_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Error 2] File or directory not found: 'user_tabs/ # REQUIRED Setting for Probe Basic'


Where is the 'user_tabs/' folder supposed to be? I've moved it to:
linux/configs and, just to be on the safe side, to linux/configs/My_Machine

Try this:

 

Something like:

loadrt or2
addf or2.0 servo-thread

net probe-wzl  <= hm2_7i76e.0.7i76.0.0.input-08-not => or2.0.in0
net probe-3d   <= hm2_7i76e.0.7i76.0.0.input-09-not => or2.0.in1
net probe-in     =>  motion.probe-input <= or2.0.out

Notes:

This assumes the "or2" is not already used

(if its already used, you need to add a new instance with the names or count stanza)

Also not sure of the individual 3d and wzl polarities

Hello,

I need read HAL pin in Python. It is not problem for me:
If the "HAL pin" exists, there is no problem:
The problem occurs when the "HAL pin" does not exist:
I would first need to find out if this "HAL pin" exists and then find out its value.
But I dont know How.

1)
Python HAL interface can check only component, not only "HAL pin".
www.linuxcnc.org/docs/html/config/python-hal-interface.html
2)
Maybe I could use Python's "Try:"
But I don't know how. I would need to check in initialization if the pin exists and store it in a variable:
halui_cmd_exist = True
or
halui_cmd_exist = False

Thanks again!

Looking at the file you linked, I see ways to simplify some parts in my remap.

This is resolved now. Only the tool length sensor's side will remain scarred

At least my understanding about emccanon.USE_TOOL_LENGTH_OFFSET() is that it's supposed to be the equivalent of G43, as it issues the same EMC_TRAJ_SET_OFFSET message. Apparently, it does not fully update the initial state.

note that 'G43' reads the tool-offset values from the tool table:
github.com/LinuxCNC/linuxcnc/blob/6c4303...erp_convert.cc#L6202

and calls emccanon.USE_TOOL_LENGTH_OFFSET() in line 6280:

BUT it also sets 'tool-offsets' in line 6299:

So it seems that you will have to handle this in the remap.

PCW, thanks a lot for the advice with the smaller resistor! I found one 2.2k with 1W in my boxes and used that today and voilá, it works as it should. Problem solved, I hope. (Don't know if I need noise reduction)Guys, I have no idea how to use sth like mux or mux_generic. I wouldn't even be able to use two inputs - but just out of curiosity , how would you do that in a HAL file if i would use an OR2:
 loadrt or2 count=1
net probe-in     <=  hm2_7i76e.0.7i76.0.0.input-08-not    
net probe-in     =>  motion.probe-input
and the second input hm2_7i76e.0.7i76.0.0.input-09 ? my programming scills are beginner level...
(Yes, I read the example in the LCNC HAL Examples to OR2 but I cannot convert that for my problem.)

Thanks and best regards!
Hanno
 

My guess would be that your change of tool-length is possibly not reflected in 'tool_offset.tran.z'.

You're right, it's not updated. Setting `self.tool_offset = pose` manually resolves the issue.

Am I missing some call to auto-update it, or does it have to be handled in the remap?

thanks Chris.
I will try 'em both.
Buildbot2 has a new master deb yesterday.
looks like your changes are included...

* qtvcp -action tool button: add dro/dtg/large font controls
* qtvcp -gcode graphics: add dro on/off view signals
* qtvcp -qt5_graphics: add enable dro functions
* qtvcp -qt_action: fix dro view keyword, add DTG keyword