Forum Replies Created
-
Posts
-
(1a) Thank you for the typo correction.
(1b) It means that moves shorter than 3 ms may not be reliable. Keep your moves at least 3 ms long.(2) You say “But in most cases the axidraw “crack” and don’t execute the command correctly.” I’m not sure what you’re saying — if something is breaking, please contact us via e-mail and we can work with you on the repair. If the EBB is not executing a command correctly, please let me know exactly what command you are executing, and in which way the behavior was not as expected.
The EBB firmware gives an upper limit for how fast it can generate steps. That is not the same thing as saying that the machine can physically move at the maximum step rate that the firmware can produce. The maximum physical movement speed (as in steps per second) depends on the mechanics of the machine, the resolution selected with the EM command, and how fast or gently you have accelerated.
I would suggest trying logging out and back in — that has resolved permissions issues of this sort in the past.
You might try logging out and logging back in.
Great!
The error indicates (though not very clearly) that the document has “screen” units (pixels), rather than physical units for the size of the document. Start with a document in Inkscape (for example a letter or A4 template), and use File > Import to bring your SVG in.
That’s a possible part of a solution. It is not, on its own, enough to solve the problem entirely.
That’s one of the things that you need to do when you open the box. :)
Glad to hear that you’ve got it up and running!
Please contact technical support; we can send you a white paper that works through the math in detail.
The resolution for any device with discrete subdivisions is always given along the native axes of resolution. For example, if you have a monitor with dimensions X by Y pixels and R pixels per mm, that value R will always be the resolution as measured along the X or Y axis of the monitor.
For the AxiDraw (V2 and newer), the native axes, accessed through the SM command, are at directions (X+Y) and (X-Y). The resolution is measured along *those* axes. So, if you set up with 1/16 microsteps (
EM,1,1) and perform a move along the native axes ofSM,1000,0,2870, you’ll end up with a movement 1 inch long andSM,1000,1130,0will give you a 1 cm movement. This is the resolution described in the user guide, and you should be able to check and verify it with direct commands. No calibration is needed– it should be correct.If you use the XM command, pay attention to what it actually does. From the documentation,
XM,duration,AxisStepsA,AxisStepsBis an alias to
SM,duration,AxisStepsA + AxisStepsB, AxisStepsA - AxisStepsB.So,
XM,5000,1130,0is an alias toSM,5000,1130,1130. The total distance travelled by the carriage is 1130 steps each, along the native axes of the machine. You should expect the distance travelled to be sqrt(2) * 1 cm.Which color display are you using, and how much voltage and current are you applying to each of the different segment types?
Can you please say what you mean by “skew” in this case?
Next, try other sizes– up to the maximum that you can plot on both the laser and AxiDraw. At some point, if they disagree, then you may have a starting place for understanding what the issue is.
The first thing to do is to make sure that each machine is giving the proper size elements. If you draw, for example, a 4-inch (10 cm) square, and print it with each machine, do you get something that is *actually* the right size when you measure with a ruler?
The error appears to indicate (though not very clearly) that the document does not have physical units set. Files that you plot are required to have physical units (typically inches or mm), and trying to plot files constructed for screen display can sometimes give unpredictable results.
I am not certain that this issue is (or is not) directly related to the layers issue.
As a first suggestion, please try plotting one or more layers from the “birthdayCard_outlines.svg” example file, just without pen or paper. You can find that file in our standard example set download, in the “from launch video” folder.
If that file plots correctly, it would suggest that there is an issue specific to something in your file. If it does not, then there’s likely something amiss in your software setup. In either case, it should point the way forwards.
We’ve heard other similar reports from users of Hardy Hershey Text. That’s not a program that we’ve written or one that we support.
Please contact technical support for Hershey Advanced, which is the tool that you probably want to use. :)
