I just had a quick look, but might go a bit deeper at another time.

The ctx/context appears to be the libusb_context struct. I guess you could just do  after libusb_init in usb.cc:
github.com/LinuxCNC/linuxcnc/blob/master...whb04b-6/usb.cc#L629
But this probably isn't the best workaround in general.

I guess most of the problems in the past has been because of the assert statement in setupAsyncTransfer? Or did the pendant never reconnect for you in the past? When I was testing and just unplugged the dongle and plugged it back in, it usually didn't fail in the setupAsyncTransfer function, so the assert statement didn't prevent reconnection.

You might also be interested in testing the changes made by Hannes:
github.com/hdiethelm/linuxcnc-fork/tree/xhc-whb04b-6-fix-v2
I believe you need to do a "git checkout xhc-whb04b-6-fix-v2" after git clone in case you want to test that. With regards to the disconnects, his solution is more elegant than decreasing loops, because it avoids trying to change mode altogether when it's clear it would fail anyway.
 

Might look at the step pulse train with an oscilloscope.

Also is it possible the servo drive is not set to position mode?
 

Okay, is there a way to verify that it is an electrical/wiring issue?

OK so that may still be an electrical/wiring  issue

(if the DRO does not move but the motors move)



 

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 set the 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.