QRadioButtons in preferences file

Well that worked a bit better. I can see an arc voltage!

On a dual monitor machine, the popup windows to set offsets etc are not constrained to the active window and were floating on the other monitor while I wondered why the screen was greyed out. They should be constrained to the application window.

I know this is not a Phill problem, but maybe Chris could review the behaviour.

I thought I'd ask while this is in development.
With a few of us using Lam drivers and servos, could we have a single error indicator for a drive fault on any joint. I think that would be achieved by oring all of the joint.N.faulted signals together.

If the user clicks on the indicator then could a window open that displays all of the joint fault pins (perferably with X,Y,Y1,Z etc displayed beside the joint number.

Possibly one spot to display this would be on one of the user buttons. Let the button go red on a fault.

Its just I had a big lost step issue on Friday becasue I was ignoring drive faults (wired to the 7i76e but not connected in HAL). I think if the fault was recognised and reported, It would have paused long before the part was ruined.

tommylight wrote:

+1 on the faults.
And that reminds me, i did order 4 more of THCAD, 1x 7i77, 2x 7i96, 2x 7i92 aaaaand forgot to order a 7i95 ! Dang, i would love to add encoders to those Lam drives and use the included BOOST feature, especially since i have already tested it and it works perfectly.
Oh well, next time.

After pricing encoders, I lost interest in that method. Instead I thought it would be possible to write a component which enables boost while accelerating which is more in keeping with what Lam suggests. One day!

rodw wrote:

Well that worked a bit better. I can see an arc voltage!

On a dual monitor machine, the popup windows to set offsets etc are not constrained to the active window and were floating on the other monitor while I wondered why the screen was greyed out. They should be constrained to the application window.

I know this is not a Phill problem, but maybe Chris could review the behaviour.

You can specify where qtvcp's builtin dialogs pop up by modifying the preference file.
I don't see where i have documented that ...

try :center,bottomleft,default are other options.
Other wise it should remember where you put them and how big they were.

If the dialog was built in the handler file then it might not follow these rules.

I have not tried it with a dual monitor system.
I'll do a little research about that - thanks