LitePlacer.com forums

Danal, Juha made a bug release and had a link to it a few posts back. Here it is again. It doesn't have the tab switching fix, but that isn't a common failure (especially if you aren't switching tabs much). You could make a new build off of my branch. Steve http://www.liteplacer.com/Downloads/LitePl...

I thought I would put a few things out here and get some feedback. The biggie is that for the up camera the GetClosestCircle does not think that the center is where the cross hairs are. My new needle offset algorithms take this into account, but I have implemented an up camera place feature and the ...

We have not had a PictureBox related crash since my last fix. I am changing the program a lot and have created a few other crashes, but those are directly traceable to me. It feels like the PictureBox crashes are fixed.

I think we are talking about three different things. At this point I was talking about a fully manual operation. Picking up a part that I know what it is, but the machine doesn't. Moving the part to the camera, making adjustments, setting them to be used by place here, moving to the spot and placing...

It seemed like the last crash was happening at tab switches. During tab switching the camera ImageBox is set to new PictureBoxes. I decided to add the ImageBox setter to the region protected by the _locker lock. It has been pushed to the PictureBoxCrashFix branch. https://github.com/sgraves/LitePlac...

Some notes on what we have found. First, the cameras are not secure in their body. The cable flexing can change where the camera is looking. We have 3-D printed a bracket to hold the cable securely and prevent it from moving. Second, the Up Camera position on the setup camera tab minus the Needle Of...

We are finding that the parts in the tape do not align precisely. This misalignment (particularly when there is a rotation) causes the part to be misplaced. Ultimately I would like to have the part aligned over the up camera during automatic placement. Presently, I would be happy to be able to do it...

Juha,
I already assumed as much. I figured you would check in occasionally, but would "vacate" according to plan. I expect you to largely forget about us for now. That is if we are one of your sources of stress. And seeing some of the posts, I expect that we are.

Steve

Still no crashes due to sharing violations, but we have had a new one. Tracking this one down... It results in the same red cross. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Argument...

Ok, I am seeing the problem. The CurrentX and CurrentY values are set from the Tiny G status message (sr), as shown below (the setCurrX function sets CurrentX). So the G0 command is issued and before it actually moves another CNC move is made. That move sees that it is very close to the "curren...