Advanced Search

I use "dark reader" and since 3 days ago it does not allow me to reply to anything here without disabling it.

Yes and no, sorry my bad, i thought i uploaded the new config there, so thank you for reminding me.
I did upload the new config there and added some more info at the top, so have a look at your own leisure.
These are also new machines i have built and use the same configs for PWM and here i did upload the new configs.
forum.linuxcnc.org/show-your-stuff/46752...ver-etcher-scratcher

Latest config with provisions for disabling PWM on program pause or stop and enabling on resume.
Edit:
Attached the latest config to the first post, also.

Tommy are you talking about the engravertest.zip?

Ich habe keine Add-ons installiert und das Design nicht verändert. 

Firefox und Microsoft Edge haben beide den gleichen Fehler. 

Was meinst du? 

Sorry but i do not have any file you need, i would have attached them on my first reply if i did.

In the ini file
HOME_OFFSET = -3
for each joint/axis
That is for metric machine, adjust accordingly for imperial.

Okay, so maybe we can conclude that somehow the hardware is not 100% suitable on your "real" setup?

If you still test on the N100, I believe you could force the setupAsyncTransfer error by putting the loops back to original values (or even higher), and jogging while a program is running.

Thanks for the very quick help. Fabex is BlenderCam renamed because of a naming dispute between blender and the author(s) of the CAM add on. 1 week ago I installed the latest Blender 5.0.1 and the latest Fabex 3.0.1 from their official repositories. Due to the famously complex non standard Blender GUI I am not sure I have all the configuration and settings correct. That is why I am looking for a simple .blend file for CNC machining which ALREADY is fully set up to generate GCode.( the resultant Gcode would probably be handy too ). That way I can back check where I might be making a mistake. If you or others have already run BlenderCAM I think any simple/ non confidential file would do the trick.
Cheers and again thanks.
Alan J

In your archive there are many files, but I can see (as ncam xml files) only the default tamplate.
Please, in ncam, use the menu "Project->Save as..." to save your ncam project as xml and post here.
Are you using a milling machine or a lathe?

Regards
Giovanni

I should have stated - the limit / homing, picked off machine, home axis - trying to home one at a time, the axis moves to the limit switch and locks, need to over ride limits, move axis off limits - all axis

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.