Advanced Search

Thanks Rod, I managed to build a deb in a bookworm chroot but it won't install on trixie because linuxcnc requires python3.11 and trixie uses python3.13. I also tried installing the deb from buildbot2 but same result. Looks like I have no option but to reinstall bookworm. Major PITA.
On that note, I recall you posted the 6.3.0-rt11-linuxcnc kernel somewhere, but I can no longer find it. Could you tell me where that is? Thanks again.
Jim
 

OK those settings should result is a +1.0V output
(as they do here)

Possible reasons for a very different output voltage:

1. Measuring wrong pins ( analog output 0 would be measured from TB3 pin 4 to TB3 pin 3)

2. Marginal 5V supply to 7I97T

3. Problem with the voltmeter

4. Damaged 7I97T analog output driver

5. 7I97T analog output connected to shorted  load

Okay first of all thank you for all your help with this, I am very new to this and have watched countless hours of youtube on ethercat and a having a hard time finding solutions to errors. I have another error 
Failed to register PDO entry: No such file or directory
LCEC: master 0 PDO entry registration failed

I want to thank everyone again for the help, I had lost hope on my project until now.

I consider having to restart LinuxCNC unacceptable. If I don't find a better solution, I will not use this pendant.

The rotary knob sounds more like a configuration issue(?). Have you checked if you see the position switch changes by running "xhc-whb04b-6 -a" from a terminal?

vibram wrote:

Hello I try to setup a mill with all servo drives run with analog command and it's working fine.

However, now I try to setup a MPG
after customizing the HAL file, here is the situation:
the MUX is correctly working for the scale and the axis.x.jog-scale is correct (value from 0.01 to 1mm)
axis.x.jog-enable works fine, same for Y and Z
axis.x.jog-counts works fine, I can see the number of pulses moving when I turn the handle
axis.x.jog-accel-fraction is set to 1

When using Axis interface with the and - button, it works fine
However; when I turn the handle, the axis is not moving at all, I don't have any error message.E-stop is off and Toggle Machine power if ON obviously. 

Any idea what could be the issue?
thank you

From what you describe, most of the MPG plumbing sounds correct, so the issue is likely in how the jog counts are actually being consumed. One common gotcha is that jog-counts alone won’t move an axis unless the jog mode is set correctly. Make sure the axis is in “teleop” or joint jogging mode, depending on whether you’re using a joints or axis configuration. Also double-check that the MPG counts are wired to the correct joint or axis pins, not mixed between the two. Another thing to verify is jog velocity: even with accel set, a zero or very low jog-speed or jog-vel-limit will result in no motion. Finally, confirm that no other signal (like another MPG channel or UI jog source) is holding jog-enable low at runtime.

Greetings Mark!
First of all, excellent work on the retrofit - this thread will end up being a literal goldmine for me. 
Last week I also purchased a 1986 MH400E and the goal is to convert the machine to LinuxCNC in the coming few months. 

Somewhere in this thread I saw that you have a 'collection of notes' for your conversion - is there any way to get these from you? I can't seem to find an email-adress available on your YT Channel as previously stated. 

I haven't quite had the time to work through all 180 pages, but I do have a quick question: 
How is the gear-changing generally handled? Do you have to command an exact speed value, or will LinuxCNC pick the correct gear for whatever arbitrary speed you command? 
Also, will the gear-change happen automatically whenever a speed is commanded, or is there specific codes that need to be ran (I would love to use the F360 CAM and I wonder if linuxcnc will handle selecting the speed automatically, or if I need to fiddle around with the post-processor?) 

Thanks and very best regards from Germany
Daniel

 

Hakan wrote:

If the drive is reducing the speed by itself you will get following errors.
Otherwise it's the settings in the ini file that are throttling the speed.

Yeh, that's what I have been playing with to determine where to set max velocity. I remembered from when I set up my plasma on a Mesa card to see how much of its 10 Mhz bandwidth I could use that there was a physical limit to how fast you could step in the real world. That's why I cut back the settings here. The design target was 10240mm/min so it fell a bit short, But the RPM is still quite respectable. I've had enough for one night.

I also might try increasing the amps a bit too

If the drive is reducing the speed by itself you will get following errors.
Otherwise it's the settings in the ini file that are throttling the speed.

So I had this theory that at default 10000 steps/rev it was running out of bandwidth when it got to 2000 mm/min (400 rpm). S0 I changed the steps to 1000 steps/rev which I assumed might get me to 10 x 2000 = 20000 mm/min
This let me get up to 8500 mm/min maximum velocity. But It did not get me to the expected 20000 mm/min (10 x 2000)
So definitely reduce the steps/rev if top end speed is important to you. I think you'll need to tweak the steps/rev to suit your design parameters.

fenton06 wrote:

Looks like the Trixie issues repo got nuked, does anyone know what happened?

Mental health issues.

Today I was able to get the spindle to rotate, but I've encountered two new problems. While the DI4 wire is connected to pin 16 of the bobbin to reverse the spindle's rotation, it always remains reversed, regardless of whether pin 16 is activated or deactivated. I checked with the HAL meter, and pin 16 is working correctly. I also measured with a multimeter, and when it's activated, it reads 0V, and when it's deactivated, it reads 5V, but the spindle always rotates in the same direction. Interestingly, when I disconnect the reverse wire from pin 16, it rotates in the correct direction, and if I reconnect it, it reverses direction, but nothing happens from the interface using pin 16.

The other problem is that the RPMs don't match, for example, an M3 S1000. I've tried to correct this unsuccessfully from both the driver and the HAL. I have a 1.58:1 pulley ratio (45mm motor pulley, 71mm spindle). My knowledge of Linux CNC is limited, and I'm not sure where to go from here.

I'm not sure if I've explained myself clearly. Sorry for my English.

Hi,

I'm interested.
I also have the problem that the connection disconnects after a while. For me, however, it's enough to close LCNC, disconnect the dongle, and reconnect it.
I'm interested in the feed setting of the rotary knob button.
This doesn't work; only the increments can be set. I was only able to solve this with a workaround.

Hi,

Is anybody interested in some development for the XHC WHB04B pendant? Both from a user perspective, but also with the development itself.

I bought a WHB04B-6 to use with my mill, thinking it should work okay. But of course there are issues. After a while, it disconnects and I have to restart LinuxCNC to get it back working.

I have already went quite deep with this, and have some and can generate more material:
 - USB packet captures with Wireshark (form both LinuxCNC and Mach3)
 - USB signal capture with logic analyser
 - WHB04B transmitter firmware
 - RF signal capture

One thing I noticed with the xhc-whb04b-6 component in LinuxCNC is that is has some blocking wait states. These can delay the USB polling of the WHB04B so much that it causes the device to reset. I fixed that (for myself), but still there are issues...

There are several possibilities:
 - improve the xhc-whb04b-6 component
 - create a new driver/component for the pendant, realtime if seen necessary
 - create a new firmware for the WHB04B transmitter, possibly also for the pendant itself

Any comments or thoughts from the community?

I guess many have the opinion that both wireless and USB pendants are a no go. Personally I don't see an issue at least for "garage application", provided its properly implemented. The main thing would be to have a watchdog monitoring the communication, which can (e)stop the machine if necessary.

Here is pwm.txt - only analog=0 

You need to checkout the correct branch. The release versions are defined by a tag dso that are locked in. You can see this in git on the branch drop down if you select the tag tab. This will let you see the exact source for the version you have.

to get the source of 2.9.8 on your pc its  :git checkout v2.9.8