I'm just thinking like the starter (which I still am at the moment :- D) At the Arduino center, you can read about 3 guides, and you know how to control a driving robot. Steering left and right with pwm, using LED's, checking switches. IMO this IS about the same with the _bert libraries, but not with JALlib.
I think levels in advancement would be great! * For starters you have all those parameters set for you (which off coarse limit you, but I don't think that's the problem for a starter) * Medium levels would have to set their own pragma's, or do the setup of (e.g. PWM with all the timers) * Last we have the standard level, which just includes the standard libraries On 14 jul, 08:12, Joep Suijs <[email protected]> wrote: > Hi Guys, > > I'll be the devil's advocate on this one ;) > > >> Pin count doesn't really matter in my oppinion. > > It does. I have the arduino with an atmega168 and ran out of pins > before my project was completed. I'd go for a 40 pin chip or larger > (smd gives you more pins at the small form factor, which is nice. But > it is less easy to build and repair). --- What I meant by this, was that you can have more pins than a arduino, but still be pin compatible. (just split up the pin headers, and put them somewhere you can access them while having a shield attached. --- > > >> It's more the number > >> of specific pins (like there are 3-6 PWM pins on an atmega168), there > >> are only 2 on a 16F877. > > Now you get close to the most anoyning thing of 'doning the best you > can for a use that does not know what he is doing'. In arduino, all IO > pins seem to be equal. So on a 20 pin board, you can configure 20 pwm > signals. But when you use them, you might notice that they don't all > behave like expected. Depending on the chip, some pin's support pwm > and work fine. But others don't support pwm and will be set either > high or low (depending of the pwm value). > And similar, you might need two pwm's, say for an h-bridge. If you > read the datasheet, you will choose two related one's, so you only > need one timer and limited setup code. But with arduino, you try (!!) > until you have two pins working like you want to. And probably make > less efficient use of you hardware (two timers etc). > > Similar issue's are there for use digital ports in the way that you > are not encouraged to put related pins on the same port etc. > > This kind of issue's made me switch halfway my arduino project: > dismantle the arduino framework, only keeping the required libraries > as includes for c++ and work form there. Much better! (and you regain > some options from C++ that are lost with arduino). > > Or to make a long story short: IMO it is a bad idea to shield the > hardware features from the user. It's like designing a car for drivers > that do not know it is common to use the left front seat. It creates a > lot of issues to be handled and a lot of work while it is not > unreasonable to expect a driver to know which seat to take. --- This knife cuts both sides too :-) For starters it might be easy (but still confusing) that they aren't entirely dependent of the datasheet setup. But hell, use the pins what they're made for!! Again, what I meant with this: if a shield uses a hardware communications port to communicate with a shield attached, and we want it to be compatible with JALuino, it's probably the best to have this done at "the same" hardware port. --- > > >> > I think too that such a board has to be kept really cheap to be > >> > successful. But also an easy programming language ( could be a problem > >> > too with JAL) > > I realy wonder why you state this. What makes Arduino more easy to use > then Jal? > Are this the super-include and function (names) provided?? --- As stated above, you don't have to know all the harder hardware settings, to get started at first. One with just some programming experience in HTML could perfectly build, and program a circuit that blinks the led in all kinds of patterns. That's the power of arduino... But next to that this is also the group that will abandon this piece of hardware sooner than more experienced will! --- I'm sorry if this all sounds like b*llsh*t, it's just my narrow vision at this case :-) Toon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
