While troubleshooting I am trying to use the online monitoring to show the netcmd# received string, I find with the wait time greater than .15 x 20 the Comm1 to the PC times out.
Have been having been problem with the RS-485. With PC connected through a RS-232/RS485 convertor that transfers data both directions fine. There is a PIC18 based embedded system that also has RS-232 (also has fiber optic for final install) that works fine connected to the PC, but when connected together the PLC apparently is putting out the command string either with NETCMD# ,or PRINT#, and the PIC doesn't respond. This is with both the command and response strings sent and received each way on the RS-232, but connect the 2 together, and no response. I feel that some of the problem is NETCMD$ timing out since the PIC is slow, with the overhead of processing the received/sent strings and 3 ADC conversions one after the other. The RS-485 is short at around 2' long, and at this moment has a 120 ohm terminating resistor across the +/- terminals at the PLC. Have tried other configurations also, both since communications to the PC are solid, I don't think that's the problem.
Any thoughts would be appreciated. :~