brice
New Member
Posts: 5
|
Post by brice on Apr 28, 2021 3:16:46 GMT -5
Dear forum,
We are encountering a communication error with our model 224 here, and we cannot happen to understand why. It has been happening with several machines. Maybe if someone had a similar experience, you could share with us a bit of your knowledge.
We are communicating the temperature data (7 channels) to a Keyence PLC through the LAN port. Sometimes, when switching the machine on, the initialization of the LAN port (Acquiring address...) fails and the LAN status becomes Module Error. Once it becomes Module Error, whatever the number of times we tried to reinitialize, it always ended in Module Error again. The error seems to disappear after a long time without using temperature monitor, but it may be a coincidence.
Would you have an idea of what the Module Error means, if there is a way to erase it, and if it comes from our LAN environment? Thanks in advance.
|
|
|
|
Post by Lake Shore Jeff M on Apr 28, 2021 7:08:17 GMT -5
The Module Error is set anytime the instrument cannot establish an Ethernet Connection. This can be due to a Ethernet module hardware issue or an improperly configured configuration. We have also seen that the Network Configuration file in the instrument become corrupted resulting in the error being seen.
For the corruption, it normally can be cleared with a power cycle or reset to default values operation, however, sometimes that does not work and the configuration has to be entered manually via the USB or GPIB Interface.
The next time you encounter one of these errors and a power cycle or reset does not clear the issue, do the following:
1. Change the Interface to either the USB or GPIB and connect a PC directly to the instrument
2. Using either our Instrument Communications Utility (USB Connection) or for GPIB, use a National Instruments
adapter and run the NI MAX application to communicate with the instrument.
3. Send the NET? command and send the resulting response to support@lakeshore.com
4. What we have seen is that the last 3 segments of the configuration become corrupted and cause the issue you
are seeing
|
|
brice
New Member
Posts: 5
|
Post by brice on May 6, 2021 1:03:52 GMT -5
Dear Jeff,
Thank you very much for your answer concerning the Module Error. We have sent the NET? command and the result is as shown below. I will also send this to support@lakeshore.com as you recommended, but it is in case it can help someone with the same issue.
0,0,192.168.000.013,255.255.255.000,192.168.000.001,000.000.000.000,000.000.000.000,LSCI-224 , ,LSCI 224 Temp Monitor LSA25ZG
We do have some blanks near the end, but is it what you meant by corrupted? Even a power cycle or a factory reset of the machine does not help in our case.
Thanks for your help.
Brice
|
|
|
|
Post by Lake Shore Jeff M on May 7, 2021 13:53:31 GMT -5
Thank you for sending the NET? query response.
The results of the NET? Command do not show any corruption and since it worked when it was at Toyo Corporation, the only thing that could be happening is that your network requires a unique network identification that is not part of the standard configuration. If this is the case, it can be entered using the NET Command so I suggest you check with your network administrator to see if that is a requirement. After entry, you would see that unique identifier in the location where the spaces appear now.
If it is needed, let me know the details and I can assist with building the correct NET Command
|
|
brice
New Member
Posts: 5
|
Post by brice on May 11, 2021 17:35:18 GMT -5
Dear Jeff,
Thank you for the continuous support. We will try to look into this identifier thing. Do you mean that in the end, we may have to define a preferred domain name and a preferred host name (as this is where the blanks are)?
I would like to add though, that the behavior of this 224 monitor is quite erratic. We are usually able to use it in the same configuration for weeks or months. Then, for maintenance or whatever, when we cycle the power of the whole equipment (224 monitor+PLC) and that we try to initialize again, we have this module error thing. And when it happens once, it becomes impossible to connect the 224 through the LAN port with anything, even a simple computer and NI MAX.
This machine was sent back to Lake Shore once already, but no problem was found, and here after using it a few weeks, the problem happened again. It is quite the enigma. We have 3 other machines working with the same configuration (224 monitor and Keyence PLC, same parameters) and they work well (so far?).
Please feel free to react if you have any idea. All the best,
Brice
|
|
|
|
Post by Lake Shore Jeff M on May 12, 2021 5:55:46 GMT -5
Brice, The Preferred domain is only needed if the network is set up to require that information in order to initialize a connection. Based on whet you are saying, it sounds like there is some other issue. I have also been contacted by our representative for Japan regarding the operation with the Keyence PLC as it seems that their demo 224 has been affected after connecting it to your equipment. I will need to investigate this more as I do not have any suggestions at this time and have no information on the PLC Ethernet Interface. If I find out any additional information, I will post it here and with our representative.
|
|
brice
New Member
Posts: 5
|
Post by brice on May 12, 2021 21:26:51 GMT -5
Dear Jeff,
Thank you for your feedback. We’ll be looking forward to hearing from you if you find out anything.
|
|
brice
New Member
Posts: 5
|
Post by brice on May 13, 2021 17:25:33 GMT -5
A brief update to say that we were able to erase the Module Error with the DFLT command, sent through GPIB. It may be a coincidence, though, so we will try to repeat the process, but would that give you a hint about what the source of the error may be? Once again, we have never succeeded to remove the error through a power cycle or through a keyboard-based factory reset (ESC key for 5 s).
|
|
|
|
Post by Lake Shore Jeff M on May 13, 2021 19:30:25 GMT -5
The DFLT command should do the same thing as the front panel Reset to Default procedure does. This erases all temporary memory and basically clears the NET Configuration which if corrupted causes the Module Error. It may be a coincidence as you said so let me know if it comes back and if either the front panel reset or sending the DFLT command clears it again.
|
|
