Advanced Search

Eisbaeeer wrote:

Hi David
Did you get running the 2A?
Im own the version with 4 axis and trying to get the right ethercat config.
The name of driver is CL57E-4A.
I will try to expand your example to 4 axis.
Perhaps you can told me, if you get it running?
Greets Lars

I have a second driver from Lichuan called OLC-E57H. I will also try to get it running. I think this should work all in same structure (hopefully).

Its critical with multi axis slaves that the xml exactly matches the pdo structure. fire up linuxcnc and in another window, type halcmd show pin cia402* Look for the status word. (or use halshow) They all should have the same value. If they don't your xml is wrong (ask me how I learnt this)

following

Ok, I have managed the following but have a few lingering issues that I am asking for help with:

One statement - the 7i91 is connected through a short parallel cable to the mx3660. ALL pins are that way. Nothing is connected to the 7i92 directly, only have another parallel [header] no wire connections.

Solved:

• I can now run xyz axis in Pnnconf to test. Note the speeds I can use are much higher than what the parallel gave me. The axis no longer crashes or loses step such as when testing in Stepconf. Happy about that.
• Can run linuxcnc - but my Estop and limits do not work so constantly running a side terminal to use mesaflash xxxx --reload
• Jog and limit switch setup attemps the axis do run in the right direction for both program and jog - according to DRO
• Did insert - use isocplus - I have 12 processors so I set it to 2-11 and the latency nose dived. Yes I have the file if asked for - less than 13,000 everywhere.
• Did learn a lot and after getting the mx3660 --readhmid file and looking at my old ini/hal set everything in a spreadsheet detailing the 7i92 pins and the corresponding mx3660 bin, allowed me to match what I had from my old Stepconf hal for pin number. Played with the stepgen number till realized I only needed three.
• Found out it was easier to edit speeds and both home/limits in the ini file.

Help please:

• thought I had a working X axis limit but lost it.
• did use the same limits/home both settings from my earlier stepconf ini - but no matter what I do the axis moves, trips the limit and stays there. I also get limit error messages when enabling so I need to over ride limits to run anything and then recheck over ride limits ever time I move something.
• I may be wrong - I think my charge pump must be set up correctly or I think the axis would not be enabled. They disable - the 7i92 red light goes on - as soon as i exit linuxcnc and upon restarting, the red light goes off.
• Could it be that because my Estop still does nothing and is setup wrong? It is still connected to the mx3660, and it disables the mx3660 when tripped but there is no relative indication or any change in linuxcnc to either enable or the abort button in AXIS - does not matter what position the switch is in but of course it must be off to enable the mx3660 to move axis in linuxcnc. 

Rather than attach all sorts of files in a shotgun approach, I thought it better to ask what anyone may wish to see before I try to post them. If I could get my ESTOP and both home/limits to work I think all would be ok for further tweaking.

I have tried the old permutations of limit switch setup - setting like my old working stepconf, setting the switch to 0 and the home to 2 sort of like the setup diagram on linuxcnc, tried "-" on first the latch velocity like i read somewhere, and everything in between one change at a time, restart and run - no luck. Do not understand what is different. Axis scale is check and accurate, DRO reads correct, ballscrews dialed in and all that.

Thanks for trying.

Duplicated the setup to a N100 mini-PC.
Couldn't crash the xhc, didn't try for that long though.
So I unplugged the dongle. Put it back.
And it restarted and continued to work. Like magic.

It didn't fail at the usual setupAsyncTransfer, it was somewhere else.
 

Hello , here is my project , i hope there is no problem that it is a zip file , and if something misses ,while the file was copiing to the usb drive i had to skip some desktop linkages ,Thank you regards Tom  

Disable "dark reader" or such add-on.

Ich verstehe das nicht. Auf diesen Beitrag kann ich antworten, obwohl ich das Thema erstellt habe. Auf die beiden anderen, ebenfalls von mir erstellten Themen, kann ich hingegen nicht antworten. 

-> forum.linuxcnc.org/42-deutsch/58439-400v...drive-gesucht#343661
-> forum.linuxcnc.org/42-deutsch/58306-umst...-erfahrunge?start=10

 

tommylight wrote:

Can you post from a phone or a tablet?
 

Das Problem besteht gerade wieder. Auf Tablet, Smartphone und PC bekomme ich die gleiche Meldung.
Liegt das an meinem Gerät? Kann ich etwas tun, um diesen Fehler zu umgehen? 

Hi guys

does someone done a retrofit of the compact 5 cnc with turret with dc motor and NO feedback?

my way would be:

add a pyvcp menu to make move from tool position to tool position.

if i reach tool 1 i set with a button that its now tool1.

every move from tool to tool would lock first back and then drive forward to next position... 

turret can rotate forward free. Backward would lock it.
after locking backward reducing power is needed.

i have here a l298n modul and a mesa 7i92 with bitfile adjusted to have pwm and 2 gpios for setting direction.

i cant find a custom library for it. But is this the correct way to do it or i am complete lost? Its not the issue to set tool 1 manual over buttons.

Forward u would use pwm 100%
Backward pwm 60%
and holding against the pawl about pwm 30%

any ideas or help?

thanks

Signals utilized for operating spindle and feed override. The feed rotary button can serve in

• Continuous move x% from max velocity
• Step move x mm
• MPG override feed/spindle
• The special position Lead.
  Continuous: In this mode jogging is performed at the selected feed rate. As long the jogwheel turns, the selected axis moves.
  Step: In this mode the machine moves steps  wheel_counts at the currently selected step size and the current set feed rate in machine units. If the commanded position is not reached the machine keeps moving even the jogwheel is not turning.
  
  Lead: Manipulates the spindle override.
  
  MPG: Manipulates the feedrate override.
  
  See here  xhc-whb04b-6  
  
    Signale, die zum Betätigen von Spindel und Vorschubübersteuerung verwendet werden. Der Vorschub-Drehknopf kann dienen als
  
• Countinou: Bewegung x% von der maximalen Geschwindigkeit
• Steps x mm
• MPG-Vorschubübersteuerung
• Die Sonderstellung Lead

         Continous: In diesem Modus wird das Joggen mit der gewählten Vorschubgeschwindigkeit durchgeführt. Wenn man                        das Jogwheel dreht, bewegt sich die ausgewählte Achse. 

          Step: In diesem Modus bewegt die Maschine mit den Schritten  wheel_counts bei der aktuell ausgewählten Schrittgröße                  und der aktuellen Soll Vorschubrate in Maschineneinheiten. Die Maschine bewegt sich so lange bis die Anzahl der Schritte                abgearbeitet ist, selbst dann wenn das Handrad nicht gedreht wird.
         Lead: Manipuliert die Spindelübersteuerung
         MPG: Manipuliert die Vorschubübersteuerung


              Siehe auch   xhc-whb04b-6

 

Hi.
Existe the postprocess for Fusion 360 fo lathe machine , with use the g7x cycle ?

Thanks

Sach mal Mueke,

willst du ein komplettes Haus um die Achse drehen?

I need 1 card, 1 rpm sensor, 1 accelerometer + cable.

I can but, i dont really know how to copy the Config to the PC right now. I need to check that

Exactly the same log message.
I also tested to unplug + plug back the dongle. Exactly the same log message.
Both ended up in the debug message in libusb.

It can of course be my hardware. It isn't to difficult to test with another test computer I have.