Hi all. TL;DR at the end.
Had a situation last week where I needed to connect a workstation running RSLinx to a running PLC code, just to extract a heap of values to excel using DDE. Trouble was, the code was for a 1769-L36ERM and all I had lying around was a 1769-L16ER-BB1B.
My first approach was SoftLogix, which I've done before and has worked, but of course SoftLogix has been more or less discontinued as far as I can tell, in favour of RSEmulate, and the program in question was too new a version and wouldn't convert back to v23 without breaking the parts of the code I needed to access. So that was a bust.
My second approach was RSEmulate, which ran the code quite happily, but I couldn't figure out how to get RSLinx on the other PC to find the emulator.
My third approach, which did the trick, was to delete 99% of the code until it would fit in the memory of the 1769-L16ER I had lying around, and just doing it that way.
So it worked, but I'd like to think there's a way to do this using RSEmulate. It seems much simpler.
Both PC's are on the same subnet and can ping each other. In fact, RSLinx on the remote PC is getting it's activations from the PC running RSEmulate, so definitely no problems with talking to each other. In SoftLogix, I could add an ethernet module to the virtual chassis, give it an IP, and then I'd point the remote RSLinx to that IP address to find the virtual controller. But it doesn't seem that you can add a virtual ethernet module to RSEmulate. Adding a virtual devices driver to the remote RSLinx session of course only shows any virtual controllers running on that machine, not the remote one.
Any ideas?
TL;DR, if I have two PC's on the same subnet, one running RSEmulate and the other running RSLinx, how do I get RSLinx to "see" the RSEmulate controller on the other PC?
Had a situation last week where I needed to connect a workstation running RSLinx to a running PLC code, just to extract a heap of values to excel using DDE. Trouble was, the code was for a 1769-L36ERM and all I had lying around was a 1769-L16ER-BB1B.
My first approach was SoftLogix, which I've done before and has worked, but of course SoftLogix has been more or less discontinued as far as I can tell, in favour of RSEmulate, and the program in question was too new a version and wouldn't convert back to v23 without breaking the parts of the code I needed to access. So that was a bust.
My second approach was RSEmulate, which ran the code quite happily, but I couldn't figure out how to get RSLinx on the other PC to find the emulator.
My third approach, which did the trick, was to delete 99% of the code until it would fit in the memory of the 1769-L16ER I had lying around, and just doing it that way.
So it worked, but I'd like to think there's a way to do this using RSEmulate. It seems much simpler.
Both PC's are on the same subnet and can ping each other. In fact, RSLinx on the remote PC is getting it's activations from the PC running RSEmulate, so definitely no problems with talking to each other. In SoftLogix, I could add an ethernet module to the virtual chassis, give it an IP, and then I'd point the remote RSLinx to that IP address to find the virtual controller. But it doesn't seem that you can add a virtual ethernet module to RSEmulate. Adding a virtual devices driver to the remote RSLinx session of course only shows any virtual controllers running on that machine, not the remote one.
Any ideas?
TL;DR, if I have two PC's on the same subnet, one running RSEmulate and the other running RSLinx, how do I get RSLinx to "see" the RSEmulate controller on the other PC?