LitePlacer.com forums

sebastian wrote:I now got optical homing and the nozzle tip changer working with OpenPnP.

Really interesting !! I would really like to get some more easy digestible information regarding OpenPnP on LitePlacer..
Did you or someone else collect the information somewhere - maybe even in a "step-by-step" guide, that would be awesome !

How stable does OpenPnP run on LitePlacers TinyG ? any software crashes ?

I have started collecting information at https://github.com/openpnp/openpnp/wiki/LitePlacer. Please feel free to add to it!

Jason

ocmaster wrote:

sebastian wrote:I now got optical homing and the nozzle tip changer working with OpenPnP.

Really interesting !! I would really like to get some more easy digestible information regarding OpenPnP on LitePlacer..
Did you or someone else collect the information somewhere - maybe even in a "step-by-step" guide, that would be awesome !

How stable does OpenPnP run on LitePlacers TinyG ? any software crashes ?

I try to document everything I found out here: https://wiki.apertus.org/index.php/Lite ... es#OpenPnP
Its not a step by step guide but if anything is unclear I am happy to help.

OpenPnP does not run on the TinyG, it just sends commands to the TinyG like the Liteplacer software does.

Just added non-squareness correction to openpnp: https://github.com/openpnp/openpnp/pull/446

Hi,

I'm running my Liteplacer with OpenPNP and it works great.
Only thing I miss is vacuum sense that I had on the modified Liteplacer software and tinyG firmware.

Anyone knows what I need to do to get the vacuum sensor to work with OpenPNP?

Martin

martin123 wrote:Hi,

I'm running my Liteplacer with OpenPNP and it works great.
Only thing I miss is vacuum sense that I had on the modified Liteplacer software and tinyG firmware.

Anyone knows what I need to do to get the vacuum sensor to work with OpenPNP?

Martin

https://github.com/openpnp/openpnp/wiki ... um-Sensing

Found the correct command to send to tinyg to get vacuum reading, $ADC0.

I can read the values the same way the youtube video shows, but it does not stop or give a warning when there is no part on the nozzle.
Looks like the ADC reading is taken before the pick.

No part on nozzle value is around 2600, part on value is 1800

So I set the value for part on to 2000 and part off to 2700. Even with part on set to 1000 nothing happens.
The vacuum pump is turn on and off after every pick, how can I get tinyg to keep this on at all time?

2017-03-24 08:13:12 ReferenceNozzle DEBUG: Nozzle1.pick()
2017-03-24 08:13:12 GcodeDriver DEBUG: sendCommand(M4, 10000)...
2017-03-24 08:13:12 GcodeDriver DEBUG: sendCommand(M4, 10000) => [tinyg [mm] ok>]
2017-03-24 08:13:12 GcodeDriver DEBUG: sendCommand(M8, 10000)...
2017-03-24 08:13:12 GcodeDriver DEBUG: sendCommand(M8, 10000) => [tinyg [mm] ok>]
2017-03-24 08:13:12 GcodeDriver DEBUG: sendCommand(G4 P0.5, 10000)...
2017-03-24 08:13:12 GcodeDriver DEBUG: sendCommand(G4 P0.5, 10000) => [posx:423.599,posy:156.388,posz:-19.100,posa:92.361,feed:164.00,vel:0.00,unit:1,coor:1,dist:0,frmo:1,stat:3, tinyg [mm] ok>]
2017-03-24 08:13:12 GcodeDriver DEBUG: sendCommand($ADC0, 10000)...
2017-03-24 08:13:12 GcodeDriver DEBUG: sendCommand($ADC0, 10000) => [posx:423.599,posy:156.388,posz:-19.100,posa:92.361,feed:164.00,vel:0.00,unit:1,coor:1,dist:0,frmo:1,stat:3, 2553, tinyg [mm] ok>]
2017-03-24 08:13:12 ReferenceActuator DEBUG: H1VAC.read(): 2553
2017-03-24 08:13:12 ReferenceNozzle DEBUG: Nozzle1.moveToSafeZ(0.41000000000000003)
2017-03-24 08:13:12 GcodeDriver DEBUG: sendCommand(G0 Z0.0000 F410, 10000)...
2017-03-24 08:13:12 GcodeDriver DEBUG: sendCommand(G0 Z0.0000 F410, 10000) => [tinyg [mm] ok>]
2017-03-24 08:13:12 GcodeDriver DEBUG: sendCommand(G1 Z0.0000 F164, 10000)...
2017-03-24 08:13:12 GcodeDriver DEBUG: sendCommand(G1 Z0.0000 F164, 10000) => [tinyg [mm] ok>]
2017-03-24 08:13:12 GcodeDriver DEBUG: sendCommand(null, 250)...
2017-03-24 08:13:13 GcodeDriver DEBUG: sendCommand(null, 250) => [posx:423.599,posy:156.388,posz:-19.100,posa:92.361,feed:410.00,vel:0.17,unit:1,coor:1,dist:0,frmo:1,stat:5]
2017-03-24 08:13:13 GcodeDriver DEBUG: sendCommand(null, 250)...
2017-03-24 08:13:13 GcodeDriver DEBUG: sendCommand(null, 250) => []
2017-03-24 08:13:13 GcodeDriver DEBUG: sendCommand(null, 250)...
2017-03-24 08:13:13 GcodeDriver DEBUG: sendCommand(null, 250) => [posx:423.599,posy:156.388,posz:-10.175,posa:92.361,feed:410.00,vel:3000.00,unit:1,coor:1,dist:0,frmo:1,stat:5]
2017-03-24 08:13:13 GcodeDriver DEBUG: sendCommand(null, 250)...
2017-03-24 08:13:13 GcodeDriver DEBUG: sendCommand(null, 250) => [posx:423.599,posy:156.388,posz:-0.014,posa:92.361,feed:410.00,vel:165.64,unit:1,coor:1,dist:0,frmo:1,stat:5, posx:423.599,posy:156.388,posz:0.000,posa:92.361,feed:164.00,vel:0.00,unit:1,coor:1,dist:0,frmo:1,stat:3]

Martin


EDIT: Think I found the problem. Liteplacer vacuum sensor reports a lower value when the part is on the nozzle. Openpnp expects a higher value?

martin123 wrote:
EDIT: Think I found the problem. Liteplacer vacuum sensor reports a lower value when the part is on the nozzle. Openpnp expects a higher value?

Please see the follow up at https://groups.google.com/d/msgid/openp ... rce=footer

We have been working on OpenPnP with the LitePlacer. Once set up, it has a lot of promise!

One thing that seems to be very problematic is that TinyG accepts commands and issues an "ok>' response immediately and then runs the command. OpenPnP expects that commands are complete before getting a response.

When homing, the TinyG sends the "ok>" and then runs through the G28.2 limit switch commands until it has homed.

When we want to add a FIDUCIAL-HOME, it seems to break the whole thing. The fiducial locator will happen before G28.2 is complete. This really throws things off.

I know that you can wait for "stat:3" when issuing a move (with MOVE_TO_COMPLETE_REGEX), but that doesn't seem to happen when OpenPnP issues the HOME_COMMAND command. I think it's only used when the MOVE_TO_COMMAND is issued.

Has anyone used FIDUCIAL-HOME with LitePlacer? I think it's pretty important, actually. The G28.2 doesn't seem to be perfectly consistent, and we notice problems with the nozzle changing (which seems to require perfection).

Has anyone used the POSITION_REPORT_REGEX with LitePlacer (or TinyG)?

Has anyone successfully used the G4 Gcode after G28.2 (or any other Gcode command) to get TinyG to block (or wait until a command is complete)?
"G4 P Dwell Pause for P seconds" (from https://github.com/synthetos/g2/wiki/Gcode-Support)

What about COMMAND_ERROR_REGEX? It didn't seem to catch the error I thought it would/should.

UPDATE: We did get the homing fiducial to work. It turns out that it can ONLY be a white (light) dot inside of a black (dark) area. I assume all fiducials are like that until the (potential) new update comes out with a fiducial pipeline.

Flavor wrote: UPDATE: We did get the homing fiducial to work. It turns out that it can ONLY be a white (light) dot inside of a black (dark) area. I assume all fiducials are like that until the (potential) new update comes out with a fiducial pipeline.

Correct, see: https://wiki.apertus.org/index.php/Lite ... ual_Homing