Messages

1

Mach4 General Discussion / Re: Message Box

« on: July 08, 2018, 08:24:10 PM »

I just wanted to mention that other message boxes appear to be working normally

Lou

2

Mach4 General Discussion / Message Box

« on: July 08, 2018, 08:20:06 PM »

Greetings All,

I am having some trouble with the message box display being hidden while executing an m6 command either in g-code or in the MDI. (refer to creating an m6 tool change by DazTheGaz in Mach4 Videos - his LUA code.) What happens is when the m6 is executed the program apparently inters into a wait state, waiting for input from the message box dialogue. Sense the boxes are hidden (they are not behind the screen) no input is possible, so the only thing left to do is close down Mach. After the program closes the message boxes appear on the screen asking for action. Click on the boxes, they close, then open Mach up again and repeat. That's the circle I go in if m6 is issued. I'm sure the solution is a simple one, I just don't know it.
If anyone has any guideance to solve this, it would make my day.

Thanks, Lou

3

Mach4 Videos / Re: Creating an M6 Toolchange in Mach4 (Part 3)

« on: July 08, 2018, 03:14:51 PM »

Greetings to all,
I’ve installed the m6 script on my machine, (thanks for everyone’s hard work), each time it runs the message boxes remain hidden. Obviously sense they can’t be accessed, it’s not possible to complete the routine. The only thing left to do is close Mach4 down. After Mach has closed the message boxes then appear allowing them to be closed also. The other messages in Mach appear to work normally. If an m6 command is in g code the machine will retract the z, move to the tool change position etc. If the command is issued in the MDI, nothing happens but it is apparent that Mach is in a wait condition, waiting for input from the message box. I’m sure there is a simple answer for this, I just can’t find it.
Thanks, Lou

4

Mach4 Plugins / Re: XHC WB04 plugin

« on: July 05, 2018, 10:53:57 PM »

Thanks for your hard work, working great. I have had this pendant from my time with Mach3, sense moving on to Mach4 I've been stuck without a pendant. Life saver!!!

Lou

5

HiCON Motion Controller / Re: Following Error

« on: June 30, 2018, 02:16:41 AM »

Craig, your welcome, and thank you.
We’ll pick this up at a later date. “Her inside” has a list about yeh long. Prioritize, that’s word of the day. It’s worth it, 45years and counting.

Lou

6

HiCON Motion Controller / Re: Following Error

« on: June 30, 2018, 12:34:23 AM »

Craig

Got it, it’ll take some time. Do you want to know how it comes out?
Thanks
Lou

7

HiCON Motion Controller / Re: Following Error

« on: June 29, 2018, 11:03:36 PM »

Craig,
Your correct on all points as usual, and it might be that you have won me over completely. It’s just an attempt on my part to justify the money I spent on this product to start with, notwithstanding explaining to my wife why I didn’t need to do that (as I said briefly before, my best friend has NOT run away with my wife).
 
I understand that I don’t need to give the 7766 any encoder info at all but if I do then the DRO’S in Mach4 will display the actual machine position based on encoder input as opposed the commanded position. Just seems there has to be some value in that.

Thanks
Lou

8

HiCON Motion Controller / Re: Following Error

« on: June 29, 2018, 09:34:10 PM »

Craig,
I’m not opposed to using the drives to close the loop, but there is a bit of rewiring to go that way . The outputs j2 thru j4 would have to be used on the 7766 as opposed to j8 which carries all step and direction as well as all encoder signals. J8 connects through a 24 pin cable to a 7737 encoder board which collects encoder signals and outputs step and direction signals through rj45 Ethernet cable connections. (It is the j8 circuitry that is activated with the closed loop purchase from VSI.) Without the use of  j8 I’m not sure how to wire the encoders. Just simpler at my level to use the 7766, not saying that there isn’t a workaround for the encoder inputs, l just haven’t dug into it yet. It may be possible to output step and direction through j2 - j4 while collecting encoders through j8 thus not closings the loop in the 7766, but I don’t yet know that. As far as using the built in software scope, that has never displayed any motor information at all, are you suggesting that maybe that function only works with the 7766 in an open loop condition? That would be good news indeed.

Thanks for your interest and any input you have to offer is much appreciated,
Lou

9

HiCON Motion Controller / Re: Following Error

« on: June 29, 2018, 08:30:02 PM »

No, sorry for not being more clear, what I meant was swapping my closed loop drivers for leadshine AM882 drivers (regular open loop) which I already own, thus avoiding closing the loop with to different devices which is what average Joe was advising against. Presently I have the loops closing within  the drives and the 7766, although the perimeters are set much closer in the 7766 than the drives. That being the case, the drives never get within an error condition. But as I understand from Craig’s explication is that this is far from ideal because of many reasons he described and probably more. It’s just simplifying an overly complex setup.

Thanks,
Lou

10

HiCON Motion Controller / Re: Following Error

« on: June 29, 2018, 07:59:18 PM »

Craig,
I haven’t yet gotten around to swapping out the closed loop drives yet, but that is the way I intend to go. That seems to me to be really good advice.

Lou