How useful is AVRco

Hi rolf,

für mich wäre als oberstes auf der Wunschliste das TCP Protokoll in Tina (UDP genügt schon bei einem Web-Zugriff leider nicht) und USB wäre auch schön.

Die Verbesserung der Fusebehandlung würde bei einem neuen Projekt einiges an Zeit sparen. Weil ich ausgiebig Klammern verwende, ist die Einhaltung der Grammatik für mich kaum von Bedeutung.

AVRCo ist für mich ein sehr inovatives Produkt. An Grenzen bin ich nur jeweils gestossen, wenn ich eine System Routine anpassen oder erweitern musste. Hier wäre ein echtes Bibliothekshandling perfekt.

Gruss

Thomas

Hallo Tassilo,

ok, das ist machbar.

rolf

@Rene

Also ich muss schon sagen : Respekt Rene !
Du schaffst es immer wieder, mich zum Nachdenken zu bewegen.
Der Grund ist meisst, dass ich von 20 Zeilen die Du schreibst, gerade mal eine verstehe. In diesem Fall die Letzte : Rene.

Dazu fällt mir ein :
Es existiert ein Interesse an der generellen Rezession der Applikation relativ primitiver Methoden komplementär zur Favorisierung adäquater komplexer Algorithmen.
Soll heissen : Warum einfach, wenn´s auch kompliziert geht?
Was willst Du uns sagen ?

Gruss Fritz

1. USB driver for AVR
2. Adding historical trends for digital and analog IO pins to simulator, and beeing able to simulate external hardware by drawing signals in time (please take a look at www.hot.ee/nppcsoftware)
3. Color TFT Support. I know that color needs much processing power, but think about cheap dedicated MEGA just for this task (and offer this hardware board for buying). This board could transparently communicate via SPI or I2C to main board. Current graphics driver could be expanded, and you could support just 1-2 LCD displays and leave it open for adding new displays as you already did with current mono graphics lib.
4. Objects

...
well, you said any idea... ops: :roll:
so here it is...
...

97. Offering enclosures like professional PLCs have. I bet that a lot of people would like to have their little device in a professional box that could be put on a DIN rail rack in cabinet. You could offer Power Supply unit, CPU unit (fixed at M128 or even better with a user selectable processor), Digital (24V, 220V) and Analog isolated I/O cards (0-20mA, 4-20mA, 0-5V, 0-10V...), Counter cards and others. High speed IO cards could be connected directly to CPU bus, and slow IO cards could be just conected to common backbone bus (just power, I2C and SPI). I had to do many jobs with Simatic S7 ($$$) and not with AVR because some people did not like small boxes that I put my AVRs into. Using something like this www.bernic.dk/Catalogue/varelister/m36/m36-index.htm is ok, but a lot of people would prefer ready solution to avoid messing with boxes.

98. Adding CFC as an optional higher layer over pascal. For example, for Siemens S7 PLCs I have many IEC 61131-3 languages to choose from, but I prefer SCL (pascal derivate) on low level and CFC on high level. You can build a block (func or proc) in pascal, and it is represented in CFC as a BOX with inputs at left side and outputs on right side (take a look at attached image). Now you can visually connect inputs and outputs by simply drawing lines, and in online mode you see online values with ability to change them! This is a real productivity boost for bigger projects and simplifies maintenance (one picture is worth a thousand words). More info at www.automation.siemens.com/simatic/industriesoftware/html_76/produkte/software-cfc.htm

99. Adding UML support