MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

15 Good

About drforsythe

  • Rank

Contact Methods

  • Website URL http://
  • ICQ 0

Profile Information

  • Gender Male
  • Location Metro Detroit Area, Michigan
  • Country United States

Recent Profile Visitors

6531 profile views
  1. SoftScreen for Xycom 2000T

    Xycom was obsoleted when Pro-face took over.  Pro-face is now a Schneider product, but if I remember correctly, there was at least one other company that was involved before Schneider.  Good luck finding the software.  Softscreen was DOS based. Someone out there has it and I am sure you won't have to worry about copyright or rules based on its obsolete status.
  2. control panel for sale

    Where are you located?  Shipping expenses are important when developing a budget. Do you have any pictures of work you have done? Are you looking to supply all components for your projects, or will you customers provide the major items and you supply the wire, terminals, DIN rail, etc.?
  3. 1756-IF16 powerup faults

    I have had a similar thing happening but with 1756-IT6I2 thermocouple cards.  My system uses a 1756-L72 with v21.011 firmware.  My cards on on a remote rack with 1756-ENBTs communicating between the racks. My system has done this erratically since it was launched.  When we power down the remote system, sometimes the whole system comes up normally and other times, one or more of the IT6I2 modules will come up faulted.  We usually have to remove and reseat the individual cards.  This has happened only with the IT6I2 modules and no other analog or digital modules.  We have tried changing the rack, the ENBT and cards.  I will also mention that it is not repeatable, meaning that it is not always the same card or cards that fault.  I have multiple IT6I2 cards in the main and remote racks.  It never happens in the main rack (where the CPU is).  Sorry my response is not a solution.  I am adding my comments in case others have seen this and to see suggestions if there are any.  Good luck with your situation.
  4. NX IO Unreliable?

    Any time a manufacturer tells you to seat / reseat the connectors to improve connection, there is a design problem.  It sounds like the connectors are prone to oxidation and/or the spring connections are weak.  Many years ago I worked with a motion control company that had a servo controller and drive in one unit that would typically work fine for 12-18 months and then would start failing.  It was found that connector pins were oxidizing.  There was such a problem with them that they recalled the units and replaced the internal connectors with ones that would not oxidize over time.  It was an expensive fix for them, but I imagine they never repeated that mistake.  I would recommend being the "squeaky wheel" with Omron and encourage others with similar problems to do the same.  Maybe if they have enough customers complain, then they will fix the problem.  
  5. Kunlun

    A quick Google search returned http://www.kunluns.com/list/?154_1.html.  Copyright info on the bottom of the page was last updated in 2018.  Contacts for the company are listed here: http://www.kunluns.com/about/?148.html.  You could try seeing if anyone responds.  Good luck.  You will most likely find that it is most cost effective to replace the HMI with a locally-available one with local support and expertise.    
  6. PLC Automation for Textile Printer

    Is this a new problem, or one that just crept up?  Do you have access to the code so you can see what the differences are between sample mode and start/auto mode?  If this is a new problem, there is probably a sensor that is either failed or not used in sample mode that is used in start/auto.  I don't think there would be an older version stored if the program was rewritten.  Are you able to connect to the PLC and view the code while it is running, or did the original programmer lock you from seeing it?  If you can get online and monitor the program that would be a good start.
  7. I am not familiar with this system, but with the info provided, it seems that the motion planner is being affected over time.  This should not be the case, as a motion control system should be more deterministic in nature.  Is there a utility built into the system that allows you to chart the motion profile as it is running?  If so, I would reboot the system and record the planned vs actual motion profile of the home routine.  Then run it again when you see the system slow down.  That would show you the differences.  Once you can definitively show the differences, you can involve the techs at Rexroth.  If you are seeing this type of change, they are probably aware of a shortcoming of the system and can show you how to remedy it.  Please post your progress here.  Your responses may help in the future.  
  8. I tried to find some info but could not locate manuals.  If you have a model number, it would be helpful.  I believe these devices are timers with multiple outputs.  In the case of this one, it looks like it has 30 possible outputs and your system has 25 of those outputs wired.  As the drum turns, the outputs turn on as the "flags" placed on the drum reach the actuation point (one spot along the drum where the individual switches are placed).  This looks like an industrial version of a vacation timer for lights in a home to make it look like people are in the house.  To convert this to a PLC, you will need to have or develop a wiring schematic that identifies which switches on the device control what devices on your equipment.  Once you have that, you should be able to draw another diagram that identifies the relationship of each switch flag to each other, which will be time-based.  If the unit still works and my assumptions are correct, it would be helpful to know how long it takes the drum to rotate one complete revolution.  If you know that, you could determine the duration of each of the switches "on" time based on the number of degrees the "flags" cover.  From there you could code your PLC based on the relationships you find with your diagrams.  I would be really interested in seeing a schematic for your system if you have one.  Good luck.  That is definitely an interesting piece of early automation.  A "keeper" for a collector, for sure!  Good luck in your conversion.  Please update this post with your findings.   After re-reading this, I see you had the model number there the whole time, in plain sight!  Sorry about that.
  9. Pneumatic Air

    I know you stated they were wired into the safety modules.  That was not the question.  I was just wondering why you think they are wired into safety modules.  If the air pressure is critical to safety, that is why.  If it is just critical to machine operation, then a normal input module would suffice.  Let's not let that trip us up, though.  I am not aware of any regulation that requires you to have a safety switch on each bank.  I could be wrong, though and if someone know differently, please share because I like to learn.  Only you and the machine designers can determine if anything is needed.  If you want to maintain consistency with the rest of the machine, could you just add pressure switches to the input air lines to the new Festo valve banks?  That would allow you to keep the Festo valve banks and still maintain the same standard that was set on the original part of the machine.  I don't think it is necessary for the switch to be integral to the valve bank.
  10. It would be helpful to know if this is a new application that you are just starting or if it is for a machine that has been running normally and this is a new fault. Excessive position error can come from many sources, including bad feedback device or cable, excessive load, stuck brake (if equipped), electrical noise, improper tuning, inertial mismatch, etc. Does this happen when in motion or sitting still? If in motion, how long does it take for the fault to occur after motion is commanded? If it happens while sitting still, does the motor have any audible noise or vibration you can feel?  If so, check your tuning.  
  11. Pneumatic Air

    It is not a requirement that I am aware of unless maybe you are in a specialized industry.  What do the pneumatic banks control?  It makes me wonder why the pressure switches are wired into a "1734 Safety RIO module".  What happens when a pressure switch is not made?  Does it cause the safety system to shut down all or part of the machine?  Or possibly lock a gate closed?  If the pneumatic system controls vertical cylinders and air pressure is required to hold the cylinders up, it could cause a safety concern if pressure is lost.  Without more info, I can only guess.  Give us an idea of what the pneumatic banks control and why you think the pressure switches are wired into safety modules. Aside from all of that, I do like air pressure switches on my machines.  I typically only do it on the main air supply to the machine, though.  I do not put them at every valve bank.
  12. FX2N-4DA

    The only manuals I know of are the Mitsubishi manuals.  Based on your question and the device you mentioned, I will guess that you are asking about the TO and FROM instructions.  If that is the case, I will do my best to explain it.  It has been a while and I am doing this mostly from memory.  The info below is generic and not specific to the FX2N-4DA.  I do not have  a manual for that handy.  Analog cards and other special function modules need to be set up then read from across the backplane of the PLC.  This is not an automatic function and is accomplished by using TO and FROM.  Whenever we want to send something to the card, we use TO and whenever we want to read from it, we need to use FROM.  The instructions work this way:           TO or FROM  [module number] [head address number] [data to read or write] [number of words or devices to read/write] Module number:  In plain English, if you have a special modules in your rack, they start with 0 and number all the way to 7 in the FX platform.  The first one is 0, the next to the right is 1, then 2, etc.  This number can be a decimal constant (k) or hexadecimal constant (h) Head address number:  This is the register in the module that you are reading from or writing to.  This number can be a decimal constant (k) or hexadecimal constant (h) Data to read or write:  This is the info you are sending to or reading from the head address number in the module.  This can be a constant (h or k) or it can be a memory location in the PLC (i.e. D100) Number of words or devices to read/write:  This is a constant (h or k) that tells the controller how many items to read or write.   Hopefully I got this right and didn't confuse you more.
  13. Can't alter program A series.

    Check for reads and writes using ANY input or output.  What I mean by that is, do a search for X0 and see if there are any reads associated with it.  They may have programmed it to read in whole words of inputs at a time and write that to an internal word (D0, for instance).  Post the program and rack layout if you are allowed.  I currently do not have the software installed, but depending on the format, may be able to get it installed.  Regarding the PC boards, it is possible they are converting the signals from DC to AC or PNP to NPN?  If you have prints, post them as well (if you are allowed).
  14. Just a thought...  Are you running RSLinx and Logix as an administrator?  That has been a solution to EDS files not getting registered properly and not recognizing certain modules.
  15. A lot of people program that way.  I think the intent is to go back to put some "default" values in but they often don't go back to finish that step.   On another note- I used to work for a distributor of Mitsubishi.  I would commonly run into the problem where someone had uploaded their programs using Medoc to create their backups.  For small, simple machines this would work fine.  For PLCs that were programmed using the GPP units, we would often run into a problem where whole sections of machinery would not work.  The problem was that the GPPs had tables that could be filled out to configure their remote I/O networks.  Medoc did not have these tables, so when the program was uploaded, that data would not get uploaded.  Therefore, when the program was downloaded again, the remote I/O would not work.  For users of Medoc, the TO/FROM instructions needed to be added to the program in order to configure the network.  In this case, people thought they were doing the right thing and because of a large gap in functionality between Medoc and the GPPs, they would get hosed.