Forum Replies Created
If this a new AxiDraw, please contact support directly; the servo on a new AxiDraw shouldn’t fail in just a couple of days, so we’ll have some specific follow up questions.
More typically, servo motors last some months or even years, but it’s not unheard of to wear one out in a couple of weeks if you’re pushing it really hard. If it’s only lasting a couple of days, it sounds like something is wrong, or you just got one that failed early for some reason.
You can improve servo life by taking care that the pen slide moves freely, without any friction– which means not over-tightening the pen screw amongst other things, avoiding extra weights or rubber bands, and minimizing the distance between the pen-up and pen-down positions.January 5, 2022 at 4:22 pm in reply to: python: Trouble with connecting via pyserial/FTDIfriend #29713
I don’t think that you need time between individual writes — my example doesn’t have them — but my script has time added for the reset after starting communication, a different word (so that HELLO WORLD isn’t confusable with the word I’m writing) and a “display” delay time after writing the text before the restart.January 5, 2022 at 4:19 pm in reply to: python: Trouble with connecting via pyserial/FTDIfriend #29712
On an M1, I would say (to start with) that any pyserial version less than 3.5 is absolutely, positively unreliable, and I personally would not even try on 2.7. The IDE and virtual environment shouldn’t cause any issues so far as I know off hand.
That you are able to communicate on Processing does very much suggest that this is a software-specific issue.
In Python3, the following works reliably for me:
ser = serial.Serial("/dev/cu.usbserial-FTE55RTK", baudrate=19200)
header = b'\xFF'
command = b'A0'
data = b'ABCDE'
space = b' '
ser.write(header + command + data + space)
January 5, 2022 at 3:00 pm in reply to: python: Trouble with connecting via pyserial/FTDIfriend #29709
If it’s working *sometimes* or partially, then I’d suspect an electronics or reset issue first.
Are things acting stable and reliable otherwise?
If you have auto-reset enabled, you may be resetting the device when you open communication– I don’t see a delay there, so make sure that you’re waiting a moment for reset to complete before trying to send data.
Those fonts are used by Hershey Text.
You can read a little bit about them in the AxiDraw user guide. And yes, they are available to AxiDraw owners.
If you’re an AxiDraw owner, we have AxiDraw Merge, which doesn’t quite work with the process you’re describing, but has different workflows that are more optimized for rendering text with stroke fonts and then plotting. There is also the Hershey Advanced CLI and Hershey Advanced python library, which do not perform mail merge nor operate the plotter, but can be used for batch processing in various ways.
As for the question about converting “standard fonts” into stroke fonts, there isn’t any straightforward way to do that. Outline fonts do not contain any data that represents the “visual centerline” of the font, so there generally has to be some degree of human-generated artistic effort to draw the apparent centerline when creating the stroke font.December 8, 2021 at 9:31 am in reply to: Can I install Inkscape and AxiDraw plugins on my computer? #29645
Inkscape 1.0 and newer does not _ever_ need XQuartz. I would recommend that you remove each version of XQuartz and Inkscape from your computer, and make sure that they are fully removed. Then, and only then, install Inkscape 1.1.1.
If Inkscape 1.1.1 asks you for XQuartz, please show me exactly what the message looks like so that we can try to figure out what’s going wrong.
The error message is unrelated to that in the other issue.
The issue that you’re having is from running an old version of the EggBot software, not updated for macOS 10.15 and newer. Update to the current version, available from here: https://wiki.evilmadscientist.com/Installing_software
We do have a “Process Illustrator SVG” extension, as part of the AxiDraw Utilities, that does specify a recommended export process for the document that includes using the Artboard — which I think may be the part that sets the SVG size.
In any case, the Hatch Fill extension isn’t handling some special case of SVG dimensions or viewbox.
I can reproduce the issue. It appears to be something with the document setup, that Hatch Fill is not handling correctly.
It’s easiest to reproduce by using the “crosshatch” option, as the perpendicular hatches are at different spacing.
If I copy the graphics to a new Inkscape document, Hatch Fill works correctly. If I copy a working object into that document, Hatch Fill has the same issue here.
I’d suggest trying our recommended AI SVG export/import path and see if that resolves it; I’m frankly surprised that Hatch Fill works at all on this documument.
It is possible to some extent by using custom code, and people have done so.
However, there is quite a bit of subtlety to the problem and our best understanding is that we cannot presently add a feature that would work reasonably well in a reasonable variety of cases. (If we did, we would have done so already, of course; it is a very common feature request.) As one starting point, consider that the Z stage cannot (in general) be moved in sync with X and Y for the simple reason that its speed does not (in general) match that of X and Y motion. As another, consider that there isn’t really straightforward graphical method for varying the color of a path within SVG.
Obviously, if you’re working one particular use case, that’s an entirely different matter. It’s a fair bit of work even for a specialized case, and so we don’t generally advertise it as a capability.
Finally, you might be aware that we *are* working towards a future solution for variable pen height. Our efforts on this topic are directed there, instead.
We do have a command line tool available for AxiDraw owners. We do not have a publicly available one.
You can use different pen-down heights for different layers, but the AxiDraw is fundamentally a 2D pen plotter; there is only very limited support for controlling the third axis.
I don’t recall what the current draw is; it’s only a 150 mA regulator. You *could* swap in a larger regulator.