Documentation needed. I am no author of perfectly formulated and
translatable manuals that anyone can read and understand.

I'll save this and post it in the files section under mods..
For the past week, the lil robot board kicked my butt, I got two
commands working right off the bat, simple, toggled in Chr$(numbers)
and it works. Except all the other commands. Nothing else works except
the two commands. Using "thier" small console programmer where you
enter hex addresses and it works.
For a week I have been here, 15-20 hours a day. Last night it hit me,
I don't really know what "windows" is sending. I know I have 'text"
transfer selected and not binary. But I don't know. I first got out
the high dollar laptop to connect to the serial line in series with
the desktop. Then thought, gee, I don't need to do this to see. I got
out a lil 232 lcd I bought to communicate with stamps. Hooked it up to
the output line, reduced the baud rate to match.

Windows throws garbage out the port. NO handshaking, No excuse.
Mscomm will now work talking to a micro controller. That explains a
lot of results in the past where things "almost" worked.


How things work as Planned:
Got a friend breaking the dlls down to determine the calls needed to
access the machine level calls I need to do in visual basic.
Dro will not work without a bit level communicator, not to a pic,
not to this board.

1) DRO, main program.. It has a communicator where you select the
chinese scales or "moto" board, or "other" transmit and recieve
formats. It will be driven at bit level. I can not, nor ever have
written dll's.. I have used them, other peoples.
YOu can once completed, load gcode onto this system and it will
load line by line and let you hand-machine a 3d object. Tool offsets
are a one button deal, as is calibration and loading of G90's format
where you have a program Real location, and a incremental location to
run a program at the "present" physical offset. THIS works, Later it
will be changed to include a movement for "table feed" not a cnc. BUT
a one plane interpolated drive. OR fancy ass table feed.

2) Machinists camera, scanner.. THIS will work with DRO setup above to
read in table locations. With the camera, it only allows you to
position table by crosshairs, or the adjustable circle to bores and
holes. WITH the laser trig-scanner.. It works by throwing a flat red
line of known color (you pick with mouse) and it scans the pixels on
screen for that color, since angle is known (camera and pixel
offset=angle) and the distance from camera to laser emitter is known,
simple trig can determine shape of the "line" throwed across object. I
did not invent this, it is used in all kinds of scanners. I am going
to make it cheap thou. Reading the scales,encoders, pic you can either
move the table, or set up a "sendkey" list to the working software,
plan is for it to "grab" snapshots as it travels down the table. NO
contact needed. It, the laser scanner write the HUGE point cloud data
back to the "included editor" like wordstar.
OKAY, I also, have a chinese scale hooked to a small 1/2" diameter
air cylinder. It strokes and reads the scale after a time period. Same
program, but it can read points in that do not intersect.

3) gcode graphical editor, a cad system where you can draw, select
points on a screen and it will do "gcode back to the editor. You can
draw lines on a grid, layout angles on screen, do all kinds of small
operations, include text comments into the gcode file. Slides or input
boxes can set Z-height. ON this setup, I am thinking, of incorporating
a " tracing system where you can pop a picture in from the camera, and
overlay holes or cut-lines on it. BEWARE the curvature of the lens
will not allow this to work 100 percent. A fact of geometry.

4) text editor, for gcode modifying or translation. Right now, it is
kinda a background deal for the gcode-graphical screen.

Epic: Right now, this is all a junk of dissassociated programs, they
have not been linked or included together yet. THEY are under mods
daily. I have added and cut out subroutines trying to determine
direction of program flow and associations of logic.

I need to think out how to publish the code. Since it is changing so
much, posting what I have is no good, yet I can not accept help.
Posting bit's of the program is not good for other programmers.. so
ideas on that is needed on HOW to do it.