Hello Guest it is April 19, 2024, 09:09:20 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 - simpson36

341
Mach3 under Vista / Re: Use of Embeeded Widows OS - Good, Bad, or Ugly?
« on: January 24, 2014, 06:38:41 AM »
If I was a commercial supplier of CNC machine tools which go into a workshop environment and are used every day to make stuff, so they have to be reliable and safe, I wouldn't want anyone fiddling with any part of the tool, including its control system.  Not only will it make it more reliable it will save me support effort and warranty problems.  If I have to use some third-party software that needs another third-party's OS to run, I'd like to lock down both of those so I know precisely what the controller software config is.  This view is based on a career spent in the electronics industry associated with a number of complex software-controlled products and systems.  Maybe these are the type of considerations that Tormach have in mind?

I can't speak for Tormach except to parrot what they have published on their web site ('white papers' etc) and the actual correspondence that I have from them that is addressed to me and in response to my specific queries.

Tormach published that they have 'locked down' the version of MACH3 that they supply for the reasons you stated. This can be a long debate in itself, but whether or not anyone agrees with it, this is their stated policy and the reason for that policy, so it speaks to your question as to what they may have had in mind. 

However, the reasons they give for using the embedded OS is so that the system timing will not be altered by unnecessary Windows services running in the background. I do not recall seeing any reference to keeping users fingers out of the cookie jar as a validation for using the embedded OS. They cited only technical reasons and then only in a somewhat narrow scope.

My only question (although it is getting harder and harder to drill down to it) is whether these technical reasons are still valid.

I remember paying some hundreds of dollars to have 32K of ram added (soldered to the MB) on my first computer; an Apple II. I can remember having two versions of Programs written in Basic. One with comments and one with all comments, blank lines and spaces removed. The purpose was to save precious ( and stupidly expensive by todays standards) memory and disc space. Years later, out of habit, some programmers were still spending time 'compacting' their code even though the compiler was already doing that for them. Some would say you can look at code and tell if it is from an old timer (like myself) or a younger programmer. The difference being the younger programmers 'grew up' with no such size restrictions . .  plus they can all touch type . . . so the commenting is very verbose and clear, while that from the Jurassic period is brief almost to the point of being some kind of secret code that only the original programmer can fully understand. 

After WWII there were Japanese soldiers who hid in the jungle for many years because they did not get the word that the war had ended. Obviously their behavior was based on outdated or missing information.

Given these real world (albeit extreme) examples, and the fact that Tormachs published information is 5 years old, and that 'computer years' are like 'dog year' only with a much higher ratio, I think it is reasonable to question whether there is still a valid reason to use a stripped down Embedded Windows XP as the Operating system for a piece of software that is specifically targeted at being a 'one-size-fits-all' generic CNC control. The intent here not to pick on Tormach, but to determine if their path is one to follow or one that is overgrown from lack of maintenance, interest, or simply frozen in time by their KISS principal.  Tormach is going to do what they do. I do not have anything Tormach, but I have many customers who do, so I need to do my homework on this thing and come to some conclusions. 

Mach is a Windows program (PP driver excepted). It is sort of like an aircraft carrier in that is does it job surrounded by an array of support ships. In the real world, it requires an array of drivers and in many (if not most by now) cases it used auxiliary hardware for additional ports or for motion control devices and other processes. To say that a single PC with an stripped down OS running plain vanilla MACH3 thru a single PP is typical (I think) is not accurate. While that pretty much describes a Tormach machine, if it were typical of most machines in the real world, I doubt there would be any need for this forum.

In any case, I am convinced at this point from information I was able to gather from other sources, that the justification for Embedded Windows as an OS has gone the way of terse program commenting and Patriots hiding in the jungle . .  i.e. seemed like a good idea at the time, but not really needed any more. 

342
Mach3 under Vista / Re: Use of Embeeded Widows OS - Good, Bad, or Ugly?
« on: January 24, 2014, 05:24:34 AM »
Simpson36

Given your general attitude I really don't have the will to try to get you to understand what I think is a very simple concept.

You're obviously immovable from your (mistaken) belief that ANY hardware base that runs ANY version of Windows constitutes a 'general purpose Personal Computer'. So I'll leave you to it.

As my dear old Granny used to say "You can't teach a pig to sing. It just frustrates you and annoys the pig".


Ian,

I think you need to retake the course 'British debating style 101'.

You can skip the chapters on:

1) exaggeration in the extreme

2) not providing even the slightest bit of support for any of your contentions.

3) presenting your opinion as facts, then going on to using those synthesized facts as support for arguments.

4) reacting to disagreement on facts as if your opponent has insulted your sister.


The part you need a refresher on is what names to call your opponent when you have exhausted your creativity in implementing steps 1 thru 4 above.

5) when loosing a debate, calling your opponent a wanker. 

You see, Ian, you called me a pig. This is incorrect. As you leave the arena in mock frustration, you are supposed to call me a Wanker

Nobody enjoys a good debate more than I, but if you aren't going to follow your own team rules, I'm afraid I won't be able to participate.   ;)

343
Mach3 under Vista / Re: Use of Embeeded Widows OS - Good, Bad, or Ugly?
« on: January 24, 2014, 05:10:42 AM »
I don't think the Tormach PC was ever intended to be a general purpose PC. It's purpose is to be a machine control PC, and nothing else.

The definition of 'general Purpose' seems to be a stumbling block. Lilkely if you ask 6 people you could get 6 answers.

So long as Tormach is still on the table, I can say for certain (because I have correspondence from Tormach management that says as much) that Tormach does not want their customers using anything non-Tormach and that they do not condone or support their users modifying the systems. In fact they go out of their way to prevent it. So for those users who are willing to be confined to that playpen, it may be accurate in a sense to refer to their 'CNC controller' as 'special purpose', but that would be because Tormach has made it so, not because the PC itself has that restriction. My opinion only, of course.

I would venture to say that the vast majority of MACH users run more programs on their CNC PC than bare bones MACH3. In my experience, MACH users have a multitude of add-in programs, plug-ins, estimators, calculators, editors, emulators (i.e.ost USB devices) . Further, while a user might not 'Surf the NET' using their 'CNC controller', there are a growing number of TCP interfaced products (smoothstepper, for example) that require the same network services as the browser.

The only reason (other than cost saving) to use an Embedded OS is to trim it down by leaving out modules and services that are not needed for a particular application. Building a special purpose OS is made simple by Microsoft by slicing up the Windows OS and putting in in an ala cart cafeteria line. You push your tray down the line taking the stuff you want, but only you know what's on the tray at the end. If someone comes along to use your OS and they need a peach cobbler routine but you only took the apple pie off the dessert shelf, then they are not going to be able to run on your system.

I have two 'CNC controllers'. One for my InTurn™ 4th axis and one for my ATC. Neither has a conventional OS,  embedded or otherwise. You cannot run a windows program on either of them, for example. They have their own code and they carry out their own tasks, period. They are indeed 'special purpose', but nobody is going to want to run a speed and feed calculator on them, so the inability to run a windows program is moot.

On the other hand, Embedded Windows is going to lack something that the full OS has (otherwise, except for cost, there would be no reason to use it). The reason I think it is safe to say it is the wrong choice for a CNC PC for running MACH3 is that unless you have some documentation describing what has been left out, it is a crap shoot every time you want to add something to MACH or utilize an ancillary program that would be beneficial to run on the CNC host machine, even if it is only a driver for an ad-in PCI parallel port, which incidentally is an actual example of a program that will not run on the Embedded OS. The program is calling services that do not exist and if the programmer included a trap for that, the program would exit gracefully with an error message. But why would a programmer do that? It is as likely that the application (or driver) would crash the OS thru a deadly embrace, crash a running app (MACH3 for example) or simply destabilize the system. rams. With an Embedded OS, there would be no way for a user to diagnose this situation (that I know of). Again, just my opinion. 

As I said earlier, at one time there seemed to be some valid reasons to create a PC with restrictions in order to remove some of the Windows 'background noise' that caused timing problems or other issue with MACH. As I learn more about this topic, I become more convinced that the published reasons (now 5 years old) for using an Embedded OS are no longer valid. Tormach is the example, only because they are the only major supplier that I know of that provided Embedded Windows (and a very old version at that) and also published their reasons for doing so.

The problem with using Tormach as a barometer is their all encompassing KISS principal. That might be the only driving force behind their continued use of Embedded Windows, so the fact that they still use Embedded Windows does not necessarily mean they have any technical basis or advantage for doing so.  It could simply be their extreme aversion to change. That's why I was seeking other opinions and advice that might be more current and not be laced with any particular vendor's ulterior motive.

The above detail may clarify my position, or it may simply further agitate the locals,  however, on reflection this forum was probably a bad choice on my part as a place to get such information. The mention of Tormach here, in almost any context, brings angry peasants bearing torches at the castle gate. Once that happens, there is no getting in or out until you give them the monster they seek. 
 

 

344
Mach3 under Vista / Re: Use of Embeeded Widows OS - Good, Bad, or Ugly?
« on: January 23, 2014, 01:19:15 PM »
Ian,

Near the bottom of your elaborate and carefully crafted anti-snipe snipe, you state this:

" . . . I have to confess though I've never used Windows Embedded  . . . . "

Therefor everything you said up to that point, or after that point, . .  is irrelevant to the topic.

Regardless of your semantics arguments, the fact is that MACH3 is a windows program and runs on 'General Purpose' Windows PC.

Yet, you made the comment:

"Of course no one would use an embedded OS for a "general purpose" system - but I'll say it again - it appears to be only you that thinks it's been stated somewhere that you might."

So it would seem you have forgotten about your 'friend' Tormach, that uses an Embedded OS in their "CNC controller" which is a general purpose PC, like or not.

I don't know what it is about that word Tormach. You say it once and you can't escape it after that.   :(

345
Mach3 under Vista / Re: Use of Embeeded Widows OS - Good, Bad, or Ugly?
« on: January 22, 2014, 06:03:44 AM »
Ian,

I am aware of the whole Tormach KISS principal, but how Tormach views the technical capabilities of their customer base is not the discussion I was looking for. Tormach has fans and foes and you are apparently the former, but debating Tormach policy is not the discussion I was looking for. I should never have mentioned Tormach, that much is clear.

My question was about the merits of using an embedded OS for CNC control. There have been quite a few reads of this thread and thus far no useful comments on the topic, so I will conclude that there are no members here familiar with Embedded OS. That is not a startling conclusion since I doubt anyone would voluntarily use an embedded OS for a general purpose CNC controller. I have been learning about embedded OS from some very savvy customers as well as doing some research on it.

While I can understand how its use would support a KISS policy, and the cost is less than half od a full OS, but  at this point I can safely say that it is not the right choice, in my opinion.




346
General Mach Discussion / Re: How fast?
« on: January 22, 2014, 05:29:15 AM »
Excellent, thanks.

Fast is no problem. Last year I built a first prototype mill using the frame castings from a new IH bench mill (largest available bench mill) to showcase and do testing on my new BT30 spindle and ATC. Here is a video of the 150lb table running at 500 IPS:

https://www.youtube.com/watch?v=_sH8nBUxIV8

The above mill was built for a customer, but I am about to start work on the new prototype mill for my own use. It will not use any 'recycled' mill parts except a 300lb Bridgeport table. The rest is all new including the frame castings. Bigger motors, bigger screws and ball slides on all axis. It will run all day at 500 IPS.

The new machine already can accommodate three different spindles, but maybe I can squeeze in an extruder head somewhere.

Very exciting stuff. Thanks very much for the info!

347
General Mach Discussion / Re: How fast?
« on: January 21, 2014, 12:31:05 PM »
The only reason I might have for moving fast is that I am mounting an extruder head on the machine for 3D printing.

Wow! Can you elaborate on this. I did not that one could buy an extruder head to mount on a CNC mill. Info please? Links?

349
General Mach Discussion / Re: How to mirror x and y with only 1 button?
« on: January 21, 2014, 12:03:27 PM »
This may not be significant to a router, but a problem with running mirrored (via negative scale) programs on a mill is that although the cords are mirrored, the path direction is not, so what was conventional will become climb milling and vice-versa.

Something to consider.

350
I have a servo spindle (using step+dir for Granite devices VSD-E) which I have configured both as spindle and as A-axis, so they have both the same LPT port pins in Mach config. .

It works.

It has been a while since I have used a parallel port, but it seems you are saying that both the Spindle and the A axis are sharing the same physical pins. If that's correct, I can't imagine the thing is working at all unless by sheer coincidence.