I need to set up a Remote connection to one of our customers. The basic system overview is a NS8-TV01B-V2 (Ethernet version) connected with NT Link (RS232) to a CP1H-XA40. The one port of the CP1H has the RS232 port for NT Link to the screen and the other port has a CP1W-CIF11 for RTUs that cannot be freed up. I am considering a eWON 2005CD and connecting to the screen with both Ethernet and Serial to Port B.
C# TCP/IP Client that sends data received from serial port. And sending it to the socket and sending. Class and pass it into the Serial and Network. 1 Why would I need a serial terminal / serial console?; 2 Some background so you get the idea. 2.1 How do this apply to Proxmox PVE?; 3 Configuration on the host. 3.1 Add a virtual serial port to the VM; 4 Configuration on the guest. 4.1 Configure the terminal if not present. 4.1.1 Reboot the VM, verify that the emulated serial port is there; 4.1.2.
The Ethernet will give me a faster connection for screen changes and the Serial will allow me to pass-thru the screen to the CP1H. But ideally I would like to just have an Ethernet connection to the NS8 and use a pass-thru connection for the CP1H, but I can’t figure out any way to do this. I did consider swapping the RS232 port on the PLC for a CP1W-ETN01-US and using Ethernet for my screen comms, but I have reservations about the speed. I read in one of the ETN01 application manuals that there shouldn’t be more than 20 functional objects on a page, and I have some very intense setup screens which probably have over 70 functional objects. Here is the trick to the passthrough that you are describing: The PLC needs a FINS Routing Table that includes both the local network (serial) and remote network (Ethernet). For the local network, use Unit 253 if the CP1W-CIF01 is in the LEFT socket of the CP1H, or Unit 252 if the CP1W-CIF01 is in the RIGHT socket. These seem backwards numerically, but they are correct.
If the NS uses Serial A, then the FINS Network in the Routing Table is 111. If the NS uses Serial B, then the FINS Network is 112. Those number are fixed in the NS. You also need a Relay (Remote) routing table entry. Remote Network = the FINS Network Number of the Ethernet network, as assigned on the NS. Relay Network = the Serial Network number assigned in step 1.
Relay Node = 1 (this is the PLC CPU on an NT Link Network). In the serial port setup on the PLC, set the Max NT Link Unit Number to 3. This gives a longer timeout on the serial port, and allows for passthrough of long Ethernet packets. When you go to connect with CX Programmer in pass through, here is what you do. Set the Network Type as Ethernet.
Set the Source Network address to the FINS Network Number for your Ethernet network. Set the Destination Network address to the FINS Network Number for the Serial network (111 or 112).
Set the Destination Node Number to 0 (I think). Set the IP Address to connect to to the IP Address of the NS.
See my video on youtube for help on FINS Routing.
It’s possible to get Proxmox to passthrough a Serial number for the HDD but it’s a right Pain in the rear to do. See. Add the drives to the VM as usual. run qm showcmd XXX (Where XXX is the vm id) Copy the command to notepad.etc, find the lines that deal with the drives e.g -drive file=/dev/disk/by-id/scsi-SATA-MYDRIVE-SN,if=none,id=drive-virtio1,cache=writethrough,aio=threads,detect-zeroes=on -device virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb (Yours will be a file if you’ve not passed through a drive) Copy them. Edit the config file for the container and comment out the lines relating to your virtual HDD with a # add the line args: -drive file=/dev/disk/by-id/scsi-SATA-MYDRIVE-SN,if=none,id=drive-virtio1,cache=writethrough,aio=threads,detect-zeroes=on,serial=MYSERIAL -device virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb. Just installed RockStor as a KVM in Proxmox 4.1, so this is my first post to this community.
I am not an IT pro just a home user/enthusiast in over his head and willing to learn. I used the new method to pass my lone HDD to RS as described in the link in the post above. However, RS is only showing 100G of some 2TB. “virtio0: local:100/vm-100-disk-1.qcow2,cache=writeback,size=1863G,serial=WDCWD20EZRX-00DC0B0WD-WMC1T1453223” I am fairly certain this is not the proper syntax, so that could be my problem.
So, I have posted a similar quest over at Proxmox. Just fyi:. Setup your VM as you normally do in Proxmox via GUI. Its because there should be no quotes arround serial number snippet from my old config when I used virtioblk: virtio1: /dev/disk/by-id/ata-WDCWD2003FYYS-05T8B0WD-WMAUR0510553,size=K,serial=WD-WMAUR0510533 virtio2: /dev/disk/by-id/ata-WDCWD2003FYYS-05T8B0WD-WMAUR0510822,size=K,serial=WD-WMAUR0510822 with virtioscsi this problem goes away since operating system is allowed to talk directly to the drive and query it for it’s real serial number.