The Probe sensor was active.

If you think you've found a bug post it here.

Re: The Probe sensor was active.

Postby cncdrive » Sun Jun 19, 2022 8:11 pm

There will be only update on this in the next development release.
cncdrive
Site Admin
 
Posts: 4741
Joined: Tue Aug 12, 2014 11:17 pm

Re: The Probe sensor was active.

Postby kim@moltved.dk » Mon Jun 20, 2022 9:59 pm

THAT IS NOT OK, THE LASTE DEVELOPER RELEASE IS FROM 25 okt. 2021, 8 month WHEN THIS PROBE PROBLEMS AND PENDANT/REMOTH PROBLEM HAVENT WORK!!
kim@moltved.dk
 
Posts: 50
Joined: Sat Nov 25, 2017 12:25 pm

Re: The Probe sensor was active.

Postby cncdrive » Tue Jun 21, 2022 1:04 am

We have just published a UCCNC version which fixes the probe/pendant problems.
The issue you reported is caused by the new SPI bus feature which will be in the next development release and it seems it makes that particular pin on port 5. stuck, because that microcontroller pin is configured for SPI and isn't released properly when the SPI bus is not used.
So, yes, this will be fixed in the next development release, we working on it with full power now.
cncdrive
Site Admin
 
Posts: 4741
Joined: Tue Aug 12, 2014 11:17 pm

Re: The Probe sensor was active.

Postby kim@moltved.dk » Tue Jun 21, 2022 5:43 pm

yes but this pin problem came with this new version! This new version is updating the UC300eth firmware.
kim@moltved.dk
 
Posts: 50
Joined: Sat Nov 25, 2017 12:25 pm

Re: The Probe sensor was active.

Postby cncdrive » Wed Jun 22, 2022 2:57 am

Yes, and we will fix it in the next release.
Are you using all ports? If not then you could avoid using port#5 for now, you could plug your breakout board or whatever is connected to your port#5 now to another port. Port#1 or #4, those are ports with the same pinout as port#5
cncdrive
Site Admin
 
Posts: 4741
Joined: Tue Aug 12, 2014 11:17 pm

Re: The Probe sensor was active.

Postby Pulcik » Sat Jul 16, 2022 5:41 pm

Hi guys,

is it possible, that the problem was in version 2114, too?
I am experiencing inconsistent G31 executions. Sometimes it happens correctly, sometimes the G31 is not executed / skipped. Let's say 30% of the execution are skipped. Even when I stay on same place, and hitting Probe Z over and over. So the start of execution are exactly the same.

I have pendant UCR201, and UC100 as controller.
Same behavior I experienced with 2115, but I downgraded, because of the bug I reported earlier.

Will try 2113 later.
Pulcik
 
Posts: 39
Joined: Thu Aug 27, 2020 10:04 am

Re: The Probe sensor was active.

Postby Pulcik » Sat Jul 16, 2022 6:00 pm

Confirmed, it is same problem.
When I turn off the plugin, everything is fine.

So it is either downgrade to 2113, or stop using pendant, right? Or 2113 have the problem too?
Pulcik
 
Posts: 39
Joined: Thu Aug 27, 2020 10:04 am

Re: The Probe sensor was active.

Postby cncdrive » Sun Jul 17, 2022 10:03 am

You can download a correction for this issue here: https://drive.google.com/file/d/1grm6Mu ... sp=sharing
cncdrive
Site Admin
 
Posts: 4741
Joined: Tue Aug 12, 2014 11:17 pm

Re: The Probe sensor was active.

Postby Pulcik » Sun Jul 17, 2022 1:01 pm

Sure, I saw that.
My issue is the second bug I reported earlier.
In 2115 I can get probe / pendant fixed, but can not use G02 move correctly. That is not a tread off, I am willing to take.
My question is not answered, still. Is that issue in 2113 too?
Pulcik
 
Posts: 39
Joined: Thu Aug 27, 2020 10:04 am

Re: The Probe sensor was active.

Postby cncdrive » Sun Jul 17, 2022 2:54 pm

You wrote that problem confirmed in a thread which is about the UCR201 related probing bug in 1.2115, so I think it is logical for me to think that you were talking about that problem.
That problem was fixed and I posted you the link to the newer UCCNC version which is still 1.2115, but we changed the API in that download, so only the API version in the software is newer and it only fixes that probing bug.

The other problem you reported I already replied in the forum thread in which you posted that possible bug.
I asked my collegue "dezsoe" to debug it and he will report the result to me.
Please understand that debugging possible bugs and issues takes time, it does not work like you reporting something and we can immediately reflect, especially not on weekends.
We need time to reproduce the issue and if it is really a bug then to fix and release it.
I will anwer you in your forum thread as soon as possible, but it will probably take 1-2 days.
cncdrive
Site Admin
 
Posts: 4741
Joined: Tue Aug 12, 2014 11:17 pm

PreviousNext

Return to Report a bug

Who is online

Users browsing this forum: No registered users and 2 guests