Advanced Search

I started getting joint following errors after I changed the following stepgen timing settings to these even values:DIRSETUP = 6000
DIRHOLD = 6000
STEPLEN = 3000
STEPSPACE = 3000This happened even though I set STEPGEN_MAXVEL and STEPGEN_MAXACCEL to be 25% higher than my MAX_VELOCITY and MAX_ACCELERATION values, as recommended.However, my power supply is a 32V 10A unit running three axes, so it might be a bit underpowered. Could this be the cause of the joint following errors?
I do have another similar power supply available, so I could use it to power one axis separately—this would help with the available current, but not increase the voltage.Any advice or experience with similar situations would be appreciated!

Not sure if there is a halcmd to do that but you can use an executable custom Mcode to call a bash script that executes this:

www.linuxcnc.org/docs/html/man/man1/axis-remote.1.html

I’m having a similar issue, I’ve run the above commands and captured the output, would you be able to help? I know this thread is pretty old.  Would it help to just paste the outputs or include as a file?

Typically you would use a mux component for this.
In you case (only 2 increments) you could use mux2

Something like:

loadrt mux2
addf mux2.0 servo thread
setp mux2.0.in0  0.0001
setp mux2.0.in1 0.001
net jog-increment-select mux2.0.sel  some_old_input_bit
net jog-increment mux2.0.out

 (your signal names and select pin names will be different)

 

Hello friend, please refer to the following code. I have the same module and it has been tested and is available. The corresponding pulse counting and other modules only require you to add PDO as needed.
<!-- IO -->
<slave idx="5" type="generic" vid="90588" pid="109252" configPdos="true">
<syncManager idx="2" dir="out">
<pdo idx="1600">
<pdoEntry idx="0x2300" subIdx="00" bitLen="16" halPin="out00" halType="u32"/>
</pdo>
</syncManager>
<syncManager idx="3" dir="in">
<pdo idx="1A00">
<pdoEntry idx="2020" subIdx="00" bitLen="32" halPin="encoder" halType="u32"/>
<pdoEntry idx="2000" subIdx="0" bitLen="16" halType="complex">
<complexEntry bitLen="1" halPin="in-1" halType="bit"/>
<complexEntry bitLen="1" halPin="in-2" halType="bit"/>
<complexEntry bitLen="1" halPin="in-3" halType="bit"/>
<complexEntry bitLen="1" halPin="in-4" halType="bit"/>
<complexEntry bitLen="1" halPin="in-5" halType="bit"/>
<complexEntry bitLen="1" halPin="in-6" halType="bit"/>
<complexEntry bitLen="1" halPin="in-7" halType="bit"/>
<complexEntry bitLen="1" halPin="in-8" halType="bit"/>
<complexEntry bitLen="1" halPin="in-9" halType="bit"/>
<complexEntry bitLen="1" halPin="in-10" halType="bit"/>
<complexEntry bitLen="1" halPin="in-11" halType="bit"/>
</pdoEntry>
</pdo>
</syncManager>
</slave>

This module, I have previous usage experience on other platforms. In principle, it can be used without any problem, but it depends on how you call the corresponding registers. This module is very easy to use. All you need to do is to send data according to the standard MODBUS template.

RODW, as you said, is correct. In the EL2809 module, I used it like this, and at the same time, testing the "general" driver and adding hal manually was also without any problems. However, problems arise when using this "Sdot" module. I received the data related to this module. Each piece of data corresponding to the PDO will be shifted by 16 bit.

Hi all,
I have a home-made pendant that can jog and set the offsets using HALUI commands.
When I set the G54 offsets (using HAL commands) I would like to refresh the Axis display so that it will show the part in the offset position.
I would like to use a HALCMD to refresh the Axis display if possible, but will use whatever is required.
Is this even possible?

Thanks in advance.

I have a MPG encoder that has 100 detents and scaled on my lathe X axis for 0.001" increments. All working great.
Once in a while I need to turn to a dimension tighter than 0.001" When I need to do this I tweak my ini file to make the MPG increments 0.0001"

I would prefer to have a toggle switch to toggle between regular(0.001") and sensitive (0.0001") mode, and be able to toggle it as required and not have to restart LinuxCNC.

Is this possible and if so how would I go about it?

Thanks,

Hi everyone,I'm planning a retrofit for my Mécanumeric MF2040 (large-format pantograph) i'll dismantle all the eletronic and leave the structure. After some research, I’m considering the following setup and would appreciate advice or feedback:Controller & Interface:

• LinuxCNC running on an old (but reliable) PC
• Mesa 7i76e Ethernet motion controller

Motors:

• 3x Delta B2 Servo Motors (220V, 750W, 2.39Nm, 3000rpm, ECMA-C20807RS)
  • Alternative: 3x Leadshine ELM0750DH80E-SS
• Z-axis motor: Still evaluating options

Usage:

• The machine is mainly used for cutting and engraving (pantograph work, large panels).

Questions:

1. Does this setup sound suitable for a machine of this size and type?
2. Any experience with these servo motors (Delta B2 vs Leadshine)? Reliability, tuning, integration?
3. Suggestions for the Z-axis motor?
4. Any compatibility issues or tips when using LinuxCNC with the Mesa 7i76e and these servo drives?

Thank you in advance for your advice and suggestions!

So it`s not going over ethercat? Didn`t think about this possibility yet. Thx a lot for the hint!

Yes, the X movement (joint 0 in the plot) is done before index is detected
but the interpolated position (spindle-revs) removes any quantization
issues:

What is the bianari file for the normal RP pico?

stepper-ninja-W5500 or stepper-ninja-W5500S

The longs motor DM542A is better than you think and is my choice of drives for NEMA23 motors if price is important.
With 25x microstepping and 48v power supply, I used the following setttings

Never mind, stupid question. All attempts result in massive errors or a segfault crash of LinuxCNC.

Thanks for looking.