gabe

Here's another round-up of results: 1) Unit ID was always on 1. Changed it to a few other IDs just to check. No progress 2) Forced reset of 232 parameters on the PLC info mode. No progress. 3) Old U90 programs don't seem to work either. I can't even pull the basic version information nor 232 parameters off the PLC to the U90 software. 4) I've tried resetting the PLC when info mode, and putting the PLC in stop mode. I think at this time, it's probably best to call it quits and put this PLC out to pasture. Many thanks for all the support though. First time on the forum and even though I didn't get the solution I was looking for, I was pleasantly surprised with the support.

Thanks for the reply. Much tea has been brewed and processed. Troubleshooting results from your suggestions below: 1) The following is from the ComLog.txt in the main program when trying to do any type of communication through the RS232 port (unfortunately, I don't think it's anything too interesting - but I could be missing something obvious): 15-12-16 21:20:44.65 : < 4,9600,E,7,1> 4, 9600, 7, Even, 1, 10, 12000 > Retransmitting 15-12-16 21:20:56.66 < 4,9600,E,7,1> > Switching Com Port 15-12-16 21:20:56.89 < 4,9600,E,7,1> > Synchronizing Com Ports 2) Playing with the timeouts didn't seem to do anything. Different combinations of baud rates, stop bits, parity, etc had no effect. Manually setting the RS232 parameters on the OPLC to match the PC's didn't work either. 3) When using hyperterminal, no response is received from the OPLC to any PC commands. I did check the serial cable output by putting a jumper between TX and RX pins to get an echo back in hyperterminal and that seems to work fine. No response from the OPLC though. 4) I'll take a look at probing the pins tomorrow. On visual inspection of the port and the board, the pins themselves and board look fine from what I see (comparing it to another M91 that does establish communication fine). But if there is any damage that I'm not seeing, I probably don't have the capability to do anything about it as my surface mount soldering capabilities are non existent. Do Unitronics distributors typically repair M91's? or would it not be worth their time typically to go through the trouble?

Hi y'all: I've been using M-91 PLCs successfully in various applications and only recently came across a customer supplied M91-2-T1 that does not seem to be able to establish communication to program via the RS232 port. The PLC powers up fine as I see the old legacy program running on the hardware; however, whenever I try to download some test ladder logic, or even pull some PLC data, I get the "Communication could not be established" error message. Things that I've tested: 1) The COM port has been verified 2) I've verified the function of the programming cable chain: Serial adapter and Unitronics MJ10-22-CS25 cable verified by using the same setup to program two different M-91 PLCs that I had lying around (for completeness, these were the M91-2-R6C models - so not an exact match). 3) I've tried adjusting internal jumpers for all combinations of RS232 and RS485 4) I've tried using the "i" button on the PLC to match the RS232 parameters to that of the PC. In case it matters, the M-91 PLC in question has the following specs as indicated using the "i" button: Model: M91-2-T1 HW Rev: A O/S Version: 3.80 O/S Build: 05 Anybody have any troubleshooting thoughts or run into something similar?