Optimize Machine Connectivity with FactoryWiz Monitoring Guide

8.7.8 Machine Connections

In order to obtain a license for a machine, you must identify the type of machine you are configuring in the Set Machine Type pane.



The type of machine will also determine which settings you are allowed to configure. As you work through the configurable settings, FactoryWiz™ Monitoring will only show you the options available for the type of machine you have selected in this pane.  These settings are described in separate sections for each machine type.

 Adam (Legacy)

ADAM machines are legacy machines that must be connected to FactoryWiz™ Monitoring through an ADAM 6051 device. Each device has 12 inputs which may be wired to receive signals from the machine. The Machine Connection pane for an ADAM machine allows you to specify the information reported to FactoryWiz™ Monitoring on each input channel.

In the first section of this pane, shown in you will enter the IP address assigned to the machine, assign the channels used to report the machine’s state to FactoryWiz™ Monitoring, and enter the polling rate.

 Input Channels


Use the Run State Channel drop-down list to identify which ADAM box input channel is connected to receive the machine’s run state signal.  Select digital input 0 (DI0) from the list if the run state signal is wired to input channel 0 on the ADAM box, DI1 if the signal is received on input channel 1, and so on.

Use the same procedure to select the paused state, alarm state and part advance channels from the next three drop down lists if the ADAM box is wired to receive those signals.

To enable the DPRNT Pause feature, click the check box.  Enabling this feature allows a PAUSE DPRNT command to override the ADAM status.  Recommend being used on machines that report as running when the they are in a feed hold status, for example: waiting to pallet change.

Use the Polling Rate textbox to specify how often FactoryWiz™ Monitoring should poll this machine. Note that the value must be entered in milliseconds. The recommended polling rate is 3000 milliseconds (3 seconds). Less than this will increase network traffic.

Audible Alarm (Buzzer)


You may also configure the ADAM box to trigger an audible alarm (buzzer) to signal state changes. Use the second section of the Machine Connection pane to configure the buzzer. This section is shown in Error! Reference source not found..

The ADAM 6051 has two digital output channels, digital output 0 (DO0) and DO1. Enable the buzzer by using the Buzzer Output Channel drop-down list to select the output channel connected to your audible alarm.

You may trigger the buzzer to sound when the machine reports any of these states:

·         running;

·         idle, with no reason set;

·         paused, with no reason set;

·         alarm, with no reason set;

·         off, with nor reason set;

·         or manual.

If you have enabled the buzzer, use one of the six Buzzer Delay text boxes to select which states will trigger the buzzer. The Buzzer Delay is the number of minutes you want FactoryWiz™ Monitoring to wait before triggering the audible alarm.

If you want the audible alarm to sound only if a state has lasted past a certain amount of time, enter the number of minutes you want FactoryWiz™ Monitoring to wait before triggering the buzzer. 

 

A buzzer delay of -1 disables the buzzer for that state. You will likely want to set the Running Buzzer Delay to -1, so that the buzzer does not sound while the machine is running normally, for example.

Set the buzzer delay to a state to 0 if you want the audible alarm to sound as soon as the machine reports that state.

Notifications


The Notifications section of the Machine Connection pane for an ADAM machine allows you to configure FactoryWiz™ Monitoring to send email notifications if one of the 12 input channels turns on or off.

You may use this to configure custom alerts. For example, you might have a sensor that detects when a door is open. If you want to know if that door is left open for more than 5 minutes, you could connect the sensor to the ADAM box and use this section to send a notification to an email list if the door is open for more than five minutes.

If the door sensor were connected to channel 0 on the ADAM box, you could configure this alert by first entering a description of the input in the On Description text box for DI0. Then use the ON Action drop-down list to select the email list you want to notify. See Email Configuration if you need to create a new email list for this notification.

You may select Do Nothing, to disable notifications, Log Only to record the event, or an email list such as Email 2, to log the event and send a notification email to the recipients of Email 2. The event is also logged when emailed.

Finally, you would enter “5” into the On Minimum text box to set the five-minute delay. 

Analog Input Thresholds


Leave these values blank.  This is for use with analog ADAM units only.  If your ADAM unit is equipped with analog inputs, please contact FactoryWiz for assistance with these settings.

Allen-Bradley machine types are any machines that must be connected to FactoryWiz monitoring through an Allen-Bradley PLC.



Enter the IP address of the PLC, the polling rate, and the PLC type.



You will then need to set the running, pause, idle and alarm tags. The tags are obtained from the PLC. You will need to specify what triggers the status as true. Example:

 

If the running status is taken from plc_status and when the value/string is “Y” when running, then:

Running State Tag = plc_status

Running Tag Condition = Y

Running Tag Type = String


Repeat for each status where you have a tag.



Enter the IP address assigned to the machine in the IP Address text box, and the TCP port number in the TCP Port text box. The default TCP port on a Brother machine is 10000.

Use the Polling Rate text box to tell FactoryWiz™ Monitoring how often to poll the machine for information. If you enter “5” in the text box, FactoryWiz™ Monitoring will poll the machine every five seconds. 

The Parse Entire Program option determines whether FactoryWiz™ Monitoring only looks at the top line of the program the Brother machine is running, or reads the entire program. This option should only be enabled if FactoryWiz™ Monitoring commands are embedded in program comments.

Note that reading the entire program may cause a slight delay when switching to a very large program. Factory Wiz ™ recommends disabling this option unless it is absolutely necessary.

The last setting in this pane tells FactoryWiz™ Monitoring where to find the part ID number. Select an option from the drop-down list, shown in Error! Reference source not found..

Select O Number if the part number is on the top line of the program or select First Comment if the part number is found on the first comment line. Select None if the part number cannot be read by one of the other two options.

Note that if you select First Comment you must also enable the Parse Entire Program option.


Enter the IP address assigned to the machine in the IP Address text box and Use the Polling Rate text box to tell FactoryWiz™ Monitoring how often to poll the machine for information. If you enter “5” in the text box, FactoryWiz™ Monitoring will poll the machine every five seconds.


Use the Polling Rate text box to tell FactoryWiz™ Monitoring how often to poll the machine for information. If you enter “5” in the text box, FactoryWiz™ Monitoring will poll the machine every five seconds.



Enter the IP address assigned to the machine into the IP Address text box and the TCP port into the TCP Port text box. Then specify how often FactoryWiz™ Monitoring should poll this machine in the Polling Rate text box.

Part ID Source


Use the Part Id Source drop-down list to describe where FactoryWiz™ Monitoring can find the part ID number.

Select:

·         First Comment if the part ID number is in the first comment in the main program;

·         O Number if the O Number of the main program is the part ID number;

·         Macro Variable if you have assigned the part ID number to the value of a macro variable;

·         Macro Variable Pointer if a macro variable holds a pointer to the O Number of the subprogram that contains the current part number within its first comment. Typically used for machines running from a pallet schedule;

·         Sub First Comment if the part id number is the first comment in a subprogram.

·         Sub O Number if the part ID is the O number of a subprogram.

·         None if you want to enter the part id number manually.

Note that Sub First Comment and Sub O Number will probably not work well if the main program contains more than one sub-program. In that case, it would be better to use a macro variable or a macro variable pointer.

If you have selected Macro Variable or Macro Variable Pointer, you will have to provide an address for the macro variable in the Part ID Source Address text box. For example, you may assign the part id number to the value of macro variable 501. In this case, you would select Macro Variable as the Part ID Source and enter “501” in the Part ID Source Box.

For pallet change machines that run a sub program for each pallet that are called from the same main program, use Macro Variable Pointer. In each sub (pallet) program, store to a macro variable the number of that program, Fanuc Example:


O1(MAIN PROGRAM)

M61

M98 P1000(PALLET 1)

M62

M98 P2000(PALLET 2)

M99

 

O1000(PALLET 1 PROG)

#501=#4115 (SYS VAR)

nc code here

M99

In the above example the main program pallet changes (M61 and M62) and then calls the program for each pallet using M98.

In the Pallet Sub program O1000, the first line #501=#4115 stores the program number 1000 into variable 501 by using the Fanuc System Variable 4115.

FactoryWiz will then look at the name associated with the program number O1000 in the program directory.

This is then repeated for pallet 2.

This is an example, do not use these M Codes or variables in your machine without reading the machine tool programming manual first.

Operator Messages

The Operator Messages drop-down list, shown in Error! Reference source not found., allows you to define which operator messages will force FactoryWiz™ Monitoring to determine the machine is in alarm state.
 
Most machines prefix alarm messages with either “AL” or “ALARM”. You may choose to have FactoryWiz™ Monitoring determine that a machine is in an alarm state based on whether the message received begins with the letters “AL” and whether the machine stops running after the message is received.

The options available from the drop-down list are:

·         Never – no operator messages will cause FactoryWiz™ Monitoring to determine the machine is in alarm state.

·         Idle – the machine appears in alarm state if an operator message presents while the machine is in an idle state.

·         Idle, Paused –the machine is in alarm state if an operator message presents while the machine is in either an idle or paused state.

·         Idle, Paused, AL – the machine appears in alarm state if an operator message presents while the machine is in an idle or paused state and the operator message starts with the text “AL”.

·         Always With AL Prefixed – the machine appears in alarm state if the machine receives an operator message that begins with “AL”.

·         Always –the machine is in alarm state if it receives any operator message.

·         When motion stops –the machine is in alarm state if a message appears while motion is stopped.

The default option is
Always With AL Prefixed.

Please note, the machine will need the extended message function option enabled to output messages.

Other Settings


Use the next four settings to set how FactoryWiz™ Monitoring should account for dwell time and whether or not it should read tool and workpiece offsets from the machine.

The Dwell Time drop-down list lets you select whether to count dwell time as running or as paused time.
  
The default setting is Paused.

Use the Poll Workpiece Offsets and Poll Tool Offsets drop-down lists to select whether or not FactoryWiz™ Monitoring reads the offsets from the machine. Reading the offsets does increase overhead, which may affect FactoryWiz™ Monitoring’s performance.
 
If you suspect that this is causing a problem, you may turn off the offset polling or use the Tool Offset Limit drop-down list to limit the number of tool offsets tracked by FactoryWiz™ Monitoring.

Setting the Tool Offset Limit to 0 will cause FactoryWiz™ Monitoring to poll all available tool offsets. Setting it to any positive number, x, will cause FactoryWiz™ Monitoring to poll only the first x offsets. In the example shown, the Tool Offset Limit is set to “10”, and FactoryWiz™ Monitoring will only read the first 10 tool offsets.

The last settings in the Fanuc FOCAS Machine Connection pane determines whether FactoryWiz™ Monitoring will consider the machine to be paused if override dials are set to 0 and which control path will be used to determine the part ID number and part count.

The F0% Forces Paused and R0% Forces Paused drop-down lists let you select whether FactoryWiz™ Monitoring should consider the machine to be paused if the operator sets the feedrate override dial or the rapid override dial to 0% while the machine is in cycle.

Use the Control Path textbox to enter the controller path number used to determine the part ID number and part count on multi-spindle machines. Generally, this will be control path 1, 2 or 3.
 
If you do not know which number corresponds to the correct path, you may have to use trial-and-error to find the proper setting.

The Monitor Primary Path Only setting determines whether FactoryWiz™ Monitoring determines the machine’s state based on all the control paths or just the primary path. This should always be set to True for single spindle machines.

If you set it to True for a multi-spindle machine, FactoryWiz™ Monitoring will consider the machine to be in the running state only if the primary path reports the running state. If you set it to False the machine will be considered to be running if any of the control paths are running.
 

It is possible to configure FactoryWiz™ Monitoring to monitor multiple paths separately, but you would need to create separate configurations and obtain separate licenses for each path you want to monitor. For example, if you have a multi-spindle machine that you have named “Machine 1”, and that machine has different control paths on the right side and the left side, you could configure “Machine 1 Right” and “Machine 1 Left” as two different, virtual machines. Each “machine” in this case would only have one spindle, and you would set the Monitor Primary Path Only setting to True.

The Fanuc control must have FOCAS option turned on.



This control type is custom in nature and requires custom software from us and licensed software from Fidia.

This connection type has been depreciated, please contact us to discuss new methods of connecting your machine.


Haas MDC using RS232 is managed in our DNC System. See the DNC manual for further information. You will not need to configure any settings in the Machine Connection pane.

The machine must have setting 143 to use this feature.





Use the Polling Rate text box to set how often FactoryWiz™ Monitoring will poll the machine for data.

Use the Part Id Source drop-down list to describe where FactoryWiz™ Monitoring can find the part ID number.

Select:

·         First Comment if the part number is in the main program’s first comment.

·         O Number if the O Number of the main program is the part number.

·         Macro Variable if you have assigned the part number to the value of a macro variable.

·         Macro Variable Pointer if a macro variable holds a pointer to the O Number of the subprogram that contains the current part number.

·         Sub First Comment if the part id is the first comment in a subprogram.

·         Sub O Number if the part ID is the O number of a subprogram.

·         None if you want to enter the part id number manually.

Note that Sub First Comment and Sub O Number will probably not work well if the main program contains more than one sub-program. In that case, it would be better to use a macro variable or a macro variable pointer.

If you have selected Macro Variable or Macro Variable Pointer, you will have to provide an address for the macro variable in the Part ID Source Address text box. For example, you may assign the part id number to the value of macro variable 501. In this case, you would select Macro Variable as the Part ID Source and enter “501” in the Part ID Source Box.

Similarly, you could assign the O number of the subprogram containing the part id number to the value of a macro variable pointer, and then select Marcro Variable Pointer as the Part ID Source and enter the address of the macro variable in the
Part ID Source Box.

 



Enter the IP address assigned to the machine in the IP Address text box.

The UDP Port is a fixed value and can not be changed.

Use the Head drop-down list to select which head / path you want to monitor.

Use the Part ID Source drop-down list to tell FactoryWiz™ Monitoring where to read the part ID number for the current program.

Select:

·         None if you want to enter the part id number manually;

·         O Number if the O Number of the main program is the part number;

·         Program name if the part number is the name of the main program;

Fusion Client needs to be installed and configured on the CNC. Point the Fusion Client to the FactoryWiz IP with compatibility type 4.




Enter the IP address assigned to the machine in the IP Address text box and Use the Polling Rate text box to tell FactoryWiz™ Monitoring how often to poll the machine for information. If you enter “5” in the text box, FactoryWiz™ Monitoring will poll the machine every five seconds.





Enter the MTConnect Agent URL in the MTConnect Agent URL text box.
 
Be sure to give the full URL and include the http://, such as http://10.1.2.100:5000/current

If you’re unsure of the URL, please contact the machine tool builder or agent.

MTConnect is licensed and supplied by the machine tool builder. For machines FactoryWiz natively connects to, we prefer to use our native protocols.

Use the Part ID Source drop-down list to tell FactoryWiz™ Monitoring where to read the part ID number for the current program.

Select:

·         None if you want to enter the part id number manually;

·         O Number if the O Number of the main program is the part number;

·         Program name if the part number is the name of the main program;

·         Sub O Number if the part ID is the O number of a subprogram;

·         or Sub Program Name if the part ID is the name of a subprogram.

You will not need to configure any settings in the Machine Connection pane.
 
All Siemens OPC DA settings are defined at the CNC.



Enter the machine’s IP address in the IP Address text box and the TCP port used to communicate with FactoryWiz™ Monitoring in the TCP Port text box. The default TCP port is 4840.

Use the Polling Rate text box to set how often FactoryWiz™ Monitoring will poll the machine for data. The default rate is every 5 seconds.

If the Siemens software is v4.7 or higher, then the Username and Password must match what is set in the CNC control.

Use the Part ID Source drop-down list to tell FactoryWiz™ Monitoring where to look for the part ID number.

Select:

·         First Comment if the part ID number is in the first comment of the main program.

·         First Comment (Sub) if the part ID number is in the first comment of a sub program.

·         Macro Variable if the part ID number is assigned to a macro variable (if you select this option, you must also enter the macro variable’s address in the Part ID Source Variable text box).

 

None if you wish to enter the part ID number manually.

Option Access My Machine OPC/UA required on the Siemens CNC and needs to be configured.

You will not need to configure any settings in the Machine Connection pane.  All System3R Cell settings are defined at the CNC.

This will only be used for one off connections. FactoryWiz will advise you on this as it is rarely used.

This will only be used for one off connections. FactoryWiz will advise you on this as it is rarely used.








    • Related Articles

    • MySQL Too Many Connections

      Too Many Connections We recommend taking a back up of your server beforehand. Set the following: You need to create 2 new DWORDS in the Registry. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters Value Name: MaxUserPort Data Type: ...
    • Troubleshooting Mazak Native Connections

      This is not for ADAM or MTConnect machines How to check Mazak Native Connections Can you ping the machine IP address? If not, check the IP address in the machine is correct. Check the physical network connection Check the switch is not blocking the ...
    • 8.8 Machine Groups

      On the Machine Groups page, you can view a list of current machine groups, add new, and delete machine groups. For purposes of reporting and filtering machines, you may predefine groups of CNCs to allow for the quick selection of a subset of CNCs. ...
    • 8.10.5 Machine Modes

      On the Machine Modes page, you can view a list of current machine modes, add new, edit, and delete machine modes. You may configure different modes, allowing you to keep track of when a machine is in production mode, actively producing parts, or when ...
    • 8.10.3 Machine Operators

      On the Machine Operators page, you may view a list of current operators, add new, edit, and delete operators that will be allowed to sign in to OperatorConnect. Add Machine Operator Click the Add Machine Operator button in the upper left corner. A ...