Advanced Search

Have you download to drive the parameter file i attached?Check the manual for the Asda-A2 drive has more detailed infos.

Hello,

I was planning to bore out a disc yesterday and thought I'd handwrite the code. The circular path would be 105 mm in diameter with the center at G54 X0, Y0, and starting at position X-52.5 Y0. Because of my lack of experience, I wrote is as a small program so I could get a preview. But the preview is not what I expected for the:The arc is started from position X-52.5, Y0.

As you can see in the screenshot, the preview shows a strange linear movement and a counter clockwise helix. But when I run the code, the machine makes a 105 mm circle in the XY plane, just as I wanted. The path from this run is visible as well (the red line). I'm guessing I'm doing something wrong, but what?
 

Hi,
it's possible to delete my account ?

My apologize ...
sorry I can not show same speed test because I am currently weeks out of office but we can just multiply or devide values ... because it is linear dependecy during constant speed movemet ... 

I can just customize current images to show exact difference ...  compensation off ferror = 0.125mm at 15m/min ...  compensation on ferror = 0.00009028mm at 1m/min and multiply it by 15 we get 0,0013542mm which is significantly less then 0.125 ..

What I remember from testing by my short eyes it whas something near 0.001mm during that 15m/min testing was done with bentch top setup without any load presented... just AX5106 with AM8xxx motor 

but I can go home for testing this weekend to create exact speed difference testing if it is neccessary

No apologies needed [img]/media/kunena/emoticons/wink.png[/img]

 

I can understand You and YangYang, its added job, but I openly disagree ... its the best time to improve lcnc and solve it at native level for ever, no other proforma hobby solution as now my is...

it should be solution for everyone who not understand it soo well as you guys... my solution of compensation will be even more inaccurate when scurve will be done and implemented ... 

I can not say you what to do, your job, your rules, your output ... thanks for your upgrade to curving
 

One way to help diagnose this (assuming it's a hal issue)  is to run
LinuxCNC, and then turn on the spindle at 1/2 speed.

Then, in a terminal window, type:

halcmd show all | grep spin > spindle.txt

and post the created spindle.txt file here.

But I have homed the axis and the little diamond, or whatever it is, is showing next to it. But Touch Off gives this error message.  I have been using this INI file for months without problems. This is a Sherline mill so there are no limit switches. The only axis that homes is A, which is not connected. It homes and sets to 0.000.

The 7I76R14.BIN image will not work as there are two program images
in the DSPIC code (the setup and working images) This is done to allow
live updates.

This is the complete 7I76 image:

 

 

Hallo,
und danke für die Antwort Luca, ich lasse mir etwas Zeit, sorry. Der Rechner läuft noch nicht wieder, ich strukturiere gerade meine EDV neu, Winterarbeit. Sobald das erledigt ist geht es hier weiter, ich melde mich, das ist bestimmt noch nicht die letzte Frage .

Gruß
Mario

I changed your Topic title to something more descriptive.

You might want to give some more information on your vfd and how you have wired it to your 7i96s.

Thank you for responding. I am sorry I did not include more info. My board is a 7i96s and now I have encoder feedback. Turns out there was a wiring error. Now I have negative values and way off when doing M3 command. I set my amt102-v to 1024ppr so i was using 4096 in pncconf. I am new to this so using pncconf appeals to me for as much of the build as I can.
I am curious if the mesa config is better than the pncconf and can I make a separate profile in it? I was working on getting the encoder working and at the same time I changed some settings and now my spindle does not work. I have the m3 come on and the vfd shows hz rising and then stabalizing but the fan on the vfd does not come on and i have no 3 phase coming out. I should not have been messing with the wiring and at the same time changing settings and will try not to do that again, but for now I dont know which one it is, the settings in pncconf or a wiring issue.

Yes, I think people get carried away chasing the minimum. If it works without error its fine, up to about 200 usec of latency works mostly, I used 130 usec for years...

 

test with this, this is dlen2 code

 

this is without

    

we know is not ideal, but at the moment, best we can do

@grandixximo

After commenting out " || (dx - moveL <= dlen2)", the scope looks like this.

Been working on a purely python touch and probe screen that does not alter the INI or HAL files. This supports Center of Hole, Edge detection X and Y plus and minus direction, Z touch, Boss Center location (circles, squares, rectangles), and Center of Pocket. Every touch/probe move has initial feed rate and then a second touch off at final feed rate. So far testing is going well with some minor debugging. I will soon add tool-change routines and support work fixtures as well.    

endian wrote:

My apologize ...
sorry I can not show same speed test because I am currently weeks out of office but we can just multiply or devide values ... because it is linear dependecy during constant speed movemet ... 

I can just customize current images to show exact difference ...  compensation off ferror = 0.125mm at 15m/min ...  compensation on ferror = 0.00009028mm at 1m/min and multiply it by 15 we get 0,0013542mm which is significantly less then 0.125 ..

What I remember from testing by my short eyes it whas something near 0.001mm during that 15m/min testing was done with bentch top setup without any load presented... just AX5106 with AM8xxx motor 

but I can go home for testing this weekend to create exact speed difference testing if it is neccessary

No apologies needed , I discussed this with YangYang. We agree this is a real issue on some hardware, but it should not be in the TP.The TP's job is to generate a geometrically correct path with proper dynamics. It does that. The path is correct.Transport delay compensation is a communication/hardware layer problem. Different drives, different bus cycles, different delays. Some drives have 0x60B1, some don't. Some run 250µs, some run 1ms. This varies per setup.Your HAL component is the right approach. It sits between TP output and drive input, users can tune lead_cycles and kff for their specific hardware. People who need it use it, people whose drives handle it properly don't.Keep the TP clean, keep hardware compensation in HAL. Well defined purposes.