Posts by Jeremy RoboDK

    I'm sorry for the late reply.

    I, unfortunately, left RoboDK last November to pursue other projects in the field of robotics.

    I will notify my former colleagues. They should find someone else to take my place here.


    What you can do is pick an offline programming (OLP) software, brand specific or brand agnostic, feed in the data from your path planning SW and let the OLP confirm if the path is feasible from a physical stand point (reach, singularities, joint limits) and generate the actual robot program in a format "understandable" for the controller.

    You will have plenty of other "details" to worry about, you can skip the kinematic and post-processing aspect of it for a cost much lower than the time it would take to develop such tool yourself.
    But obviously, if your time has no "value" (it's a hobby let's say), nothing is impossible and you can create such tool.


    I see, I miss interpreted your need. I'll take another look at it.

    Still the rounding function should be the way I described it.
    It will, indeed, return the zone_mm, but within acceptable values for the robot controller.

    Between 1 and 100 in this case. I also convert it as an INT to remove decimal.


    I just found the problem.

    Someone created a custom post-processor for this project, which is very cool. (The post-processor translate from the simulation (RoboDK Language) to the robot language (.LS in this case))

    But they didn't implement the Rounding section.

    We currently read this:

    def setZoneData(self, zone_mm):
        """Changes the zone data approach (makes the movement more smooth)"""
        self.CNT_VALUE = 'FINE'

    While we should see something like this:

    def setZoneData(self, zone_mm):
        """Changes the zone data approach (makes the movement more smooth)"""
        if zone_mm <= 0:
            self.CNT_VALUE = 'FINE'
            self.CNT_VALUE = str(int(min(100,max(1,zone_mm)))) + ' %'

    Using a custom post-processor is the best way to generate exactly the type of code you are looking for.
    But you need to be careful to no remove feature while adding new ones, which was the case here.

    I will add to Lemster's message:
    What do you want to learn exactly? Robotics and AI is a wide topic, especially theses days where pretty much everything is "robotics".
    And what knowledge do you have in robotics so far? You've been in the manufacturing industry for a few years, very cool. Doing what? What is your general technical background?
    One can learn almost anything, just make sure you properly asses your current knowledge and actual goals.

    Hi there,

    Let see how we can help you with this.
    Can you provide your .rdk file?
    Can you also provide the NC file out of Alphacam? (I think you should find it in your Temp folder just after you press "launch robot integration" from Alphacam (type %temp% in a file explorer window to reach your temp folder automatically).


    Hi guys,

    I'm a bit late to the show, I'm sorry. For those more active on the forum, feel free to tag me in next time.

    First of all, RoboDK can create "FINE" and "CNT" motion.
    From your Curve Follow Project or your Robot Machining project.
    Here's where:

    Are you working with a NC file from a CAM software or the points extracted from either the 3D model or imported from a CAD software?

    In the first case, the point distance will be set by the CAM software. You can change the tolerance there.
    If it's extracted from the 3D model imported in RoboDK, you can change the CAD Import Settings to increase or decrease the number of points. I love to have high number of points at this stage.
    You can do the same with the CAD plugin by changing the "Linear tolerance" parameters.

    Then you can right-click the curve in RoboDK -> "Split curve" -> "Set point spacing" to define the distance between the point of a curve section.

    Another method is to go to "Tools"->"Options"->"Programs" and set a "Minimum distance between point" for your linear motion.

    Hope it helps.


    I'm not Jeremy, but you should probably tag or PM him, so he gets an alert about this. I know he's generally pretty busy.

    Thanks, SkyeFire! Busy I am, fortunately! ^^

    Hi Mike!

    Thanks for the great comment! Our team and I work hard on the content we release!

    I answered your PM, BTW.

    Ok, about the "Change my mind." Let's give it a go.

    Let's get this out the way first.

    I don't have any experience with Robotmaster.
    I know some of their capabilities and features through research and demo, but nothing more than that.

    We are indeed just a group of "industrial robot ppl" who had a problem "Simulating and generating robot programs for multiple brands without having to sell a kidney along the way."
    So we made one...

    ("Made"... "Make" would make more sense as it's a never-ending process/project. One that we are pretty passionate about, to be honest.)
    We created a tool to help you bridge the gap between your idea and a working robot by removing some of the programming pain points.
    But it's still just a tool; it won't do everything for you. It's so flexible that we can cover a lot of use cases, but the user still needs to find the correct parameters for his project.

    We do Stone Milling with other customers, using external axes.
    Have you tried our software?

    Inside RoboDK, you can recreate your station by importing the robot from our library, creating your external axes, etc. (explained with the videos you already know about).

    You can then Sync the robot and the external axis together.

    All of this should be pretty straightforward.

    You mentioned using Mastercam.
    RoboDK has a plugin for MasterCAM that lets you transfer your CAM program directly to RoboDK with just the click of a button.
    So that's one step you won't have to bother about later.

    Where things will get a bit more complicated is when you will have to optimize the path with the external axis.
    It might go well for the first few parts, and you might find the right set of parameters in a few minutes, or you might spend a reasonable amount of time figuring out the right recipe for your setup.
    Once you know about your system, generating new parts is very fast.

    We do not offer on-site support/training, but we provide a call with the purchase of a license.
    You can then purchase paid support bundle if you need our direct help. Otherwise, we provide support via email. (Exactly what I was doing before ending up here.)

    I don't know what to say; try it out; if it's a tool for you, great.
    It's the kind of tool that you might need to think around a bit to use the full potential of, but if you can do so, it's super powerful.
    (Talking as Jeremy, not Jeremy from RoboDK. I work at RoboDK because I love the product, not the other way around. You can do so much with that thing for the price.)

    Anyway, I hope it helps.
    Robotmaster must be a good product; they've been out there for years, and a bunch of people are using it.
    It won't be a wrong choice if you go down that road.
    Have a great day.


    Really, the entire Simulation side of the industry is ripe for some enterprising startup to make a really disruptive entry, with a lower-cost alternative that doesn't have all the legacy baggage of the Big Dogs.

    We are trying man, I can tell you we are trying really hard days in and days out.
    But it's hard.
    Keeping the cost down comes with limitations.
    We can't afford to have a huge team of dev to create all the features we are dreaming of.
    We can't afford to have ppl with good experience with each robot brand as there are so many out there.

    Every penny we make we reinvest in development. No fancy office, almost no overhead. Just a small group of ppl passionate about robotics trying to bring a cost-effective alternative to the field.

    Anyway, going back to work. ^^

    And yes Collin is one of our resellers, a nice and friendly one. But I had to check the name after reading his post because it looked really really shady at first.
    I'm super happy to see that you guys are keeping an eye open for that. We really appreciate it. :love:

    You can try to increase the rounding settings in your Curve Follow Project (CFP) under "Program Events" -> "Set rounding".

    You can also open the generated program by "right-clicking" on it (the white one) and select "show instruction".
    You can then find your "set speed" instructions and modify the acceleration.

    The operation speed can be changed in the CFP and the transition speed in the CFP->Program events.