Advanced Search

only the onboard mii chips do not run, the w5500 runs with all boards and toolchains.

the programmer on the additional board is very slow, better use a USB blaster to access the JTAG pins, it works great with openFPGAloader

I would prefer the i5, it has the ECP5 on it and is best supported. It's also so big that you won't get it full

Cheers,
Olli

 Hallo,
I tested the new version today and noticed that when I round the corners P64 P10.0 the speed of the axis (joint) does not behave as expected (yellow circle).
The acceleration (green circles) is interrupted by (blue circles) whereby the change in acceleration (jerk) appears to be too large.
At P64 P0.0 the axis (joint) behaves as expected.
Can this behavior be set via parameters?

 

Gruß
Rüdiger

Hello,

let check this topic  ... It will be in the general 99% same as for CanOpen setup.. but datas config should be little bit different...

regards E..

I have never had issues mounting the THCAD inside the control box. The plasma has a CNC interface connector so its designed for this.
You will not have issues.

You should just need to use HOME_OFFSET to get your gantry square and rely on your encoders to keep them that way

Look at the example in the docs for a MPG for axis selection and scaling. I think there is also a MUX4

Oops, just thought. the tension should be able to be done using home offsets

Once the fabric is tensioned, linuxcnc should be able to use the joint axes to control 4 motors in unison. Normally, it is just used for 2 on both sides of a gantry but I know its Been used on a 4 joint Z axis where all 4 corners are lifted..

I think you should use halcompile because this also lets you document your component via a man entry and the web site in the same file.
For new contributions, you should be using 2.10 (master) branch as 2.9 is frozen.
Using C would just add extra work. Not sure on user space comps though. I have never written one.

Both is fine.
The .comp format is more compact and easier to understand and maintain particularly for people not totally familiar with pure c.

Note that the component should remain compatible with older configurations.

I would think that your biggest issue is going to be the stretching of the fabric and that partly cut sections are going to get bunched up as you move the material back and forth.

I have picked up 4 new motor drivers and ac servos. I am trying to understand how I can use these with LinuxCNC..
I've been searching but can't even figure out how to start..  Has anyone used the Omron G5 hardware?

Thanks for any help.

Personally I would add the compensation to the kinematics model but if you feel more comfortable using a hal solution then why not give that a try.

There is also the external offsets feature:
www.linuxcnc.org/docs/devel/html/motion/external-offsets.html

One easy way is to use a mux8:
linuxcnc.org/docs/2.5/html/man/man9/mux8.9.html

This way you can net your three spindle signals to the three selections of the mux and you can define your modbus values to the corresponding inputs of the mux.

I am using mb2hal (modbus) and it exposes a pin `mb2hal.00.00.int` that is an input, the values can be 1, 2, or 5. I need to set the values based on other bit pin:

if spindle.0.forward = true then mb2hal.00.00.in = 1
if spindle.0.reverse = true then mb2hal.00.00.in = 2
if spindle.0.on = false then mb2hal.00.00.in = 5

How do I create this logic in the hal?