Advanced Search

Is that 4.1V under load?

4.1V and no load indicates either a damaged output or low 5V supply

What were the low state voltages of the DIR outputs?

I currently have a custom M6 remap that intermittently gets stuck on a line with an M66 (M66 P7 L3 Q10

I am assuming it's an issue with queue busters in my gcode, and I have a rough understanding of how queue busters work, and why they can cause problems, but I would have thought an M66 is exactly one of the ways to prevent a remapped code or gcode program from getting stuck, as explained here:
linuxcnc.org/docs/html/remap/remap.html#..._position_prediction

The tool change also gets stuck occasionally within the second half of an if statement on a G53 G1 move. 

Any general advice around queue busters (or other causes) for a tool change to get intermittently stuck is appreciated!

Edited for clarity

You changed nothing but line 24 ?

That's correct

You might want to update to 2.9.8 as there have been some bug fixes since 2.9.3 (not sure if that is why it doesn't work for your though)

Thank you for the suggestion.
I just measured the DIR signals, they all work fine.
The voltages are between 4.1 and 4.9V which seem a bit low to me, but it should still work with 3.3V.
Any other ideas?

andypugh wrote:

cnbbom wrote:

The Kernel Headers are not available for download. Is it necessary, or can I use the one I have here?

The ones on the server are the ones you provided, so yes. 
But you don't need them unless you are compiling from source. 
And this link works for me... www.linuxcnc.org/dists/trixie/base/binar...ai-amd64-1_amd64.deb

Thanks, Tommylight told me it was the same one I already had here.

Hi!
Thanks for the interest. I'm currently finalizing the cost analysis based on a small production batch.

My target is to offer a Starter Kit for 99€, which includes:

1x Base Board: (USB interface, ATmega core, 4x Encoder inputs, 3x Analog inputs, and DAC outputs).

2x Expansion Modules: Adding 16 Digital I/O (8+8) to the system.

Individual 8-bit expansion modules will be around 20€.

I'm currently refining the 'v2' hardware to eliminate the minor layout issues of the prototypes and optimize for small-scale production (aiming for an initial batch of 30 units). This price point allows me to offer a robust, pre-assembled solution while covering the extensive development of the HAL driver and firmware.

I'll keep you updated on the v2 progress and when I'll be ready to ship!

andypugh post=341318 userid=723Qual é o erro? Os eixos são frequentemente uma fonte de ruído elétrico. O erro persiste mesmo com o hardware do eixo desconectado?

The error consists of: creating a machine in linuxcnc, I follow these options that allow me to use automatic spindle control. But after completing the configuration and opening linuxcnc, the PC shuts down, and I need to reset the PC.
This is my configuration in the photo, but if I disable:
spindle pwm,
spindle cw
amplify enable      I can operate the machine.

Hi, 
here is my configuration.
It works. I use XYYZ.

But please note, maybe someone here can give me a tip.
The servos need a few seconds before they are ready.
After starting Linuxcnc, it takes 3 seconds for the X-axis to be ready.
Then another 3 seconds for the YL-axis to be ready.
Then another 3 seconds until the YR axis is ready. 
Then another 3 seconds until the Z axis is ready.
If I press the machine ON button too early, the error I described occurs and one axis does not move during homing.

Maybe someone knows what the problem is, or is there a way to only turn on the machine when all servos are ready? 

 

cnbbom wrote:

The Kernel Headers are not available for download. Is it necessary, or can I use the one I have here?

The ones on the server are the ones you provided, so yes. 
But you don't need them unless you are compiling from source. 
And this link works for me... www.linuxcnc.org/dists/trixie/base/binar...ai-amd64-1_amd64.deb

What's the error? Spindles are often a source of electrical noise. Do you see the error even if the spindle hardware is not connected?

Getting myself in a mess wrt to a machining job on a three axis mill and three tools that get manually changed.
Spindle has a quick change system that accepts ISO type holders. Each tool has its own backend.
I have been setting the three tools by calling T1M06, T2M06 etc  in the MDI, putting the appropiate tool into the spindle and then touching it down on a setting gauge, until it registers zero, clicking the Tool touch off button. Repeat for the other two tools after calling for the tool change.
Then I take one of these tools, and use the Z touch off button to touch off onto the work piece datum.  
Can then check the tools individually, by changing to the tool, running G43 in the MDI, and Issuing G0 Z0.
The Z figure in the DRO, is zero and the tool is at the workpiece daum height. So far so understandable.
At this point things get a bit shakey if say I want to pull T1 tool out of its holder another 10mm because I've not allowed enough clearance between the collet nut and the  workpiece.
If I adjust the tool, and put it back over the setting gauge, which is at the same fixed point on the machine it was at the start, and re tool touch it off and call G43, the z height reading on the DRO is zero again, but the actual z position wrt to the workpiece  is around 12mm off from being where I expected it to be.

I think I am missing a bit of the puzzle somewhere, as I cannot see mistake I am making.

Thanks

It would be good if there were more reports from people who have now installed RTAI without freezing, restarting, or crashing. Because now I realize that something between RTAI and my CPU doesn't work, and the problem is getting the spindle to work through automatic control. For now, I can use the spindle manually on its keyboard since, for the first time, I can control the machine with RTAI.

Im struggling to understand why it works for both of you. I have 2 different machines and a laptop and it works on none of them. All 3 computers running 2.9.3.

You changed nothing but line 24 ?

Hello Hartwig,

I am using the 7i97T exactly for that. But for the automatic toolcanger, wich hast some hydralic pistions, I will need extra I/Os.

-The 7i97T is for the movment of the axis, spindle and encoders.
-The 7i84s is for the control of the toolcanger.

Do you unterstand?

@3404gerber thanks for your all response. Finally I was able to make it working. Added spi_clk_div=32 in remora-spi arguments.
But it was never required earlier. I am using raspberry pi 4b.