Sign in to follow this  
Followers 0
lostcontrol

SoMachine

6 posts in this topic

We are having difficulties establishing communications to a TM258LF42DT4L. Our setup is: • A XP-SP3 Virtual Machine with SoMachine V3.1 • The VM has a static IP of 192.168.45.90, the magelis was configured for 192.168.45.11. When I added the device to the gateway, it would not connect or find it • The magelis was ‘pingable’ from the VM, so no networking issues. • We changed the VM to 10.10.209.90, as the default IP for the M258 was 10.10.209.229. We can ping this now, & connect to the Web Server from the Host & VM. • Still no connection from SoMachine to the M258, via the auto discovery or by adding the device manually. • Tried the USB programming port. There is no option in SoMachine to select USB connectivity. The VM recognises it & installs the drive. • We can use the Drivers utility to test the connection to the M258 though. We have not been able to find any other manuals, everything points to that the scan network utility should work. The only thing we can think of is that it is the VM. We are going to try & install on a native OS to see what difference that makes. Can anyone provide any assistance on where we may be going wrong? We are very disappointed that we could not even connect in the first instance...

Share this post


Link to post
Share on other sites
I don't use any of mentioned products but it looks like networking issue. what kind of VM you are using and can you describe network setting of the VM a bit closer? are you bridging network adapter or using NAT etc?

Share this post


Link to post
Share on other sites
VMWare Workstation, adaptor set to Bridged directly to NIC. VM IP set to DHCP, static etc, tried everything. The VM is the only thing we suspect could be the cause, but as everything is pingable & the Web Server is accessible, it should work.

Share this post


Link to post
Share on other sites
Try to Reset the Gateway (note: it is assumed that M258 Controller appears under Virtual Machine's Win XP Device Manager/Modems when using usb connection) Go to Start-->All Programs-->Schneider Electric-->SoMachine Gateway and select Reset Gateway. Next go to SoMachine/controller's Communication Settings and uncheck 'Secure online mode' and set Filter to 'none' from the pull down menu. Click on 'Scan network' button to see the M258. Click on 'Set active path' button to be able to download the program or go online with the controller. If M258 controller appears as 'grayed-out' in the Gateway then make sure that project controller type matches actual TM258* number which you are connecting to. Hope this helps.

Share this post


Link to post
Share on other sites
I had similar issue with my first experience. SoMachine doesn't use Ip adress, web server and ping does. This is why you can't reach the plc with SoMachine. However you need to be in the same subnet of the plc, so if you can ping, this means your Ip setting is correct. Check in Program tab, double clic on ethernet, Ethernet Protocol must be set to Ethernet 2 not IEEE 802.3 - see picture. Mark_ade instruction is good, but you also need to set the controller name. It must match the one you use in your project, to do so, scan the network, then once the controller appear, right clic on controller and select Change device name... You'll be able to assign this controller with the one you use in your project. You need to clic on Set active active path as well. Don't panic, you'll lost communication, it's normal because plc default Ip adress will be changed to the one in your project (set in ethernet tab). If left few screen shot to help If it doesn't work, give us some feedback, you'll try to help.

Share this post


Link to post
Share on other sites
I know this is a year old, but I'm 99% sure you can't program the M258 line with USB. The M258s are part of an agreement with B&R and are re-branded X20 PLCs, none of which can be programmed by USB. Schneider did the same thing when they bought Elau, put USB programming ports on them when they changed the name to PacDrive3 and then never added the ability to use the programming port. Schneider software tends to not use the IP address by default and there should be a setting in SoMachine to use the IP address, which can eliminate many connection issues. Sometimes Windows Firewall gets a little picky when it comes to SNMP, which is how most auto discover stuff works; you may want to check those settings as well in your VM.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0