Another communications problem

[vanbry]

Morning,
I've read all the threads that I can find, but I can't figure out just what's wrong. I've got a Cadet w/OSP5020L.

I'm trying to get the rs232 up and running. The cable is right, but I'm getting errors both sending and receiving files.

I've checked my parameters, and all seems to be well there.

When I try to send to the computer, I get this error:
output data is ?
!

When I try to send to the machine from the computer, I get this:
2585 tape file name not same ERROR '

I'm just trying to send a small file named test.min
I added $test.min to the first line of the program, and that doesn't seem to make a difference. It gives the erros immediately, so I know it's communicating.
Any ideas would be appreciated.

Thanx,

Keith

[Superman]

Assuming that you are using PIP

From control to PC using PIP

$TEST.MIN%
....
M30
%

set PC to receive the file
<PIP> <PUNCH> TEST.MIN <WRITE>

From PC to control using PIP

$TEST.MIN%
....
M30
%

set PC to send the file
<PIP> <READ> CN0:,TEST.MIN <WRITE>

(note the comma after CN0(zero not letter oh) , the CN0: defines the port, the comma indicates what you want to rename the incoming file as, the % on the first line terminates the filename sequence, a % only on the first line is best to start fault finding as the rename function will give a default name of A.MIN,,, but the comma after CN0:, is normally standard

[Oti]

Try removing the $TEST.MIN from the start of the program. Some older controllers cannot handle it and will alarm out. The program will come in as A.MIN and can then be renamed.

[danielponciano]

ok

[Algirdas]

the first You tried was sending parameters from OSP to PC. That was "data pip" mode. You can send all parameters, You can send only selected, so it asks "output data is?".
For part program file sending You need to go to edit mode first and use PIP an so on as Superman described already.
You can set parameters to have CN0: by default and no need to input file name.
Parameters for Lathe are little different from the same for Machining center. Pay attention: port settings for input are not the same as for output.
2585 tape file name not same ERROR '
two possible reasons:
parameters: ISO/JIS; EIA code; 7 or 8 bits; checksum incorrect. maybe together with wrong cable causes some symbols received improperly. Try to change these parameters and see the result. Try change communication speed. Faster is better.
another reason: file name mismatch, as alarm message says.

[vanbry]

Thanks for the help so far It looks like part of my problem was the port settings...I had baud rate set on the pc to 4800, and on the cadet, they were set at 19200. I thought I changed them to 4800, like the instructions said, but apparently that didn't take when I set it. I saw the "W01 ALARM-D power on effective parameter set" at the top of the screen when I changed it, but I thought it meant that I had to turn the power off and back on for it to take effect. I guess I have to learn how to change that yet too.

Anyways, I'm able to use PIP and send a test file just fine. When I try to send a longer file, I get this error: 2154 SAT full ERROR 2005C. It's only a 2k file, so I'm not sure what that means...and it's the same as a file that I keyed in by hand on the machine, so I know that the buffer can run a file that big.

By reading the manuals, I thought I was supposed to used data pip to send a file. Nothing beats real people to help!!!

[Algirdas]

on the cadet, they were set at 19200
That's surprise. I have seen max baud rate 9600 on Okuma. As far I know semiconductor components used, it can reach 9600 max. on Okuma.
I had to turn the power off and back on for it to take effect
yes, there are some parameters acting that way. You need to turn off the OSP. It's good to change them all at once, and then one turn off is enough.
I'm able to use PIP and send a test file just fine
congratulations. That's good beginning. Have you some lower case characters in the text?
2154 SAT full ERROR 2005C
2kB must go normally. I use 4kB and 8kB for communication tests. Check if Your user disk (BB1:?) has enough free space.
It could be because of communication error also. Check handshake settings. Handshake depends on cable configuration also. There is setting to generate one of handshake signals internally, so this better to have set to external handshake signal for real file transfer. Internal is useful for test purpose only.

[vanbry]

on the cadet, they were set at 19200
That's surprise. I have seen max baud rate 9600 on Okuma. As far I know semiconductor components used, it can reach 9600 max. on Okuma.
I had to turn the power off and back on for it to take effect
yes, there are some parameters acting that way. You need to turn off the OSP. It's good to change them all at once, and then one turn off is enough.
I'm able to use PIP and send a test file just fine
congratulations. That's good beginning. Have you some lower case characters in the text?
2154 SAT full ERROR 2005C
2kB must go normally. I use 4kB and 8kB for communication tests. Check if Your user disk (BB1:?) has enough free space.
It could be because of communication error also. Check handshake settings. Handshake depends on cable configuration also. There is setting to generate one of handshake signals internally, so this better to have set to external handshake signal for real file transfer. Internal is useful for test purpose only.

Hi Algirdas,
My user disk was full. I deleted some files, and then it send just fine. Thank you so much. For whatever reason, 19200 seems to work okay, so if it isn't broken, I won't try to fix it!! I'm just happy to be able to send programs. This machine doesn't have the LAP option, so programming at the console is a major pain. I've just got to tweak my cam post for a few items now, and I think I'm good to go.