Hello Guest it is March 29, 2024, 12:50:52 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Davek0974

1221
General Mach Discussion / Re: Bridgeport Knee Mill Conversion?
« on: September 05, 2016, 03:49:54 PM »
Ok, recent issues being fixed now, moving right along - servo tuning.

Have done nothing on these apart from an auto-tune in CSMIO setup. I thought the results were ok, but having spent a few hours today scouring the 'net it seems they were pretty bad really. The first video here shows one axis after an auto-tune. Now, I have zero experience with servo's being stepper builds up to this build, so I stand to be fully corrected but, i think the graph shows pretty bad over-shoot or oscillation?

https://youtu.be/IOAS4LMJzcg

So, throwing caution to the wind, i dived in and removed all of the "I" and "D" parameters as well as the "ff" or fudge-factor i think its called. That seemed to improve things so i started increasing the gain in steps of 1,000 and the graph seems better to my untrained eye?

The following error is lower, dead-band is reached faster and the dials on the machine no longer overshoot and slowly wind back to a stop - this was a concern as i could see it affecting cut quality etc.

This video was shot after my messing around...

https://youtu.be/Yr4joMqo61Q

Now, please feel free to rain on my parade, but does the last video look happier than the first?
Is there any issue running with zero "I". "D" & "ff" values?
I can't hear any grumbling from the motors, there is no visible 'hunting' at idle, following errors are down and the dials now stop on a dime as shown.

The Z axis would not tolerate as much gain and did go into permanent oscillation once so i backed off a fair bit but still no "I", "D" & "ff" values.

Suggestions?

1222
Thanks Hood,

Yes its UserDRO 1501 to 1503 now.

I have fitted a reset button on screen now and yes it does work as i thought earlier, so all i need to do now is fit a pulse of some sort to trigger the counter each time Mach comes out of reset, that shouldn't be too demanding i think, just a matter of figuring the best way. I am using the 5v supply to the encoder for the pulse to the input of the line driver, still not sure if it should be 0v or 5v though, but it works on 0v.

Back to the main issue...

The new screen-set with user DRO and code moved to a VB button seems to have fixed all the troubles, been messing with it for a good couple of hours and cat get it to lock-up or otherwise stall or mess about. Tool height-setter can be called any time, works every time, macros still work before and after using it, all motion calls still work.

Thanks all

1223
Thinking about a reset button over my coffee ;)

Should be simple - just needs a vb button on screen that sets a #var to whatever value is in the encoder counter when pressed, lets call it #null-me-out

In the macropump code the sum would now be...

set user dro to (encoder-count - #null-me-out) / steps-mm

any reason that should not create a button that can zero out the DRO at any given reading?

1224
Hood (mainly), I just got a reply from Cs-Labs re the reset or index situation....

"
The counter value of the CSMIO-ENC module are reset with reset in Mach3 and that is the only way to zero the counters.
 
To solve that you can use your own UserDRO to which you will copy the counter state.
Whenever you want you can reset your UserDRO state.
The UserDRO reset isn't about entering 0 value to it.
It's about adding or subtracting the value to get the 0 in your UserDro.
"


So that answers it then - to reset the counter you have to reset Mach3, the index just enables the counter initially.

So, with some thought, a 'Zero" button should be do-able but i'll save that for another day i think, it works well as long as the reader is down at ref position when you get going, my one is a bit stiff (ooh-err) as the linear motion is pretty poor but was free :), your linear guide version won't suffer this issue.

Interesting.
 

1225
General Mach Discussion / Re: Bridgeport Knee Mill Conversion?
« on: September 05, 2016, 07:44:06 AM »
Fair-do's :)

Yes i now know what can happen with those two lines of code, and also that the improved version fixes that issue, also not to apply a kludge over an issue even if it fixes it unless the issue cannot be fixed properly ;) Been very educational has this project.

1226
Wojtek or Andrew, can't recall which, advised me that actually using a line driver for the Index pulse would be a be the correct way but as I had it done with the pulse and it worked I have never changed it. It could be that having the line driver pulse it then the Index will reset every time the button is pressed rather than just once after reset, not sure......

Hood

As i now have the differential feed for the index/reset but it made no change, reading up on the signal to feed the line-driver with got me to this point..

I am currently pulsing the index input low with a button but the encoder provides a voltage output - see diagram in pic below.

The encoder instructions list the output as "Provides a voltage output" for this model.

Should i really be supplying a +5v pulse instead?

1227
General Mach Discussion / Re: Bridgeport Knee Mill Conversion?
« on: September 05, 2016, 06:58:18 AM »
Thanks Stirling, yes, i think I have now addressed all issues on this balls-up, i will try and refrain from "thrashing" again but to somewhat mitigate my balls-up, I did test the use of the OEMDRO manually before plunging in and it did seem safe, i was unaware of the M-Code issue as I presumed that as the 2010 screens was working very well, there were no issues in just editing one of the called macros' .

Anyway, I am confident that all the issues will disappear tonight .

Thanks for your patience, apologies for having a higher than average specific density in the brain area :)

1228
General Mach Discussion / Re: Bridgeport Knee Mill Conversion?
« on: September 05, 2016, 06:37:40 AM »
Just to nail the lid on this saga, I have modified the custom screen-set on which Ger21 kindly left a neat little gap next to my new user dro, and have managed to add a VB button, so i can now get rid of the double macro call as well as the OEMDRO issue - this should put my system perfectly in line with Hood's proven working version :)

1229
I think Stirling has identified the issue and I will test it tonight, it appears either my ill-advised use of DRO803 is the issue and/or the fact that i am calling the macros from a macro and not running the code directly in a button.

The pudding will be proved tonight ;)

1230
General Mach Discussion / Re: Bridgeport Knee Mill Conversion?
« on: September 05, 2016, 06:07:53 AM »
Your'e a star Stirling, and Hood, and I'm an ass ;)

I'm so glad it was not just me getting the odd results, even though it was my fault.

I have now got a custom screen set from Ger21 with the A axis DRO removed and replaced with UserDRO(1444) so that should solve all issues instantly as it will not be connected to anything internally.

I guess pressing the stop button resets the interpreter?

I will abort further testing and go straight for the new screen-set and test on that, no point in beating the dead horse any more.

Ger21 was right in his reply though as even Hood's suggestion of using the OEMDRO(100) i think, is a Mach DRO for encoder 4 although it seems it works ok for this usage as he reports. Maybe it is more allied to the Mcode calling issue than the actual DRO used as Hood has his code in the buttons??

As for your last paragraph I am still trying to get my head round that conundrum! Sounds like a real hornets nest of trouble there, is there a safe way to not run into that issue or prevent it happening?