2.9.2

I press this to enter the editor within Linuxcnc.
I have changed the editor in the ini from gedit to mousepad with no change. 
 

@andrax
I created a new configuration using your templates for .ini and .hal files from the A6 Absolute Homing topic. The .xml file is mine and I deleted all of the SDO configurations. The axis is named "X" as you suggested. Attached are the configuration files.
The names of the pins are according to your .hal file, nothing is changed there. I had to make some changed in my .xml file to match.
Now, I opened and closed LinuxCNC a few time and the coordinate of the axis seems to save after each time the machine is closed. When I press "Home All" button the axis is immediately set homed and coordinates does not change.
Let's start with the custom CiA402 homing step by step. I attached two pictures one from .ini and the other from .hal file. What I described as "default" is the default configuration settings as if homing was executed. My question is, when I uncomment the "CiA402 homing" rows in both file, should the "default" rows be commented?

Howdy!  I have a DD UC300 installed in my CNC router.  I use DrufelCNC as my software interface. I like the software, but it is limited in features, support and is too expensive for a licensed copy.  I read an old thread indicating that a USB interface has a latency problem and that only the ethernet version (EC300) is supported by reflashing the controller.  Is this true?  Should I upgrade to the EC300 or is there support for the UC300?

Thanks in advance,

Rick  

The entry for python is missing in ini file. In my config, its after [RS274NGC]
Make shure toplevel.py is in the path, and  stdglue.py if needed for remap


[PYTHON]
PATH_PREPEND= /home/jef/linuxcnc/configs/Python/
PATH_APPEND=  /home/jef/linuxcnc/configs/Python/
TOPLEVEL= /home/jef/linuxcnc/configs/Python/toplevel.py



Edit:
I was wrong with the python entry. PYVCP panel works without that

The problem is that python 2.7 which you use was deprecated with the release of Debian Bullseye in favour of Python 3. The only solution is to rewrite you scripts using Python 3. Python 2.7 and 3.0 are not compatible.

You could post your INI-file, a screenshot or whatever command you use to start your G-code editor.

Brilliant video Adam! Nice repair.

How did you manage to connect to the drives?I’ve installed the software, but I can’t get a connection

7I95T firmware with 6 PWMs on P1

(If you need just 4, use num_pwmgens=4 in the driver command line)

 
 

Thank you. Will try to pursue your suggestions tomorrow.

I definitely hear you on the stock waste and that may be a good reason to increase my guide bushing axis to be 18 inches, however, I have a method where the actual full headstock length will not be all waste, based on how my stock will insert into the drive servo, I will get about 40% of the tag 5c headstock as usable stock, so knocking it out from 5 inches to around 3 inches.

So you are saying that with a traveling steady rest and gang tooling, I should be able to have every lathe side cutting tools (ignoring drills and boring bars for now) be able to cut right at the entrance of the bushing? I am trying to imagine this. If it is possible, in that case, during a tool change, I just need the guide bushing axis to retract the stock all the way back, and only then cause the cross slide to move to the new tool location, then the stock pops back out of the bushing and cutting proceeds? I need each lathe tool to have its cutting edge right at guide bushing entrance.

My issue is with each tool holder, your actual cutting edges will not all line up, for example, I dont want my 55 degree side cutter to be cutting right at the bushing, but my parting tool has to cut 5mm beyond the bushing just based on where the cutting edges line up in my taig tool holders.

Also, if I add a Y axis and live tooling, in that case would you recommend the W axis?