re: PC, Dumb box and Software
Posted by
ballendo@y...
on 2000-12-10 17:05:15 UTC
John,
(snips,inserts below)
1) percieved or real ability to network easily. People don't want to
network a dos computer or rely on disks to transfer files. Since most
are using a windows based product for design...
2) Dos is on the out!, as far as MS is concerned (discussed in
previous posts)
3) Linux is still seen as the "techie" or "propeller-head" OS.
4) RAD (Rapid Application Development) programming tools like Delphi
and Visual Basic make Windows programming easy and fast(as long as
you do not try to get "too close to the computer". Means you work
WITH windows, and not AROUND it!)
5) comfort level and familiarity. Whether or not they'll admit it,
people like it! And they've become 'used' to it.
I've mentioned before, perception is often more important than
reality. If only we lived where the BEST products owned the
marketplace, instead of the 'best promoted'!
more important, IMO. We should at least have it 'scheduled' for
development and inclusion.
the RAD tools above, will be able to write their own CNC control S/W.
Thus getting exactly what each desires. Also it will be easier for us
who already program to give something desired, ASSUMING the 'smart'
part is done well...
little problem to add the facility for updating the 'smarts'. I'd
even say it would be folly not to include such provisions...
starts to happen, the chickens and eggs will both arrive shortly...
Hope this helps.
Ballendo
(snips,inserts below)
>I have been following the threads on the dumb box versus smart boxWe don't NEED windows. People WANT windows! For a few reasons.
>over the last few days with interest.
>I firmly agree with Mariss about using the PC to do the calculations
>and then rely on a cheap box to convert the signals. This open up
>questions though about the whole train as regards conforming to most
>peoples needs.
>Taking [1] first. Why do we need windows? References keep being made
>to this but taking the fact that the PC will be a machine operating
>system taking in files it can use any base system.
1) percieved or real ability to network easily. People don't want to
network a dos computer or rely on disks to transfer files. Since most
are using a windows based product for design...
2) Dos is on the out!, as far as MS is concerned (discussed in
previous posts)
3) Linux is still seen as the "techie" or "propeller-head" OS.
4) RAD (Rapid Application Development) programming tools like Delphi
and Visual Basic make Windows programming easy and fast(as long as
you do not try to get "too close to the computer". Means you work
WITH windows, and not AROUND it!)
5) comfort level and familiarity. Whether or not they'll admit it,
people like it! And they've become 'used' to it.
>The boot up time of DOS over windows is far greater and also it'sLinux stability is legendary! Boot time only matters after a crash :-)
>stability. I personally can't see any reason for using windows -
>perhaps i'm missing something ?
I've mentioned before, perception is often more important than
reality. If only we lived where the BEST products owned the
marketplace, instead of the 'best promoted'!
>Going onto [2]. From what I have seen in this list most people are<s> and a decent look ahead to prevent burning.
>using routers or millers with a few using lathes.
>Lathes can be controlled by the same software with the exception ofMicrokinetics also has threading. Look ahead will become more and
>threading. Lets not leave this out in the design stage. Out of all
>the proprietary systems mentioned only Ahha has lathe threading.
more important, IMO. We should at least have it 'scheduled' for
development and inclusion.
>This now leaves two areas of design - the software to run the PC andThis will be where the smart box can shine, IMO. Many people, using
>box. This need to be able to handle normal G code moves for mill,
>router and lathe, including threading. Have a decent look ahead and
>ideally a graphical screen.
the RAD tools above, will be able to write their own CNC control S/W.
Thus getting exactly what each desires. Also it will be easier for us
who already program to give something desired, ASSUMING the 'smart'
part is done well...
>The box then need to take these outputs and send them to the machineIf the box uses modern 'bits' in its' construction, it should be
>as S&D signals in real time. It may pay at this time to build in a
>plug in port into the box to take add on cards at a later date such
>as lathe threading
little problem to add the facility for updating the 'smarts'. I'd
even say it would be folly not to include such provisions...
>I realise that it's a chicken and egg situation but unless they areI think you'll find that if this thing gets some steam and really
>taken together then neither is any good without the other.
>John S
starts to happen, the chickens and eggs will both arrive shortly...
Hope this helps.
Ballendo
Discussion Thread
John Stevenson
2000-12-10 13:21:09 UTC
PC, Dumb box and Software
PhilC
2000-12-10 14:01:44 UTC
Re: [CAD_CAM_EDM_DRO] PC, Dumb box and Software
machines@n...
2000-12-10 15:55:40 UTC
Re: PC, Dumb box and Software
PhilC
2000-12-10 16:15:53 UTC
Re: [CAD_CAM_EDM_DRO] Re: PC, Dumb box and Software
ballendo@y...
2000-12-10 17:05:15 UTC
re: PC, Dumb box and Software
Jon Elson
2000-12-10 23:10:20 UTC
Re: [CAD_CAM_EDM_DRO] PC, Dumb box and Software
michael.hutton@k...
2000-12-27 13:02:16 UTC
Re: [CAD_CAM_EDM_DRO] PC, Dumb box and Software