Advanced Search

npostma wrote:

... 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?

It is not underpowered for stepper systems, might be for servo systems, so not the cause of following errors for steppers, but might be for servo systems.

I don't know why, but we can try to find out why.

Can you replace the lines that creates all the input pins and out pinswith "complexentry", there are several examples above in the file.
Do you still get the shift?

That may be so but the other two icon themes to not use the turtle/hare symbol.

 

 

You would ruin my panel:
 

 

Aciera wrote:

A minor thing but you might want to rename the 'turtle jog' to something that applies to all the icon themes. Maybe 'Slow/Fast Jog'

 

Please NO

It is a common designation:
 

You would ruin my panel:

From what I read the EL6021 could perhaps work. Ethercat master will create a virtual serial port over which modbus is communicating.
IgH Ethercat master supposedly supports virtual serial ports when compiled with the right option. But I have no idea of how to set this up in linuxcnc context. I mean it will be a virtual serial port so the standard mb2hal etc are used, but to set up the virtual serial port?.

Thanks for the update!

A minor thing but you might want to rename the 'turtle jog' to something that applies to all the icon themes. Maybe 'Slow/Fast Jog'

 


- I would VERY much like  a column for rotation in the offset table instead of having just the currently active 'Rot' value.
- I would suggest to rename the  column 'Offset Name' to 'Comments' and have it's values empty by default. That would be more consistent with the tool table.
- I would suggest to change 'G92' to 'G52/G92' as those parameter values are actually shared by the two offsets.

 

the stepper-ninja-w5500.uf2 is the file you need if you make like this.

the pico only is not enough, you need a w5500 module also, or a W5100S-EVB-PICO

 

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.