Hello Guest it is September 23, 2023, 08:03:13 PM

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 - mrprecise44

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 »
Classic Shell website says:

What are the system requirements of Classic Shell?
 Classic Shell supports Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2. There is only one installer for all and it covers both 32-bit and 64-bit operating systems. Not all features are supported for all versions of Windows.

Does Classic Shell support Windows 10?
 Starting with version 4.2.1, Classic Shell supports Windows 10 TP build 10041 and later. Of course, since Windows 10 is not officially released, glitches are possible.

Does Classic Shell support Windows RT?
 No, Classic Shell does not work on Windows RT (either 8 or 8.1). There are two reasons for that. First, Windows RT runs on devices with a different CPU, which is incompatible with regular Windows applications. And second, Windows RT does not allow non-Microsoft software to run on its desktop.

Is Classic Shell Free?
 Yes, Classic Shell is free for both personal and commercial use*.


I went to the website of "Classic Shell", and under the topic FAQ's, they specifically state that it will not run on Windows 8.1 RT.

Also, I emailed the author of "startisback", and asked the same question regarding his program running on Win 8.1 RT. I just received the reply; Will NOT run on Win RT.

Win RT apparently is a totally separate kind of application from Win 8.0, and Win 8.1 Why MicroSoft would make such a program is anybody's guess. Windows 8.1 RT is the program on the MicroSoft "Surface" family of tablet computers. Mine is a Surface-2, and is certainly a nice tablet with a superb touch screen, and full size USB 3.0 port, memory chip port, sound port, HDMI port.

If I knew this incompatibility issue, I would not have purchased it. The MS "Start" package that you must work thru seems to be designed for social networks, and sending/receiving pics and music. They call the different applications "Charms" and in the several hours I have tried to use make sense of it, has been a totally "maddening" experience.
It almost seems to be more of a "psychological experiment", than a usable computer.


I have a Foxconn mini on the back of a 17" Acer monitor, and it works great. 2-USB 3.0 ports, and 4-USB 2.0 ports, Ethernet port, WiFi
etc. I installed a 120 Gb SSD. It has run an ESS plasma machine, and is now running a little desktop router/engraver.

Has anyone considered using one of these 12" Tablets running Win 8 Pro. With a Bluetooth keyboard, it could be a complete system taking up very little space. It is a touch screen, and pretty powerful.


There is a vid on Youtube of a tablet running UCCNC router; Mach3 would be no different. Just be sure to not get Win 8 Rt. The Rt version of windows will not even run the very popular Classic Shell for Win 8.


I am not sure that several months without an answer to a valid question is shooting from the hip. At $200 + a pop it's quite a bit more than a visit to Starbucks. Just my sentiments.
I did install an ESS on a big plasma machine about three months ago for a person who engaged my services to finish a job that was abandoned by the prior "CNC Specialist." I got it working, but the critical issues getting the THC controller and the ESS to work correctly were answered by the maker of the THC, Randy Ray in Texas, not the ESS forum. I also posted a question on the Warp 9 forum, and never received a reply.
When the ESS first connects properly, after you get the TCP working, it asks if you want to use the default settings.  I just click on yes, and it makes the connection. The pages of the ESS setup are pretty extensive, but I never messed with anything, except after I was assisted by Randy, that there is a Plasma check box in the setup that must be set. It seems to have a lot of check boxes for "future use" with no documentation that I have ever found.  I also find that rather odd, for a business with as much exposure as the Mach3 forum provides. I also learned all the negatives after the purchase, and had begun installation.

I decided to use the ESS after so many praises on the Mach3 forum, and the comments that is is more "noise" tolerant than the USB version.   Although I did not purchase the ESS, the person who owned the Plasma machine did, I am responsible for making the machine work if there are future problems. I am not pleased with the current state of affairs regarding support, but that is the way it is.

My next two CNC builds are NOT not including the ESS. I have decided to use the UC300-5LPT which is a USB connection to the computer, and it has 5 I/O ports plus an Analog I/O port. I am using the CNC4PC C-10 boards for I/O (simple, reliable, well proven), and will be using the Analog port for spindle motor control. It also has an extensive I/O set-up for buttons, relays, switches etc., and is very well documented. All programming of I/O is thru drop-down menus, that you scroll thru until you find the OEM you want. That is really slick.
CNC4PC is the US distributor. Last but not least, they answer all questions promptly, and they are not even located in the U.S. I have been very impressed with their approach to business. A question asked on their commercial website posts back an immediate response that they received your message, and will get back to you the next business day. They also publish their future enhancements that will be available in the near future.

One of the principal engineers of the company is also available on CNCZone.

In conclusion, the UC100, and 300 have totally automated setup for installing drivers and firmware, so there is no messing around with getting into Windows system. They have an option that you can have the computer log on to their website, to automatically check for the latest firmware, and install it automatically. I have one machine now running with the system for about 3 weeks, and it works flawlessly.


I don't know if it makes a difference, but you have soft max = 100.00, and soft min= 100.00;
Max and Min cannot be the same value.

There are 3 areas in setting up an axis that must not conflict.

1. Config/Ports & Pins/Motor Outputs
2. Config/Ports & Pins/Input Signals
3. Config, drop down menu Homing/Limits

You must have settings wrong in your config. That is the same behavior you described regarding using the "Probe" for your floating head. When a home switch is setup, whether it is x,y, or z, it will stop when the switch trips, and reverse until the switch opens. When the switch opens, Mach3 then sets that axis to zero. After that happens, Mach3 does not move, unless you have programmed the macro to make additional moves.


In plasma, you don't set the Z switch as a probe. You should only have one switch that trips as the floating head moves up, after the torch comes in contact with the work.
Set the switch input as the Z Home.
When the Z Home switch trips, the action causes the Z axis to reverse direction, and move UP until the Z Home switch opens.
At this point, the Z axis is set to Z0.
The distance from the initial point of contact when the torch touched the work surface, and the distance the Z axis moved  to set the "Z" Zero is the "OFFSET".

You can determine what this offset dimension is manually.
Go to the Mach3 diagnostic page and jog the Z until the torch tip is close to the work surface. Set the jog steps to .001, and begin jogging down until the Z home indicator LED turns on.
Set the Z axis to 0.000
Now begin jogging UP until the torch head is just barely clear of the work surface. You can determine this using a piece of paper.
Write down the distance the Z axis moved.
This is the "Offset" distance for your floating head. This offset is entered into the Plasma cutting program, so the machine "knows" how far to move vertically, to set your programmed cutting height, and the pierce height.


General Mach Discussion / Re: Displaying Loop Number
« on: April 20, 2015, 04:27:07 PM »
I also wanted to see how many loops remained in a running program. However, I used OEM 222. Here is my setup.

1. Make a tiny DRO, about half the size of the G-code button  that is next to the Reset button, on the standard 1024 screen. I used MachScreen. There is some space just level with the top of the Reset button, to the right.
2. Click on the DRO after you have it to the right size and place, and a window will open up on the right for setting the parameters.
3. Click on the "Format" line, and the OEM functions open up.
4. Scroll down until you get to "Sub program depth".
5. Double click, and all the info is entered into the window.
6. Edit the format line, dbl click and a new window opens up for formatting the number output. I used; 2 leading digits, 0 trailing digits, Type (radio buttons) double.
The format should now show %2.Of
7. Save file and exit MachScreen.
Run a test program with L10, and the numbers in the new DRO will start at 10, and count down with each pass through the loop.


General Mach Discussion / Re: Seperate tool path files
« on: April 03, 2015, 11:35:23 PM »
Hi nzlowie:

Why don't you use home switches.  If you used optical sensors for the X,Y,Z home position, and saved your G54 work offset, after a power down/restart, you can get back to your saved G54 home position within tenths. Even good quality mechanical micro switches will repeat pretty close, .001/.0015) for most general machine work.


Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 »