Advanced Search

I will do one last test with an Advantech Aimb 505 card with an i5-6700 processor. I tested the latency with Trixie and under stress it does not exceed 40 microseconds with a maximum delta of 2. I asked the customer if I could do this test and he will give me the machine available. Also because, now the only solution we are waiting for is a new version of Ethercat that is adapting Grandixximo?

A little preview of what’s coming soon.
This will soon allow you to create a board from the flow config,
or at least a template.


->

->

->


 

RotarySMP wrote:

Has that bug been reported to the Devs?
 

Yes.
github.com/LinuxCNC/linuxcnc/issues/3455#issue-3089348330

There's another spindle synchronization bug, possibly related, that I encountered at the same time last year.  @Aciera found a workaround for it, but I don't know if the two are related.
github.com/LinuxCNC/linuxcnc/issues/3556#issue-3398986003

I don't have the skills to really figure out what's causing the two problems, much less contribute to a fix.

EDIT - I somehow messed up pasting the forum links when I first reported the bug, but one can highlight the link and right-click to open the forum thread.

I've tried using qtdragon hal bridge function in every way possible, but it's not working. According to qtdragon documentation, if I understand correctly, if I define HALBRIDGE = hal_bridge
and also define a macro in the MDI_COMMAND_LIST in de INI file, qtdragon creates other pins that I can access through halbrdge , but these never appear in hal Show. I also understand that these pins related to the created macros can be accessed through external buttons, but unfortunately, there's no documentation on how to do this. In my configuration, I control some functions through external buttons connected to halbridge but for other functions, such as activating a macro, I can't, or I don't know how to, do it with halbridge.

Hi endian,thank you again. I made a completely clean test now with only the AX5125 connected on the EtherCAT bus, no other slaves connected.

I used your files from the zip exactly for the AX test. The startup initCmds file is your Antrieb-1-AX5-0-initCmds.xml unchanged. I only pointed my machine config to that file.

Current result is much better now:
the AX5125 reaches OP when it is the only slave on the bus.Current ethercat slaves output is:
0 0:0 OP + AX5125-0000-0216 EtherCAT Drive (SoE, 1 Ch.)

The important dmesg lines are these:
EtherCAT WARNING 0-0: Slave does not support changing the PDO mapping!
Currently mapped PDO entries: 0x0086:00/16 0x002F:00/32. Entries to map: 0x0086:01/16 0x002F:01/32 0x0024:01/32 0x0050:01/16 0x81E4:01/32 0x81E5:01/32EtherCAT WARNING 0-0: Slave does not support changing the PDO mapping!
Currently mapped PDO entries: 0x0087:00/16 0x0033:00/32 0x00BD:00/32. Entries to map: 0x0087:01/16 0x0033:01/32 0x00BD:01/32 0x0054:01/16 0x0028:01/32 0x81CC:01/16 0x81CD:01/16EtherCAT 0: Slave states on main device: OP.My currently active AX slave config is:
slave idx 0
type generic
vid 0x00000002
pid 0x14056012
name Antrieb-1-AX5-0
configPdos trueMDT PDO 0018 entries requested by config:
0086:01 16 bit
002F:01 32 bit
0024:01 32 bit
0050:01 16 bit
81E4:01 32 bit
81E5:01 32 bitAT PDO 0010 entries requested by config:
0087:01 16 bit
0033:01 32 bit
00BD:01 32 bit
0054:01 16 bit
0028:01 32 bit
81CC:01 16 bit
81CD:01 16 bitDC config currently used:
assignActivate 730
sync0Cycle 250000
sync0Shift 0
sync1Cycle 750000
sync1Shift 0

So the situation now seems to be:
before, the drive stayed in PREOP plus ERROR with MBX_SOE.
now, with only the AX and your startup file, it reaches OP.
but the drive reports that its current mapped PDOs are still the smaller set with subindex 00, while the config wants the extended subindex 01 mapping.

My main question is:
is this already the expected next step, meaning I should now reduce the config to the fixed PDO set the drive actually reports as mapped, or is there still a missing startup/configuration step that should switch the AX5125 to the full 01 PDO mapping?
In other words: now that the drive reaches OP, what is the correct next step before I put the other slaves back on the bus?

Thanks a lot for your help. 

Ich sehe gerade, dass die Chinesen die Aliexpress Anzeige geändert haben und nun zwei verschiedene Karten in der Beschreibung sind. Keine Ahnung was man bekommt, wenn man die bestellt. Ich meine jedenfalls die hier. 

Dieses Fallback Bitfile ist blinkende LED und alle Pins IO. Du brauchst das gar nicht, sondern nur das Bitfile, das zu deiner Maschine passt. 

Die ersten drei Zeilen sind nur zum Testen vom neuen Bitfile, weil es in den flüchtigen Bereich geflasht wird. Falls das Bitfile nicht mit der Karte funktioniert, wird beim trennen und neu verbinden der Stromversorgung das ursprüngliche Bitfile geladen und die Karte ist wieder ansprechbar.
Untere drei Zeilen braucht es, damit es nach dem Trennen der Stromversorgung im Speicher bleibt, aber eben nur wenn das Bitfile mit der Karte funktioniert. Sonst braucht man JTAG.

Deine Karte ist keine 7i98 sondern eine chinesische F7i98. Ist wieder eine andere, zu der ich nichts sagen kann. Mit 7i98 meine ich die hier: de.aliexpress.com/item/1005012092221990.html
Deine kann alles Mögliche sein. Ich vermute, die wird ebenfalls nicht mit originalen Bitfiles von Mesa funktionieren. Jetzt weißt du aber wenigstens wie man es testet, ohne dass gleich alles kaputt ist

Die JTAG Pins bei deiner scheinen anders zu sein, als bei anderen Karten. Keine Ahnung was man da macht. Man kann den IC aber auch direkt flashen (dürfte der zwischen Ethernetbuchse und FPGA IC sein).
Ich empfehle jedenfalls entweder die verlinkte 7i98 zu kaufen, oder die oben gezeigte 7i92, falls 34 Pins ausreichend sind und die 7i98 zu teuer ist. 

Vielen Dank für die schnelle Antwort.
  diese Karte aber Vers. 1.1 habe ich gebrickt und warte jetzt auf eine neue. 
Sie schickten mir diesmal die Doku + Bitfile vorab und schickten anschliessend die Meldung: "Sehr geehrter Kunde, Bitte beachten Sie, dass die Bedienungsanleitung und die Bit-Datei, die wir zuvor gesendet haben, alte Versionen sind. Die aktualisierten Dokumente werden in Kürze an Ihre E-Mail-Adresse weitergeleitet.Alibaba Translation"

Habe eine neue Doku bekommen, jetzt allerdings ohne das 7i98_fallback.bit File. 

Wenn ich das richtig verstehe muss ich doch sowohl den Fallback-Speicher als auch den "Arbeits"Speicher flashen. 1x mit 7i98_fallback.bit mit den ersten 3 Zeilen Deiner Anleitung.
Die Endungen der 3 Zeilen --fallback bewirken das der Fallback-Speicher geflashed wird .

Dann muss noch der Arbeits-Bereich geflashed werden mit z.B. 7i98_5ABOBX3.bit. Wenn am Ende der Zeilen kein --fallback steht, wird der Arbeitsspeicher geflashed. 
Irgendetwas muss ich da doch falsch verstanden haben...
Denn wann werden die Speicherbereiche wirklich geschrieben und nicht nur simuliert ?
Grüße !


 

Has that bug been reported to the Devs?

@JT - 

Thank you for the update and new pins.  I pulled the latest deb and Flex is recognizing the additional spindle connections I put in my test GUI.

This doesn't affect me directly - I have no GUI spindle controls, just displays - but are there similar multi-spindle control pins?  I didn't see any update in the docs about those changing.

A little update as I've found the issue. It was the spindle-at-speed signal. Connected to encoder feedback it would go off in axis mode and I assume it's Gmoccapy behavior that it halts all motion if that signal is false.

Still took me embarrasingly long to figure that out.

HI good mornig at all.
The GUI, can running on Debian 10 ?

Thanks

  Hello to everybody
I use to retofit mill and lathe with linuxcnc , all of them with probe basic.
All of them are working  , i do this for hobby.
Now  i build a hot wire foam cutting machine , a large one , 3m*1,7*1,7 m ,(for 1,2*1,2 section cutting) 4 independent axis
It is configurated with 7i92+7i76 board (old type both of them , remain from other project ) , including the mechanics , remain from projects  , linuxcnc , axis - foam configuration.
On desktop looks like work.
I need an advice , a configuration , an ideea how to manage the wire change of lenght , with a stepper motor , not mechanicaly with spring , pneumatic cylinder , or weight on both sides.
Something like a 5th axis.
I tryed with double y and v axis (vertical axes) ,  mirror axes like routers , XYYUVV  , the mirror axes move and rotate a whell and 'recover' the lenght of the wire , but in my opinion is a better solution , I think with only one motor that can compensate and manage the lenght change.
Thanx in advance
Denis

papagno-source wrote:

The machine with refClockSyncCycles=-1 normally doesn't emit any noise, except for some window movements.
With refClockSyncCycles=1, it emits some noise.
With both refClockSyncCycles=-1 and 1, the command
ethercat upload -p 0 -t uint16 0x1C32 0x01 returns 0x0002 2
Pin pll-error oscillates around -1200 to 1300

When moving windows Linuxcnc's servo loop takes too long time.
There usually is a message in the start window saying that.
If you monitor pll-err in halscope or record it with sampler you will
see a spike in pll-err.
There is some more fundamental work needed to make linuxcnc independent
on such events.
Wouldn't surprise me if this is the difference between 4.19 and 6.

Had another peek at the vid on a bigger screen, and each pass is certainly starting to the right of the previous pass.

Start of pass 2, chip is forming on the right of the insert:
 

Two rotations later, and you can see a second groove forming to the right of the first pass... but it isn't much deeper.
 

Third pass, and now there's a 3rd groove  - also to the right.  And also isn't much deeper.  Maybe deflection, but I didn't see the stock wobbling a ton or climbing the insert.  Almost like it isn't going any deeper each pass, just shifting to the right.
 

In addition to running a no-Q value test, it might be helpful to set up a halscope with the Z-axis position and the spindle index signal.  Try to see exactly where the Z-axis is when the index signal is triggered, and does the Z-axis then start moving immediately?

My earlier suspicion about the start point being the same may not be accurate - hard to spot 0.1mm-0.2mm shift of the insert on video.

Finally, you could put an ink pen in the tool holder and run a series of 3 to 4 G33 moves, using the pen to draw a thread.  Since "The G76 canned cycle is based on the G33 Spindle Synchronized Motion", multiple G33 passes should help you determine if the synchronization start point is exactly the same place without any other motion distractions.

Try it at different spindle speeds - but use the same speed for each set of repetitions.  If you want to test my claims about the bug, run a 4-pass test, but increase the spindle speed by 100-200rpm each pass.

If the start point is the same every time during G33 (same spindle speed) - but not during G76 - you've got a threading-specific problem.
If it's not the same, you've got a more fundamental synchronization problem... mechanical or LCNC configuration.  Or you may be encountering the bug I mentioned earlier from a different direction.