Mendon Systems

MrPLC Member
  • Content count

    490
  • Joined

  • Last visited

Posts posted by Mendon Systems


  1. Syswin was never a very good piece of software. The last PC I used it on was running Windows 98 so I can't help you with XP pro. Here are your options as I see it: Option 1: Haul one of the XP Home PCs from your house to the site to do the repairs to your friend's system. Option 2: Get a copy of CX-one or CX-one Lite to install on the XP pro system.

  2. From your description I suspect that you will need to use a PID loop that is sampling the input to regulate the voltage out. The question is .... what voltage are you trying to regulate?? Your maximum output voltage will be 10 volts so the highest level you could get would be about 9.3 volts.

  3. I suspect the mixed I/O is going to limit your choices somewhat, particularly the 120 volt inputs mixed with analog inputs. I have used 120 volt terminal block relays as a voltage conversion to get around that limitation on small controllers. You might want to look at Omron CJ2M or CP1H controllers as an option. I have no idea about their availability to you though.

  4. I have been using Radnor welding cable for that application. It is rated for 600 volts and 105 C. Radnor cable I suspect that RussB has the correct answer. The people that make DLO cable greased a few palms!

  5. Without knowing all the details of your network setup it would be impossible to solve your problem. It does appear that what you have done so far isolates the problem to an issue between your PC and your network rather than a PLC problem. As far as alternative methods, I normally use a touchscreen with data logging capability to capture data from PLCs and upload the data file from the touchscreen on a scheduled basis.

  6. Specifically what do you mean "the PLC software would keep crashing"???? Does the PLC stop operating or do you lose the communications with it??? Which Ethernet module are you using on the CP1H??? The fact that moving the Ethernet connection to a different adapter on the PC changed the symptoms leads me to suspect that your problem is related to your network configuration.

  7. Another possibility ....... Put your test in a scheduled task that runs once per second off of the rising edge of the P_1s clock pulse. That will give you the absolute change over one second, then do your range check.

  8. I had a problem with an NS5 that lost the ability to write to the CF card and froze up a while back. It would run OK until the first write to the data log then froze. It was finally resolved by updating the firmware. Since I did that the NS5 seems to work OK. That system does not use the web server so I'm not sure if that is related to this issue. NS firmware update

  9. I think your brute force approach with the relay will work best. You could use the rising edge of the $SB0 bit from the NS to reset a timer. If $SB0 stops pulsing the timer would time out and reset the HMI.

  10. Generally they are in the Txxxx and Cxxxx registers in memory although that differs slightly in the older PLC models like the CPM and CQM series. Timers and counters normally count down to zero, so the value in the register is the remaining time or count value not the accumulated value.

  11. You should be able to look up the message in the Alarm/Event Settings under the PT tab. Use the Message column to find the text and use the Address column entry to determine what generates it. If there are a LOT of messages you can export the whole table to a .CSV file and sort through it with Microsoft Excel. That's about all the insight that I can give you. I generally don't use the NS terminals for projects.

  12. Hmmmm ................... One obvious possibility is that the program in the NS doesn't match the offline copy. One way to check that is to force each alarm bit on in the PLC and see if they show up correctly on the NS. Can you give us an example of what you are seeing compared to what you expected to see?

  13. The other configuration that should be mentioned here is what is commonly referred to as "wild leg" 230. It is actually a fairly common power system installed at small sites like machine shops that need 3 phase motor power and created by phase converters or transformers. It consists of the normal 230 single phase with two phases at 180 degrees phase angle and 120 volts to ground. The third "wild" phase is a 90 degrees phase angle to the other two and 187 volts to ground.

  14. 230v single phase is always as Bob described it with a phase angle of 180 degrees and a grounded neutral. The problem comes in when someone tries to use the same device on 3 phase. Most 3 phase is 208 volts with a 120 degree phase angle BUT occasionally you can run into some really strange voltage combinations. I ran into one old system recently that was 230 volts leg to leg with one leg grounded and another that was 230 leg to leg with no ground reference at all. It is probably safest to continue doing what you are doing now!

  15. Well ............ technically you are correct. The binary value for numbers less than 10 is the same, but it is poor coding practice to provide a decimal argument to a function that requires BCD.

  16. One more thought on this issue ................... I believe you must wait about 250ms after the initialization word is set before you can read the analog inputs. It seems as though the P_1s clock pulse should inherently do that, but maybe it doesn't. Try adding a short time delay at startup before reading the input word. I include a startup timer in every program just to let things stabilize before making any rash decisions.
    1 person likes this

  17. I think your initialization words are invalid. For 0-10vdc the init word I am using is #80DD. Edit: I retract that statement! #80FF would be a valid initialization word for 0-5vdc/20ma. I looked at a couple of CP1L programs that I have here and I do not see anything obviously wrong with your test program. Maybe some something with the connections??

  18. The CQM1 has a 1 minute clock pulse. You could use that to drive a counter with a preset of 1440 (minutes per day). The problem with that approach is how you would synchronize it so that the counter always starts with 0 minutes at midnight. It might be simpler just to set up a counter for each output and reset them every time the output cycles.