10-23-2024, 03:01 AM
Hi,
I've been learning RoboDK for the last few weeks and believe the software will prove very useful for my intended application of programming motion control camera moves.
However, I have been struggling mightily to get any kind of helpful response from support over the last 10 days. Initially I was on an trial/educational license so I understand the delays in support at that point- then I purchased the full professional license in the hope that I would then get the support I need, as I am now moving forward with a project where the performance of my Borunte 1820A will be critical.
Even with the professional license and requesting support directly from the software, I'm still not getting any response from RoboDK.
To reiterate what I've said across many emails, I'm taking on a big project and I am begging for the driver and the uncompiled post-processor for the Borunte 1820A (note: this arm is actually mislabeled as 18020A in RoboDK). I understand the current driver only performs joint movements, that's ok for now and I'll be happy to work with the RoboDK team in any way I can to help develop this driver.
Thanks,
Nick
I've been learning RoboDK for the last few weeks and believe the software will prove very useful for my intended application of programming motion control camera moves.
However, I have been struggling mightily to get any kind of helpful response from support over the last 10 days. Initially I was on an trial/educational license so I understand the delays in support at that point- then I purchased the full professional license in the hope that I would then get the support I need, as I am now moving forward with a project where the performance of my Borunte 1820A will be critical.
Even with the professional license and requesting support directly from the software, I'm still not getting any response from RoboDK.
To reiterate what I've said across many emails, I'm taking on a big project and I am begging for the driver and the uncompiled post-processor for the Borunte 1820A (note: this arm is actually mislabeled as 18020A in RoboDK). I understand the current driver only performs joint movements, that's ok for now and I'll be happy to work with the RoboDK team in any way I can to help develop this driver.
Thanks,
Nick