[A_Camera]

In single register it also won't set a frequency , on start the plugin is reading your Sset field and will set that frequency if its 1000 or above.

OK, will try later tonight and get back.

[Dan911]

OK, will try later tonight and get back.

When you find time try this one I removed the 1000rpm limit and test>>>>>>>>>>Attachment 354138

[A_Camera]

When you find time try this one I removed the 1000rpm limit and test>>>>>>>>>>Attachment 354138

Will have the results in a few minutes. In the meantime, the one you posted in #8 is not working. The bps is OK, but the rest is the same. Have tried with minimum rpm 1000 and also 8000, just in case... but the results are as before.

Edit:

OK, now tested this one as well. Sorry, but no champagne yet...

Multiple register writing mode:

Now it seems that polling starts and is going on normally as in the single register mode before, but the spindle speed sent remains zero, even though I configured the minimum to 1000 and also tested with 8000.

Single register writing mode:

Now even the frequency is sent, but only four zeros, so even here we still have a problem, probably the same.

BTW, I am using UCCNC 1.2032 but I should not think this is a problem.

[Dan911]

Will have the results in a few minutes. In the meantime, the one you posted in #8 is not working. The bps is OK, but the rest is the same. Have tried with minimum rpm 1000 and also 8000, just in case... but the results are as before.

Edit:

OK, now tested this one as well. Sorry, but no champagne yet...

Multiple register writing mode:

Now it seems that polling starts and is going on normally as in the single register mode before, but the spindle speed sent remains zero, even though I configured the minimum to 1000 and also tested with 8000.

Single register writing mode:

Now even the frequency is sent, but only four zeros, so even here we still have a problem, probably the same.

BTW, I am using UCCNC 1.2032 but I should not think this is a problem.

WOW, never expected to read this, this makes no sense. The only other possible cause would be a cultureinfo problem that's been addressed and tested.

Please try this version I uploaded, I appreciate your time.

>>>>>>>>>>>Attachment 354172

Thanks,
Dan

[A_Camera]

WOW, never expected to read this, this makes no sense. The only other possible cause would be a cultureinfo problem that's been addressed and tested.

Please try this version I uploaded, I appreciate your time.

>>>>>>>>>>>Attachment 354172

Thanks,
Dan

I was thinking about the culture info last night after I turned my computer off, and yes, it's been addressed, but not for everything or every situation. At least that's how I remember a later discussion with Balazs, and my understanding is that it must be taken care of by each plugin programmer. Those two lines cause no trouble for anyone in US and are a PITA if missing for non-US users. So, if you have now added those two lines then I am confident that that was causing the problem. Anyway, we won't have an answer for another 10-12 hours because I can't do any tests before.

Edit:

Here is the discussion of the culture settings I was referring to:

forum.cncdrive.com ? View topic - New Problem

I think the conclusion was that it has to be handled every time and is only fixed for the handling of macro loops since they are compiled by UCCNC. A plugin is compiled before installation by the programmer. Kelevra in that conversation "fixed" his plugin problems by simply changing OS to US version. While that may be OK for some, it is not a solution, just a QD work around in my opinion. It is better not to have limitations if it is possible to avoid through adding those two lines.

...and here is the post with the clear answer from Balazs:

forum.cncdrive.com ? View topic - New Problem

Yes, those are the 2 lines which can be used to set the thread cultureinfo to EN-us and that fixes the problem.
But if you create for example 10 different threads in your plugin from different functions then you have to take care to write those 2 lines into all of the functions which are used to create the plugin threads before you start calling UCCNC functions from the threads.