pcmccartney1

Generally, the vendor will supply there own set of motion AOIs.

VFD #1 and do a firmware upgrade.  Because it truly has new components. By the same token, VFD #2 was recently tested for working condition.

I could be corrected, but the source protection you are talking about is only for version 20 and later.  I presume you want to change the program for use with v17.  To do so you will need to open the original in v20, turn off the source protection in the security tab of the controller properties and save to a new name. Then change the controller to v17 and it should convert the program.

Also remember that the order of the bits in INTs and DINTs are reversed.

Check to see that it's seated properly.  If problem still exists, then replace.

The was a change between version 20 and 21.  For v20 and older, you would use the Logix CPU Security Tool.  For v21 and newer, you use theFactory Talk Security via Factory Talk Administrative Console with an adminsistrative account username and password and the Security tab of the Controller Properties based on the Logical Name. There's an entire manual to download and read to setup Factory Talk Security with Factory Talk Administrative Console.

Suggest you download and read the ethernet function manual IB(NA)-0600628ENG-B. Understand that by default the drive parameters are set to be controlled by hardwired inputs and outputs and the HIM (human Interface Module).  To control via ethernet, you must parameterize the drive to accept control and frequency reference via the ethernet.   Unfortunately, I have no experience with Beijer PLCs or any knowledge of their capabilities and communication protocols.  I saw a resource regarding comms via Modbus TCP and CANopen.   Once the PLC and VFD are talking, then write code to read and write to the VFD.  Different platforms use different terminology, but most use what is called implicit or explicit forms to read and write to the VFD.  You'll need to determine what the Beijer capabilities are.  Maybe find an example code at either Beijer or Mitsubishi to help you.

Why is the DB so much hotter than the Machine #1? Also disconcerted about the DC Bus voltage difference. What is the result is you change the wiring to omit the DB thermostats signal?

Haven't looked at RBAC.  I do use FT Security for a specific customer (150+ sites) because the process is patented.  I've locked it down such that you can't even open the ACD unless you have the specific VM Image (i.e. computer name and ability to login to FT).

How did you configure your RSLinx Communications Driver?  Which one did you use?  Is your computer's NIC setup in the same subnet as the PLC?

If this is not applicable, then ignore me.  Is the 1769-IT6 compatible or does it have to be a 1762?  I presume that you found the module when offline with the 1500.

Any idea how to obtain or calculate the Day of the Week from WorldClockTime or any other attribute? There is a KB about a specific instruction GDW for SoftLogix 5 only.

Your earlier picture shows the MNet module is already inhibited, so good call on removing it.

@PaulKim1003 Wanted to get back to you and thank you.  It worked quite well for me.  My associate built his own but studied yours and found them to be quite similar.  There are many formulas on the web that describe how to get day of week.

Dumb idea here...can you open the med in a text editor and change the version.  You know, like an L5K for Logix? Or is it truly locked because of the different versions of SQL?

In your base OS, goto Devices and see which COM ports are occupied.

You'll need to check to see if COM3 is being used by another device.

That would be wonderful!

Looks more like a IO board.  Takes all field wiring and the cable on the lower right goes back to an input or output module.  Like a Phoenix Contact product and also has individual fusing. 

Seem to remember those having a large memory card for application storage, almost PCMCIA looking.

You need to determine the Xycom's Remote Screen Change capabilities and match up with that.

To pturmel's point, I've done udts quite a bit.  The only real hurdle is the limitation on the size or bytes of the udt.  The udt must also contain a connection status tag.  The limitation of normal tags is around 500 bytes while safety tags is 250 bytes, I think.

I might be over simplifying this but... Seems the box or case erector needs to know when to drop or push the box onto the conveyor between the cleats.  Why not have a prox detect the cleat and maybe an adjustable delay timer to determine when to "release" the box?

Does the manual describe the data type and access type?  Fearing that it's read only rather than read/write.

Check the battery Check the cabling for the signals board to the robot base Lastly replace the signals board.