SmartProbe.ngc / G38.4 not working

[sopac]

Hi I'm rather new to EMC but wanted to give probing a try, gridprobe.ngc works just fine, but when I tryed smartprobe it would do its initial decent and when the probe tripped it would just hang there. upon further troubleshooting I realized the the G38.4/G38.5 just doesnt work, I get a message that the probe is already clear which is not the case verified thru Halmeter and by running a G38.2 which would give a message that the probe is already tripped.

I am running EMC 2.3.5

any help is appreciated.

[sopac]

I have tried compiling both 2.3.0 and 2.5-pre and both have the exact same issue, I have also tried creating a new config with stepconf and no change there either. am I alone on this one?

[sopac]

after further fooling around i discovered that G38.4 will actually work if I invert the parport input (change parport.0.pin-15-in to parport.0.pin-15-in-not) very strange. this of course is no helpful to me since I have a NC probe.

Is there a workaround to invert further down the line perhaps?

[sopac]

I was able to get it working by using ladder to invert the inverted input required to make g38.4/38.5 work. if any body has the same issue and wants further details about the work-around let me know

[sliptonic]

It looks like I'm hitting the same problem. Any additional details you can provide would be appreciated so I don't have to reinvent this. Much thanks.

[cradek]

Fixed.

SourceForge.net: Enhanced Machine Controller: Detail: 3040806 - G38.4 and G38.5 is not working

[pyrojon]

Is there any chance that this fix will be available as an update, if not how long will we have to wait for the next release that fixes this problem?

thanks

Fixed.

SourceForge.net: Enhanced Machine Controller: Detail: 3040806 - G38.4 and G38.5 is not working

[chester88]

according to the logs: this bug fix has been placed in the 2.4.
When the next bug release is has not been stated that I know of.

Chris

[pyrojon]

Hmm, I must be doing something wrong because it's not working for me in 2.4

according to the logs: this bug fix has been placed in the 2.4.
When the next bug release is has not been stated that I know of.

Chris

[chester88]

I wasn't clear.
its been added to the 2.4 repository but has not been released yet (2.4.7)

Chris

[pyrojon]

Ah, thank you. I guess I will wait for the next update.