Re: Whither goest DOS?
Posted by
ballendo
on 2002-01-25 05:55:18 UTC
Chris,
I'm both for, and against "hardware assistance", as my recent posts
attest. My answers are numbered to your snipped post, reposted below
1)Hardware assist is an mostly an issue when it is a "closed" system.
I must then rely on the factory to provide me answers. And I will not
really klnow if the answers I am given are "for real", or just cover-
ups to deal with product insufficiencies... Of course there is also
the reality that hardware is always going to cost "something", and as
Ron G mentions in a later post (I skipped ahead to get Bills
message), it is a GOOD solution for HIGH VOLUME products, where the
development can be spread out over many units. How many cnc
controller apps do you think are HIGH volume?
But it also tends to create a "lock" on what can be done, development
wise. Look at flashcut, and you can see this. That is why you keep
telling us that when "they get there new 32 bit version out..." Will
this require you to buy a new hardware box?
A software only solution (like master5 and emc, when used for
steppers) can be COMPLETELY rewritten with no "cost" to the already
established customers. They just load the new code, and get the
benefits. No updated control box to buy. Also no hardware to design,
build, test, stock, repair, provide warranty for, etc. I've said it
before, there's a REASON Bill G is the worlds' richest man.
(In fairness, a WELL designed hardware box approaches this re-
configurability nowadays, as it can also be updated as long as its
underlying "architecture" is sufficient for the needed/desired
changes)
The "dumber" the box is, the better is the "hardware solution" ,IMO.
This is why I like Mariss's idea (at least as I presently understand
it).
As long as I'm software-only based, I can run as long as the s/w
platform is available. And I'll bet that 20 years from now an old pc
will be easier to find than an old (replacement) flashcut box! (for
when mine wears out/breaks) And flashcut may not even be around, or
may not feel like supporting that "old" control box. Anyone in cnc
has seen this in machines from bridgeport to Camtech. Before anybody
says the software may not be supported either, keep in mind that a
hardware failure prevents me from working. Lack of software support
in the future, after I have been using it for awhile (let's keep the
apples with apples, and oranges with oranges) only means I can't do
NEW things...
2) Well, I can. Master5 runs very smoothly for me, and OpenCNC
(whichis expensive, but still based on windows and s/w only) is just
like dedicated controls in its operation. The ABILITY is there; only
the price will need to come down, which WILL happen as others
continue to discover how to do it with windows in s/w only.
3) This is not a hardware vs. software issue. Both will require
systems "suitable" to their needs, both now and in the future. Linux
and other os's burp on graphics cards. Hardware burps on signal
levels, duration, and protocols. It's true, master5 on a computer it
likes, sings (literally. You can hear the smoothness of the motion in
the motors)
Hope this helps.
Ballendo
I'm both for, and against "hardware assistance", as my recent posts
attest. My answers are numbered to your snipped post, reposted below
1)Hardware assist is an mostly an issue when it is a "closed" system.
I must then rely on the factory to provide me answers. And I will not
really klnow if the answers I am given are "for real", or just cover-
ups to deal with product insufficiencies... Of course there is also
the reality that hardware is always going to cost "something", and as
Ron G mentions in a later post (I skipped ahead to get Bills
message), it is a GOOD solution for HIGH VOLUME products, where the
development can be spread out over many units. How many cnc
controller apps do you think are HIGH volume?
But it also tends to create a "lock" on what can be done, development
wise. Look at flashcut, and you can see this. That is why you keep
telling us that when "they get there new 32 bit version out..." Will
this require you to buy a new hardware box?
A software only solution (like master5 and emc, when used for
steppers) can be COMPLETELY rewritten with no "cost" to the already
established customers. They just load the new code, and get the
benefits. No updated control box to buy. Also no hardware to design,
build, test, stock, repair, provide warranty for, etc. I've said it
before, there's a REASON Bill G is the worlds' richest man.
(In fairness, a WELL designed hardware box approaches this re-
configurability nowadays, as it can also be updated as long as its
underlying "architecture" is sufficient for the needed/desired
changes)
The "dumber" the box is, the better is the "hardware solution" ,IMO.
This is why I like Mariss's idea (at least as I presently understand
it).
As long as I'm software-only based, I can run as long as the s/w
platform is available. And I'll bet that 20 years from now an old pc
will be easier to find than an old (replacement) flashcut box! (for
when mine wears out/breaks) And flashcut may not even be around, or
may not feel like supporting that "old" control box. Anyone in cnc
has seen this in machines from bridgeport to Camtech. Before anybody
says the software may not be supported either, keep in mind that a
hardware failure prevents me from working. Lack of software support
in the future, after I have been using it for awhile (let's keep the
apples with apples, and oranges with oranges) only means I can't do
NEW things...
2) Well, I can. Master5 runs very smoothly for me, and OpenCNC
(whichis expensive, but still based on windows and s/w only) is just
like dedicated controls in its operation. The ABILITY is there; only
the price will need to come down, which WILL happen as others
continue to discover how to do it with windows in s/w only.
3) This is not a hardware vs. software issue. Both will require
systems "suitable" to their needs, both now and in the future. Linux
and other os's burp on graphics cards. Hardware burps on signal
levels, duration, and protocols. It's true, master5 on a computer it
likes, sings (literally. You can hear the smoothness of the motion in
the motors)
Hope this helps.
Ballendo
--- In CAD_CAM_EDM_DRO@y..., CL <datac@l...> wrote:
<snip>
1)>Why is hardware assistance that big of an issue. WinDeskNC has
>clearly shown that it does not make the cost of a control out of
>reach.......
<snip>
2)>I am not sure I can say that the current Windows COntrols could
>run near as smoothly as Indexer.
3)> The only thing we hear for real problems is the occasional
> hiccup with hardware compatibility. I can only Imagine what kind of
>challenge it would be to assure operation of such a concept on ALL
>hardware available. From what I know, Hardware issues may be exactly
>why a "Black Box" proves to be a safer business venture. I have
>heard that when you have a computer it likes, it works very well.
>
Discussion Thread
ballendo
2002-01-23 04:42:43 UTC
Whither goest DOS?
Tony Jeffree
2002-01-23 06:31:07 UTC
Re: [CAD_CAM_EDM_DRO] Whither goest DOS?
Marcus & Eva
2002-01-23 08:21:41 UTC
Re: [CAD_CAM_EDM_DRO] Whither goest DOS?
studleylee
2002-01-23 08:27:58 UTC
Re: Whither goest DOS?
Randy Gordon-Gilmore
2002-01-23 08:45:28 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
David Goodfellow
2002-01-23 08:48:19 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Carol & Jerry Jankura
2002-01-23 09:19:20 UTC
Whither goest DOS?
pfrederick1
2002-01-23 09:50:41 UTC
Re: Whither goest DOS?
Fitch R. Williams
2002-01-23 10:22:41 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
CL
2002-01-23 10:38:32 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
CL
2002-01-23 10:47:29 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
dlantz@a...
2002-01-23 10:51:14 UTC
RE: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Jon Elson
2002-01-23 10:58:07 UTC
Re: [CAD_CAM_EDM_DRO] Whither goest DOS?
Carol & Jerry Jankura
2002-01-23 11:02:45 UTC
RE: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Jon Elson
2002-01-23 11:14:20 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Drew Rogge
2002-01-23 11:17:00 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Kevin P. Martin
2002-01-23 11:21:51 UTC
RE: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
ccstratton
2002-01-23 11:50:52 UTC
Re: Whither goest DOS?
Tim
2002-01-23 14:19:22 UTC
RE: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
ccs@m...
2002-01-23 14:31:16 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Hugh Currin
2002-01-23 14:37:02 UTC
Re: Whither goest DOS?
Smoke
2002-01-23 15:28:08 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Ray
2002-01-23 15:38:38 UTC
Re: Re: Re: Whither goest DOS?
Randy Gordon-Gilmore
2002-01-23 15:41:07 UTC
DOS is dead; long live DOS :-)
Chris L
2002-01-23 15:42:06 UTC
Re: [CAD_CAM_EDM_DRO] Re: Re: Re: Whither goest DOS?
Russell Shaw
2002-01-23 16:03:25 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
wanliker@a...
2002-01-23 17:21:13 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Bill Vance
2002-01-23 17:59:53 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
pfrederick1
2002-01-23 18:10:01 UTC
Re: Whither goest DOS?
Russell Shaw
2002-01-23 18:30:49 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Mr. sausage
2002-01-23 20:16:28 UTC
RE: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
waynegramlich
2002-01-23 20:53:03 UTC
Open source CNC buffer [Was: Whither goest DOS?]
ballendo
2002-01-23 20:56:09 UTC
Re: Whither goest DOS?
Chris L
2002-01-23 21:22:04 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
ballendo
2002-01-23 21:35:17 UTC
Re: Whither goest DOS?
Bill Vance
2002-01-23 21:40:43 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Carol & Jerry Jankura
2002-01-23 21:48:13 UTC
RE: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
ccs@m...
2002-01-23 22:00:11 UTC
Re: USB or Ethernet machine control
Jon Elson
2002-01-23 22:11:30 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
ballendo
2002-01-23 22:36:41 UTC
Re: Whither goest DOS?
ballendo
2002-01-23 23:02:09 UTC
Re: Re: Whither goest DOS?
ballendo
2002-01-23 23:06:15 UTC
microcontrollers for cnc was Re: Whither goest DOS?
ballendo
2002-01-23 23:18:21 UTC
Re: Whither goest DOS?
ballendo
2002-01-24 00:50:52 UTC
Re: USB or Ethernet machine control
Ian Wright
2002-01-24 02:18:35 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
pfrederick1
2002-01-24 05:02:06 UTC
Re: Whither goest DOS?
dlantz@a...
2002-01-24 05:22:28 UTC
RE: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
pfrederick1
2002-01-24 05:25:09 UTC
Re: Whither goest DOS?
Carol & Jerry Jankura
2002-01-24 05:54:58 UTC
RE: [CAD_CAM_EDM_DRO] Re: USB or Ethernet machine control
pfrederick1
2002-01-24 08:11:09 UTC
Re: Whither goest DOS?
JanRwl@A...
2002-01-24 10:22:41 UTC
Re: [CAD_CAM_EDM_DRO] Re: USB or Ethernet machine control
Jon Elson
2002-01-24 10:54:27 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
CL
2002-01-24 11:02:25 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
ccs@m...
2002-01-24 11:10:34 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
CL
2002-01-24 12:11:09 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
ccs@m...
2002-01-24 12:24:01 UTC
Re: glitchy step signals
wanliker@a...
2002-01-24 12:44:21 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Luc Vercruysse
2002-01-24 13:57:00 UTC
Re: [CAD_CAM_EDM_DRO] Open source CNC buffer [Was: Whither goest DOS?]
Russell Shaw
2002-01-24 14:48:07 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Carol & Jerry Jankura
2002-01-24 19:05:21 UTC
RE: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
ballendo
2002-01-25 00:38:01 UTC
Re: Whither goest DOS?
ballendo
2002-01-25 00:47:16 UTC
Subject headings vs. OT was Re: Whither goest DOS?
ballendo
2002-01-25 02:07:05 UTC
Linux cnc OTHER than EMC was Re: Whither goest DOS?
Ian Wright
2002-01-25 02:41:16 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
ballendo
2002-01-25 05:55:18 UTC
Re: Whither goest DOS?
Dennis Dunn
2002-01-25 06:31:26 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Russell Shaw
2002-01-25 06:39:34 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
ballendo
2002-01-25 07:04:06 UTC
fpga's for b-box was Re: Whither goest DOS?
ballendo
2002-01-25 07:10:06 UTC
Re: Whither goest DOS?
Dennis Dunn
2002-01-25 07:37:33 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
CL
2002-01-25 11:18:26 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
ballendo
2002-01-25 12:29:51 UTC
windows controllers master5 was Re: Whither goest DOS?
ballendo
2002-01-25 12:43:33 UTC
Re: Whither goest DOS?
dkowalcz2000
2002-01-25 13:09:00 UTC
Re: USB or Ethernet machine control
ballendo
2002-01-25 13:21:02 UTC
Black boxes was Re: USB or Ethernet machine control
j.guenther
2002-01-25 13:45:47 UTC
RE: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Paul
2002-01-25 17:24:31 UTC
Re: [CAD_CAM_EDM_DRO] Black boxes
Russell Shaw
2002-01-25 17:38:28 UTC
Re: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
Jon Elson
2002-01-25 22:24:06 UTC
Re: [CAD_CAM_EDM_DRO] Black boxes was Re: USB or Ethernet machine control
Jon Elson
2002-01-25 22:42:11 UTC
Re: [CAD_CAM_EDM_DRO] Black boxes
ballendo
2002-01-27 04:50:03 UTC
"gutting" black boxes was Re: Whither goest DOS?
ballendo
2002-01-27 05:20:55 UTC
All those in favor of simple interfaces, say "I" was Re: Whither goest DOS?
ballendo
2002-01-27 06:41:41 UTC
Re: Black boxes
ballendo
2002-01-27 18:33:01 UTC
master 5 group for computer info was Re: Whither goest DOS?
Chris L
2002-01-27 18:48:57 UTC
Re: [CAD_CAM_EDM_DRO] master 5 group for computer info was Re: Whither goest DOS?
Raymond Heckert
2002-01-27 21:09:36 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black boxes
Tony Jeffree
2002-01-27 22:15:52 UTC
Re: Patent searches (was Black boxes)
Scot Rogers
2002-01-27 22:58:49 UTC
RE: [CAD_CAM_EDM_DRO] Re: Whither goest DOS?
ballendo
2002-01-28 05:09:36 UTC
Us Govt. patent site was Re: Black boxes
Tony Jeffree
2002-01-28 05:24:30 UTC
Re: [CAD_CAM_EDM_DRO] Us Govt. patent site was Re: Black boxes
ballendo
2002-01-28 05:50:11 UTC
Us Govt. patent site was Re: Black boxes
Tony Jeffree
2002-01-28 07:03:07 UTC
Re: [CAD_CAM_EDM_DRO] Us Govt. patent site was Re: Black boxes
ron ginger
2002-01-28 18:39:05 UTC
Black boxes
wanliker@a...
2002-01-28 18:48:09 UTC
Re: [CAD_CAM_EDM_DRO] Black boxes
ballendo
2002-01-29 02:19:50 UTC
Re: Black boxes
Fitch R. Williams
2002-01-29 04:40:14 UTC
Re: [CAD_CAM_EDM_DRO] Black boxes