Messages

361

CVI MachStdMill (MSM) / Re: The Brains

« on: July 23, 2010, 10:37:11 AM »

OK, I'll buy that the numbers are 1%, 2% and 6%.
I guess I was tired and when I read the brain immediate compare operation to the value of 1.0, I converted 1.0 to 100% (thinking that 1% would be in the 0.01) - but I forgot the units on the DRO are %.

So we have a brain that, as long as the FRO is between 2% and 6%, it will cause a cycle start event. If the FRO is set in that range, the cycle start events will be generated at whatever the run period of a brain is (probably the mach 1/10 sec background cycle - but I'm not sure, only guessing re the actual brain run loop run period).

Does the "I can't type into the MDI line before it closes" happen only when the FRO is between 2% and 6%?
I'd guess that if the FRO is reset to 100%, the "I can't do MDI" symptom does not occur?

Since a cycle start will close the MDI Line, this means that the MDI line is getting cleared every  1/10 of a second.
That would seem to explain why one can't get type text into the MDI line - right?

Dave

362

CVI MachStdMill (MSM) / Re: The Brains

« on: July 23, 2010, 01:14:58 AM »

UH, Guys....?

OK, I got curious and at least one of those brains frankly strikes me as a bad idea...

Perhaps I miss read the brain logic - but it seems to me to be saying that

if feed Ovrd < 100% then feedhold the machine (and turn on a user led 2222)

followed by a rung that says

if user led (2222) is on
(which I think is intended to indicate that this brain's prior rung created the feed hold)
AND (now)
200% < feed ovrd < 600%
AND
the mach feed hold led is on (I.e. the program is paused)
THEN
     **** automatically do a cycle start action *****

If I understand this correctly, I could drag the FRO slider to < 100% and a feed hold happens, when I then drag the slider to above 200% the machine starts running the loaded code...  without the operator ever touching a cycle start button.

My first reaction was "really"?!?  Doesn't anyone else think that generating cycle start events by any entity other than the human operator is more than a bit dangerous?

Or is there more to this context (i.e. other stuff this brain is working with) that would mitigate the danger?
Maybe there are other semantics to LED 2222?
Did I miss something here?

...AND a cycle start event will terminate an open MDI input line.
MDI stands for manual data input - where the D in MDI is "data", and data here really means a block of gcode.
You can't be trying to put a gcode block into the input queue to be executed at the same time that the gcode interpreter is running a loaded program.... which pretty much explains to me why the activation of this brain will close an Open MDI input window...

Dave

363

CVI MachStdMill (MSM) / Re: Go To Zero

« on: July 23, 2010, 12:36:24 AM »

This issue has been corrected in MSM Beta 2.
Dave

364

CVI MachStdMill (MSM) / Re: ReadMe file woes

« on: July 23, 2010, 12:19:39 AM »

Grumph, sputter, choke, Grrrrrrrrrrr    

Dave
 

But now I see there's another "readme" file to download & "skip".

Karl

365

CVI MachStdMill (MSM) / Re: ReadMe file woes

« on: July 22, 2010, 10:03:21 PM »

Hi Karl!
I was wondering when you'd show up... after all I did leave a comment just for your amusement in a sticky thread above.
Good to hear from you and welcome aboard.
I hope you'll like using the MSM beta.

Dave

366

CVI MachStdMill (MSM) / Re: ReadMe file woes

« on: July 22, 2010, 07:28:37 PM »

Mike,
Did you get the readme file ok?
If not, I can send it to you via email etc.

BTW - Fearing my wrath? That idea would have my better half chuckling

Dave

367

CVI MachStdMill (MSM) / Re: Edge Probing

« on: July 22, 2010, 02:55:09 PM »

FYI - for those following this thread, I spoke with Tom earlier today.
He's planning on using MSM to do a job he has to get run.
(Brave man to do a real production part on beta software, I suggested that beta software should not be part of a critical path job, but he wants to use MSM).

In a couple of days when his parts are done, and schedule is more flexible, he and I will get back in touch to figure out the probing things he is seeing.

Dave

368

CVI MachStdMill (MSM) / Re: Edge Probing

« on: July 22, 2010, 01:17:34 PM »

Hi,
I'm glad you like the screens so much you don't want to go back to 1024....  
(Something I learned in high school: how do you sell a puppy dog? Get a kid to take it home "on trial" overnight...)  

Remember to put the geom of the edge finders into the tool table! ALL GEOMENTRY comes from the tool table.
(See manual section 12.1)

I sent you email with my direct contact info yesterday - did you get the email?
Have you replied (I don't have email form you)?
If you'd replay by direct email with your phone #, I"ll arrange a time to talk with you via phone.
I think we will need an interactive, real time conversation to sort this out for you.

Be forewarned, for debugging we'll need to set up a clean, from scratch install of mach 3.43.10 and MSM beta 2.
I know that will kill off your accessories temporarily. Once we sort out the probing operation for you (it is working fine for multiple others), the other extensions you have can get added back in one by one.

We'll get you running eventually.

Dave

369

CVI MachStdMill (MSM) / Re: Inhibited LED

« on: July 22, 2010, 12:23:13 PM »

Tom,
great - one more bug squashed!
Dave

370

CVI MachStdMill (MSM) / Re: Inhibited LED

« on: July 22, 2010, 11:57:24 AM »

A thought comes to mind -

there is a brain that actually drives the drives the inhibited LEDs on the screens. It should be auto loaded by Mach when mach starts, but maybe it is missing or got turned off somehow.

Please look in c:\mach3\brains\autoload and check if "MachStdMill Safety Lockout LED Display" is in that dir.
if it is present, please use the menus to do Operator - Brain control. The dialog that appears should include 4 brains all of which have names that start with "MachStdMill" - all of them should be checked as enabled. If they are not enabled, please enable them and then click "reload all brains".

check the inhibit led - is it now working?
(BTW the MDI labels will also flash yellow when things are inhibited).

Dave