Re: Black Box Goals
Posted by
mariss92705
on 2002-01-31 12:06:33 UTC
(38538) Luc,
Not only is it possible to do with an 8-bit processor, it has
actually been done before.
I designed a product that did exactly that with a 4MHz Z80 that sold
many hundreds of units. The differences were the update rate was 256
per second and had only 2 axis. Otherwise it has the same specs and
capabilities as in the "Black Box Goals". The unit is still being
sold today; it is the Centent CN0170.
The difference is it has a proprietary command language and is
overpriced in my opinion. In fact I am borrowing from my own work of
a decade ago for the all-important motion algorithms to speed up the
design cycle.
The difference today is the processor I'm going to use (Z-80 based;
what a surprise) is 6 times faster and has 16-bit harware multiply.
I'm trading some of that speed in for a 4 times higher update rate
(1,024 vs. 256 / second). The Z80 required writing muliplication
routines. The best I could do was about 900 clock cycles for a 16X16
multiply; it now takes 12 clock cycles and saves an enourmous amount
of time. This savings I'm trading in for an additional 2 to 4 axies.
The other difference today is surface mount technology. We have an
SMT production line which permits much lower prices due to automation
and minaturization. Small is cheap, big is expensive.
By using a standard language (G-Codes) and modularization (have only
the parts you need in it), makes it a viable proposition.
The "Black Box Goals" does not cut new ground, it improves on what
has already been demonstrated to work. This is not a "pie in the sky"
thing.
(38484) Bill,
That is the way I'm thinking of going with this. Open "architecture"
on both the hardware and software. Every additional axis places a
burden on what is essentialy an interrupt driven routine. It all has
all of 500 to 750 uS to execute all the axies, yet leave enough time
to have the background program to do its thing to keep the interrupt
routine "fed".
(38485) Ron,
You bet, I'm going for the first 4 G-Codes only. The currency of
exchange has to be steps; it can't know what your leadscrew pitch is,
whether the motor is a stepper or servo, what the steps per inch is.
The serial protocol is undefined yet; I only know the bandwidth will
be low.
(38495) Ray,
The only way it will get skinny is if it ia a very tiny piggy bank.
This will be cheap.
(38502) Chris,
The advantage with a connector per axis card is it is easily
identifiable as belonging to a particular axis, it is easy to switch
a motor/drive from one axis to another, unplug an axis while the
others stay connected, etc.
(38505) Ron,
Feature creep or flexibilty? I want to keep options available in the
hardware design stage. Hardware design changes are very expensive
later on when some feature that was not initially included becomes a
necessity. Once a design is comitted to, it is very hard to "open it
up" to incorporate an oversight. On the otherhand, some feature that
turns out to be uneeded simply winds up as an unpopulated area of a
printed circuit board. Better the latter than the former.
(38530) Mr. Sausage,
The package will be very small, maybe about the size of a Mitchner
novel in paperback. Black anodized aluminum enclosure of course.
(38537) Mike,
If the thing is alive, it has to service an interrupt 1,024 times a
second. This results in an I/O R/W every interrupt. This can trip a
re-triggerable one-shot that lights an LED.
Mariss
Not only is it possible to do with an 8-bit processor, it has
actually been done before.
I designed a product that did exactly that with a 4MHz Z80 that sold
many hundreds of units. The differences were the update rate was 256
per second and had only 2 axis. Otherwise it has the same specs and
capabilities as in the "Black Box Goals". The unit is still being
sold today; it is the Centent CN0170.
The difference is it has a proprietary command language and is
overpriced in my opinion. In fact I am borrowing from my own work of
a decade ago for the all-important motion algorithms to speed up the
design cycle.
The difference today is the processor I'm going to use (Z-80 based;
what a surprise) is 6 times faster and has 16-bit harware multiply.
I'm trading some of that speed in for a 4 times higher update rate
(1,024 vs. 256 / second). The Z80 required writing muliplication
routines. The best I could do was about 900 clock cycles for a 16X16
multiply; it now takes 12 clock cycles and saves an enourmous amount
of time. This savings I'm trading in for an additional 2 to 4 axies.
The other difference today is surface mount technology. We have an
SMT production line which permits much lower prices due to automation
and minaturization. Small is cheap, big is expensive.
By using a standard language (G-Codes) and modularization (have only
the parts you need in it), makes it a viable proposition.
The "Black Box Goals" does not cut new ground, it improves on what
has already been demonstrated to work. This is not a "pie in the sky"
thing.
(38484) Bill,
That is the way I'm thinking of going with this. Open "architecture"
on both the hardware and software. Every additional axis places a
burden on what is essentialy an interrupt driven routine. It all has
all of 500 to 750 uS to execute all the axies, yet leave enough time
to have the background program to do its thing to keep the interrupt
routine "fed".
(38485) Ron,
You bet, I'm going for the first 4 G-Codes only. The currency of
exchange has to be steps; it can't know what your leadscrew pitch is,
whether the motor is a stepper or servo, what the steps per inch is.
The serial protocol is undefined yet; I only know the bandwidth will
be low.
(38495) Ray,
The only way it will get skinny is if it ia a very tiny piggy bank.
This will be cheap.
(38502) Chris,
The advantage with a connector per axis card is it is easily
identifiable as belonging to a particular axis, it is easy to switch
a motor/drive from one axis to another, unplug an axis while the
others stay connected, etc.
(38505) Ron,
Feature creep or flexibilty? I want to keep options available in the
hardware design stage. Hardware design changes are very expensive
later on when some feature that was not initially included becomes a
necessity. Once a design is comitted to, it is very hard to "open it
up" to incorporate an oversight. On the otherhand, some feature that
turns out to be uneeded simply winds up as an unpopulated area of a
printed circuit board. Better the latter than the former.
(38530) Mr. Sausage,
The package will be very small, maybe about the size of a Mitchner
novel in paperback. Black anodized aluminum enclosure of course.
(38537) Mike,
If the thing is alive, it has to service an interrupt 1,024 times a
second. This results in an I/O R/W every interrupt. This can trip a
re-triggerable one-shot that lights an LED.
Mariss
Discussion Thread
mariss92705
2002-01-30 14:10:08 UTC
Black Box Goals
rainnea
2002-01-30 14:23:30 UTC
Re: Black Box Goals
methadras
2002-01-30 14:29:23 UTC
Re: Black Box Goals
vrsculptor
2002-01-30 14:38:45 UTC
Re: Black Box Goals
Drew Rogge
2002-01-30 14:40:56 UTC
Re: [CAD_CAM_EDM_DRO] Black Box Goals
andyolney
2002-01-30 15:02:52 UTC
Re: Black Box Goals
methadras
2002-01-30 15:16:17 UTC
Re: Black Box Goals
rainnea
2002-01-30 15:31:28 UTC
Re: Black Box Goals
mariss92705
2002-01-30 15:36:11 UTC
Re: Black Box Goals
Bill Vance
2002-01-30 15:54:34 UTC
Re: [CAD_CAM_EDM_DRO] Black Box Goals
ron ginger
2002-01-30 15:59:36 UTC
Re: Black Box Goals
Smoke
2002-01-30 16:01:47 UTC
Re: [CAD_CAM_EDM_DRO] Black Box Goals
methadras
2002-01-30 16:16:07 UTC
Re: Black Box Goals
rainnea
2002-01-30 16:27:56 UTC
Re: Black Box Goals
William Scalione
2002-01-30 16:45:22 UTC
Re: [CAD_CAM_EDM_DRO] Black Box Goals
Raymond Heckert
2002-01-30 17:02:04 UTC
Re: [CAD_CAM_EDM_DRO] Black Box Goals
Chris L
2002-01-30 18:32:27 UTC
Re: [CAD_CAM_EDM_DRO] Black Box Goals
Smoke
2002-01-30 20:47:30 UTC
Re: [CAD_CAM_EDM_DRO] Black Box Goals
aspaguy
2002-01-30 22:57:47 UTC
Re: Black Box Goals
Mr. sausage
2002-01-31 04:49:53 UTC
Re: [CAD_CAM_EDM_DRO] Black Box Goals
michael.hutton@k...
2002-01-31 08:36:16 UTC
Re: [CAD_CAM_EDM_DRO] Black Box Goals
Luc Vercruysse
2002-01-31 08:48:46 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
methadras
2002-01-31 09:32:04 UTC
Re: Black Box Goals
Smoke
2002-01-31 11:34:32 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
mariss92705
2002-01-31 12:06:33 UTC
Re: Black Box Goals
Drew Rogge
2002-01-31 12:16:13 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
Carlos Guillermo
2002-01-31 12:56:08 UTC
RE: [CAD_CAM_EDM_DRO] Re: Black Box Goals
mariss92705
2002-01-31 13:41:22 UTC
Re: Black Box Goals
aspaguy
2002-01-31 16:30:47 UTC
Re: Black Box Goals
Jon Elson
2002-01-31 22:28:45 UTC
Re: [CAD_CAM_EDM_DRO] Black Box Goals
michael.hutton@k...
2002-02-01 06:05:30 UTC
Re: [CAD_CAM_EDM_DRO] Black Box Goals
ballendo
2002-02-01 07:52:02 UTC
Re: Black Box Goals
ballendo
2002-02-01 08:29:46 UTC
jog handwheel for plasma or big router was Re: Black Box Goals
ballendo
2002-02-01 09:34:03 UTC
Re: Black Box Goals
Mr. sausage
2002-02-01 09:54:22 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
Mike Gann
2002-02-01 10:12:56 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
Smoke
2002-02-01 10:28:30 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
michael.hutton@k...
2002-02-01 10:35:50 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
mariss92705
2002-02-01 10:44:46 UTC
Re: Black Box Goals
Smoke
2002-02-01 10:57:18 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
ballendo
2002-02-01 11:00:44 UTC
Re: Black Box Goals
michael.hutton@k...
2002-02-01 11:07:37 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
ballendo
2002-02-01 11:10:30 UTC
jog handwheel for plasma or big router was Re: Black Box Goals
j.guenther
2002-02-01 11:12:01 UTC
RE: [CAD_CAM_EDM_DRO] Re: Black Box Goals
ballendo
2002-02-01 11:17:48 UTC
Re: Black Box Goals
CL
2002-02-01 11:27:16 UTC
Re: [CAD_CAM_EDM_DRO] jog handwheel for plasma or big router was Re: Black Box Goals
mariss92705
2002-02-01 12:26:15 UTC
Re: Black Box Goals
methadras
2002-02-01 13:18:07 UTC
Re: Black Box Goals
mariss92705
2002-02-01 13:29:06 UTC
Re: Black Box Goals
William Scalione
2002-02-01 14:17:30 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
methadras
2002-02-01 15:29:39 UTC
Re: Black Box Goals
ballendo
2002-02-01 15:51:03 UTC
Using PC power supplies was Re: Black Box Goals
methadras
2002-02-01 16:57:57 UTC
Using PC power supplies
aspaguy
2002-02-01 18:50:21 UTC
jog handwheel for plasma or big router was Re: Black Box Goals
Chris L
2002-02-01 19:01:23 UTC
Re: [CAD_CAM_EDM_DRO] jog handwheel for plasma or big router was Re: Black Box Goals
ballendo
2002-02-01 19:12:42 UTC
jog handwheel for plasma or big router was Re: Black Box Goals
Raymond Heckert
2002-02-01 20:38:06 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
Jon Elson
2002-02-01 22:08:54 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
Tony Jeffree
2002-02-02 00:15:20 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
mariss92705
2002-02-02 13:34:13 UTC
Re: Black Box Goals
Mr. sausage
2002-02-05 11:47:28 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
CL
2002-02-05 14:05:00 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
William Scalione
2002-02-05 15:22:47 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
wanliker@a...
2002-02-05 18:22:44 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
mariss92705
2002-02-05 21:40:34 UTC
Re: Black Box Goals
Jon Elson
2002-02-05 22:45:13 UTC
Re: [CAD_CAM_EDM_DRO] Re: Black Box Goals
Carol & Jerry Jankura
2002-02-06 05:35:39 UTC
RE: [CAD_CAM_EDM_DRO] Re: Black Box Goals
ballendo
2002-02-06 09:25:54 UTC
OT Re: Black Box Goals