Advanced Search

I guess SPI would tie you to an arm platform or trying to bit bang from the host PC.
SPI is not recommended for long distance runs (its only really meant to board comms), even 6 or so inches can be unreliable when approaching MHz speeds. Seen this when experimenting with a Mesa 7c81.

Serial can use differential signals if there is noise, SPI differential signals can play havoc with timing at speeds.

And in reality unless you have a real hardware serial port, the serial comms is USB (at the host PC), doesn't run in realtime......in fact there is no realtime serial driver for Linuxcnc.

Hello everyone. Happy New Year 2025.I was able to get by with pncconfig I have my two XY axes that work super well, I have the Z axis with a little bounce and above all I have the Y axis that scrolls after its movement the X and Z axes are fixed and precise. I have especially after the Estop all the axes that scroll at low speed, a few hundredths per second, I noticed that I had connected 28 V to my 7i77 card instead of 24 V would it not be a little too much for the card my power supply is closer to 400 V than 380 hence this small extra value.Could you help me to finalize my final setting. Thank you for your help. Eugene

hello
Thanks for your good work
I had a question
Why don't you use spi communication instead of using serial communication?
In my opinion, more reliable performance can be expected using spi connection

The program cannot work correctly with Cyrillic characters in the text program.
I am attaching a file with Russian characters. I'm asking for help. How can I make probebasic understand Cyrillic?
 

Danke für den Hinweis. 
Hab ich leider so aus der Standard Anleitung nicht verstanden. 

 

It appears to have been caused by this commit  in July which seems to affect the HAL Python module.
It only affects locales that use commas instead of periods in floating point numbers.

A workaround until we get a permanent solution would be to edit src/emc/rs274ngc/interp_internal.hh and change the following:

Line 998 from:
       to:
     
Line 1000 from:
   to:
   and then recompile.

Hi rodw,

SheetCAM looks like it gets the nod. Many thanks.

It does have you start by scanning the plans on a (big) scanner and into an image file (.JPG, etc.). For that, maybe I can buy time on a scanner. I do own the plans and the scan would only be for my use.

On top of buying time on a cutting machine maybe I can get my boat realized (and keeping me busy) without actually having a CNC machine.

To reiterate my very first post: I have a fair amount of *nix/device driver and kernel experience and if a need comes up let me know how I might help.

Thanks,
Tom

That was "a" problem but not "the" problem. I changed HOME_SEQUENCE to 1 and the behavior remains the same. I commented out all the other HOME_* parameters and still no change. There is still something else I'm missing.

The homecomp.comp file talks about joint._.request-custom-homing as selecting the custom homing process, and the joint.0.request-cia402-homing pin is net'ed to the x-home-request in your cia402_homecomp.comp, but does not get set from Home All, even when HOME_SEQUENCE is positive non-zero.

I tried to attach my files to the last post, but they seem to have vanished.  Here is another attempt.
 

Okay so I have the basics working and now I want to get my toolsetter doing what I need.
It is hooked up and in QT dragon I have my positions setup so it will go to the toolsetter location. Then I can do the touch plate op and it hits the sensor and backs off properly.
From what I can tell it sets it based on the workpiece height and or tool sensor height parameters in the offsets tab which is not what I want.
I just ordered an ATC spindle so very soon I will be setting it up with multiple tools in toolholders with saved tool offsets so I can set them when I change a tool and then just have it pull the tools with the saved offsets.

For the moment though my first priority is to be able to put in a cutter, set it's offset with the tool setter, zero z to my part. Then if I break a cutter or want a different tool for the next op to be able to change the tool, set height, and have that offset to the new tool is at the right height for the next op.

Then a secondary goal would be to be able to change tools manually in multi tool setups.
So basically wanting something like Gcode calls next tool, machine goes to XYZ where I manually change the tool, then machine goes and touches off the toolsetter. Then goes back to machining the next op.

Is there a good guide for doing this? I searched a bit and didn't find anything that looked super helpful.

TomAlborough wrote:

Maybe so, maybe so.

But part of me wants to use a Pi 5 for *something*.
 

You can only accomplish your object in life by complete disregard of the opinions of other people.
Aleister Crowley

Have a look at Sheetcam for all of  your CAM, nesting and scanning with its scananything addon.

I have the same question is this available?

Maybe so, maybe so.

But part of me wants to use a Pi 5 for *something*.

It would take the pleasure out of building and just turn it into a very tedious task.

I'm not sure I could make an image/picture that was not materially distorted but I will look into ways to do it.

I would like to run an option past you:

-- Tape the plans to the bed of the rig.

-- Replace the cutter/lens with a stylus.

-- I just saw a "CAM USB camera" online that gives you a view of the exact place where the (stylus) hovers over the plans. (I can not find it online right now...)

-- Then:

    -- Jog the steppers with a joystick to place the stylus over the "start" of the tracing

    -- Touch a button on the joystick to register the current location on the plans/bed

    -- Jog the steppers again to get to another point on the plans and press the button

Observations:

  -- Straight lines would be easy; curves would require help digitizing gracefully, but I have some thoughts

  -- The file of points would have to processed into a file of "cuts".

  -- Plans involving multiple parts would have to be digitized a part at a time. The parts would then need to be laid out on (a 4 x 8 sheet of stock say).

Thoughts?

Thanks,
Tom
  ​​​​