Advanced Search

alright now, any questions?

aDm1N wrote:

I started from scratch with the standard examples. I made some adjustments, and now Remora Input 4 is responding. However, this only happens when the emergency shutdown is disabled in the GUI. So, Remora probably only starts working after that.

that makes sense.
refer to tuxcnc example

I havent tested it, but this looks like what you need to do. you need to modify the portion of your halfile that already references it

DarkPhoinix wrote:

I have recreated the problem with the function generator. Now I am sure the problem lies in the configuration, or so I believe. For now, I would like to know which parameters I need to set to have the same parameters for frequency and pulse times in the hal and ini files (like pulse 1,000,000ns frequency 988Hz). Thank you again for your patience!

refer to the previous posts. replace the stepgen in your config.txt with the DMA stepgen. Make sure the step and direction pins are the NVEM one. The step time and space parts are what you need to configure. I dont know the units. start at 1 and 1 and go up from there.

I need hardware suggestions.  There seems to be a gap in my knowledge, and in my research.

I just got a new CNC router, and it came with a Grbl-based controller.  I always used LinuxCNC in the past on my DIY machine, and I can already tell that I'll probably be happier if I switch to LinuxCNC on the new one.

The most recent incarnation of the old machine was driven by a Raspberry Pi and a Mesa ethernet card.  The Mesa was connected almost directly to the limit and estop switches, and the step/dir lines went to a quad stepper driver board I got from Sparkfun a long long time ago.  The wiring was a horrible rat's nest of jumpers running between pin connectors glued upside down to a plank.  (I'm not exaggerating.) And I don't want to use the Sparkfun board again, for various reasons.

At some point I'm going to want to use the Mesa card with the new machine.  But what I'm picturing, that I don't have, is the "interface" board.  It needs to take 24V power, and have 3 or 4 of those little 16 bit stepper driver modules.  And it needs to have a bunch of screw terminal strips, set up to logically simplify the 6 or 7 pairs going to switches, the 3 or 4 connections to the motors, and all of the interconnect to the Mesa.  Basically what I want is an XYZ CNC router breakout board, with drivers.

But all I can find is complete controllers:  all of what I described, hardwired to an ATMega328, or ESP32.  Or, all of what I described, in the form of an Arduino hat.  Better, but still not very Mesa-friendly.

Can anyone point to the product I'm looking for?  Or tell me (nicely what I should be looking for instead?
 

 

 

Estop is the same way. With Estop, we are connecting a remora.input to LinuxCNC estop. Estop is a very subjective thing, and varies between setups. They can be complicated and require more hardware. Murphy has posted a simple example, and tux from a few pages back has posted a more detailed one.

Notice how the inputs are different on each of their different estops, which makes no difference because we are connecting remora.input.whatever to linuxcnc estop.

Tuxcnc is more complicated, He is using LinuxCNC components (not remora) to configure the estop logic. it includes a latching component, I assume he has one of those red buttons. Im not as knowledgeable with all the estop logic, as I live dangerously. The estop loop is a function of LinuxCNC and you need to connect it to remora in a way that suits your setup.

Sorry about that, I'll take a look tomorrow.

We have 3 phase power in houses, always, rated at 3x380V +-10% and can pull 16A at home from any plug, 32A in workshops/garages.
Lately the local provider started complaining if we pull over 15KW over long duration's, i do not blame them, we have 100A at our disposal.
To spite Americans (since i still refuse to go there despite being granted a Green Card 17 years ago), we can charge a Tesla at home with 22KW on any socket around the house, 60KW if we push it!
And that is with no permissions or requests or installing superchargers!

grijalvap wrote:

I understend what you mean but I want to keep the temporary tools because they are in the GCODE file, the operator don't has to select.
 

If you set the cut parameters up correctly (eg replicating sheetcam toolsets in qtplasmac by importing the Sheetcam tools), the user still won't need to select anything. Instead, Sheetcam will pass the tool number to QTplasmac in the gcode and it will retrieve the corrrect settings. Keep sheetcam the master of toolsets and update QTplasmac if you change settings.
 

 

here is a before and after

 


observe both configs. they are mostly the same, but some pins are different.