Advanced Search

meister wrote:

An open source programmer usually only sees the problems and errors that users have, but very rarely reports of success.

So I would be very happy if you could give me a little feedback.


OK so yeah I am guilty of exactly this, and most of my errors are my own doing! 

For me RIO has allowed me to update my two wood router style machines with closed loop to the controller, after my MESA cards died, not trash talking MESA in any way, where I live its hot and humid, VERY hot and VERY humid, for 75% of the year, electronic boards tend to not particularly like those conditions. 

Moving forward my next machine to retrofit is a 2.5 Ton milling machine, I have no real concerns with doing so, I can setup closed loop control (Brushed dc servo's) for all three axis, and even the spindle can be closed loop to linuxcnc as it is also brushed DC, around 200 Volts. All this just works in RIOCore, yes a 200 V 4KW Brushed DC motor is a little spicy but I only need to worry about the power stage, its still just a motor, and RIOCORE has it covered. 


Cheers.
Russell.



 

Hello everyone, I am relatively new user here. I was trying to test my is620n drives from inovance with linuxcnc ethercat and kept running into problems.
I am using the hal file and xml from another user here on the forum but slightly modified.
The problem I am facing is that the drive stays in PREOP and I am not able to get any motion out of it.

I am posting my files here, thank you!

 

Wenn das Alarmsignal des Steppmotors nur 5 V liefert dann schalte doch mit dieser ein Relais das die 12 V Ein und Ausschaltet
und lege die 12 V auf den PIN

Juergen

Start with controlword, statusword, opmode and opmode-display.
 

Ich habe das Support Manual.

"The 7I76EU field inputs have a nominal input resistance of 10K Ohms to field power ground. 7I76EU inputs sense positive input voltages above a preset threshold. For best general purpose use, default input threshold is 50% of the field power supply voltage with 10% hysteresis. That is with a 24V field voltage an input must be brought to 60% of 24V= 14.4V to be sensed as high and then brought to 40% of 24V = 9.6V to be sensed as low.These accurate thresholds and hysteresis allow high speed field signal detection whilemaintaining excellent noise immunity."

So wie ich das verstehe müssten bei 12V mindestens 7,2V anliegen um ein "High"-Signal zu erhalten.
Damit komme ich ohne eine kleine Verstärkerschaltung nicht weiter.
Richtig?

Als Schrittmotor möchte ich gerne diese verwenden...
www.omc-stepperonline.com/ess-series-2-2...vdc-1000cpr-ess23-20

Thanks for figuring that out!

wheeeee

0.97mm calibration offset is HUGE, you have wrong going on there, that should just be the trigger distance of the probe. You should use a larger calibration object so you aren't in an acceleration state. The cal offset should be a really small number, 0.04-0.08mm for most decent mechanical hobby probes. The probe tip diameter must be entered into the tool table in the column. (I this is where you're issue is coming from and why your cal offset is so large. Use only fast probe feed rate (set slow probe feed to 0.000). Use something like 200mm/m fast probe feed rate.. Be sure to reset the offset prior to running calibration. Run in probe position only mode for calibration. Make sure your step of width is a decent amount past the edge, at least 10mm or so.

Whatever is the lowest you might use.
Last china one i had needed 3 turns to work reliably at 20A, and that was the lowest it could be set despite the knob being marked as 10A as well as showing 10A on the display. At 33A shown/set it would do 45A, and at 60A it would do 60A.

I haven’t run my ect60 drive for more than 30 minutes, so I haven’t seen this problem.

I appreciate all your documentation however. I’m also running a pi4b.

When you installed the Ethernet switch, did you maintain the series cabling for all the drives? Put another way, do you have just the pi and the first ect60 connected to the switch?

I wonder if a loop configuration using the Ethernet port on the pi, plus one more usb dongle Ethernet port would also solve the problem.

I probably worded the statement poorly - but the table, vise material column is 100% trammed with each other no question


I would just disregard that statement, what I meant was when I probe the corner the probe does appear to be in the correct location, at least close enough that if I brush the probe along that wall, the ball (whose central axis is now along X or Y) deflects enough to re-trigger, meaning the probe is fairly close to the true corner.

However, the easier statement is that when I compared the origins, the probed origin is around 0.815mm off the true corner (as compared to using a mechanical edge finder). So for some reason, when I use my probe, the origin that is recorded is 0.815mm AWAY or INTO the actual wall.

I use a dial test indicator to make sure the probe ball tip is concentric so its definitely not that.


Can there be some issue in probe-basic or linuxcnc that is not correctly applying the diameter? Or miscalibrated somehow internally but on the UI shows the correct value??

I only tried at 45 amps. How low is worth testing? 

Try this for the keys

I see what you mean, even when it starts with multiple key entries only the last group of keys get sent

ffffrf wrote:

also if I use the probe to probe the edge, then move to the origin and slide the probe across either X or Y wall of the metal at the 0 value for that axis, it does retrigger the probe, doesn't that mean the probe is functioning correctly and its a linuxcnc side issue?

No, from what i can gather it means the machine/table/material is not trammed properly.
Or what am i missing?

Hey so I did another test - setting the origin manually with an edge finder makes it work as expected.


However, I can't for the life of me think of what the actual issue is in that case then? The probe calibration all looks correct, the diameter is set in the tool table.

When I compared the edge finder origin vs the probed origin, the probed origin is about 0.815mm off in each of the axis. The probe diameter is 1.95mm, calibration seems correct.

Do you think it is more likely a probe issue or a linuxcnc issue? Clearly the post processor/CAM is correct

I just can't think of anything mechanical with the probe being the actual issue

edit: My probe tip diameter is 2mm, when I do probe cal it says the probe cal offset is 0.97mm - and measures the circle as 5mm

EDIT2(MORE IMPORTANT): also if I use the probe to probe the edge, then move to the origin and slide the probe across either X or Y wall of the metal at the 0 value for that axis, it does retrigger the probe, doesn't that mean the probe is functioning correctly and its a linuxcnc side issue?