Machsupport Forum
Mach Discussion => Mach SDK plugin questions and answers. => Finished Plugins for Download => Topic started by: poppabear on February 02, 2009, 09:34:21 PM
-
Special Features:
Mach MAD is a Real Time Monitor and Diagnostic tool, targeted
at the OEM manufacturer, Retrofitter, Service, Mach Screen Designer, or Mach Customizer. With it its 7 Non-Modal screens you can look at, Change or Press any: OEM button, OEM/User LED, OEM/User DRO, Serial Modbus Local Variable, TCP Modbus Local Variable, Read all the Smart Labels, Read/Set all the User Labels and Tickers. Choices are from drop down windows, there is a “Quick Pick” page that has listings for Buttons, DROs, LEDs and it has a “MDI” line for sending code to Mach3. The other pages are Object specific dedicated pages: Buttons, DROs, LEDs, Serial MB, TCP MB, Labels/Tickers. All 7 of the Non-Modal windows can be resized, minimized, and since they are modeless you can do things on your Mach screen while watching the results on the Mach MAD screen, and vice versa. Note: you cannot change Mach OEM Read-only DROs/LEDs.
You can also Pick a UserLED to show the Mach MAD dialog from Mach’s screen.
It is a LARGE plug in, so mach will take a few more seconds to load than normal. The User LED that you can use from Mach3 Screens is user assignable, BUT does NOT have a memory iwith it. Since the Plug in is not ment to run all the time. Just when you need to Customize, trouble shoot, or setup your machine.
The Help button opens a "Flash" help screen.
Cost is only $10.00 dollars, payable to my paypal account: PoppaBear"AT"Hughes.net (Remove the "AT" and replace with @).
You will need to send your Full Name and a valid email for me to send the install to you.
Screen Shots below.
Scott
-
remaining screens.
-
NOTE: The "Show Window" control LED Feature. To use this, you put a button on your Mach3 Screen (and a LED if you want for visual conformation, but you dont have to). On the quick picks page, Tick the Radio button that Says "Use Control LED", then in the User LED # box, put the User LED # you want to be your control LED that your button on your screen will toggle on off. THEN YOU MUST PUSH THE UPDATE BUTTON, to set the variables to the status of the radio and LED# choice.
Hit the "OK" button to close the Quick Picks page. Then on your screen push your "Show MAD" button. When your LED turns on the Quick Picks screen will appear.
BUT it is a ONE WAY thing, to close the Quick picks or other screens you will need to close them like normal. The Control LED you will need to toggle from ON to OFF and back to ON to once again re-show the Quick Picks screen, since the LED and Show is running in the Update loop of the plug in, it by necessity is a State variable.
Scott
-
Hey Scott, It looks like you have put a great deal of work into this.
Can you give us a senario where we would need this?
I know you know all about it, but for me its not obvious what it will do, or why I should have it.
Possibly a screen capture video explaining it would be benificial.
You need to look after remedial guys like myself :)
You're a good man,
Benny
-
in an nut shell it lets you monitor or change any thing in Mach on the fly. Like if your designing a Screen set, or writing a VB macro, or testing your Modbus device, you can step through your IO, or change your IO, or screen values, states, what ever, adn watch ALL the things you are trying to effect from ONE place, you can also SEND changes of data out or read it in from all the DROs, LEDs, Serial MB vars, TCP vars, Labels/Tickers, push buttons all at one central point.
verses flipping through pages to see what is lite or what the value of that dro is, or openiing the Modbus test window, OR opening a Brain View to see what is happening with your IO. You can also send out G and M codes directly from the Main Page.
Hell it is 10 bucks, buy it and play with it, you probably blow more cash than that at one stop through the McDonalds........ I know I do......hehehhe
scott
-
I'm sure its good, but I cant think why I would need to do those things, and McDonalds tastes better.
I hope you market it well and get some rewards for your work.
Benny
-
oh well, to each his own..........
good luck to you as well Benny, do you and Jay still have your screen website?
scott
-
Nah the site died a death b4 we even got it up. It was a dumb idea at the time.
EDIT : If you really want to make a buck, I'd work closely with Brian to implement a new screen designer.
Art one gave me the source for scrren 4. They might even do it again. That way you could fix it and sell i as a third party designer.
-
hey would you pass it my way the screen 4 source and I will try and debug it.........
scott
-
Id love to, but that was many installs ago and I no longer have it.
I would ask Art or Brian for it. Its not like they are giving away the source code for Mach.
I'd be surprized if they said no. Let me know how you go.
There is however one problem I see. While you may be able to fix the designer source, there may be display bugs at Machs end too.
BTW how are you getting hooks to all the displays and in outs for Mach? You could almost build a third party mach display, surely?
-
Mach4view and the standard engine and trajectory stuff........
-
Ok, 2 things real quick for you Scott.
The flash help screen, is there anyway to make that be on top of all windows like a normal help file? Kind of cumbersome to move everything around and resize just to get to it.
Also, when I disable the plug-in and go to exit Mach 3, I get this error in the screenshot below.
Thanks,
Dave
-
Hi Scott,
Disabled plugins don't get the 'cleanup' callback. For this reason I never use it any more. Use ' the 'shutdown' notification instead.
-James
-
hmmm Hey James, would you elaborate more on how your using Shutdonw notifictaion in the clean up section, or where you use it.
Budman: Flash screen help, no not really, it is ran in windows shell. It is meant to to be read for set up and use. It would be easier to add a second screen monitor.
scott
-
Hi Scott,
The SHUTDOWN notification is:
#define SHUTDOWN 0x12000e // Undocumented notification
Here is the MyNotify code from a customer plugin:
// myCleanUp is NOT called if the plugin config has
// been disabled while the plugin is loaded. This
// will cause a hard crash if the modeless dialog
// is not destroyed and the Mach3 HWND detached
// from the CWnd object
if (message == SHUTDOWN) {
// Free the form that
// was created at startup
if (NULL != FreeForm) {
(*FreeForm)();
FreeForm = NULL;
}
if (NULL != dlg) {
dlg->DestroyWindow();
mach3CWnd.Detach();
delete dlg;
}
dlg = NULL;
}
-James
-
Hey James
Let me Poke a few quesitons at you.
the "#define SHUTDOWN 0x12000e" is this going at
the top of the .cpp with the includes?
my notify is in this format:
void myNotify ( int ID)
{
if( ID == RangeStart )
{
dlg->ShowWindow(SW_SHOW);
}
} //myNotify
not: (message==.....) Can I use Int ID to see the message == shutdown
i.e. if( ID == SHUTDOWN)
if (NULL != FreeForm) {
(*FreeForm)();
FreeForm = NULL;
}
What is "FreeForm" and where does it comefrom/do etc.
do I have to have somthing about it in the header file?
scott
-
Hi, Yes ID is the same as message. Ignore FreeForm it is a customer specific function I neglected to remove. Cut and paste!
Yes, the #define goes up top with the includes.
-James
-
Getting the same error as Dave.
It happens on shut down of Mach, after disabling plugin.
Greg
-
Hey Scott,
fooled around with the plugin,
Im getting the same error when disabling the plugin, just once... no big deal though.
One thing i might suggest is that you remove the ability to tick the checkmark on LED that are not user LED
If for some reason you tick the checkmark even though the LED is turned off, it might be confusing. although it resets if you select another led and go back to the one for which you ticked.
Its no big deal though, just a thought
Great work friend.
Fernando
-
Hi Scott!
very nice, youve mail ..and money ;)
Thanks and best regards
Wolfram
-
Ok
thanks guys, James has found and offered the solution for the error message if you uncheack plug in enable and shut down.
I had gotten this also, but, it didnt really effect anything. Mach Comes back up fine.............
BUT, I will implement his fix for this and resend you all a version 1.2
Fernando: The Cheack box for the LEDs is a "Read Only" check box. it just reports the state of the led your looking at you cannot change the state of an LED by cheacking or uncheacking the LED check box. The only way it changes is for you to push the toggle button. the code in the button flips its state and the cheack box just reports its new state.
I will look and see if there is a way to disable unser Input into the check box, if there is, I will fix it to, otherwise it will have to stay.
I was looking for some quicky, "Owner Draw", code in which I could replace the cheack with a solid green, and un cheack with solid Grey, like the LEDs do in Mach.
scott
-
Hey James tryied your solution, I still get the error box after unticking and closing Mach3. The Error box is really no big deal, I just push NO on attempt recovery, and mach comes back up just fine.
I put this up with my Includes on the MachDeviceimplementation.cpp
#include "MainPage_Dlg.h" //****The header file for the Dialog for this plugin***
#include "Buttons_Dlg.h"
#include "DROs_Dlg.h"
#include "LEDs_Dlg.h"
#include "SerialModbus_Dlg.h"
#include "TCPModbus_Dlg.h"
#include "LabelTickers_Dlg.h"
#include "SSSystemsLLC_dlg.h"
#define SHUTDOWN 0x12000e // Undocumented notification
Here is what mynotify looks like:
void myNotify ( int ID)
{
if( ID == RangeStart )
{
dlg->ShowWindow(SW_SHOW);
}
if (ID == SHUTDOWN)
{
if (NULL != dlg) {
dlg->DestroyWindow();
mach3CWnd.Detach();
delete dlg;
}dlg = NULL;
if (NULL != dlg2) {
dlg2->DestroyWindow();
mach3CWnd.Detach();
delete dlg2;
}dlg2 = NULL;
if (NULL != dlg3) {
dlg3->DestroyWindow();
mach3CWnd.Detach();
delete dlg3;
}dlg3 = NULL;
if (NULL != dlg4) {
dlg4->DestroyWindow();
mach3CWnd.Detach();
delete dlg4;
}dlg4 = NULL;
if (NULL != dlg5) {
dlg5->DestroyWindow();
mach3CWnd.Detach();
delete dlg5;
}dlg5 = NULL;
if (NULL != dlg6) {
dlg6->DestroyWindow();
mach3CWnd.Detach();
delete dlg6;
}dlg6 = NULL;
if (NULL != dlg7) {
dlg7->DestroyWindow();
mach3CWnd.Detach();
delete dlg7;
}dlg7 = NULL;
if (NULL != dlg8) {
dlg8->DestroyWindow();
mach3CWnd.Detach();
delete dlg8;
}dlg8 = NULL;
}
} //myNotify
I get Error code 9991 attemp recovery after changing from enabled to disapbled and closing. Like I said it really isnt a big deal, Mach will reopen, I just tick NO on attempt recovery. I can go back and reenable the plug in, close and reopen, and it all works fine again.........
scott
-
Scott,
The resources I am freeing are apparently not the same as what you need to free. Since you are using MFC modeless dialogs the dlg->DestroyWindows is probably appropriate. BUT, if your plugin shuts down clean when the 'MyCleanup()' is called why not just put the code you have there into a function and call it from the SHUTDOWN notification?
Also, if you use the DbgMsg library I posted with my tutorial (dbg.cpp and dbg.h) you can put trace messages in to see exactly where the code is failing.
-James
-
the code is I posted I pasted over from the MyCleanup function so now it is in two places in the cleanup for normal closure and in the mynotivy for disableling and then closing...........
I use "MessageBox" in my code to see what is happening, (a trick Ed sold me on). I guess it just doesnt work for my case, and that is ok, the error doesnt realy do anything just an annoyance.
thanks for your time and suggestions though.
scott
-
and that is ok, the error doesnt realy do anything just an annoyance.
Indeed but you may want to at least add this info to your program so you don't get asked about it over and over - ;)
Dave
-
I will Add a "Read Me 1st" in the Zip file, for future installers going out, that explains this.........
Good Idea Dave.....
scott
-
Hi Scott,
Here is a good article on owner draw LED style controls.
http://www.codeproject.com/KB/buttons/LedButton.aspx
-James
Ok
thanks guys, James has found and offered the solution for the error message if you uncheack plug in enable and shut down.
I had gotten this also, but, it didnt really effect anything. Mach Comes back up fine.............
BUT, I will implement his fix for this and resend you all a version 1.2
Fernando: The Cheack box for the LEDs is a "Read Only" check box. it just reports the state of the led your looking at you cannot change the state of an LED by cheacking or uncheacking the LED check box. The only way it changes is for you to push the toggle button. the code in the button flips its state and the cheack box just reports its new state.
I will look and see if there is a way to disable unser Input into the check box, if there is, I will fix it to, otherwise it will have to stay.
I was looking for some quicky, "Owner Draw", code in which I could replace the cheack with a solid green, and un cheack with solid Grey, like the LEDs do in Mach.
scott
-
Mach MAD version 1.2 was sent out today to all, I have added a new feature!!!
the Control LED and User LED choice is now Remembered between opening/closing of Mach3 (I had several request for it, so I added it).
ALSO: The control LED will SHOW the "Quick Picks" when you turn it on, AND, it will HIDE the ANY and ALL of the pages when it is turned off (upto all 8 of them).
When you Turn the LED back on, only the Quick Picks page will SHOW again, you will have to use it to launch SHOW the other pages like usuall. Just realize that if you playing with the LED functions and you toggle the state of the USER LED that you have choosen to contol the visibility of the windows you can turn yourself off..........
I put a "MAD Diagnostics" Button and LED on my Screen sets on my Diagnostics page, comes in real handy.
Further: I have NOT really noticed any impact on the Processor use time, with constantly running MAD vs. not running it. My comp has a 1.6 gig processor, so if your running a slow(er) comp check to see if you see any real impact if not, you can probably run it all the time if you want.
Scott
-
Greetings,
I made a "Stock OEM" Mach Mill screen set that has a "Mach MAD" button and LED next to it, to control the appearance and disappearence of the MAD Windows.
I put the Button/LED at the lower Left under the "History" and "Clear" buttons. The Control LED next to it is UserLED 2220. You will need to put this number
in the Control LED box on the quick picks page, and hit the UPDATE button, also make sure the Radio button for "Use Control LED" is turned on. If you are using Version 1.3 from the installer that I sent out to everyone, then Mach will remember the state of the control LED/and User number next time you open it.
The Screen set is called: 1024MAD.set
NOTE: the button and led are on the "Park" page so they display on all screens.
it is attached,
scott
-
Version 1.4 has been sent to everyone on the list.
I added version information to the top title bar of the Quick Pics dialog window.
Also: The new installer will install the IMPROVED MAD screen set....... I upgraded from the
screen above to there is a Cool "Ring" type LED around the Mach MAD button!! (like the one around the Resetbutton).
Read the Read me file that comes in the Zip, it will tell you about other minor changes/upgrades...
scott
-
MAD 2.0 is released!!
New Featrues Added!!!:
I added 3 more pages:
* Trigger Macro Page: This can trigger upto 15 Macros from a userLED, the Macro will run
ONCE per change of state from off to on.
* Trigger User Labels page: This can trigger upto 6 Userlables from a userLED, you can put
a message for LED ON, and one for LED Off.
* Trigger Tricker page: This can trigger upto 6 Tickerlables from a userLED, you can put
a message for LED ON, and one for LED Off.
You can change these on the fly! This will allow you to Run: Macros, Labels (dual message), Tickers (dual message) from External or internal sources. Just assign a User LED to the fucntion you want. Then put the label or Ticker message in the ON box and if want a different one you have an OFF box for you use too.
For Macros you just assign a User LED to trigger it, and just put the Macro # and hit the update button for all the above.
You can bring in External or Internal events through a Brain or what ever and do your thing!!
Version 2.0 has been sent out to all on my list.
Screen Shots attached.
scott
-
Mach MAD 2.1 emailed out. Hood found a small glitch in where the Ticker labels would not start Ticking on start up, it was fixed. Thanks Hood!!
I have been having some trouble with my email service lately so you do not get 2.1 (you who have already purchased), email me at my normal Email,
(I can sometimes receive), and I will email it out to you on my Yahoo account until my service gets off thier butts and fixes the email issue.
scott
-
Mach MAD 2.2 emailed out, ADDED that you can use OEM Leds as well as UserLEDs on the three trigger pages.
scott
-
Well I figured out how to do Modeless Tabbing Windows, and so I am adding a NEW feature to Mach MAD
There will be a new Menu choice under Mach MAD called MAD DRO Message.
this will be a window with 8 Tabs in it, it is so if you have higher end Programmable Axis Drives and/or Spindle Drives (VFDs).
You can assign a User DRO that each Drive can write to one UDRO for the X, Y, Z, A, B, C and S (Spindle). Through the modbus
so that you can send the "Status and/or Error codes" from that drive to the UDRO, the plugin then matches the number in the UDRO with the Numerical Code, that you enter, and displays the Error or Status Message in a Ticker that you choose.
for instance all your Axis Drives and Spindle Drives could all talk to your PLC through a modbus between them and update a register in the PLC with the drives current status and/or error code then code would then be sent to mach3, the plugin would then display in a ticker the status of each of your drives and Spindle drive dynamically.
So you can have Advanced Diagnostic, or Status information comming in from all 7 axis displayed on upto 7 different Tickers!!
scott
-
Here is some screen shots of Message DRO in action on Mach Mad.....
It is reading Status codes from 6 Drives and 1 VFD from the serial Modbus.
There is a screen shot showing status codes being scrolled on Tickers.
Each Drive and Spindle can have upto 10 Error or status Messages per axis, spindle.
You assign a Single Cfg number for your Serial or TCP modbus, then you assign ONE local address to each drive coming in.
Then you pick ONE UDRO and ONE Ticker for each axis. Then on the Axis and Spindle pages you put in the Drive Code number, and in the edit box you put in the "String" that will scroll across the ticker you have choosen to display that axis. (remember to put spaces before you string so that you will have some time to read the ticker as it scrolls). NOTE: You can have everyting all writing to the Same ticker if you want, but if you had or more drives codes then they would both be writing to the ticker.
If you dont want to use an Axis, or the Spindle for messaging, just leave the Default 2256 in the UDRO number and the other defaults values for dont use in the other perameters. I just showed a screen shot for the Spindle message page since the axis pages are just like it, and spindle is probably the most likely to get the most use.
Screen Shots Below, The installer has been mailed out to all on my list.
scott
-
Version 3.5 has been mailed out to all on the purchase list.
I have added a VB scripter window that you can now run VB Cypress Enable/Mach Specific VB from the Plug in!!!
screen shot of the new window below.
scott
-
Ha!!!!!!!
Tom, I used your Shutdown code of "14" that you found, and it has worked for me as well. Now a user can "Uncheck" the Plugin, and then close Mach and NO errors are generated. I found out that when I was using the other Shutdown code, that it would not go into the destroy window code section in My notify.
I am running Windows Vista 64 here so it appears that for this OS at least that ID 14 is a good Mach closing ID.
Thank you for finding that ID, if you dont mind please post up how you found that ID number for the Mach closing.
I have an "Updated" Mach MAD 3.6 now......... that no longer has the closeing errors under the above conditions, I have a significant list of users, so if you want the "Updated" version send me an email and I will send it to you.
scott
-
NOTE:
I have roughly 112 users now, and of them using vs. 3.6, 2 of them reported that they still get a closing or crash error when they close. So for those 2 people I sent them the previous 3.5 version that had the original error on closing IF you uncheaked the plugin then closed Mach3. If any others of you have a crash issue please email me at "poppabear"AT"hughes.net" and I will send you a 3.5 version.
I suspect that there is a 3rd "Notification" message that those two get on their computers other than the Two that Tom and Jemell found. Brian has said that when Mach vs 4.0 is released that he will put in a Known Shutdown ID that will solve the issue, when he releases the new SDK as well.
Scott
-
MAD 3.7 was sent out to all on my list.
Latest Notes:
In 3.7 I had to change back to the style (like 3.5), that caused the problem below.
The reason being that if a user did the below:
ALSO in 3.7, I added the MyNotify() disable ability, that if the plugin is disabled,
but still in your plugins directory. It will not load its PostInit Windows.
If the Mach MAD plugin is enabled and you go and disable it
in the configure plugins dialog box, changing the green cheak to
a read X. When you close Mach, an "error" dialog or two, appear
just click NO on both of them. they are just complaing that the
plug in was not enabled when closed.........
Also, you will note a slight delay in start up of Mach once you reopen mach
after you enable the plugin, since it loads a large amount of resources.
It has NO impact on the Processor time, or update loop of mach3.
In 3.6 I had eliminated the above issue, BUT, It would NOT "Remember" its last state.
since Mach crashes if you try to call a MyCleanup()
from the MyNotify() for shutdown. it crashes mach3.
Basically, I chose to "Retain" the memory ability, but to do that, if you do
the above disabling the MAD plugin then, close mach, you get the TWO closing
error message boxs. just click no on both of them.
scott
-
Scott,
How can I use the plugin to act like a touch probe. I set one of the user Led toggle buttons to oem825 but it won't light my led up. It works with a real probe though.
Mike
-
???
UserLEDs are only in the range of 1000-2255, "825" is an OEM Led and is read only.
scott
-
HA!!! Thanks to Zafar, he has found out that the "bug" that was causing the 3.7 to crash mach3 was (at least on his computer) the ACPI, so if you turn that off and re-install the 3.7 that should fix your problem for those of you that said that 3.7 was crashing mach3 (3 reports), and you had to go back to 3.5. With the ACPI disabled Zafar has said that that fixed the problem.
If you need me to send you 3.7 again, if you want to try out turning off the ACPI let me know.
scott
-
Just an update, when Brian gets out the new functions/way of doing plugins, with Rev 4, MADs price will be going to 25.00 per copy, and I will be doing some small extra user friendly feature stuff.
This will be a redo of the plugin, plus adding some nice user features to make it a little friendlier. Both old and new users the price will be 25 bucks per copy........
scott
-
Scott -
That's still a great deal!
Will you make it so that the new version is useful for both V3 and V4 code?
I'd like to be able to use the new numbering scheme when working on V4 code and the old scheme when looking at V3 stuff.
And while I'm thinking about it, a suggestion:
It would be nice to be able to set a DRO/LED number without having to scroll sequentially thru the pull down values - I've used the 1700 range for the MachStdMillScreen set for V4 & it's getting a tad tiresome to scroll that far each time I use machmad :-0
Dave
-
"And while I'm thinking about it, a suggestion:
It would be nice to be able to set a DRO/LED number without having to scroll sequentially thru the pull down values - I've used the 1700 range for the MachStdMillScreen set for V4 & it's getting a tad tiresome to scroll that far each time I use machmad :-0"
Yes, that is one of the changes I am making........ I may just do a last update to V3 MAD, call it 3.8 that has the ability to enter directly the code.... just
been to lazy to go back in and change all that, but I will send out a 3.8 to all on my mailing list.
If you bought a copy from Peters or Aurturos website, then you will need to download the last V3 update from those sites......
The new Plug in, be adding in the Parameter ability, to the V4 as soon as Brian gets the new VB/Parameter system stabilized.......
V3/V4 compatablilty....... as far a the plugin goes v3 and v4 will NOT be compatable, the plugin code it self is being completely restructured, BUT, as far as implementing the V3/V4 VB, OEM: Dros, Leds, etc. both old and new, as long as the old Calls are supported, I will leave them in......
Dave, BTW: Thank You for the feed back, you the first guy who has ever given me any feed back on MAD.......... :)
scott
-
Scott -
Yea, customers: the source of all problems in a business ;-) - Take the lack of feedback as a good thing <grin> - you know how it is with people (myself included) - we complain about things we don't like, tend to ignore the things we do.
So here is some more feedback: MachMad is the a very handy tool. I'm working on a V4 screen set (Prototype being done on V3) and I use MachMad all the time in the process. I am always using the VB window to run a 3-4 line test of something to figure out what mach is really doing (as opposed to what a doc says it might do) - it's much easier than opening an editor & creating a button etc.
Here is a feature I'd love to have - but I suspect it may not be possible external to mach itself...
The problem: The lack of common IDE features makes debugging mach VB code a real pain - it feels like a nostalgic exercise in using early '70's programming tools. Thankfully, the Cypress VB embedded in mach provides breakpoints, but it offers no way to monitor or change variable values while debugging.
The wish: I'd love to have a way to monitor VB variables (I use MM to monitor Mach DRO, LEDS etc) - but I suspect that being able to do that requires you to be inside the interperter.
BTW- my understanding of the current plan is that while the V3/V4 plugins are different, the V3/V4 macros will be able to coexist on V4. V4 VB code will use a directive up front to tell mach the macro is (all) v4 code calls. Existing VB macros (really any macro w/o the directive) will be interpreted as V3 calls.
Dave
-
Dave,
Thanik you for the feedback :)
I have changed all the dropdowns to Editable dropdowns and have been checking them, I do believe I have them all, so now you can enter the code, directly into the drop box main line.
Here is the way that will work:
for instance to switch to page 3 of a screen, put the number 3 into a button drop down, then "Press" the activate button and it will goto screen 3, etc.
your Wish: That would be nice, but as the VB interpreter IS inside Mach3, so I dont have anyway to get to that kinda stuff, my suggestion for what that is worth,
is set your vars, = to a DRO (for numbers), and a User Label in mach for your strings.......... and watch those DROS, and/or lables in mad they change when the var does.......... sorry, that is the best I can do, withoug Brian being involved.......
I will do the best I can to make V3/V4 VB stuff work in a "make sense" manner in the new one.
3.8 will be out very shortly......
so, check your email............
scott
-
Greetings,
Mach MAD 3.8 is out (for those that have purchased from me directly, you will get an update,
Via email, for those that bought copies from Pete or Aurturo then you will need to download the
New version from their respective sites.
New for version 3.8 is a minor upgrade:
Now in the list/dropdown boxes, you can now just put your OEM code number in directly, instead
Of scrolling down the drop down list for it. The Draw back for that ability is this.
If you choose to enter an OEM number directly,
i.e.
Your using the "Button" functions, and lets say OEM code 3 is in there, and you want to make
It OEM code 1, just put a 1 in the dropdown box and hit the button and poof you go to screen 1.
BUT, if you choose to go back (on that dropdown), and use the autoscroller after using the manual number entry override, you have to pick (scroll and pick), the OEM code TWICE for it to take!!!!!! If you don't enter your numbers manually then you don't have to worry about this.
ALL dropdowns now have this feature, so if you know what numbers you want, you can enter them your self for much faster use then scrolling down the long list……….
scott
-
Hi Scott,
I installed MM 3.8.
It seems to have brought back a bug I think I remember from early versions?
With 3.8 installed, I get a MM dialog box that I have to "OK" whenever I close mach.
FYI, this didn't happen with the prior version (which I think was 3.7 but I'm not positive as I didn't check the version # before I uninstalled it to install 3.8 )
Dave
-
that is an error box, for ONE of your Serial or TCP Modbus windows, Open each one, and look at all your configs, in the modbus the "Local Var" boxes range from 0-128, so in one of those boxes, you have some other number intered, use the scroller when you find which one, and pick "0" from the scroll list twice then hit OK.......
With Hand editing, you can choose to put numbers that are outside what the box will take for what it represents, and I put ranges on the boxes, if you out of range, you will get errors like that.
scott
-
hum,
I opened both the Serial and TCP modbus pages - they all show the value as zero (expected as I don't have modbus and have never used the pages) - I then clicked the update button on each item to make sure they were set to zero... I also looked thru all the other pages for an out of range value - didn't fin any.
I still get the dialog when exiting mach...
Dave
-
Dave,
Also check the Mad Message, it is the menu item under plugin control that is under Mach MAD.....
the first page on that, also has modbus cfgs. that range 0-128 check them.
the range 0-128 is only for the Modbus local vars on both TCP and Serial, it is the only place that
range restriction exist.
If that doesnt fix it, then pehaps uninstall and reinstall MAD, (and mabey Mach3).
scott
-
Scott -
that fixed it.
The Local MB entries were all set to 1024 for some reason - I changed them to 128=NoUSe and the dialog went away.
Thanks
Dave
-
Will Mach MAD plug in (Maintenance and Diagnostics ) help with faults which require you to Reset mach, the problem is very intermittant
-
Having problems with Mach 3 with something intermittant requiring a reset, will Mach Mad indicate what caused the need to reset Mach3 i.e. if a limit switch caused the problem do you see a latched Led for instance. Does the above make sense.
regards
Denis
-
Will this plugin allow me to modify Mach3 2010 Screen set?