(you are viewing a thread; or go back to
list of threads)
LDmicro.GitHub news v5.3.0.0 (by Ihor Nehrutsa)
https://github.com/LDmicro/LDmicro/releases/tag/5.3.0.0
== Release 5.3.0.0
* Added Release 5.2.0.a by Jose GILLES
* LdMicro32 release 5.2
http://cq.cx/ladder-forum.pl?a...;parent=8128&tt=1549645797
* LdMicro32 on Github
http://cq.cx/ladder-forum.pl?a...;parent=7956&tt=1548617794
== Release 4.4.4.0
* Fixed: LDmicro closes unexpectedly #144
* Fixed: Compile as Interpretable Byte Code fails with the error:
"Must choose a target microcontroller before compiling" #141
* Fixed: LDmicro compiles sketch for Arduino even if PIC MCU is selected #101
* Fixed: Cannot set a value greater than 0x7FFFFFFF in a variable of 4 bytes. #146
* Fixed: In simulation mode when pressing an input, if not selected pin MCU, then LDmicro is closed. Issue #132
* Fixed: The code generated by "Compile ANSIC" for the SRAND insyruction #133
* Updated: Italian locale. Thanks, Claudio Birello.
* Wiki: UART communication FAQ
https://github.com/LDmicro/LDmicro/wiki/UART-communication-FAQ
* Updated: The UART RECEIVE, UART SEND instructions can receive/send a more
than one-byte length variables. "Number of bytes to transmit:" parameter
must be less or equal to the size of the used variable. Value 1 byte is
compatible with the previous LDmicro version.
The parameter "Wait until all bytes are transmitted:" controls the algorithm
of the transmission: if 1 - all bytes are transmitted in one package,
if 0 - one byte per a PLC cycle. When all bytes are has transmitted,
the output condition is "true" during one PLC cycle. Value 0 is
compatible with the previous LDmicro version.
See: UART communication FAQ part 2
https://github.com/LDmicro/LDmicro/wiki/UART-communication-FAQ-part-2
(no subject) (by Ziggy)
Is LDmicro 4.x.x no longer the way to go?
(no subject) (by Alex)
Oh yeahh
LDmicro.GitHub news v5.3.0.0 (by DanielH)
Hello, Igor!
I'm very happy seeing you again in the LDmicro forum!
Thanks you very much for v.5.3.0.0!
I will test it next days on bare metal PIC16F887.
I haven't buyed the ATmega1280 TQFP yet, to test LDmicro with it, perhaps I will have it in next weeks.
Best regards,
DanielH
(no subject) (by Tom J.)
YEAH BABY!!! Thanks Ihor!
(no subject) (by Tom J.)
What is the maximum number of bytes we can receive/send now? I think this is going to be the ticket to using Nextion with LdMicro.
The new menu structure looks great and efficient too, fantastic!
(no subject) (by Alex)
could you please try it in your Nextion and share if success
(no subject) (by José GILLES)
Thanks Ihor for your integration of ldmicro32-5.2 to your official release 5.3.
I hope it'll be a great version !
I'll report observations, if any, as soon as possible.
LDmicro.GitHub news v5.3.0.0: a bug arises (by DanielH)
@Ihor
I'm fear that a bug arise in v5.3.0.0 (observed by Alex, too).
Insert rung after (using Edit menu or shorcut) copies the following rung after selected and then insert it after the selected rung.
Insert rung before (using Edit menu or shorcut) copies the selected rung and then insert it before the selected rung.
There is no way to insert an EMPTY rung editing an existing program nor creating a new program.
The only "trick" that I can do editing a new program, is to left the first rung empty and then to copy it to a new desired position between other rungs, or after last rung.
Could you kindly amend your new version?
Will be greatly appreciated.
Best regards,
DanielH
(no subject) (by Samukelo Shezi)
Ihor and Jose, you have just displayed a wonderful cooperation. Thank you gentlemen. Please keep it up, and God bless!
(no subject) (by MGP)
Thanks Ihor for the new "black box" version, and the new undocumented pulser and stepper instructions ;)
(no subject) (by Tom J.)
I don't have any problem adding a new rung in a new ladder but it's definitely glitching when adding a rung to a ladder written in earlier versions.
Also USRT RECEIVE says "send" in the popup configuration window instead of "receive", not like it matters.
(no subject) (by Ihor Nehrutsa)
to Tom J.
>>Also USRT RECEIVE says "send" in the popup configuration window instead of "receive", not like it matters.
What you mean, please attach a screenshot.
(no subject) (by Tom J.)
I was close from memory, it says in the UART RECV configuration "Number of bytes to transmit" where It seems like it should say "Number of bytes to receive", and "Wait until all bytes are transmitted" where it seems like it should say "Wait until all bytes are received".
Again not the end of the world.
Warning about external libraries (by José GILLES)
I've started testing new 5.3 version with my external libraries for ARMs, AVRs and PICs.
Beware : It can't work as expected for the time being because of some little mistakes during merging of 4.4 and 5.2 versions.
I know what's wrong and I'll have a look at it with Ihor as soon as possible.
Best regards
José
(no subject) (by Tom J.)
I haven't noticed any real problems as long as I start a new ladder rather than modifying one from a previous version. I'm a hobbyist though so not using it every day. Thank you to both of you for working on this project, LdMicro is an amazing software.
(no subject) (by Wojciech)
Hi guys
Anyone have problem with ADC reads? It doesnt work well or at all.
(no subject) (by Luis)
Hi, I also have the same problem with arduino uno
(no subject) (by Ihor Nehrutsa)
to Tom J.
I renamed 'transmit' to 'receive/send'.
to Wojciech and Luis
Please give more information. Please attach minimal Ld file with an ADC.
(no subject) (by Wojciech)
hi
I used a simple project from manual, general variable as timer delay. I choosed ATmega328. The reading variable doesnt changing.
So i asking whether i am do mistake or is problem with software.
(no subject) (by Alex)
attach ladder
(no subject) (by Wojciech)
Here you are
(no subject) (by Tom J.)
Is there an updated version of v5.3.0.0?
UART SEND and UART RECEIVE are capable of more than one byte now but it reverts to 2 bytes for me. I'm assuming it's user error and not v5.3.0.0's fault but I haven't fiddled with it yet.
INTERLOCK RELAY (by ricardo aguilar)
PERFORM THE INTERLOCK RELAY CIRCUIT FOR ARDUINO UNO
WITH 2 INPUTS AND ONE EXIT
UP TO THE ARDUINO DOES NOT HAVE THE EXPECTED BEHAVIOR
I LEAVE YOU THE CODE
I DO BAD PLEASE
THANK YOU
(no subject) (by ricardo aguilar)
INTERLOCK RELAY
(sin asignatura) (por ricardo aguilar) (by Paulino)
Attached here you have the interlocking relay.
adjunto aquí tienes el rele de enclava miento.
altertive (by aydin)
If the stop button is pressed, it will not start
alternativo (por aydin) (by Paulino)
The operation is Press the XSTAR, the output YLED1 is activated.
Pressing the XSTOP button resets YLED1.
To make it work again you must press XSTAR again.
Do not put the XSTOP closed does nothing use more memory.
as long as the STOP button is activated no matter how much you press the XSTAR it will not work. until the XSTOP is pressed.
Tell me what you want me to do.
Keep in mind to put the resistors on the pushbuttons to ensure that when you do not press the pushbuttons, send 0V
El funcionamiento es Pulsas el XSTAR, Se activa la salida YLED1.
Al pulsar el pulsador de XSTOP resetea YLED1.
Para que vuelva a funcionar debes Presionar otra vez XSTAR.
No pongas el XSTOP cerrado no hace nada usa mas memoria.
siempre que este activo el pulsador STOP por mucho que pulses el XSTAR no funcionara. hasta dejar el XSTOP de oprimir.
dime que quieres que haga.
ten en cuenta de poner a los pulsadores las resistencias par asegurar que cuando no oprimas los pulsadores mande 0V.
(no subject) (by ricardo aguilar)
Thanks aydin and Paulino the explanation, I already have it clear, I will continue practicing
regards
Post a reply to this comment:
|