Hi Kurt,

that sounds like a very fun and interesting project. Personally I would be very interested to know exactly which Tamiya kits you're using and where you purchased them. Building an arduino on wheels is also a project, which is on my wish list to try if I find some time. So I would be very interested in your progress and your findings. ... like also what kind of motors and what kind of battery are you using and how much radius of action (of running time) does those that give you?

But on the topic of that missing H-bridge. We don't have this part in Fritzing yet. It probably will be in with the next release. And we'll have a script with which you could easily generate other DIL-package chips.

So at the moment you'll have to wait a little, or you can try to make the part yourself (though that will be a struggle with the current version of the parts editor and missing documentation on the subject).

Thanks for trying out Fritzing. Be sure to watch out for our next release and please describe your project more detailed once this website has its projects section more functional.

best dirk

Ah, very nice! Thanks for sharing that.

And I didn't see any battery in the photo's but I assume you've got so much surface that its easy to 'rubberband' some 9V batteries onto.

And I really would advice you not to kill yourself making that H-bridge Fritzing part. We already have this on our todo for the next release. If you indeed can manage making a working board by placing two 555's next to each other, I think that will be much less work.

Please keep us updated on the production of the board and any other problems that arise from trying this with Fritzing.

Thanks! dirk

Exactly.

The tutorial you refer to was meant for the previous (eclipse) version of Fritzing. (That's why it's in archive and not on the new site). Since then a lot of changes have been made to the image format (now multiple layered svg's instead of png's) and the xml part files.

So you would really have to wait until we've updated this DIL package generator to be compliant with the current version. Until then ... I think your double 555 solution could work for now.

Stay tuned.

Cool work! Can you maybe send us the Fritzing sketch? From looking at the instructable pictures, I guess we could use it as an example to improve our autorouter. (Just send it to info aat fritzing doot org.)

Cheers!

Cool there is a H bridge in the new version ;) im so very happy

im working on it. as soon as i get something usefull i will send it to you. regards.

We've just made some improvements to the autorouter, maybe it goes better with that one? It actually might also help to redo the Fritzing sketch, just to be sure that no bugs have made their way into your file.

And yes, we would be very happy about a Spanish translation! We have a native Spanish speaker in our team, but he could then spend more time on development. It's only a few hours work and Qt has a convenient tranlsation tool. Let us know and we'll set you up!

Hi Kurt.

Thanks for offering to do the Spanish translation. In order to get started, please download a program called "linguist" which is made by the people who make Qt (our development environment). You can either download the whole development environment or you can download a mac or pc copy of linguist from here.

You will also need to download our Spanish translation file. This is an xml-based file that holds all the English-language words and phrases in Fritzing. You can find that here.

Here are some hints for using linguist:

Use the file/open menu item to load fritzing_es.ts. Now what you see down the left side is a list of files. Clicking any file shows, in the top right area, all the items that need to be translated in that file. You can select those items 1-by-1--the one that's currently selected is the one you will be translating, and that's what the text entry area, in the center right, is for.

Note the three tabs on the bottom--"warnings", "source code", "phrases and guesses"--they're all very helpful. "Source code" gives you context of where the text appears in the source code, so you can figure out the intent of the text. "Phrases and guesses" tries to match what you're working on with examples you've already completed--double-clicking an example will put it into the text entry area and save a lot of typing. "Warnings" lets you know about missed punctuation, and the like.

Another really handy shortcut which saves a lot of typing is to use control (command) b--that copies the currently selected untranslated text into the text entry area.

Let us know if you run into any difficulties, and thanks very much for helping out.

Cheers,

• j

All you need for the translation task is the Linguist tool. The complete Qt toolkit is only required if you want to work on the source code itself - in that case it would be C++, yes.

(If you're curious and want to try it out, the easiest is to try the Qt Creator beta, a new IDE especially made for Qt: http://www.qtsoftware.com/developer/qt-creator)

Hi Kurt,

Once you're ready to upload the .ts file, you can go to this issue in our issue tracker and use the "attach file" link to post us the file.

Thanks again for your help.

Cheers,

• j

Posted. fell free to send feedback. regards.

Hi. Any Feedback?

Yeah, another big thank you from me! Especially since you are our first community contributor. From now on find yourself in the About section. :)