Forum Replies Created
-
Posts
-
Sorry for the slow reply here– I’m glad that we were able to help out through e-mail. :)
And, thanks for the tip on the pen– we’ll add it to our list of recommended pen choices!Hi Paul,
Thank you so much for giving that a try, and I am sorry that it was not much better of an experience. It sounds like 0.7.5 is a mixed blessing in terms of interface, and additionally does not fix the main issue. Version 0.7.5 is still “pre-release” and I think that we still have some work to do before we can give it an “official release.”Question: When you cancel a painting, and you say that it “fails to get exactly back to the home position,” does it go home when you press the “Park Home” button, or is it genuinely losing position? (Perhaps obvious, but these kinds of tests can be run without a brush in the machine, so that you’re not wasting paint or paper.)Version 0.7.5 has a new feature that may help us get to the bottom of the responsiveness issue. When you open up RoboPaint, please press Ctrl-Shift-D to open up the dev tools window. There, click on the “console” tab which will log what’s going on behind the scenes. Is there anything different that happens when the interface becomes unrepsonsive?We are aware of — and I am also not happy about — the version number issue. ( https://github.com/evil-mad/robopaint/issues/113 ) Perhaps we could title the app something like “RoboPaint 0.7.5.app” to skirt the issue.If you haven’t yet been able to send a signal or reprogram the clock, it could be the case that there is a physical connection problem.
You might consider trying to run our example code from within Processing. That code is tested and works well, and should help to eliminate a connection problem as the issue.From the docs, you need to send a full 12 bytes of data: “A0HELLO…..” to indicate both the text, and the decimals to display.
The new version of RoboPaint, version 0.7.5 has been posted, and you can give it a try if you like:
The new version of RoboPaint, version 0.7.5 has now been posted. Would you please give it a try?
Well, I’ll be a monkey’s uncle: The Y-direction manual walk in Inkscape totally cannot go backwards towards home!
I have no idea (1) how we missed this or (2) how it managed to survive out there so long without anyone else reporting it first. So (1) I’m very sorry for the error, (2) *thank you* for finding it and (3), we’ll get a fix in place very soon.From what you describe, it sounds like your hardware is actually working, so it could well be a bug in that software– please let me check and see if I can reproduce it here.
Hmm. That’s not good. The LEDs in any given column are all wired together (in parallel) at their anodes (high sides), and then the LEDs in any given row are wired together (in parallel) at their cathodes.
Thus, if a full column were out, I’d suspect the transistor (or demultiplexer chip that drives that transistor). If a partial column is out, I’d normally suspect that there could be (for example) a cut in the circuit traces. But there’s actually no place (or set of places) in the circuit where you could cut the traces and end up with the pattern that you’re seeing.Instead, there’s some kind of other error going on here, and I’ve never seen anything like it. Possible things that could cause this pattern would include:– A large number of LEDs not fully soldered– A large number of LEDs installed backwards. (Test, by pressing the leads of a spare LED across the leads of an LED on the back of the board.)– Programmed to display that pattern.– Short circuits (extra connections), due to stray wiring or over-bent wires.That certainly suggests that it’s a bug in Robopaint, not a hardware or firmware issue. (Is that good news?) We should have that new version of Robopaint for you to try in the next day or two.
OK— great– progress! Please let me know what you find with the cable, and we’ll get you taken care of. :)
Thanks– there are some newer versions, but we would would recommend sticking with the version that it came with for the time being. At some point in the future there will be a real “recommended” update, but for the time being, the original will give the best compatibility with the software.
It sounds like (for whatever reason) the extensions are actually not installed correctly. I do not recall hearing of this problem occurring on Windows before. I’d suggest unplugging the Eggbot from your computer until the computer (on its own) is responding correctly.
The error message that you should get when you try to talk to the Eggbot is “Unable to find an Eggbot…” However,it’s not getting far enough to look for it. Please try re-installing the Eggbot software, using the installer: https://code.google.com/p/eggbotcode/downloads/detail?name=EB_Ext_2_2_2_r3.exe Is that the firmware that came with your WaterColorBot? (If so, what color is the EBB?)
Hi Paul,
I’m sorry to hear about the trouble. I’ll ask the author of Robopaint to check in on this. But, I’m also wondering if there could be a hardware problem at the root. Have you tried using RoboPaint RT or the Inkscape extensions for WaterColorBot? If there’s a hardware problem (an intermittent disconnect), I would expect it to show up there as well.Secondly, we will likely have a new beta release of RoboPaint out in a few days, which might be able to help shed some light on the issue. (Or perhaps, even fix it.)
