Twido problem

Hi

I have a problem with a Twido PLC. There is a machine which makes tin-plate profiles with holes on given coordinates. On HMI can add/choose a recipe with coordinates. My problem is that the press is not working anymore after pressing a few holes in some recipe cases. The number of pressed holes depend of recipe. With some recipes working well. There is a bit (%M23) which can be set when the coordinate became zero (because I use %MD[%MW200] as koordinate where is %MW200 is my "pointer" which incerements with 2 after pressing) and its negate is condition to pressing. My doubt is that this bit is set to 1 before the coordinate became zero, because there is a counter which counts pressed wholes and this bit reset this counter. When I have 12 coordinates this resets after 9th hole and don't want to press anymore. Cutting is working well. The M23% should be reset when encoder counts the length. Looks like this bit set to one before it should be set and after "get stucked". Is it possible? In my application software is not. I can't connect to plc because the machine is 2000 km from me

1) look for a duplicate output instruction on that bit that may be setting the bit before its intended time

2) it may be possible that the counter counting pressed holes is "double counting" and reaching its preset early

3) Are you range checking %MW200 before using it indirectly to verify its not "pointing" into a memory area that it shouldn't be?

4) (I'm not familiar with Twido's memory layout but this could be a problem) Can %M23 be part of a larger memory address, like a bit in %MW1, or a bit in %MD0, that if written to could be "stepping" on %M23?

I'm betting on #2

(Welcome to the forum)

jstolaruk said:

1) look for a duplicate output instruction on that bit that may be setting the bit before its intended time

2) it may be possible that the counter counting pressed holes is "double counting" and reaching its preset early

3) Are you range checking %MW200 before using it indirectly to verify its not "pointing" into a memory area that it shouldn't be?

4) (I'm not familiar with Twido's memory layout but this could be a problem) Can %M23 be part of a larger memory address, like a bit in %MW1, or a bit in %MD0, that if written to could be "stepping" on %M23?

I'm betting on #2

(Welcome to the forum)

Click to expand...

Thanks for the reply


I don't think that counter counting double because this not reaching the number of holes but reset before, and one of the reset condition is %M23 (others not possible to reset it in this case). I'll put some recipes with results which we tried.
For instance recepie 1:
MD0=3000 ( length )
MD2=270
MD4=540
MD6=810
MD8=1080
MD10=1350
MD12=1620
MD14=1890
MD16=2160
MD18=2430
MD20=2700
MD22=2970
MD24=0

Error: Press doesn't work after 9th hole anymore. The hole counter is reset after nine to zero

Other recepie:

Recepie 2
MD0=3000 (length)
MD2=233
MD4=466
MD6=699
MD8=932
MD10=1165
MD12=1398
MD14=1631
MD16=1864
MD18=2097
MD20=2333
MD22=2563
MD24=2796
MD26=2980
MD28=0

Error: Press is not working after fifth hole. If the last two coordinates is deleted (MD24=MD26=0) machine works perfectly. My problem is that my app software "doesn't know" at the time of stopping about last two coordinate. It looks only the actual coordinate, and it knows that all holes pressed when the coordinate became zero

Recepie 3

MD0=3000 ( length )
MD2=250
MD4=500
MD6=750
MD8=1000
MD10=1250
MD12=1500
MD14=1750
MD16=2000
MD18=2250
MD20=2500
MD22=2750
MD24=0

There is no error !!!!!!

There is no error on UV profiles (hole 400mm from the begining, 400mm before the end and in the middle) on different lengths (2600mm,3000,3250,3500….)

All good but the details are in the code.

jstolaruk said:

All good but the details are in the code.

Click to expand...

Here is my app with readme

The biggest problem with Twido is the name. What were they thinking?
Sorry, couldn't resist.

Thanks for your help. I sent an e-mail about my problem to Schneider, maybe they can help me