Hello Guest it is April 27, 2024, 04:14:07 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - budman68

671
I'm sorry, Ian, I thought you meant for me to save the script in from the "empty" VB Script Editor, instead of just loading the macro file into the actual folder ......duh....  :D

Now I saved an "empty" one and it loads up fine with the normal reset flashing and jogging works as well.

Dave

672
After following your instructions With the macropump still unchecked in General Config: The DRO's in Mach still jog, but the LCD does not update to reflect those movements.

After that happened, I checked the run macropump in Gen Config and restarted and the same thing, no movement on any buttons or flashing reset.

So there's obviously some sort of "roadblock" or bottleneck that isn't allowing the macropump to work upon startup? Possibly try a simpler macropump example?

Thanks,
Dave

673
No, no, I'm the one who's sorry for thinking that is all that would be in the Macropump. I guess there are many ways to use this and was just thinking you should be able to read my mind  ;)

I wanted to add some more details about the startup that I missed. The DROs do show up on the LCD screen and read exactly what are shown in the DRO's in Mach 3.

Quote
switch off your macropump. From what you said above - Mach should now work ok - yes?

Yes, correct.

Quote
open vb editor - paste macropump code - run code in editor - does it come out on your LCD? is Mach still OK?

Yes, it worked. As soon as I hit the "run script" (green arrow icon), the LCD screen updated to reflect exactly what was on the Mach 3 DROs

Dave

674
Hi Ian,

Sure, but it'll look very familiar ;o)

Thanks,
Dave

675
Hi Terry,

When I have everything connected, with the macropump in the macro folder, and "run macropump at startup" checked in General Config, I start Mach 3, and what SHOULD happen is my RESET button should immediatley start flashing as normal. Instead, it just sits in the red "state" and when I click on ANY buttons, they do not do anything. Nothing at all, like it's completely frozen.

The minute I uncheck the "run macropump at startup", all works fine. Somehow, something isn't happy running with it or it's as you and Ian, said, somethings just not being transferred correctly.

I have a Shuttle Pro plugin, and a Pokeys plugin as well.

Thanks,
Dave

676
General Mach Discussion / Re: limit swithes
« on: July 09, 2011, 08:51:08 AM »
Mikee,

When having so many issues, possibly you should look into keeping one PC for your machine, and another for all internet and design work. Wireless accessories can cause many noise problems whether it be for internet or keyboards and mice.

As for the Machine PC, not sure what OS you're running, but you may want to look into optimizing the PC to run more smoothly. Have a look here:

http://www.machsupport.com/downloads/XP_Optimization.txt

Dave

677
General Mach Discussion / Re: Download's dead at machsupport
« on: July 08, 2011, 06:35:28 PM »
Working perfectly for me here as well.

Hope that helps-
Dave

678
Hi Fred,

Just a note, I didn't have a problem with your macro either, it worked just fine on the later version of Mach. It just isn't working on my earlier (prefferred version V3.039).

Thanks for the info though.
Dave

679
Hi Ian,

No DRO info on the status bar with that macro. As for using the version that I've stuck with, even though everyone has told me in the past (including Brian and Art), "if the version you're using is working properly, then continue to use it", I still tried to upgrade at one point (because I heard it was more stable), and it wreaked havoc on my macros that I used since I set up Mach 3. I vowed not to do that again, lol!!

I'm half afraid to change anything as I'm just not as educated in this field as most of you and the last thing I want to do is have my machine down.

I'm sure I've already taken up a lot of your time, but can you briefly explain what changes in a Mach revision/version that makes one version suitable for some macros and not suitable for others? Of, course, now thinking about that stupid question, I guess if you knew the answer, you'd be able to map out a macro that would work correctly with version 3.039, right? lol!  :P  Sorry for sounding dumb...... I guess it's all in the coding of the program, yes?

Thanks again,
Dave

680
Steve,

Hadn't visited this thread for awhile and all I can say is..... WOW, just wow, beautiful work-  :o

Thanks for sharing,
Dave