Jump to content

TT_ZX

Members
  • Posts

    77
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by TT_ZX

  1. If ModBus is enabled then it will accept valid commands from any device.  It has no security built in as far as I know.  I assume this is because it is designed to operate inside secure networks and not be exposed to the internet.  You will need to devise your own methods for securing the connection.  This may be by white listing IP addresses from external networks on a router or using a VPN or ssh tunnel.

     

    You could try enabling the ModBus Scan FB only when required.  This could be done locally via a push button or on a time basis.  You could even send it a text message or define your own protocol using the Protocol TCP/IP function block to change the bit.  I haven't done this before but I can't see why it won't work.

     

    Mod_Bus_Access.png

  2. I understand your concerns, I have the same concerns myself.  There is no way to limit the range of accessible registers which is a real shame.  This question pops up on this forum occasionally.  If you have a particular range of registers that hold sensitive values you can copy them to a data table at the end of each scan and then restore them at the start of each scan.  A bit of a hack that may or may not be suitable.  When giving a list of registers to 3rd parties to be read into SCADA systems I always buffer them into a vector of XI's etc.  This means they can only be read and not written to because there changes would be overwritten.  Not entirely foolproof of course.

  3. Hi micpalmia. I recommend configuring the turbine PLC to be modbus slaves.  This only requires 2 nets to be added to the PLC code.  It doesn't get much simpler than that for the PLC technician.  Have a look at the example "V280_Ethernet_TCP_MODBUS_IP_Slave.vlp".  I think you will have more trouble getting a secure connection from your remote server to the PLC than with the PLC itself.  I don't know what the network is between the remote server and the PLC.  From your post it sounds like you will be doing the server software.  Would you care to elaborate a bit more?

  4. I would use CANbus with Unitronics UniCAN protocol.  This is very simple to use and works great.  Use a good quality cable, run the cable away from VFD and power cables and EMI shouldn't be a problem.  Flywheel diodes are not mandatory but are recommended.  It depends on the coil and how often it is switched on and off.  In your case, I would use them on the Siemens 3RT1015.  I don't bother on small relays with infrequent switching.

  5. What sort of limitations are there on the tags and data tables on the UniStream platform in regards to memory?  For the V1040 we have 120k for the data tables.  With UniSteam I understand that memory is allocated dynamically rather than having a fixed memory pool for data tables but I can't see any way of determining what sort of resources have be allocated in a application and how much is remaining.  I don't want to go down the road of developing a memory intensive application and suddenly hit a brick way when I run out of resources.  Can someone please explain how I can check this.

  6. I have the same issue and as far as I know it is the expected behaviour.  The same thing happens when you hide an object on top of a frame, you see the background color, not the frame.  To work around this issue I use a piece of the background image for a binary image or list by pointer.  This is a pain though because you often have to change the piece of background image if you move the object.  If your background image has a background colour of its own, make sure this is the same colour as the HMI background.

    xq0.png
     
×
×
  • Create New...