Advanced Search

Hi Patrick,

so, regarding the encoder resolution I have come one step further. It actually is configurable and the default value is 4000 counts/rev.
I suspect that the drive doesn't have a "real" hardware encoder but uses hall sensors or other electronic tricks to know/estimate the position. Thus the resolution can be set kind of arbitrary and is dependent on the accuracy of the sensors.

I was able to set the resolution to 10_000/rev without problem. But the question remains how accurate that actually is and if such a high resolution makes any sense. I think I'll settle with just 1_000/rev which will still give me an accuracy of 10µm in combination with my 5mm/rev ball screw.

If you're interested in more details, let me know and I will share what I found out.

Regarding the XML configuration I'd be interested to see what you came up with.

Good luck with your exams,

Uwe

 

The THCAD connection should not have any effect on the 7I96S unless there was
some kind of issue with the 7I96S side (encoder side) wiring, as the plasma
(Analog input) side of the THCAD is completely isolated from the 7I96S.

Is the THCAD2 in the same case as the 7I96S?
 
 

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