Messages

841

VB and the development of wizards / Re: How to set the feedrate with a button

« on: March 06, 2013, 04:28:58 AM »

A little caution here guys with where you are so far. Feedrate is 1000. You press the button and feedrate drops to 10. But what happens if a gcode F1000 happens to come along? You press the button again expecting a feed of 10 but you get a feed of 100,000.

Ian

842

General Mach Discussion / Re: XML file error or Mach 3 confused !

« on: March 05, 2013, 10:37:25 AM »

hi buba - welcome

post your xml and someone will take a look at it

Ian

843

Machscreen Screen Designer / Re: User DRO (Counter)

« on: March 05, 2013, 08:09:35 AM »

 

844

Machscreen Screen Designer / Re: User DRO (Counter)

« on: March 05, 2013, 07:48:43 AM »

works just fine here. please post your macro.

845

Machscreen Screen Designer / Re: User DRO (Counter)

« on: March 05, 2013, 07:30:43 AM »

The point is that if your macro works in the CB editor then changing the code is irrelevant to your problem. I only provided my code because it's the simplest code to do what you want.

The correct location depends on YOUR profile name. If you're using the standard screenset then your profile is displayed at bottom right on the main (program run) screen. The default is usually Mach3Mill. Then you save your macro as c:\Mach3\macros\YOUR PROFILE NAME\M1001.m1s

Ian

846

Machscreen Screen Designer / Re: User DRO (Counter)

« on: March 05, 2013, 07:02:56 AM »

you don't need any while isMovings, sleeps or variables for what you're doing. If all you want to do is increment a DRO with each call to the macro ALL you need is the single line

SetUserDRO(1010, GetUserDRO(1010)+1)

Type it into the vb editor and try it - THEN make sure you save it correctly and in the right place. If you do that it will run from the MDI AND from GCode.

Ian

847

VB and the development of wizards / Re: Difference between Macro and Button Script?

« on: March 04, 2013, 11:42:25 AM »

If not response time, why should probing precision depend on feed rate?

You're the hardware guy - you tell me 

The presumption you offered is one I've heard before but as I've said is not one I agree with. This is how I satisfied myself long ago that it's not the case.

Take a microcontroller dev board (PIC, ATMEL whatever you like) and program it to count a number of interrupts on the pin of your choice. Connect the axis step pin from Mach to that interrupt pin. I set it to count an arbitrary 50,000 step pulses but it doesn't matter. When it hits that 50,000 count, program it to activate an output pin connected to the probe in pin of Mach.

Now send the axis to 0, reset the microcontroller, then do a G31 Z(whatever) that takes it to a position BEYOND 50,000 step pulses on YOUR system. Have the gcode var monitor open looking at var 2002. If all is set up correctly you'll see a value in 2002 that is the trip point and represents the distance YOUR system travels for 50,000 step pulses. Now repeat at your leisure at ANY feedrate you like. The value in 2002 will ALWAYS be the same and as I've said will be the distance Mach traveled when it tripped.

I hope you'll agree this models a probe that trips at the exact same position every time and thus takes out of the equation any mechanical issues. It also proves that Mach's ability to read the probe trip AND store that position is INDEPENDANT of feedrate.

Cheers

Ian

 

848

VB and the development of wizards / Re: Difference between Macro and Button Script?

« on: March 04, 2013, 07:50:59 AM »

Ian, useful comment, I am using the parallel port.  Nevertheless, quicker feeds do seem to affect the accuracy when I try them, and I think I have seen other posts saying the same.

Indeed - my comment was in reply to your presumption as to WHY.

Anyway - to your code... There are a few potential gotchas in there that may be causing issues. The first one is that you make no use of the first contact test. Perhaps worse is that the first contact test result can drop through to the second test.

Also your use of goto is badly structured (as goto invariably is) in that you jump out of an if clause - this can cause all sorts of hard to track bugs. I suggest you loose the label and the goto and use a repeat loop and sign the plege that you'll never use goto or labels again.
 

Ian

849

Modbus / Re: Modbus Slave simulator

« on: March 03, 2013, 04:25:37 PM »

 

850

Modbus / Re: Modbus Slave simulator

« on: March 03, 2013, 03:08:50 PM »

I mean really, just say it out loud once.

OK you got it

WTF? - It's Sysiphus NF Sparticus you amateurs 

Ian