To add another program, go to the last line in the last currently entered program, move the cursor to just ahead of the *, enter another *, which will then move to the next line. Add a % in front of that * and proceed as usual. To scroll thru programs, you can just go into edit and hit % and <word search> repeatedly. Each time you search for % will take you to the beginning of the next program. If you want to describe the program, you can enter text in parentheses after the % and before the * in the first line like %(WOOD DUCK)* This is something I've never seen in the 3000 docs, but it works fine because the control ignores whats in the parentheses when its running. If you prefer program numbers, its easier to enter them as a letter and number combination on the line before the % line at the start of the program. Then you can search for P1234 for example, scroll forward to the first program line, leave edit mode, and you're ready to go on Program #1234. Caution though, because the program number is before the line containing the %, if you just search for P1234 and then exit edit without scrolling forward to the first program line, you'll make the previous program current instead of the one you planned to use. This can make for some real surprises
The same text in parentheses thing can be used anywhere in the program, for tool descriptions for future reference or whatever. As long as you put it in parentheses, the control acts as if its not there.
Okumas read strictly in diameter. Offsets in X are entered as diametral offsets, and the control halves them internally to make the required change in radius position.
I tried cutting a .625" cylinder with MDI and came up at .650" So I manually moved the X - thinking it was reading Dia, to .620 and cut it with S1000 M3 G1 F30 Z0.0000... then mic'd it and came up with .643"
The first cut indicates your offset was off by .025" You then moved the tool .005 on diameter, so you should have expected the next cut to be at .645" You got .643", or .002 less than expected. If the first cut was substantially heavier than the second, the .002 difference could come from deflection that occurred in the first cut, but not in the light second pass. If you took a couple more .005 cuts and got .638 and .633, then you'd be pretty sure the .002 difference was deflection. Not sure how you're setting x offsets, but the best way to set them accurately would be to take a manual light cut, and then, WITHOUT MOVING THE X AXIS, go into the tool offset page, and on the keyboard you'd enter X.643 <CAL>. When you do this, you're doing no calculations to arrive at the offset. You simply make a cut, measure the resulting diameter, and enter that amount. The cal function tells the control that the X position of the turret with this tool active produces this diameter. The control internally takes that info and calculates the proper offset for the tool based on that info, and enters it into the offset page.
A word about your feeds.....the control comes up in inches per revolution at startup. Your F30 looks sorta suspicious, as that would give you a feed of thirty inches per revolution. I'm gonna assume your feed wasnt quite that heavy
Also, if you were in MDI and entered M3S1000G1Z0F30 all on one line, and then hit cycle start, you should modify that. Start the spindle as one command, and then put your motion command in once the spindle is started. As written above, the motion and the spindle would start simultaneously. Generally it won't be a problem, but its always a better practice to program such that you're sure the spindle is at speed before any motion commences. This would apply regardless of whether you were entering commands in MDI or running a program from memory.
When keying a program in, or entering one via a BTR or your DTE device, you can eliminate the non-significant zeros. Z0 is the same as Z0.0000, Z.5 is same as Z.5000, Z1 is same as Z1.0000, and so forth. Saves time, and also saves memory, which is scarce on these older controls. I dont have any manuals here at home, but there's a key near the editing keys that will strip out all spaces and unnecessary other stuff in a program to minimize memory usage. I never put spaces in a line of code anyway, but thats just me. If the spaces make it more readable for you while getting things set up and proving a program, then you can put them in and strip them out later once the program is proven if you plan to hold a lot of programs in memory and need max space. In programs without branches, line numbers serve no purpose in these controls either. Unless they're of some benefit to you, they can be left out.
Also, be very cautious of code generated via one of the converter type programs. Okumas have quite a few commands that don't follow the same format as Fanuc, and most converter programs I've seen tend to be more geared toward Fanuc controls, or controls with Fanuc emulation. Actually, if you learn to use the LAP features as much as possible, you'll soon find you can write programs by hand in just a few minutes. LAP is found in your 2028 section of the manual, and is all your auto roughing, grooving, drilling, and threading routines. Some of the stuff you can do isnt real obvious in the manual. For example, to use LAP for drilling, you specify a face grooving routine with the groove at X0. Add whatever peck increment you want to that grooving cycle and you have a peck drilling cycle. Take a look too at G75 and G75 in your 2028 manual. Those will do auto chamfers and corner radii by just adding either G75 or G76 to a G1 move, and specifying an L value for whatever chamfer or radius you want. Lots easier than creating a chamfer via an X-Z move or a radius via a G2 or G3, because the control does all the thinking when you use G75 or G76.
I had never heard of your DTE device, but it appears that its the equivalent of a BTR, but done via software in a PC. Always seemed to me that was something that someone would have done, as it ain't rocket science. I still need to add a BTR or something to one of my lathes for loading programs, so I'm curious if you happen to know what the DTE costs.