Forum Replies Created
-
Posts
-
If I understand the issue, it may be that the pen-up and pen-down positions were set too close to one another (almost the same) rather than either necessarily being too high.
First, is the laptop also running Windows?
Second, you may be able to add AxiDraw support to your copy of RoboPaint 0.95, if it is working otherwise and you have a working AxiDraw configuration file for 0.95 on your other computer. On my Windows machine, the machine configuration files are located at:
robopaint\app-2.0.0\resources\app\node_modules\cncserver\machine_types .Within that folder, you should find files like “watercolorbot.ini” and “axidraw.ini” — you should be able to copy one of these RoboPaint 0.95 machine configuration file to the corresponding folder on your other computer to add AxiDraw support to it.
Towards getting v 2.0/2.1 working, it would be very helpful if you could post a request directly at https://github.com/evil-mad/robopaint/issues — the author of RoboPaint may be able to weigh in, and may have debugging suggestions.
Finally, is there any chance that you could skip robopaint entirely, and use our python-based software or the CLI interface instead? We do have a full-featured python library for AxiDraw that can plot SVG or use XY movement commands. If you need turtle move commands, we could probably add those pretty quickly. There’s more about this here:
https://axidraw.com/doc/py_api/We do not currently offer an auto-feed mechanism for AxiDraw. We have, however, seen quite a few cases where people are using them.
Some are home-built mechanisms — complex and special-purpose. Some others are as simple as a cheap inkjet printer set in front of the AxiDraw, to “print” a blank page before printing each page with the AxiDraw.
More commonly, though, people use existing paper handling tools. Print shops have tools to move paper from point A to point B, and the print shops that are using our machines use standard paper handling tools to put material in front of them.
If it’s DOA, please contact customer support for a replacement. (They should definitely not die immediately.)
Generally, though, the pen-lift servo is the one component that you should expect to wear out over time.
The primary limit to the lifetime of the servo motors is that the tiny DC motors inside them wear out. Once a servo starts buzzing, that means that it’s moving its motor constantly, and will die very soon after. (Buzzing means that the motor is moving constantly.) Heat seems to be a factor, so reducing the stroke or the amount of weight to be lifted can help extend the life. Applications where the servo has to move more weight (including rubber bands, weights, etc) tend to reduce life further. If your pen-lift stage doesn’t glide smoothly up and down, then we should address that, as it’s one of the biggest factors that can give you a reduced servo life time.
One other concern is that the motor may still jitter while the machine is not otherwise in use. We made a change in the most recent version of the EBB control board, adding a MOSFET to control servo power. (This version is distinguished by using a micro-USB connector, rather than a mini-USB connector.) This allows you to turn off servo power, and (by default) does so automatically after 15 minutes. From the age of the machine, I’m guessing that you have the mini-USB connector, not the micro-USB connector. Accordingly, it’s a great idea to unplug the AxiDraw from power when it’s not in use.
I’ve already responded to your separate email on the same topic. But briefly, we do not not sell the pen stages separately, and we do make custom larger sizes, including the size that you’re asking about.
Here is a version that you can try:
https://evilmadscientist.s3.amazonaws.com/scratch/artcon.cOK, great– let us know if you need help with anything else. :)
What platform are you using, and how far did you get through the installation instructions?
Which model of EggBot are you using?
It sounds like you’re saying that (A) was correct, and (B) was not– that is, that this is actually a separate “run time” which is not equal to the setting on the DIP switches.
If I understand what you are saying, there are now a number of separate delay intervals. Let’s give them names so that we can tell them apart:
(A) The post-trigger delay, fixed at 3 seconds. We’ll call this “TIME A” to be clear.
(B) The time delay, set by the DIP switches. We’ll call this “TIME B” to be clear.
(C) A third time delay, called “TIME C”, that is somewhere in the range 0.3 – 0.5 seconds.
(D) A fourth time delay, called “TIME D”, that is 0.2 seconds
(E) A fifth time delay, called “TIME E” that is in the range 0.1 – 0.3 seconds, or perhaps 0.2 – 0.3 seconds.
You have given me several different values for these different time delays. If these values are going to be set in the program only, then you need to pick values for each of these, particularly TIME C and TIME E that still have time ranges.
Let’s see if we have this all together then:
The changes (versus the standard program) that you are asking for are now as follows:
(1) Change PB3 from an input to an output.
(2) Add a time delay (“TIME A”) of 3 seconds after receiving a trigger, without doing anything else.
(3) After that time delay, simultaneously turn on the relay and turn PB3 high. This occurs at “TIME A” after the initial trigger signal.
(4) After some to-be-specified time (“TIME C”), take PB3 low. The time between the initial trigger signal and PB3 going low is “TIME A” + “TIME C”.
(5) At a time of “TIME A” + “TIME B” – “TIME D” from receiving the trigger signal, take PB3 high again. This is an interval “TIME D” before the end of the relay turning off.
(6) At time “TIME A” + “TIME B” (the time delay set by the DIP switches plus three seconds after the initial trigger), turn the relay off.
(7) At time “TIME A” + “TIME B” + “TIME E”, turn PB3 low.
Then, wait for the next trigger.Is this correct?
I’m still not following.
You are saying that “Par Time = Run time”. Okay.
(A) It also sounds like you are saying that “Par Time = Run time = time set by dip switches” — is that correct?
(B) It also sounds like you are saying that “Par Time = Run time = 0.3-0.5 seconds” — is that correct?
I don’t see how it can be both.
I should also reiterate: Making these changes to the code is straightforward — but I cannot do it if you cannot state clearly _exactly_ what is supposed to happen.
Can you write down what exact sequence of events you want? It seems like there are additional things here that you still have not explained.
I’m not sure what the “par” time is. On numbers 3, 6, and 7, I’m really not sure what it is that you’re asking for.
Seriously– you bought a product from someone. They are required to assist you. Ask them for help.
You’ll need to ask jjrobots for help — the EggBot software only supports EggBot.
Which model of EggBot do you have?
