Jump to content

Adamkse

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Adamkse

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, I now have my Remote I/O module connected and communicating correctly but I now have an issue with the Analog Input module. I have some 4-20mA transmitters wired up to the inputs but the LEDs are all blinking. The manual suggests that it is because the field power is no connected. This is correct as the device is powered from another 24V supply. Any ideas? Any helps is greatly appreciated. Cheers, Adam
  2. Hi Cam, you have cracked it. Thanks for your help. Here are all the answers in case this helps someone else. 1. I did it from the cmd prompt with all 4 packets received. Just tried there with the uniapps and got a tick so I guess that was successful? 2. I had the panel IP and and CPU IP set the same. Changed this and all green lights and status 6. 3. It is an isolated network. 4. I set the IP using the BOOTP server in unilogic with the no.9 dip switch.
  3. I removed and replaced the module with no luck. I am fairly sure that they are in correctly. In the URB Remote I/O Adaptor structure the Operational State is 0 so I guess that is where the problem lies. The only variable that is a 1, is the Enable bit. Communication Error Code is 0, IP address is as expected. I looked through the help file on the Operational State but couldn't find anything to help resolve it.
  4. Hi Cam, Thanks for the reply. I do not have a power distribution module installed. Should I? Running Unilogic 1.28.34 edit: all my instrumentation are powered from a separate 24V supply. There are no loop powered devices.
  5. Hi, I have recently installed a URB-TCP expansion module into an existing system. My issue is that the MOD light is FLASHING RED and my IOS light is FULL RED. Connected, I have a DO08CH URD-0008CH in slot 1 and a AI08O URA-0800O 8 Analog Current Inputs, 10 RTB in slot 2. The AI08O has all 8 LEDs flashing green. I can ping the module so I think it is communicating OK. Any help or info would be great. Let me know if you need any more information. Cheers, Adam
  6. Hey all, I figured it out. The issue was the set/reset coils not functioning properly. The do not work as local, function in or function out tags. Only global tags. Not sure why but when they are now global and working OK.
  7. Hi all I figured it out. In real life the heater was off as the code suggested. The issue was related to the set/reset coils not functioning properly. The do not work as local, function in or function out tags. Only global tags.
  8. I am aware of the search function. I did not have the software in front of me at the time of the post. I can now confirm that there are no other instances of the "float_start_command" and got it working by changing the contacts back to regular ones as opposed to the transition contacts. Not sure why it wasn't working in the UDFB but I will play around with it and see if I can figure out what was going wrong now that I have something that works. Thanks for your help. Adam
  9. One other thought on this. Does the one instance per tag, per program include disabled rugs? There may be disabled rungs that contain these tags but I would have thought that was ok?
  10. Copied it then changed the tags and deleted the copied function in/out and local tags it created. Does this not work? I don't believe that there are any other instances of the "float_start_command" tag except for what you have in the screen shot but will confirm tonight. As above I will confirm they are the only instances but I am fairly certain they are. Yes, the UDFBs don't allow transition contacts for some reason. Thee is no special reason for putting it in a UDFB as I only use it once. But I thought I may use it again in the future and it makes the code a bit neater.
  11. Hi guys, Thanks for the response. I couldn't set them as transition contacts as they are "function in" tags. I moved it to the main ladder and still doesn't seem to work. the set coil will not go high now? I don't quite understand how the set/reset coils work. the documentation states: "Set Coil separates the coil from the action or condition that energized the coil. Once energized, a set coil's result is no longer dependent on the action that energized it." Surely only the reset coil can unlatch it? Also, the networks are back on separate rungs. Was just
  12. Hello, I am having trouble understanding how the "Set Coil" and "Reset Coil" work. My understanding is that the Set coil, once energized, stay energised no mater is the RLO goes low. Is that correct? My code seems to switch off the set coil when the RLO goes low. Any ideas on where I am going wrong? Thanks, Adam
  13. Noticed that my PID_HLT output was called "PID Output bit" and not "PID Output" as I had. Still the same problem but the oposite way round "HLT1 OUT" is always 0 even if "PID Output bit" is changing.
  14. Hi, I have a PID function block with an embedded PWM function which should turn a heater on and off with a duty cycle. However it is always set on (1). When I monitor the PID UDFB the output from the PWM is 0 but the main ladder has it as a 1. If i drill down further in the PWM UDFB then that is also 0. I don't understand what is happening. Any help would be great.
×
×
  • Create New...