HYPlugin and 2017 Screenset

[zymurgy42]

UCCNC Version 1.2036, 2017 Screenset V1.06 and Hyplugin V1.00094 (ENABLED and Call startup both selected!)

Using the default screenset and hyplugin, I set the hyplugin SACT field to 20050 (recommended). Edit screenset to match. Spindle starts and I can control speed +/-

Wen I do the same in the 2017 screenset, spindle won't start (relay in VFD clicks).

Put 2017 screenset SACT field back to default 869 value, spindle starts, but field doesn't update (as expected).

2017 screenset SACT field at 869 value, update hyplugin SACT filed to 869, spindle starts, but field flickers at 3000 (minimum speed). I can increase / decrease speed, but SACT field is constant at 3000 (it flickers, as I think your screenset is writing there as well).

Happy for guidance in the errors of my ways

Gordon.

[ger21]

Are you changing the RPM field in the screenset, or the S field? Sact is the RPM field, I believe.

[zymurgy42]

Gerry,

I'm using the orange colour slider, to vary speed.

Gordon.

[ger21]

No, When you edit the screen, which field are you changing?

[zymurgy42]

Gerry,

It's the field beside the S: which has a labelnumber of 869

sact.JPG (20.01 KiB) Viewed 28351 times

Gordon.

[ger21]

Sact is the RPM field, #870.
I think your changing the wrong field.

[zymurgy42]

Gerry,

You are correct. Use the right field and all is OK

Thanks Gordon.

[Dan911]

Hi Gerry,

What labelnumber are you using for the slider for spindle override?

The HyPlugin monitors and uses the plus and minus buttons for spindle override, buttons 135 and 134 in default screen. The plugin does have a secondary check and the override will still work but I suspect it will respond much slower. If you aren't using labelnumbers 135 and 134 for the override please let me know so I could adjust plugin.

Dan

[ger21]

The slider works differently than the buttons.
Buttons 134 and 135 increase or decrease the value in Field #233, which is the SRO DRO.
The slider manipulates Field #233 directly. You'd probably be better off monitoring Field #233, rather than checking for the button presses.

I'll send you a link to the latest screenset this afternoon so you can test with it.

[Dan911]

Monitoring field #233 is the secondary check I mentioned in previous post and original method used. Some users mentioned a slight delay with that method and using the 135,134 buttons fixed that. I will take another look for other possible solution.

Dan