Ah... so it's the MPG module slowing down the response. The Feedhold button is also attached to it so probably that one too.
This is the VB example they sent:
'10V = 4095 / 0V = 0 'IN 0 a = GetInput(80) SetOEMDro(800, a) 'Dro X 'IN 1 b = GetInput(81) SetOEMDro(801, b) 'Dro Y 'IN 2 c = GetInput(82) SetOEMDro(802, c) 'Dro Z 'IN 3 d = GetInput(83) SetOEMDro(803, d) 'Dro 4
Communication is VERY poor with them. Asked them about accessing the I/O from within a brain, but instead got a VB example. Probably could do the rapid override in VB, but think it would be much slower than a brain.
Hood, talking about speed, I was very disappointed with the rather slow response of the feedhold with the IP-S. Also FRO and SRO are pretty slow to respond. Just wanted to confirm it's the same for you. With the SS, for instance, with the controller frequency set to 4Khz, the feedhold and FRO respond almost instantaneously.
Deleted the XML and created a new profile again. Now this issue is gone. Have no idea how it was getting access to the old XML after I did windows restore.
Now got to the MPG. The way it is, is strange, because it appears that they made all the settings for me and I can't change it. I have a pendant with a momentary enable switch for the resolution select and the axis select (like they show in their example in the manual), but funnily this switch also enables/disables the MPG wheel, although physically they are not linked (like can be seen in their example). Is it the normal way it works? Also pressing this switch activates the two digital outputs on the MPG module as seen on the diagnostics LEDs. Have no idea why it happens.