Advanced Search

You can also just add ~220 ohm series resistors in the PWM lines

The main hazard is ground differences/HF noise causing negative
input voltages with unlimited current. a series resistor will protect against
this.

Yes I'll take care to put a BOB betwen P3 and the hardware until I grab a specific card from mesa store

Thanks a lot, have a good day

Can't see an oword problem, but have added some oword path checks to help to see if it's just a path problem. qtdragon will complain if the oword path is not found.

Someone loaned me a Probotix-based CNC Router. I need to make up some very simple wood frames, but I cant seem to the the controller to recognize the router table. I realize that I know very very little about LinuxCNC, and would rather contract and pay someone to help me. This could be local, in Novato, CA near San Francisco, or by remote desktop (Teamviewer, Anydesk, etc.). Could someone make some time to look at the setup and get me started?
Thanks!!
Anthony (415) 883-1476

You probably run Gmoccapy 3.4.6.
I suggest to update LinuxCNC to the latest version, then you will find a new setting called "G-code theme" where you can select another theme for the G-code.

Ok I pushed work to master to allow selecting auto switch to MDI for macro buttons and HAL pin macros on Qtdragon's setting page.

I didn't get a change to push it to the other Qtdragon variations.
I have not looked into the O word problem yet.

No USB controllers do not work with LinuxCNC due to inherent latency issues and not being "real time".
You should get a Mesa board, not UC300 whatever, it is natively supported in LinuxCNC, be it PCI or PCI-E or Ethernet versions, and their support is by far the best on planet Earth.
Take some pictures of the control box and post them here, maybe you can get away with just an old PC with a parallel port, or an add on parallel card costing 10-15$.

I was at it again today.
Threading does not work again, absolutely the same behavior as before.This time I could try G33 with the problem present. Running the exact same code multiple times, every subsequent run cut slightly to the right of the last by very even amounts.Now I am really confused. It worked a few days ago. That day it worked over and over, and now it does not work at all.
RPM does not seem to make a noticeable difference, or at least it does not work no matter how low I go.I don’t even have an idea what that tells me. The hardware is obviously capable of working. Is it some intermittent contact somewhere?The encoder being the problem is really the only thing that makes sense to me, but all tests I did point to it being OK.If anyone has an idea what I should test to find this, I would highly appreciate it.

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.