Forum Replies Created
-
Posts
-
Yes, it’s an open source project. You can the docs on our documentation wiki, linked from the product page.
@robboz4: We have been running Yosemite since before the public beta, and have not needed to compile or install LXML to fix that error.
Starting with a _fresh_ copy of Inkscape 0.48.5, please check to see if the extensions are working. Try, for example, Extensions > Render > Gear.For Yosemite, you’ll need to install a fresh copy of Inkscape (the latest version is 0.48.5) and manually install the Inkscape Extensions. (More info here: http://wiki.evilmadscientist.com/Installing_software#Mac )
Do not run the EggBot installer; it has not been updated for Yosemite yet, and has a conflict that will cause the LXML error.Check your LEDs to make sure that they are all facing the same direction. It is likely that D13 is backwards.
Once you fix that, check to see which LEDs are lit when D12 is supposed to be on. Check carefully to see if there are any solder joints that are not solid, at *any* of those LEDs that you’ve listed. Also check to be sure that there are not any unintended connections between the LEDs, or (for example) the resistors that lead to them.@tabermudes: This is not a related issue; please start a new thread so that the prior participants are not notified by mail every time that a reply is posted. We are closing this thread to prevent further replies here.
(And before you open that other thread, please check to make sure that the 9V power supply is plugged in and working. Do you still have lights on your board when the USB cable is unplugged?)Can you please answer the other questions as well?
It seems most likely that there is an internal error within the servo motor itself. Please contact customer service and we can send you a replacement.
I’m not certain that I understand exactly what you are saying; we do not have any native spanish speakers on staff.
Let me try to understand. When you first start using the EggBot, the pen keeps a constant distance from the egg. But later, the servo motor slowly increases the distance from the egg. You need to change the endpoints in the software to make it work again.You have tried different servo motors.You have tried a different controller board (EBB).You have tried the latest software.Is this all correct?Some questions:* Which latest software are you using? The original installed version on the EBB is the recommended version (not the latest).* When you adjust the software settings for “pen up” and “pen down” positions, are they the same every time? Does it always turn on with the same settings?* Does the servo position change if you are *not* drawing on an egg?* What power supply are you using? Is it the one that came with the kit?I can’t really guess on the novelty, since that depends a lot on who you are and what you like to do. We hear from quite a few people who have been using theirs regularly for years, but we’d also guess that many of them just live on a lonely shelf somewhere.
The EggBot Pro is faster to set up for different types of objects, and is a little more pleasant to use– both in how it feels overall (solid aluminum is really nice!) and the fact that there is better visibility from the front side. However, there is very little (if any) real performance difference between the two, in terms of what speed and output quality you can expect. Both the Deluxe and Pro have “top of the line” performance.
Awesome– glad to hear you’re up and running. :D
There are a number of things that have to work correctly for programming to work: The software environment, communication speed, USB interface, the cable, and power. If you’d like to try serial communication with the clock, that’s a good first check before trying to program. Make sure that you use a communication speed (in the serial monitor) of 19200 baud. (See here for more detail: http://wiki.evilmadscientist.com/Alpha_Clock_Serial )
Double check that your FTDI connector is oriented the right way. (“Black” side to “Black” side.)Double check soldering connections at the microcontroller, J5, R4, C10. The latter three are *only* used for programming, so everything could be working perfectly fine otherwise, only it can’t be programmed if there’s a problem at one of those points.If you continue to have difficulty, you might consider sending the microcontroller (or the whole clock less digits and case) back to us for an upgrade and for us to double-check that everything is working and it can be programmed.First, begin with the shape that you want to draw (the annulus).
Duplicate the shape, so that you have a copy of it that can be used to draw the two circles.Draw a very thin rectangle that cuts overlaps both the inside of the shape and the outside of the shape. (Look at the picture in the docs; where the thin rectangle is drawn.)Subtract that rectangle from one of your annuli, and apply the hatches to the resulting shape.The Hatches (rough) fill does not automatically work on hollow regions. We have some workarounds documented on our wiki, as well as some other fill methods that work on hollow regions.
In practice, we usually either use the the “tiny cut” method, or the Hatch Fill extension.The best method depends on a couple things: What kind of temperature sensor, and what you want to do with the data. If it’s an analog sensor, you might want to use pin PA5 as an input (pin 35 of the IC), which is not otherwise used.
As far as the software goes, it again depends what you’re trying to do. One easy way would be to put the display routine in place of one of the features that you’re not using, like the 5 letter words, for example.Take a look at how a5editFontChar works.
Inside, it has:byte offset = (3 * (asciiChar – a5_asciiOffset));A byte is the same as a uint8_t, an unsigned 8-bit variable. It can only range between 0 and 255. Noting that a5_asciiOffset is 32, it is the case that if asciiChar is equal to 117, you getoffset = 3*(117 – 32) = 3*85 = 255.For any asciiChar greater than 117 (ascii ‘u’), you’ll run into a problem there.The following lines of code are:a5_FontTable[offset++] = A;a5_FontTable[offset++] = B;a5_FontTable[offset] = C;
So, it should be clear that even that edge case of ‘u’ will not actually work, because it still increases the value of offset, even if it began at “only” 255.
