forum.cncdrive.com

CNCDrive,

I installed ver 1.2022 in a new directory along side ver 1.2020. I transferred my profile, macros, plugins etc to the new install from ver 1.2020, everything appears to have transferred properly with regards to settings. I run 1.2022 and the firmware updates to the UC100.

In diagnostics, the probe LED lights when I touch probe or touchplate. I perform a G31 move by MDI, movement starts, but the probe trigger is ignored (although the probe LED lights in diagnostic page during the move happening), and axis movement does not stop till reaching end position of G31 command. My tool setting macro also does not stop movement on touch anymore.

I go back and run ver 1.2020, the firmware updates again, and everything is working as normal?

My configuration that isn't working is:
software ver 1.2022
firmware ver 3.0090
hardware version 2.000
API version 2.0880
Device type UC100



Any thoughts or suggestions?

Regards,
Eric Brust

Post your .pro profile file please to let us check/test with your settings.

cncdrive wrote:Post your .pro profile file please to let us check/test with your settings.

Thanks for the very quick response!

I've attached both the .pro files from the 1.2020 and the 1.2022 installations.

regards,
Eric

PS: The forum won't allow uploading .pro file extentions, put in zip file.

Eric,

I've tested with your settings and it is really not working.
What I see so far or at least it seems to be that the probe setting does not apply for some reason on the software startup.
I came to this conclusion because if I load your profile then the probe does not work, but if I press the Apply settings button then it starts working afterwards.
I'm passing the issue to the API developer guys now, they should correct this issue very soon.

Also I will check how can I can allow to upload not only .zip files but other file extensions also.

I am having the same problem with probe not working after the update,

cncdrive wrote:Eric,

I've tested with your settings and it is really not working.
What I see so far or at least it seems to be that the probe setting does not apply for some reason on the software startup.
I came to this conclusion because if I load your profile then the probe does not work, but if I press the Apply settings button then it starts working afterwards.
I'm passing the issue to the API developer guys now, they should correct this issue very soon.

Also I will check how can I can allow to upload not only .zip files but other file extensions also.

Hi Balzas,

today I installed 1.2022 on my office PC, brought the UC100 in from the router to the office, and used the exact same profile I attached above to setup that installation. I attach a set of wires between pin 13 and 25 to emulate a probe trigger manually, and on my office PC, probing works as it should (stops on trigger)... yay!

Back to the shop/router with the UC100, that installation of UC100 still shows probe trigger in diagnostics, but doesn't stop on trigger. So I uninstalled/reinstalled, loaded the same profile, and it still doesn't work.

I thought I would report that I seem to have one installation (not actually attached to a machine) that works, and one installation that doesn't work, using the same UC100 device and the same .pro file... just to add more feedback/confusion .

regards,
Eric Brust

Hi Eric,

Thank you for the updated information.

I think the problem will be probably PC speed dependent then, there was a similar problem eariler with the encoder settings which we corrected,
there the execution was given back too early to the main thread, the download thread did not make sure properly that the data was downloaded,
but it returned the handle too fast, so the next download of other datas could override it before the data was actually download to the motion controller.
And on startup things happening in parallel threads for fast startup, so then these download threads can have less power from the computer than when later the PC is in about idle and then you press the Apply Settings, so on startup this is why this is more likely to happen if the problem is what I think is.
I think there will be something similar with the probe data now, but my collegue started working on this today, so I will know more soon and it will be hopefully corrected soon.

cncdrive wrote:Hi Eric,

Thank you for the updated information.

I think the problem will be probably PC speed dependent then, there was a similar problem eariler with the encoder settings which we corrected,
there the execution was given back too early to the main thread, the download thread did not make sure properly that the data was downloaded,
but it returned the handle too fast, so the next download of other datas could override it before the data was actually download to the motion controller.
And on startup things happening in parallel threads for fast startup, so then these download threads can have less power from the computer than when later the PC is in about idle and then you press the Apply Settings, so on startup this is why this is more likely to happen if the problem is what I think is.
I think there will be something similar with the probe data now, but my collegue started working on this today, so I will know more soon and it will be hopefully corrected soon.

Hi Balázs,

Any news about this? Or is this the only occurrence of the problem? I mean, you confirmed that Eric's configuration is right and that the G31 in his case is causing problems, not stopping in time. This is very serious since it may crash the probing tool or cause other damage. Probing is critical, so it would be very interesting to know the results of your colleagues work.

My collegue corrected the issue, working on the testing now...

cncdrive wrote:My collegue corrected the issue, working on the testing now...

Great to hear, thanks for the update Balazs. I'd be happy to test the updated version if it helps you guys validate the fix.

regards
Eric Brust