problem SOMOVE root element is missing

[lapelect]

Somove version 2.8.2.0

So basically i'm just trying to configure my com option in SOMOVE so my rs485 adapter can communicate with the LXM32M

We Just changed computer here and the other computer were working fine. But this computer is on windows 10.

Everytime that i click on the gear for advanced option on the top right corner of the window. the message

root element is missing.

So at first i tried a few different things, i didnt work.

Then i decided to completely uninstall so move and DTM LXM32 library just to make sure.

After restarting computer, i went on schneider website to redownload somove and the dtm.

Unfortunately i still have the same issues.

I would be happy if someone can help

Thanks

Best regards

[lapelect]

my technical representative found this but this does not work for me.

https://www.se.com/ww/en/faqs/FA365159/

[lapelect · Accepted solution]

The only way it would work was by desactivating all the other USB and Port on the PC.

Talk about it with Schneider to finally discover that was a bug in version 2.8.2 of so move. So i downloaded the version before which is 2.7.5. Now it is working flawlessly..

[Fleo]

Hello,

I recently encountered the same problem.
However I use SoMove version 2.6.5.
So I don't think this is a bug in SoMove.

I guess the problem appeared on my computer when I installed EcoStruxure Machine Expert Basic 1.1 Patch 1 which updated the serial Modbus driver to version 14.15.
This new driver created a Windows user account named SE-Account, dedicated to driver management.
To make the driver work properly, I had to remove the Windows autologon. And I'm waiting a little bit before logging in to give the driver time to start.
I don't like this situation but I haven't found any other solution.

Going back to an older version of SoMove you probably also changed the Modbus driver version.

[Kolod]

Try restart NetAccess service.

[Fleo]

Thank you very much Kolod for your tip with NetAccess.

Indeed I already tried to restart this service before you mentioned it... But I couldn't. I thought I had lost admin rights with this service (related to SE-Account).

I tried again after your message and it worked!

So I made several tries and I found that this service (and others) is very long to start after Windows bootup. When the service is in "starting" status, it's not possible to stop it (unless I use a kill command). But when the service reaches the "running" status, I can easily stop it and restart it.

Well, now I'm looking for the cause of abnormal slowness of communication related services. Maybe the domain administrators pushed some changes to my computer, which had an impact on Schneider's services and drivers?