|
LDmicro Forum - release file |
|||
|
|
|
(you are viewing a thread; or go back to list of threads)
release file (by Chris)
This is the exe with combined languages.
btw. translation for the follow words are missing. "&Languages" "English" "German" "Spanish" "French" "Italian" "Portugal" "Turkish" What features do you want further. My plan is to implement it, if i like it and release the file/s prior to remove/replace a lot of code.
(no subject) (by Samukelo Shezi)
Copy paste please, if you can. And, SPI support. If you have time, there has been a lot of requests for the PIC18F backend support as well. Thank you to you, and of course, Jonathan.
(no subject) (by Chris)
Thanks for the suggestion, the Pic18F target seems reasonable. Please suggest some MCUīs.
For copy and paste, if itīs enought to copy one item or one rung then itīs possible to implement without problems, or you refer only to copy and pasting a string inside the dialogs ? SPI support and direct lcd support as other possibility come with annother branch and this break up some conventions and as such are not directly compatible. I have written a backdoor to access the HW, actually it works only on 1bit or 16bit and is unpublished. When changing the backdoor itīs possible to access byte variables too. Tell me if this is enought for you to use the JW spi module of the pic cpu.
(no subject) (by Samukelo Shezi)
How about the PIC18F4520 for starters. Let's first see your work on it,
and we'll take it from there. It wouldn't hurt, I guess, to have copy/paste both on the rungs, as well as on the dialogs. As for SPI, I am not sure what "JW" SPI is, but why don't you lay it on and let us play with it?
(no subject) (by Chris)
For the pic18 i have selected the PIC18F1220/1320 as controller for the implementation. Then this tree pic18 uC.
"JW" was a typo, sorry it should be "HW".On my developement copy i have a backdoor for pic register manipulation. If the variables are named __123__ then bit 3 of file register 15 is accessed as bit variable or file register 123+124 is accessed as word variable. Currently it works only on bit and word variables, but the interface need to be expanded for byte access too. As example to use the HW SPI one must move the output byte to the variable __0x13__ and when bit __0x98__ is set the variable __0x13__ can be moved back in order to read out the result. Actually, because itīs made as word access and not byte access, the result must be cleaned from the additional byte, using mul 256 and div 256.
(no subject) (by Samukelo Shezi)
Thanks. I look forward to seeing your work.
(no subject) (by Chris)
I want reintroduce numerical identifiers as primary id,
still allowing aliases. actually: -----[]----- suggested: ---[]-9999-- or --{ Avalue-test + 32000 }-9999-- but if the name is too long, ---{ #9999 + 32000 }--- instead of the very long identifier. Is this ok, or someone have a better idea. Having global numbers is convenient for modbus and for hw access. Annother possibility is using 32bit interger or floating point on dedicated number range without needing new type of operators.
(no subject) (by David R)
Hi
I wish there was something i could do to help but I can only do the most basic c++ I am vary willing to get 18f targets and make pcb's to test and help bug fix. Regards David
(no subject) (by Chris)
Iīm now near to releas it, but there are significant differences, so i ask if it should be a spinoff/branch
or not of this project. No direct mapping between pin and cpu are hardcoded, this is made on asm file and theoreof only a somewhat cryptic compiler error gives infos about wrong assotiation. Itīs possible to have custom code written in basic that are executed, but if you write mcu specific code here, then the ladder become non portable to other type of cpu. There are required a lot of other files, this is not more one file exe solution, no problem to run it from usb stick. There are several third party product merged into the source, and some donīt have the gpl license. This are outsorced to externals dllīs or executables. The simulator is removed from the source, the code is compiled and executed rung by rung. Each item inside the rung have one unique id and simulation token that update the active/inactive input state of the item. The output format of the vm is changed. The resource usage is more than the previous release, more flash code is wasted.
supported cpuīs (by Chris)
Supportet cpu type for pic as i have changed the bakcend, for avr the list is tiny, but still longer as the actual one on this application.
p16f627a p10f200 p10f202 p10f204 p10f206 p12c508 p12c508a p12c509 p12c509a p12c671 p12c672 p12ce518 p12ce519 p12ce673 p12ce674 p12cr509a p12f508 p12f509 p12f629 p12f635 p12f675 p12f683 p14000 p16c432 p16c433 p16c505 p16c52 p16c54 p16c54a p16c54b p16c54c p16c55 p16c554 p16c554a p16c557 p16c558 p16c558a p16c55a p16c56 p16c56a p16c57 p16c57c p16c58 p16c58a p16c58b p16c5x p16c61 p16c62 p16c620 p16c620a p16c621 p16c621a p16c622 p16c622a p16c62a p16c62b p16c63 p16c63a p16c64 p16c641 p16c642 p16c64a p16c65 p16c65a p16c65b p16c66 p16c661 p16c662 p16c67 p16c70 p16c71 p16c710 p16c711 p16c712 p16c715 p16c716 p16c717 p16c71a p16c72 p16c72a p16c73 p16c73a p16c73b p16c74 p16c745 p16c747 p16c74a p16c74b p16c76 p16c765 p16c77 p16c770 p16c771 p16c773 p16c774 p16c781 p16c782 p16c83 p16c84 p16c85 p16c86 p16c923 p16c924 p16c925 p16c926 p16ce623 p16ce624 p16ce625 p16cr54 p16cr54a p16cr54b p16cr54c p16cr56a p16cr57a p16cr57b p16cr57c p16cr58a p16cr58b p16cr62 p16cr620a p16cr63 p16cr64 p16cr65 p16cr72 p16cr83 p16cr84 p16cxx p16f505 p16f54 p16f57 p16f59 p16f627 p16f627a p16f628 p16f628a p16f630 p16f636 p16f639 p16f648a p16f676 p16f684 p16f685 p16f687 p16f688 p16f689 p16f690 p16f716 p16f72 p16f73 p16f737 p16f74 p16f76 p16f767 p16f77 p16f777 p16f785 p16f818 p16f819 p16f83 p16f84 p16f84a p16f87 p16f870 p16f871 p16f872 p16f873 p16f873a p16f874 p16f874a p16f876 p16f876a p16f877 p16f877a p16f88 p16f913 p16f914 p16f916 p16f917 p16hv540 p16lc74b p17c42 p17c42a p17c43 p17c44 p17c752 p17c756 p17c756a p17c762 p17c766 p17cr42 p17cr43 p17cxx p18c242 p18c252 p18c442 p18c452 p18c601 p18c658 p18c801 p18c858 p18cxx p18cxx2 p18f1220 p18f1320 p18f2220 p18f2320 p18f2331 p18f2410 p18f242 p18f2420 p18f2431 p18f2439 p18f2455 p18f248 p18f2480 p18f2510 p18f2515 p18f252 p18f2520 p18f2525 p18f2539 p18f2550 p18f258 p18f2580 p18f2585 p18f2610 p18f2620 p18f2680 p18f2681 p18f4220 p18f4320 p18f4331 p18f4410 p18f442 p18f4420 p18f4431 p18f4439 p18f4455 p18f448 p18f4480 p18f4510 p18f4515 p18f452 p18f4520 p18f4525 p18f4539 p18f4550 p18f458 p18f4580 p18f4585 p18f4610 p18f4620 p18f4680 p18f4681 p18f6310 p18f6390 p18f6410 p18f6490 p18f64j15 p18f6520 p18f6525 p18f6585 p18f65j10 p18f65j15 p18f6620 p18f6621 p18f6627 p18f6680 p18f66j10 p18f66j15 p18f6720 p18f6722 p18f67j10 p18f8310 p18f8390 p18f8410 p18f8490 p18f84j15 p18f8520 p18f8525 p18f8585 p18f85j10 p18f85j15 p18f8620 p18f8621 p18f8627 p18f8680 p18f86j10 p18f86j15 p18f8720 p18f8722 p18f87j10 sx18
(no subject) (by David R)
Hi, The only reason I would need to upgrade chip from what is all ready in ldmicro is to get more program memory and faster.
I find the large list of processors at the expense of loosing convenience of simulating and compiling the code as well as wasting more valuable program memory not as good as i was hoping! Would you consider reducing the parts and keeping the speed and user friendliness of the current system? Regards David.
(no subject) (by Chris)
The simulation remain, itīs implemented only differently.
The compiling takes longer, but itīs possible to compile it from the application, the pin assigment is more difficult, at the same time it allows incorporating external things like shift register ,i2c expander or spi dac without problems as normal inputs/outputs or variable mapped hardware. The same is with conversion. At example if instead of 1023 max value the adc should be 12.50V (value of 1250) or 25V or 255V or from -10 to +10V itīs simple to do, instead on the actual implementation itīs moor difficult. For the memory increase, unfortunatly i donīt have big sample projects. If you or other can share some files, i could tell the differences and extract the different percentages of resource usage based on type of operation, system overhead and overall speed differences. There are differences how the code is generated and size differences and itīs even possible that the size is less than the actual implementation. For small program, the generated hex file need more flash and ram. If you can share some files and donīt want that the files will be public, send it to [email protected] Regards Chris .
(no subject) (by David R)
Hi Thanks, I have attached A program it is close to being full.
adding 2 more formatted sting's will fail it. Regards David.
(no subject) (by Chris)
Have someone one bigger example with many serial and parallel
circuits inside the rungs.
(no subject) (by David R)
I think this file requires ldmicro_999_rungs
(no subject) (by David R)
This file for anybody interested receives data from the cheep
linear scales
(no subject) (by Sam)
Hi Chirs! When are you planning to release this ?
(no subject) (by Chris)
This week
(no subject) (by moto)
Hi Chirs! When are you to release file ?
I'm expecting
(no subject) (by Ciobanu Rivelino)
Me too !!!
Is Atmega 328 on it ? If not pleaseeee. Is very good for reprograming Arduino Regards
release file (by J R)
Hi Chris! When are you planning to release new version of Ldmicro? I'm expecting for your new version and new features included in this version.
Regards J R
release file (by William S)
Hi Chris,
I understand that you been supporting the PIC/AVR chips but, have been wondering if you will release new version of Ldmicro Propeller chip by Parallax since the PICoPLC program that I currently use doesn't support serial and the person started it isn't supporting the program anymore from what I can tell?
(no subject) (by Magno Medeiros (Brasil))
Hello Chris, I am also one more that awaits its new version of ldmicro, if possible remember to add the function to copy and paste, it certainly make it much easier for users of this software. grateful.
(no subject) (by Ziggy)
If this is to be a Christmas release may I add a request please.
Is it possible to add a high speed counter functionality limited in speed by the chip's own counting speed limit?
(no subject) (by Sam)
hey buddy..! r u lost or what? if you need help, just post in here, we can also give an helping hand.
New version of Ldmicro (by chaminda prasad)
Hi mr Chris!
When are you hope to release new Ldmicro? I'm expecting for your new version . Regards chaminda srilanka
celebrating x'max (by chaminda prasad)
To all the members of this forum Happy New Year and those celebrating Christ's Birthday Merry Christmas.
thanks chaminda srilanka
Post a reply to this comment:
|
|
|