Re: Video cam based profile probing
Posted: Tue Dec 03, 2019 3:38 am
Just a small update.
I've been getting chunks of the plugin sorted out and working better. Things done over the last few days of a long holiday weekend :
--Added DXF file export, using 'NetDXF' library. File is currently a AutoCad 2004 format, which imports into VCarve and Lightburn with no issues. Still need to cleanup how data is collected (ie, jumping from one profile to another records the 'jump' between the profiles as a line).
--Added camera selection functionality and ability to start/stop camera.
--Added adjust ability to the 'mask' size/shape and rate of angular change. The mask is what limits the region of interest for finding the edge in the camera view.
--Added an 'auto stop' function so that after a full 'lap' around a profile is completed, the movement and recording stop automatically.
--Added another control method for the line following called 'angle/velocity control'. This method uses PID to try and center over the line, but velocity and travel direction are outside of the PID loop.
Testing is working out OK on my machine. My CNC computer is only able to grab ~15 fps from the camera, but it's still doing an OK job. Once up and running, however it puts a strain on the CPU at ~80% utilization (old core2 duo small form-factor desktop with 2 gig ram and Win7 32bit. I'm guessing this PC is at about the bare minimum.).
Attached are some sample DXF outputs from tracing a scrap of wood with laser-cut edges and shapes. The output curves in the 'compare runs' dxf show results using various PID control values, including runs around the profile with excessive oscillation due to poor turning values. NOTE: I zipped the files due to forum not accepting .dxf format files.
Rob, Keith, Tweakie,
I'm hoping over the next week or so, to do some cleanup work, and to pack the plugin and all support DLLs into a zipfile, and to write a short manual if you are still willing to give it a whirl for testing. Unfortunately, things like the PID values will have to be self determined on your individual machines, but I hope to at least write a simple process to help get you going. I also plan to leave a lot of the info I'm using for de-bugging in the plugin so if something doesn't work right, hopefully we'll be able to figure it out quicker.
regards,
Eric
I've been getting chunks of the plugin sorted out and working better. Things done over the last few days of a long holiday weekend :
--Added DXF file export, using 'NetDXF' library. File is currently a AutoCad 2004 format, which imports into VCarve and Lightburn with no issues. Still need to cleanup how data is collected (ie, jumping from one profile to another records the 'jump' between the profiles as a line).
--Added camera selection functionality and ability to start/stop camera.
--Added adjust ability to the 'mask' size/shape and rate of angular change. The mask is what limits the region of interest for finding the edge in the camera view.
--Added an 'auto stop' function so that after a full 'lap' around a profile is completed, the movement and recording stop automatically.
--Added another control method for the line following called 'angle/velocity control'. This method uses PID to try and center over the line, but velocity and travel direction are outside of the PID loop.
Testing is working out OK on my machine. My CNC computer is only able to grab ~15 fps from the camera, but it's still doing an OK job. Once up and running, however it puts a strain on the CPU at ~80% utilization (old core2 duo small form-factor desktop with 2 gig ram and Win7 32bit. I'm guessing this PC is at about the bare minimum.).
Attached are some sample DXF outputs from tracing a scrap of wood with laser-cut edges and shapes. The output curves in the 'compare runs' dxf show results using various PID control values, including runs around the profile with excessive oscillation due to poor turning values. NOTE: I zipped the files due to forum not accepting .dxf format files.
Rob, Keith, Tweakie,
I'm hoping over the next week or so, to do some cleanup work, and to pack the plugin and all support DLLs into a zipfile, and to write a short manual if you are still willing to give it a whirl for testing. Unfortunately, things like the PID values will have to be self determined on your individual machines, but I hope to at least write a simple process to help get you going. I also plan to leave a lot of the info I'm using for de-bugging in the plugin so if something doesn't work right, hopefully we'll be able to figure it out quicker.
regards,
Eric