Jump to content

ahoover

Members
  • Content Count

    31
  • Joined

  • Last visited

  • Days Won

    1

ahoover last won the day on February 12 2019

ahoover had the most liked content!

Community Reputation

5 Neutral

About ahoover

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

2,445 profile views
  1. Is this another solution? Just learned to use the copy byte function in the logic menu.
  2. Jason Hartley, That would be greatly appreciated!! I'm actually using a Unistream PLC, but should be able to get what I need from the vlp. Thank You ------------------------------------------- 6 hours later, this post still not approved by a moderator so will just edit it.... I did get a working program now. Figured out to always use modbus address zero. I'm sure I could still learn a lot from a working example....
  3. I am using the exact same controller specified in the first post(CMMO-ST-C5-1-LKP). Am wondering if somebody that got it to work could give me any pointers to get started. Am pretty sure the setup is done correctly on the controller, but I'm having problems figuring out what the modbus addresses should be. If it is not too much harder, I would like to access some parameters as well as the cyclic data. I want to do direct positioning. I appreciate any help!
  4. The button is setting a bit on press and resetting the same bit on release. A manual machine process is being activated when a particular HMI is loaded, and the button is being actively pressed by the user, this particular button does not initiate a change screen. The problem as described happens only when the following steps happen: user is pressing button to activate manual process, a critical machine fault occurs (emergency stop etc.) while HMI button is being pressed, the critical fault triggers an "action", the "action" unloads the process screen. In this scenario the bit linked to t
  5. Just curious if anybody else has experienced this issue. I have an HMI button that needs to be "pressed & held" to run a process. The button is setting a bit on "press" and resetting the bit on "release". This all works fine, except in the case of an "action" causing an HMI change while the button is pressed, this causes the button to never release, or at least the bit never gets reset. My ladder code has to monitor for an HMI change and reset the bit when this happens, which seems a bit clunky compared to how smooth most things operate with Unistream. Or am I missing something si
  6. I did not install the networking cable myself. Should get them to make sure it is isolated from any power lines. Do believe they ran a Cat 6 cable for what its worth...
  7. At the very least it sounds like I'm not the only one experiencing these types of issues. I could take another look at the email logic see if anything can be cleaned up. Thought I had the perfect workaround for email encryption limitations with smtp2go.com, but now some other issues are raising their ugly heads. Am not using any XB's, and the only TCP functions are remote connection with Unitronics apps and email. Usually for projects requiring internet connection we use Unistream. I'm thinking this project might be an upgrade candidate, and be the perfect opportunity to try out t
  8. Am doing Modbus RTU, it is pretty straight forward, setting speed and reading status from a couple VFD's. Allen
  9. I don't believe turning on SB 168 changed anything. In this case socket 2(SB 149 turns on when socket 2 is connected) is listening on port 20258, socket 0 (connected = SB 147) is listening on port 20259. So they connect on port 20258, SB 149 turns ON, they disconnect, socket 2 closes and SB 149 turns OFF. Same for port 20259, though they usually use port 20258. The problem is, sometimes when they close the connection from their phone app, SB 149 stays ON like somebody is still connected on port 20258. In reality nobody is connected anymore but socket 2 did not close and can therefor
  10. I am also not the expert on networking, else I wouldn't be having these issues, right? I understand you basically need a socket for each different type of network function, remote connection, email etc.. I have one socket set to TCP, server, on port 20258. After this socket is initialized it "listens" for an incoming connection request on port 20258 from a remote client. Another socket is set to TCP, client, on port 20256, it reaches out an makes a connection to the email server when the program needs to send an email. The 3rd socket is set to UDP_RAW on port 20257, it is used by the DNS
  11. I am the boiler tech for dkmiller16. Socket 2 in the program is setup as a slave, protocol is TCP, port is 20258. The problem they are experiencing is that sometimes the socket does not close when they disconnect from the app. I did change power up value of SB 168 to 1, though it appears that would only apply when the physical network link got lost? There is one unused socket left, I guess it could be used as an alternate remote connection port. I might do this, and make the rising pulse of SB 149 initialize the alternate socket and vice versa, this would always keep the one
×
×
  • Create New...