One uses Profibus and the other is MPI. I see now that a standard serial cable is insufficient. I like Ethernet based protocols . Most of our equipment is new, the only programming I've done that required a serial cable was for the micrologix line.
As an aside, the S7-300 memory cards can be inspected/modified using a binary editor (e.g. HxD) - I've successfully modified the data on the memory card to change the program operation (this was purely an academic "can I do this exercise" I might add)
One uses Profibus and the other is MPI. I see now that a standard serial cable is insufficient. I like Ethernet based protocols . Most of our equipment is new, the only programming I've done that required a serial cable was for the micrologix line.
Perhaps I'm crazy? I spent a hot Arizona summer working on a handful of S7-300's with a print out in FB, but only STL for editing due to the offline programs being lost and relying on uploads. I got through it, but it was a hellish experience.
On the s7-300 the MPI port is connected to the HMI while the DP (PROFIBUS) port is free. The MPI cable is of the 'pass through' variety (don't know the correct term), where there is a port on the back of the connector. This CPU I can take offline at will since we are still re-commissioning this older system.
For the other CPU, it looks like it uses Profinet actually and ultimately connects to our ethernet/ip network via an Anybus-X gateway. I can simply build a profinet cable with a standard rj45 and a 4 pair wire, correct?