Switching from version 1 to 2
Davide Schiarizza
Everything worked fine.
With the new software I have so many problems.
I'm using an MKS controller with Marlin installed.
with "readerface" the machine moves well on all axes.
With OPENPNP 2.0 I can't even configure it.
Who helps me?
mark maker
Hi Davide,
whatever you do, use Issues & Solutions.
There are basically two options, and you can easily try out both.
- Take your old config and upgrade it to OpenPnP 2.0.
- Start fresh and let Issues & Solutions help you setup the
machine.
About option 1:
This should in most cases just continue to work. All your
settings will be migrated to the new version. Believe me, here has
been a lot of development effort put into making this possible.
After you have asserted that everything works, you can start
exploring new features, by using Issues & Solutions from
there.
- Go to the .openpnp2
directory, backup and then delete everything that is in there:
https://github.com/openpnp/openpnp/wiki/FAQ#where-are-configuration-and-log-files-located
- Copy your .xml files over from the sibling .openpnp directory to the .openpnp2 directory.
- Make sure it was a copy and not a move, so you still have the backup.
- Start OpenPnP, it should now migrate everything.
- Start following Issues & Solutions.
https://github.com/openpnp/openpnp/wiki/Issues-and-Solutions - Whenever you reach a good new state, make sure to do File
/ Save Configuration.
- OpenPnP backs up of all your configuration saves, so you can
always go back.
https://github.com/openpnp/openpnp/wiki/FAQ#how-can-i-go-back-to-an-oldworking-configuration
Pros: it should allow you to continue using your machine
as is. It should even support old, outdated controller firmwares,
as long as you keep things as they were.
Cons: OpenPnP will carefully keep your old settings, and your old manual machine calibration. But manual "hand-eye" calibration is not as good as the new automatic vision and motion based calibration. Old settings are limited to the old feature set, for instance part settings and vision pipelines are based on old methods, that are very much outdated. Much better, easier to use, self-tuning pipelines are available.
About option 2:
- Go to the .openpnp2
directory, backup and then delete everything that is in there:
https://github.com/openpnp/openpnp/wiki/FAQ#where-are-configuration-and-log-files-located
- Start OpenPnP, it will automatically make a fresh configuration.
- Forget everything you knew about how to configure OpenPnP.
- Start following Issues & Solutions instead.
Believe me, in 99% of all cases, it knows better (smart-ass it
is).
https://github.com/openpnp/openpnp/wiki/Issues-and-Solutions - Almost all aspects of setting up and calibrating a machine is
now guided that way. Watch these videos to get an impression,
but be aware that these are already outdated again, and
everything is even better now:
https://youtu.be/md68n_J7uto
https://youtu.be/Pxg6g3KI5_E
- Get used to the new Vision Settings system:
https://youtu.be/W63GbSf5BHk - Learn about the new multi-shot:
https://youtu.be/P-ZudS7QQeE
- Whenever you reach a good new state, make sure to do File
/ Save Configuration.
- OpenPnP backs up of all your configuration saves, so you can
always go back.
https://github.com/openpnp/openpnp/wiki/FAQ#how-can-i-go-back-to-an-oldworking-configuration
Pros: you will get the most modern configuration that way. Much is automatic nowadays. Calibration of your machine will be very thorough, using the latest, best calibration methods. You'll get the new vision settings and pipelines that can easily be adjusted, without even going to the Pipeline Editor:
https://github.com/openpnp/openpnp/wiki/Exposed-Pipeline-Parameters#application-of-the-parameters
Cons: if you have a Smoothieware or TinyG controller, you
will likely be forced to update the firmware. OpenPnP needs some
standard G-code features, that older versions of the firmwares
were missing. Some bugs were fixed too. It needs those things to
work flawlessly, to offer the new advanced motion features and to
discover some things about the controller, so it can automatically
configure OpenPnP for you. It is not difficult to upgrade, but it
will take some time and concentration, to do it right.
https://github.com/openpnp/openpnp/wiki/Motion-Controller-Firmwares
With option 2 you will have to re-import the placements, parts
and packages from your CAD. If that is easy for you, I recommend
doing it that way. You'll get the new stock vision pipelines
automatically.
If it is not easy, you can also copy the parts.xml
and packages.xml over to the
.openpnp2 directory, before
you start OpenPnP. You can then still follow the following guide
here, to get the new pipelines:
https://github.com/openpnp/openpnp/wiki/Computer-Vision#using-new-stock-pipelines
_Mark
Who helps me? --
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/b086eee1-eccf-45b8-98b4-2388c32e0576n%40googlegroups.com.
Davide Necchi
Hi at all,
In some of my projects I have this issue:
I have a dual head machine that share the vacuum pump. Placing some component like big inductor, i need to place the component leaving empty the other head, to prevent falling.
Now I have to manually disable the inductors; place all the other components and then re enabling the inductors and finish the job.
I know that the solution is increase the vacuum pump (or using two pump), but for now I try to find a software solution.
Thanks
Davide
mark maker
Unfortunately, there is no such solution.
--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/8D1AA2D0-5F2D-4127-BA68-A00F7A456969%40hxcore.ol.