simulate in 2.3, this one in 4.0.7

2.3v:

https://www.youtube.com/watch?v=sUTMYV0xE58


4.0.7v:

https://www.youtube.com/watch?v=aX9OEiEk66c




I forgot to say that when i want to compile and i didnīt select the MCU and pins in 2.3v it shows a message to select them (and HEX file is not created), in 4.0.7v it shows a message too, but it creates the HEX file anyway, that hex file doesnīt work because it doenst have MCU and pins (i guess it shouldnīt create HEX file or am i wrong? or is it correct that if you press compile then it creates hex file , but it doesnt work because you didnīt select MCU and paramters in that case we would be wrong and not the Ldmicro, i donīt nknow if i am clear? ).

to Alex

More difficult question with message about TON timer.
1)
In manual.txt we can read about
...
> TURN-ON DELAY Tdon
...
It is possible to manipulate the counter variable elsewhere, for example with a MOV instruction.
...

and about
...
> RESET Trto Citems
...
TON and TOF timers are automatically reset when their input goes false or true, so RES is not required for these timers.
...

I think that these two sentences contradict each other.
I think, that changing the timer value using RES or MOV
is a bad style of LD programming. RES or MOV breaks time interval of TON and you can get uncertain time delay.
I would prefer to make a TON inaccessible to external influences.

2)In simulate.cpp v2.3 there is a code with text to messages
but it is shown when TON 'nameX' used twice as TON 'nameX'.
...
switch(flag) {
case VAR_FLAG_TOF:
if(Variables[i].usedFlags != 0)
return _("TOF: variable cannot be used elsewhere");
break;

case VAR_FLAG_TON:
if(Variables[i].usedFlags != 0)
return _("TON: variable cannot be used elsewhere");
break;

case VAR_FLAG_RTO:
if(Variables[i].usedFlags & ~VAR_FLAG_RES)
return _("RTO: variable can only be used for RES elsewhere");
break;
...

3)v2.3 and v4.x.x generates similar internal code.
v4.x.x not blocks this instructions and saves backward compatibility in this.
But message says you about possible problems.
You get HEX equivalent to v2.3

4)Please send me your Proteus project. I want to test.
I am not inclined to remove this message.

I made a test of 3 intervals of a total 100 seconds, let me explain:

every 90 seconds i took a picture for 3 times(due to that the timer in proteus resets every 100 seconds so i took 3 times a picture in the 90 second)


2.3v :

WITHOUT RESET for timers

interval 1(90 second):
89.9995820

interval 2(90 second):
89.995620

interval 3(90 second):
89.9955420

USING RESET for timers

interval 1(90 second):
89.9995820

interval 2(90 second):
89.995620

interval 3(90 second):
89.9955420



4.0.7v :

WITHOUT RESET for timers

interval 1(90 second):
90.294483

interval 2(90 second):
90.621683

interval 3(90 second):
90.9462

USING RESET for timers

interval 1(90 second):
90.256283

interval 2(90 second):
90.621683

interval 3(90 second):
90.9462

It seems that in 4.0.7v time increases duration in the interval 3 it should be 90 seconds but it is almost 91 seconds (90.9462) in 2.3v it keeps with 0.99 diference (89.99 in all intervals with or without RESET). But this is only simulation, i attacha file for images and ladder.

i got the same error, while generating ansi c for arduino, in my case ldmicro freezes and inputs and outputs for simulation dessapear after getting the error bwolf describes.

i attach image

i mean using the same ladder compiled with its own ldmicro version, each video is 35 sec interval test.

You must measure delay time between raise signal on input and raise signal on output of TON element.

raise front of input ___/-----------\_____
and raise front of output ____/-----\_____

TON and TOF, RTO usually must use for create time delays between the signals.

When you use it to generate a cycle XXX, then you must add one PLC cycle time to calculate a period of cycle XXX.

For example: Tcycle XXX = TON + TON + 1PLC = 50+50+10= 110ms

i saw files attach, good explanation, i guess osciloscope is better than counter timer.

instead of using 1 sec TON in ladder i used 500ms+500ms=1 sec, actually in 4.0.7v time was more stable than 2.3v



----[TON 500.0 ms]---[TON 500.0 ms]----------------( )--

Here is the LDfile.

Yes, I had already found it.
I use another variable now, and it works.

I thought it was a bug this morning but I forgot the OSF after the uart instruction.
Sorry for the late reply.

The attached file is another possibility end this was the program I had in mind.

Could you please attach the hardware schematic?

thanks a lot, wow i googled tachistoscope

My serial HP display is working again and I made a small video of the program above, only I replaced the photocell with a button.


https://www.youtube.com/watch?v=wG_n6ZqwhqM

Yes, only 1 wire + GND is needed, the onboard pic, in this case is programmed as serial display driver and so it's a standalone display and easy to use.

I can program the onboard 16F628a as serial driver or counter or whatever ;) in LDmicro.
This video, I made 2years ago, gives you a better view and the counting is software for video purposes.

The display is obsolete.

https://youtu.be/5w9AKaGBv3c

Building you own? you need to buy such a display (DL2614 or DL2616) if you can find one, they are very obsolete.

The software is written in LDmicro and if you have such a display I will make a schematic and cleanup de software and add some comment in the program for you, but not before you have a display ;)