[OkumaWiz]

The green screens were not L-G controls but were L controls typically. Is yours for sure an L-G ? Ie does it have animated graphics and not just the Trace? Communication protocol is different on the two controls.

[slodat]

The control says OSP500L-G. Guy I bought it from said it’s a 1986 LB12. It definitely has the green monochromatic screen. I haven’t found any graphics or trace. The machine is new to me. I’d really like to get the serial Read working. Any help is much appreciated.

I’m using an Ausys DNC PRO. If there’s another working combo I’m willing to change my setup. I am able to Punch to the DNC Pro just fine. With all sorts of different settings.

[machinehop5]

I'm having a heck of a time getting my OSP500L-G green screen LB12 to communicate via RS-232. I can send from the control to the DNC Pro and it works every time. I can a myriad of errors whenever I try to send even a 3 line file DNC Pro -> control. I've read a lot of threads on here, spent many hours experimenting, and I'm at a loss.

Is anyone knowledgeable about the older Green screen configuration? I'd really like to send programs to the lathe.

...If, you are able to Download from CNC to PC...but not the other way then I would say there is a Format error of beginning of the Part Program you're trying to Upload.... try starting the Program with a BLANK line #1...on Line #2 a "%" a Percent Sign may or may not be needed at End of the program also....Seq Numbers may or may not be needed.

Post a Sample program you have would help.


DJ

[slodat]

I am unable to transfer a file I got from the control back to the control.

[Algirdas]

if you can compile clear detailed description. I am lost. So you transfer the file from one machine to another or what?

[machinehop5]

I am unable to transfer a file I got from the control back to the control.

Post the File you transferred

[slodat]

RS-232 cable is built according to this sheet I found on here:
Attachment 494186

1986 Okuma LB12 with OSP500L-G control. Bootup screen:
Attachment 494188

Parameters:
Attachment 494190

Attachment 494192

Attachment 494194

This is what I get when I try to transfer from PC to CNC. (PC is an Ausys DNC Pro):
Attachment 494196

This is what I get when I transfer CNC to PC:
Attachment 494198

This is the file that I transfered from CNC to PC. I am unable to transfer the same file PC to CNC. I hand keyed this program into the control.

$T3.MIN%
G50S3500T0101
G96S3000M4
G0X.76 Z.2
G1 X-.1 F.004
G0 Z.1
G0 X.76
G0 Z-.03
G1 X=-.1
G0 Z.1
G0 X.72
M2
%

I have tried several different settings, etc. I can always transfer CNC to PNC. I have received a litany of different errors, to no avail. The OSP500L-G that I own does not accept a baud rate number is Optional Parameter Word 39. It's set to 0 as shown in the images above.

[machinehop5]

...try adding % to the 1st Line of your program...if, that doesn't work. add a Blank line (CR/LF) to the 1st Line then, with the % on the 2nd Line...then your posted program just the way it is..

edited-

%
$T3.MIN%
G50S3500T0101
G96S3000M4
G0X.76 Z.2
G1 X-.1 F.004
G0 Z.1
G0 X.76
G0 Z-.03
G1 X=-.1
G0 Z.1
G0 X.72
M2
%

[Superman]

%
$T3.MIN% <<<<<..... get rid this line
G50S3500T0101
G96S3000M4
G0X.76 Z.2
G1 X-.1 F.004
G0 Z.1
G0 X.76
G0 Z-.03
G1 X=-.1
G0 Z.1
G0 X.72
M2
%

The 1st % let's the control begin recording the start of code to be saved, the $ indicates the name to be saved as in the control (filename can be altered on "READ" line)
Last (2nd) % is used to terminate the transfer and close the file.

So....
- One % at start AND one at end ...only
- Remove the file naming part (after $,before 1st %) to assist diagnosis of xfer issues.

Not sure of the earlier models, but.... there is different settings for READ and PUNCH. Both areas need to be checked.

Same goes for the xfer software on the PC. It also may have independent settings.

[slodat]

Tried that

2504 no tape data ERROR

Top of screen does show READ A.MIN

And, thank you for your help! Really appreciate it.

[slodat]

Changed bit 1.5 and now it locks up. So, that's not it!

[Algirdas]

what does it mean "locks up" ?
I would say using the minimal cable is bad idea at this case. Handshake lines are shortened, so you don't get any idea about handshake. So does OSP and doesn't say any error message.
By the way the picture at the comment #9 is showing wrong wiring as well.

Check the comment #5