Sorry for bumping an old thread but this seems to be the closest issues that is similar to what I am currently seeing.

We are running Desigo Insight V5.1.204 with PXC100-E.D units (firmware version 2.20.241 plus some other slight variations of code)

We are seeing intermittent communication errors with the PXCs, the logs of each are reporting run time errors.

We've been told that the firmware should be fine, although it looks to be quite old based on other threads here.

Any help would be great, thanks very much

------------------------------------------------------------------------------------------
Split from Desigo cc v6 - Facing frequent communication failure to server .

neeno

Sorry for bumping an old thread but this seems to be the closest issues that is similar to what I am currently seeing.

We are running Desigo Insight V5.1.204 with PXC100-E.D units (firmware version 2.20.241 plus some other slight variations of code)

We are seeing intermittent communication errors with the PXCs, the logs of each are reporting run time errors.

We've been told that the firmware should be fine, although it looks to be quite old based on other threads here.

Any help would be great, thanks very much

Hi,

Your hardware and firmware combination doesn't seem right. It's not possible to have V2.20.241 firmware in a PXC100.E.D. The PXC100 started out at V4 from memory.

What logs do you have that report run-time errors? Post them please.

Is the IP network standalone, or are you on a customer's network?

Regards,

Thanks for the quick response. 

That was my thinking too. I've attached a snapshot of two separate devices in Desigo insight ( see the top device is on v5.1 and the bottom is on v2.x - the second doesn't look right I agree) Although hands up I have limited experience in this area.

I work in IT, I'm just working with a third party who supports Desigo Insight v5 for us.

Here's a second screenshot of the logs from one of the devices that was causing us issues

Hi,

Ok, no worries.

For the V2.x device - it may be the case that this is an older type of PX controller. Is this an IP device as well?

What logs do you have that report run-time errors? Post them please.

Is the IP network standalone, or is the system on a managed network? The system will generally be set up to talk to the PX controllers via UDP port 47808.

Regarding the Database Revision that you highlighted, this shows the number of times that the PX has been imported into the system (i.e. after software changes).

Regards,

Right that's an IP device too. It's a managed network and we are only seeing issues on these specific devices

Port 47808 is open but we are just seeing intermittent drops in connection on some of the Siemens devices. 

I've added a second screenshot above for the run time errors we saw on the device itself

Thanks again

Hi,

Are the comms problems recent? i.e has the system been running for a while, then issues have appeared?

MS03 - this relates to comms between the PX and one of the Management Stations (i.e. the Desigo PC).

Regarding the error log:

It looks like the PX is stopping and starting regularly, i.e. the entries at 18:47:39. Then the IP link comes back up.

Is the log from the V2.x or V5.1 PX?

Do you know if the PX controller is continually rebooting itself? 

Regards,

It's long term intermittent issue that was around before I joined the company.

The log above is from the V2 device.

Regarding the controller rebooting itself, it's possible but I've yet to see any specific logs from it yet.

Do you know if there is a non-disruptive way to request logs from the controller itself?

Hi,

If the controller is rebooting itself, then it stops controlling the plant it's connected to. Once the controller starts back up, the plant will be back under control. The client should be able to advise you if this is the case.

How often does the V2.x FW PX drop offline and show the entries similar to 18:47:39? Is it random, or all day every day? What about the V5.1 FW PX?

The screen shot from Desigo showing the log file - this data is being read directly from the PX.

Regards,

It happens once every few months and it stops production

On the V5 device- that's a separate site. Although we did see a similar issue a few months ago at that location and I believe that some work was performed on the controller there and we have not seen a repeat of the issue. Although, going by the intermittent nature of the issue I'm unsure that was a fix. We had asked but the details of the fix but it has not been shared 

I've read in various places that it's recommended to upgrade to Desigo Insight V6 or migrate the solution to Desigo CC v3 to ensure a more stable solution. I'm guessing that implies that there are known bugs with Desigo Insight V5, but I can't find anything documented online.

Other than the cost associated with an upgrade / migration from a Desigo Insight V5 solution, do you know if there are any other known stability issues or well documented reasons to move to Insight V6 or Desigo CC?