Advanced Search

DRO updates to the inputed position about a second after .1 inches is inputted and the motor continues after that. The DRO doesn't update again until another input is entered. 

Does the DRO show movement when jogging should  stop?
 

No, I don't know how to change log level even.

Fresh git clone of libusb1.0, configure and make.
Fresh git clone of linuxcnc.
It has been the same behavior/problem with the libusb-1.0 via apt in debian.
This is a problem since a long time, years.
And this N100 PC is relatively new, latest debian and don't have any history.
Except the linuxcnc config, it is the same.
Hard to find something that sticks out.

I provoked the xhc a bit. Easily crashes with wrong loop setting. But it now recovers after three seconds.
This is a situation I can live with. It would have been better with no crash. Until then, this is fine.

The modification I made was in libusb1.0.
What I see is that if one setthe problem will not appear, the callback function pointed to by context->log_handler will not be called.
Do you know if this can be done in the xhc component code?
It would be good to use std libusb1.0 libs.
 

All the results have been done with the AXIS GUI inputs.

Does jogging via the GUI work?
 

I made this tool manager for the second generation QtDragon, but there's no reason it couldn't be a standalone application. Currently, you can assign tools to groups, such as Drills, spiral upcuts, whatever. Each tool can be assigned material specific cutting parameters and the running time for each tool is tracked according to how long it was in the spindle while a program was running. The linuxcnc tool table is the source of truth and tools can only be added or removed by editing the tool table. The database can be exported to csv or html.  I'm not a machinist, so this was only a guess on my part about what kind of data to record. Looking for suggestions on features, changes, etc. Regards.
Jim
 

 


Note that you can download the latest Spartan6 compatible version of the Xilinx tools
(ISE Webpack 14.7) for free but you do need to register.
 

Well unfortunately, that will not fit.

This fits: 



(7I44 with 4 sserial ports and 4 BISS channels on 1 and 7I52s (6 stepgens 6 encoders) on 2)

And this  fits: 

 

(7I44 with 8 sserial channels on 1 and 7I49 on 2)

But 7I44 with 4 sserial ports and 4 BISS channels on 1 and 7I49 on 2  does not fit.

Options:

1. Trim uneeded interfaces from last option (PWM.BISS, sserial channels etc)

2. Use two FPGA cards



 

Hi LinuxCNC community,I am running a Mesa 7C80 via SPI on a Raspberry Pi 5. Because my main axes and spindle are handled over EtherCAT, I am not using the standard StepGens.I need to drive three linear coil motors that require a standard 5V hardware PWM signal. Could I please request a custom bitfile that replaces the first three StepGens with PWM Generators?Specific Routing Request:

• TB7 (Normally StepGen 0): Replace with a PWMGen.
• TB8 (Normally StepGen 1): Replace with a PWMGen.
• TB9 (Normally StepGen 2): Replace with a PWMGen.

Ideally, I would like the primary pin on each of those terminal blocks to act as the PWM output, and the secondary pin to remain available as a standard GPIO so I can use it for the Direction signal.Thank you in advance for your time and all the support you give this community!

Good job tracking that one down!

Did you previously increase the libusb log level somehow? If so, then maybe that's why it segfaulted for you, but not for me. regardless, looks like a libusb bug to me.

Perhaps, I found out what is happening to the drives. I read the PDO mapping part of the manual again and it seems that the PDO mapping objects - 1C12h(RxPDO) and 1C13h(TxPDO) are set to some default values. The PDO mapping cannot be saved in the EEPROM of the drive and therefore the master needs to set the desired mapping in the PREOP state of the drive every time when the drives are powered on.

The output in terminal that show "Gap" in PDO entry is because there is no object mapped to that free slot - PDO mapping is set to fixed.  Here  is the PDO mapping part of the manual. It can be seen that 1C12h should be set to 1600h and 1C13h should be set to 1A00h to activate the variable PDO mapping.

Attached is the PDO mapping objects description from the manual and it shows that they expect data type of ARR(perhaps array). Apparently, LinuxCNC EtherCAT master should define a variable PDO mapping and what objects to include in the mapping.

In my opinion, the PDO mapping should be defined in the .hal file or create a script that executes once when the EtherCAT master detects slaves, similar to the first scan bit of a PLC.

The compensation needs to allow for tilt of the saddle as it moves along the bed. There is typically more wear on the front way than the rear, and this is (I believe) what causes the machined diameter to vary.

You could measure a parallel test bar with a dial indicator at various points along the bed, and use the "lincurve" component to calculate the required offset (and then add that on between motor-pos-cmd and and the input to the PID)

Any that you do find will be second-hand. And old.

I would follow PCW's advice and change to a supported FPGA card. The 6i24 is in-stock at Mesa, but would need a PCIe motherboard rather than PCI.
It doesn't look like Mesa have stock of any full-size PCI cards at the moment.
(The 5i24 is the PCI version of the 6i24 but shows as out of stock)

The 6i24 will work with the same daughter cards as the 5i20.

It would be necessary to change "5i20" to "6i24" throughout the HAL file too.

No, there hasn't been a 2.10 release, and that was the development version when my email was sent.

This is the state of the .comp in the 2.9.8 release tag.
github.com/LinuxCNC/linuxcnc/blob/v2.9.8...nts/toggle2nist.comp

(no debounce pins)

So far so good. Next big thing is the wireless jog wheel.