i have to admit it, the topic about time in ldmicro was always concerning me because i wanted it to be the more exactly it could, so i thought that making a clock from here:

http://cq.cx/ladder-forum.pl?action=viewthread&parent=3084

was the best way to test it, so i tested it the more it could last with ldmicro 4.X.Xv, it worked for 3 weeks without any problem because there was a balckout in my house :D , but, before the blackout a little number one (literally) showed up (iamge attach) but it was working ok, after the blackout i decided to test it in ldmicro 2.3v, it worked very well during one day, because fortunatly i catched it the moment it reset it self , milliseconds was like the seconds (i donīt know if i explained it very well), and the hours and minutes reseted, then the milliseconds that its speed was like the seconds then turn to milliseconds again, everything was reseted, so even there are some bugs in ldmicro 4.x.xv because it is under fixing, it works pretty well.

i would like to share some bugs (if not, correct me please):

BUG 1:

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

the zone where I/O pins, internal, counters, etc are shown are invisible, they are there but invisible when open a ladder file. (i opened a 4.0.7v ladder with 4.0.9 v)

BUG 2:

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

this bug is described in:

http://cq.cx/ladder-forum.pl?action=viewthread&parent=5651

it shows a message "RAM out of memory".

Important, in this video, this ladder file was in "ANSI C code" format, so when i pressed and I/O (invisible) it shows up a list of pins but is says "falta pata" i think i would be in English "missing pin" the problem i thats when it is in "ANSI C code" it should show up a message like in 2.3v (image attach), that tells me that i canīt add pins because it is in "ANSI C code".

BUG 3:

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

Important, in this video, again i opened a 4.0.7v ladder with 4.0.9v and message describe in "BUG 1" didnīt showed up.

In this video i did te opositte, i opened a 4.0.7v ladder with pic format (16f877A) and then i chosse "ANSI C code", then i compile, finally it shows up a message describe in "BUG 2".

When this message shows up, both timers "T1" and "T2" of the video turns invicible, then i click on "R1" and it turn invicible too, then i canīt click anything, i think it shows up an invicible char of pins, but remember it is now in "ANSI C code"...

i had to shoot it with the task-manager because i couldnīt click on the "x (cancel)" of the invicible char.

i tested it, first of all, thanks for your reply, great progess error message shows up preventing that we canīt choose pin because it is en ansi c. I tested turning from ansi c to pic, and from pic to ansi c.

1)

Here something, in ldmicro 2.3v, when i select a pin (with a microcontroller set), for example pin 33, and then i select ansi c code, that Pin on MCU (pin33) disappears because now it is in ansi c, but, when i select back again the same microncontroller, same pin 33 shows up again, in 4.0.10 pre release,if i do it the same way, my pin 33 is not restored i have to add it again, this could be a little problem when selecting from MCU to ansic c for big ladders, we would need to add again all I/O pins, i think pins should be restored when selecting from ansi c to a the specific pin.

2)

there was a error described here:

http://cq.cx/ladder-forum.pl?action=viewthread&parent=5651

that hex is created any way, it was fix in this release (4.0.9) but it creates *.asm if error anyway.

3)

and last, sincerely not a big deal, but when the error message "Must assign pins for all I/O" (image attach), 2 clicks are needed for closing the message and not one :D

sorry in 1)

last sentence should be like this:

i think pins should be restored when selecting back from ansi c to the specific pic.

Hello Ihor:

pre-release 4.0.10 looks very promising! :-)

But i found some 'funny' behavior:

If you load the 'hello-m328.ld' and choose 'compile' (F5) or 'compile HEX' from the menu, the file is compiled to a HEX-file named 'hello-m328.hex' as expected.
If you then choose 'compile ANSIC' from the menu, the compilation behaves als before with 'compile HEX' but a file 'hello-m328.c' is generated which also contains HEX data.
If you again choose 'compile ANSIC' a 2nd time from the menu, a file 'hello-m328.c' is generated which contains C-source...

Another question: why do you delete the existing 'hello-m328.hex' if one chooses 'compile ANSIC' after ???

Happy testing ;-)

all of that described before happens after compiling hex in menu

version 4.0.7 no effect master control relays in this version, ok in version 2.3

Saludos. Amigos tengo un problema. He bajado versiones de ladder soportado con arduino mega. Hago el programa, lo compilo, lo vinculo al proteus. Todo bien hasta ese momento. Cuando le doy ejecutar el proteus carga el programa pero el diseņo no ejecuta las instrucciones dadas en el programa. PAra ver si era el arduino, lo hice con un pic y tampoco funciona.
Es importante mencionar que en versiones anteriores del ldmicro, como por ejemplo, el 2.3 , el proteus lo carga y el diseņo ejecuta las instrucciones dadas. Sería de gran ayuda tu opinión al respecto. De antemano muchas gracias por la pagina web.