Dynomotion Forum

For reasons I won't go into right now, this is now the current priority project, as I need a bigger mill. Servos are in the process of being ordered. Three 1.2kw 3000 RPM for the main axes (the originals were 1kw SEM DC brushed, and I've been advised 110frame 1.2KW will be a better match than 1KW 90...

I was about to post and say that doesn't work, but then realised you mean to use SetOrigin to set the global offsets, then use that code to make them active, which it does. At least in simulation (I've not got a KFlop handy to test it while connected), although the DRO doesn't immediately reflect th...

Moray, Thanks for the response. I can certainly understand you not wanting to give away all that work, or putting something out there that you don't feel isn't quite finished. But it never hurts to ask. Hope you can get things running how you like. Maybe you can post a short YouTube video of your m...

I'm also using a G52 call to set the global offset. Again, is that the best way? You should be able to change the G92/G52/Axis Offset with the same call as above with index of 0. /// <param name="index">Origin index - 0 for G92 offsets, 1-9 for fixture offsets</param> I'm sure I tried that while lo...

Hi Dan, at the moment I'm undecided whether I'm going to share the full code for this or not. I've got a few ideas I'd like to implement, which will be a lot of work, and I'm not sure I'd want to publish the code for no reward. I will certainly be uploading a complete exe so others can use the progr...

I've just realised what the problem is. The handler use inches, but I've had a bug in my single step code, where the first line gets skipped, so the G21 was ignored, I've not realised, and I've not been zoomed in close enough to see anything other than a green blob in my viewer. Plus I seem to have ...

I'll probably take the easy option, and just change it to a blocking message box, as nothing should be moving during this program.

I've hit an issue with the graphics :-/ If I single step through the code (I'm using Dynomotion.ngc), everything works as I expect. I step 20 times, the handler triggers 238 times, and if I step as far as the first 'o', it's been triggered over 10'000times. However, if I try running the code (either...

Use a sub-routine, and then configure one of the custom M-codes (I just used M110, but anything from M100-119) to activate an output bit. If you only want to have the horn sound for a set amount of time, configure another custom M-code to deactivate the output bit, and put a dwell (G4) command in be...

Thanks Tom, that's what I guessed. This is part of my tool changer initialisation code, so there are a few prompts to get information, then various messages if something specific fails, followed by a generic failed message, and it's mostly done with non-blocking message boxes and state machines wher...