Messages

1

Modbus / Re: two modbus TCP devices at a time ?

« on: September 06, 2018, 01:51:46 PM »

Listen, the simple question was answered in my first (simple) answer.
There is no difference between cross-cable and switch connection- if addresses are set correctly.  Both will work identically. I used a cross cable.
And I can't say anything about your PLC. I don't know it and I do not have the time to work into it. Sorry.

Uli

2

Modbus / Re: two modbus TCP devices at a time ?

« on: September 06, 2018, 12:47:53 AM »

Hi,

I am sorry but this has got nothing to do with my posted software here. It is an issue with your PLC.
You have to ask the manufacturer of the PLC for specifics, he should be able to help you.

Uli

3

Modbus / Re: two modbus TCP devices at a time ?

« on: September 04, 2018, 01:38:56 PM »

you can always connect two ethernet interfaces with crossover - provided that you set matching  ip adresses manually.

Uli

4

Feature Requests / Re: Restart Modbus TCP connection

« on: November 15, 2017, 07:17:13 AM »

No, I didn't.
Just looking at the MMI and presented functions does not yield an answer to the question how it works as a complete setup including a necessairy 3rd party hardware module. I do not have a reliable comparison of controller modules and those that are saiid to be proven good, look too expensive for me - at least if I bought  them  just for evaluation purpose.

Uli

5

Feature Requests / Re: Restart Modbus TCP connection

« on: November 14, 2017, 01:59:16 PM »

Craig,

I did not want to start a discussion about the future of ArtSoft. From their standpoint it might look perfectly right to change to Mach4. What they missed is at least offering an attractive upgrade model. They expected their loyal users to buy the software from scratch, pay on top something like double the software value in a motion controller while not keeping all the work spent in the old Mach3 setup. So in total it is more than 4 times of what the users paid for their  Mach3 setup, a lot of work and the risk you always have with the change to a 'totally reworked' software.  This did not work out as you can see in the low penetration of Mach4 in the field.
I don't know the solution for this problem.

Uli

6

Feature Requests / Re: Restart Modbus TCP connection

« on: November 14, 2017, 04:43:42 AM »

Tweakie,

this is exactly the problem. Users love their Mach3. But in the course of time the world around changes and new ideas and meanwhile common technical solutions cannot be realized due to the lack of further development.

And it is not about ME not willing to learn and innovate. If ths was the case, I wouldn'd ask for better coverage of the Modbus TCP  implementation.
There is a difference between linear innovation (evolution) and the need to jump into a completely new field (revolution).
The second one always asks for an evaluation of alternatives with possibly more options or better cost profile.

For now I want to stick with Mach3. I solved the problem of addressing different Modbus TCP devices ( http://www.machsupport.com/forum/index.php/topic,35651.msg244336.html#msg244336) and maybe I'll find a solution for the reconnection problem. We'll see.

Uli

7

Feature Requests / Re: Restart Modbus TCP connection

« on: November 13, 2017, 02:16:25 PM »

Craig,  I bought Mach3 years ago, it does what I need, everything on my machine is perfectly built and running.
If I had the need to re-learn, re-setup, re-configure and re-inverst in software as well as in hardware (no LPT..), I certainly would first check how it compares to available alternatives.
This is not to blame ArtSoft. I am and always was a strong proponent for Mach3. Maybe that's why I am a bit unhappy to see that this era is coming to an end.

Uli

8

Feature Requests / Re: Restart Modbus TCP connection

« on: November 13, 2017, 07:21:52 AM »

Yes, I guess that's true.
It is a pity, looking at all these happy Mach3 users around and such a small percentage of Mach4 (at least in Germany).

Uli

9

Feature Requests / Restart Modbus TCP connection

« on: November 13, 2017, 02:07:37 AM »

The Modbus TCP plugin works fine, if all devices are already up and running when Mach3 is started.
If a Modbus TCP device is powered on fter the start of Mach3, no connection is established. This leads to irregular function, in worst case to a crash (i.e. VFD does not start spindle...)

I suggest to (at least one or all)
 - reconnect to all activated Modbus devices when reset condition is released
 - automated reconnect to all activated Modbus devices if they fall off
 - automated reconnect to all activated Modbus devices in time periods
 - offer a function to initiate a Modbus reconnect by script
 - offer a function to test for established Modbus connections

Thanks
Uli

10

Modbus / Re: Multiple TCp modbus devices

« on: October 03, 2017, 12:19:50 PM »

This is an old thread, but finally there is a solution: http://www.machsupport.com/forum/index.php/topic,35651.0.html
 

Uli