Advanced Search

got a new card didn/t help. same messages. I finally just install version 2.9.4 and everything works.

Post your custom homing procedure please.

My bad, aluminium is about 1.2 kg for 1200mm
So it is about 2.5 times as heavy but many times stronger against deflection.
That is why the choice was made for the 80x40 extrusion profile.

The guides weigh a lot more there, more could be gained there.

Thanks for the reply.
I removed it but it had no effect.

I would try to remove the PARAMETER_FILE (sim_mm.var) and then start the program

W4 is not used on the 7I84U, its position does not matter.
(note that the 7I84U was tested with the as shipped jumper settings)

What LEDs are illuminated on the 7I84U when the system is powered
(but linuxCNC not running?)

You should have 2 yellow LEDs and 1 red LED illuminated. If not, 
there is a power issue.

Do you have both FIELDA and FIELDB voltages applied? 

 

I just noticed that halui.axis.x.pos-relative read the value correctly and it retains it after restart. The axis.x.pos-cmd always starts at -496.2247. When i move the robot the halui.axis.x.pos-relative reports the correct absolute position but the robot moves as if it has been started at -496.2247. Any ideas?

Hi, I have a delta robot built on ethercat and running linuxcnc.
We recently got drives with absolute encoders so i had to make a specific homing procedure that just triggers the internal homing on the drives.
The drives then reset their encoder positions internally to 0 or home offset if it's set in HAL with lcec.
Then, when using the robot i could move it somewhere, turn off linux cnc and then start it again and linuxcnc always shows the same position when starting [ 0. , 0. , -496.22474747]. When i disable the home offset this number still stays the same. I move the robot to [0,0,-700], restart and it still shows the same position, and then moves "ignoring" the soft limits. The encoders themselves retain their position information properly, it's just linuxcnc that reads it wrong (or doesn't read it for some reason) What am i missing here?
Here are the files for my config.

vibaration at 40krpm

 

PACKING LIST
SPINDLE MOTOR 1pcs used
ISO20-ER16 6pcs brand new
1.Orders will be shipped out within 3-5 working days once payment received. Please make sure the phone number is valid.2.We Will ship by DHL/fedex/tnt serice . You will be updated the tracking number via ebay and email. Generally, it takes 15-30 delivery days to your shipping address.3.Kindly please note the tax fee and clearance fee are not included in the item price. You have to take the responsibility for the tax and clearance fee.4. Please feel free contact us if you have any question


This email address is being protected from spambots. You need JavaScript enabled to view it.

www.ebay.com/itm/187367138385

He comprobado por si había cortocircuito y no encontré ningunoLa tierra la tengo conectada de todos los cables blindados en una sola punta dentro de la caja de control en una barra de tierra que a su vez esta conectada a la tierra de la redEl problema fue cuando conectar el thcad2 antes de conectarlo, estuve cortando y todo funcionaba bien también es verdad que lo conecta y no lo configuré en linuxcnc por el hecho, que no encontráis la pantalla de thcad2 en pncconf y no se como configurarlo en .hal y solamente le di hacer una prueba arrancando la antorcha y ya los motores no se movían al instante.

ya pedí los chips pero me gustaría encontrar lo que a producido el fallo antes de que me pase lo mismo. Podrías ayudarme. Gracias de nuevo

Thanks for the link.
Looking at locale.

LC 2.9.2:
Menu-config has an extra step for setting locale.
When en_AU is selected, a pop-up shows C.UTF and en_AU.UTF, adds a warning about setting locale, then Ok to accept en_Au.
Then locales are generated before returning to the menu-config dialog.

LC 2.9.4
The extra step is not present.
The return to the dialog is too quick to see if a locale is generated.

Research on Debian locale seems to require editing of files.
I will start reviewing this tomorrow (and re-read the reference link).

John

Thank you for your pointers in the right direction. Helps a lot.

Unfortunately the 7i84 still does not report back. I just discovered that jumper w4 needs to be removed, even though it's not mentioned anywhere. I've been running a simple half file and use your suggested mesaflash prompt to check available serial devices. Is there something else I can do?

loadrt hostmot2
loadrt hm2_pci config=sserial_port_0=000xxxxx

loadrt threads name1=servo-thread period=1000000

addf hm2_5i25.0.read servo-thread
addf hm2_5i25.0.write servo-thread
addf hm2_5i25.0.pet_watchdog servo-thread

start

For axample:
Aluminium extrusion profile L=1200mm (2.9 kg) vs aluminium 50x50x2 tube L=1200mm (3.6kg)

I must say that the weight comparison seems very counter intuitive.

[edit]

you are comparing aluminium extrusion profile to  50x50x2 steel tubing (8000kg/m3).

The most likely problem is that you have 'anglejog.current-scale' = '0'.

Note that the 'anglejog.scale-in' value is only sampled when 'anglejog.enable-in' is false. (See 'Notes' in the man page linked above)

You may want to have a look at the anglejog sim config :
configs/sim/axis/anglejog