Advanced Search

 

 

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.

Pgain and ff1 and deadband are parts of the remora stepgen and used to tune motor control/feedback. feedback control has nothing to do with encoders or input from the motor. it is an internal math shit connected to the stepgen to tune motor position control like you would a servo.

regular stepgen and DMA stepgen have no difference in LinuxCNC. The same concept as inputs applies to the stepgen/dma stepgen. In the Config.txt you tell the MCU that pin P1_22 and P1_17 is step and direction of joint 0, which is remora.joint.0 which is connected to LinuxCNC joint.0

The DMA stepgen is a faster hardware based stepgen and requires dedicated hardware pins. LinuxCNC does not know if you are using DMA stepgen or regular stepgen and it does not care.

Looking at the EC500 DMA stepgen config, we can apply the same concept to the NVEM config.txt The config.txt for your specific board, and is just a way to tell the remora what pins do what. The default stepgen is regular stepgen because it is less to tune. If you want to change your stepgen to DMA stepgen, lets compare the config.txt DMA stepgen and apply it to the NVEM config.

 

If there are no hardware conflictions (there arent in this case) we can go about changing the stepgen to DMA stepgen. In this case the pins are the same for both boards. so replace your entire stepgen with the DMA stepgen and make sure the pins match the pins on your board

 

The config.txt file tells the MCU which pin is going to do what. so Pin P4_20, the imxrt1052 MCU pin, is assigned the title of remora input 06 . when pin P4_20 is triggered, the MCU tells remora that remora.input.06 is triggered.
Not to confuse things and its hardware restrictive, but you can make "remora input 06" to be whatever pin you want it to be, it doesnt matter what pin is input 5 or 6, but it has to match up.

The remora.hal file connects remora pin remora.input.06 to LinuxCNC pin joint.0.home-sw-in (this is the x home switch) So when pin P4_21 is triggers, it tells remora that remora.input.06 is triggers, which triggers LinuxCNC joint.0.home is triggered (x axis homing pin)

the remora.hal and LinuxCNC do not know if you have an NVEM or an EC300 they do not need to know and they do not care.

spincycle wrote:

I assume the procedure is similar for newer drives if running analog?

Yes.

spincycle wrote:

I would tune the velocity/torque in the drive software, then tune position through Linuxcnc.

Yes.

spincycle wrote:

It looks like a few of the modern servo drives I've looked at have encoder outputs. Those will just run back into a Mesa card like the 7I97?

Yes.
3 for 3, nice!
New drives can also be controlled by step/dir and also have encoder outputs, and those can again be used in LinuxCNC.
And there are several boards from Mesa that can be used, not just 7i97, a lot of combos there so when you are ready to order stuff, ask here first as we have the Mesa Master with us here, always, in the form of PCW.