You have no items in your shopping cart.

New HIDS Drum Scales!

Click Here to Learn More!
Support: 858-292-2710

Why does my HI 1756WS module intermittently stop?

Last updated 05/05/2014 10:04 AM

Question

My HI 1756WS module hangs during parameter write or read command. The enable bit gets set after sending the command, but the done bit never goes active. The result is that the program hangs at this step.

This only happens in 1 of 10 attempts, which means it functions most the time but it's not reliable. Why does my HI 1756WS module intermittently stop?

Answer

There are three possibilities that might cause your HI 1756WS or your HI 1756-2WS to exhibit the symptoms you describe. They are:

1. The MSG instruction has some corruption. This is not necessarily seen when looking at the instruction, but rather in the background of the instruction. This is normally a result of copy and pasting the instruction from one program into another, especially if the original program was written in a different version of RSLogix. To correct this issue delete the MSG instruction and re-enter it manually.

2. The MSG instruction may be running multiple times. If this happens, when triggering the MSG instruction with code that should cause it to run only once, it will run multiple times causing the MSG instruction to eventually fail. The way to correct this issue is to place a one shot in the logic before the MSG instruction. This will prevent it from running multiple times.

3. The data in the source tag being used by the MSG instruction is corrupted/changed. This can happen if the user is using the same tag for both the source and destination. If the instruction does not go through properly, the data can be overwritten with bad return data. Once this happens, the instruction could then be trying to send commands that are not valid or do not have the proper data to go along with the commands.

With electronic instruments there is always a possibility that the module itself may have a problem. However, if the routine runs 9 out of 10 times, this would not usually be the case, especially if it is only one or two command routines instead of all routines. If the module itself has a corruption in the memory the user can run a memory clear command, command #148 (94 hex), SETDEFAULTPARAMS. This will clear out any internal corruption.

NOTE: If you clear the memory the module would be returned to factory default settings and would need to be completely re-setup and calibrated.