Inventables Community Forum

PicSender G-code sender

@JanVanderlinden, @StanPhillips let’s move the PicSender discussion here.

What steps have you tried? Make sure the Arduino/X-controller is connected with the USB cable, select the Com Port, Set the baud rate to 115200, and click open. Pay attention to the messages in the console window. Make sure that no other program has the Com Port opened.

Really need the error text to know how to help with this issue.

2 Likes

Please post a screen shot, too.

1 Like

I will get out to my shop this afternoon and try it again.

So something just popped into my pea brain.
Could my Kaspersky virus protection play a role in my problems?

I’m not familiar with that program, but it is possible, probably not the issue.

Ok, I will attempt to post some pictures along with a brief description what is happening.
The first couple of pictures shows my wiring and hook ups to the laptop.(and yes, I’m proud of my granddaughter’s stickers that she put on the laptop)



This is where I start picsender.

This is where I Click to open the program.

Running $H

Jogging X Y X seems to work ok. (honestly, this is more than I have been able to do before)

Send a file= ok
It runs and after a few seconds it stops.
I cannot cancel, I cannot pause, I cannot close, I cannot restart, I cannot exit.
Nothing works.
I have to pull the USB plug to make the spindle and the dust collector stop running along with the program.

Can you post the first 25 lines of that G-code file here?

Is this what you mean?
G17
G20
G90
G0Z0.5000
G0X0.0000Y0.0000S16000M3
G0 X3.6784 Y1.9322 Z0.2000
G1 Z-0.0175 F10.0
G1 X3.6790 Y1.9335 F80.0
G1 X3.6751 Y1.9282
G1 X3.6704 Y1.9234
G1 X3.6731 Y1.9249
G1 X3.6784 Y1.9322
G1 X3.6855 Y1.9285
G1 X3.6918 Y1.9428
G1 X3.7004 Y1.9677
G1 X3.7394 Y2.0931
G1 X3.7445 Y2.1074
G1 X3.7503 Y2.1199
G1 X3.7576 Y2.1305
G1 X3.7632 Y2.1357
G1 X3.7696 Y2.1395
G1 X3.7769 Y2.1419
G1 X3.7847 Y2.1423
G1 X3.7915 Y2.1409
G1 X3.7829 Y2.1490
G1 X3.7774 Y2.1525
G1 X3.7708 Y2.1555
G1 X3.7654 Y2.1569
G1 X3.7613 Y2.1571
G1 X3.7578 Y2.1563
G1 X3.7542 Y2.1546
G1 X3.7502 Y2.1513

Yes, that’s what I meant, but this is not the file that you were running when you got the error.

ok, so now I, confused.
I thought I ran a V carve file for an acrylic sign.
Sorry, I guess I’ll have to start over.

The error message shown for line #14 is as reported directly from Grbl to PicSender. It is not from PicSender.

Grbl does not like the format of lines like “G2 X1.1625 Y5.500 I0.0000 J0.3375 F60.0”. By relocating all the F60.0s to before the G2 lines on which they occur, Grbl will run the code. This will require editing your VCarve post processor file.

This is the pp I use for VCarve Desktop 8.5 with my SO2. It is for inch mode (G20).

File Name: Grbl 2017_inch.pp

+================================================
+

  • Grbl - Vectric machine output configuration file

+================================================
+

  • History
  • Who When What
  • ======== ========== ===========================
  • EdwardP 11/02/2015 Written from Grbl_mm.pp but
  •                 set G20
    
  • EdwardP 11/02/2015 Commented out arcs as these
  •                 slow GRBL performance appear 
    
  •                 interpolated anyway.
    
  • EdwardP 18/06/2015 Explicitly set absolute mode (G90)
  • Mark 24/11/2015 Updated for interim 0.9 spec.
  •                 Renaming to be machine specific.
    
  •                 Removing M30 from Footer.
    

+*************************************

  • changes 2/10/2017 - J. Champlain
  • www.picengrave.com
  • add back M30
  • add back arcs - separate F command from first arc
  • remove tool change command
    +change extension to txt
  • rename to Grbl 2017_inch
  • add S0 M05 to file end
    +================================================

POST_NAME = “Grbl 2017 (inch) (*.txt)”

FILE_EXTENSION = “txt”

UNITS = “INCHES”

±-----------------------------------------------

  • Line terminating characters
    ±-----------------------------------------------

LINE_ENDING = “[13][10]”

±-----------------------------------------------

  • Block numbering
    ±-----------------------------------------------

LINE_NUMBER_START = 0
LINE_NUMBER_INCREMENT = 10
LINE_NUMBER_MAXIMUM = 999999

+================================================
+

  • Formating for variables

+================================================

VAR LINE_NUMBER = [N|A|N|1.0]
VAR SPINDLE_SPEED = [S|A|S|1.0]
VAR FEED_RATE = [F|C|F|1.1]
VAR X_POSITION = [X|C|X|1.4]
VAR Y_POSITION = [Y|C|Y|1.4]
VAR Z_POSITION = [Z|C|Z|1.4]
VAR ARC_CENTRE_I_INC_POSITION = [I|A|I|1.4]
VAR ARC_CENTRE_J_INC_POSITION = [J|A|J|1.4]
VAR X_HOME_POSITION = [XH|A|X|1.4]
VAR Y_HOME_POSITION = [YH|A|Y|1.4]
VAR Z_HOME_POSITION = [ZH|A|Z|1.4]

+================================================
+

  • Block definitions for toolpath output

+================================================

±--------------------------------------------------

  • Commands output at the start of the file
    ±--------------------------------------------------

begin HEADER
“( Date Created = [DATE] )”
“( Material Width [XLENGTH] inches )”
“( Material Height [YLENGTH] inches )”
“( Material Thickness [ZLENGTH] inches )”
“( Home X/Y = [XY_ORIGIN] )”
“( Z Zero Position = [Z_ORIGIN] )”
+"( Tool Bit = [TOOLS_USED] )"

+“T1”
“G17”
“G20”
“G90”
“G0[ZH]”
“G0[XH][YH][S]M3”

±--------------------------------------------------

  • Commands output for rapid moves
    ±--------------------------------------------------

begin RAPID_MOVE

“G0[X][Y][Z]”

±--------------------------------------------------

  • Commands output for the first feed rate move
    ±--------------------------------------------------

begin FIRST_FEED_MOVE

“G1[X][Y][Z][F]”

±--------------------------------------------------

  • Commands output for feed rate moves
    ±--------------------------------------------------

begin FEED_MOVE

“G1[X][Y][Z]”

±--------------------------------------------------

  • Commands output for the first clockwise arc move
    ±--------------------------------------------------

begin FIRST_CW_ARC_MOVE
“[F]”
“G2[X][Y][I][J]”

±--------------------------------------------------

  • Commands output for clockwise arc move
    ±--------------------------------------------------

begin CW_ARC_MOVE
“G2[X][Y][I][J]”

±--------------------------------------------------

  • Commands output for the first counterclockwise arc move
    ±--------------------------------------------------

begin FIRST_CCW_ARC_MOVE
“[F]”
“G3[X][Y][I][J]”

±--------------------------------------------------

  • Commands output for counterclockwise arc move
    ±--------------------------------------------------

begin CCW_ARC_MOVE
“G3[X][Y][I][J]”

±--------------------------------------------------

  • Commands output at the end of the file
    ±--------------------------------------------------

begin FOOTER

“G0[ZH]”
“G0[XH][YH]”
“S0 M05”
“M30”

Grbl 2017_inch.pp (4.7 KB)

1 Like

My sincere apologize for not knowing which file I used.
I thought it was a file that I ran this past weekend for a V carve.
However, I have customers in tomorrow and need to check out for now.
I will try it again either tomorrow evening or the next day, and pay better attention as to what I’m doing.
In the 4 short months that I’ve been doing this, I have found that most of my problems are due to a lack of knowledge and I really appreciate all your efforts.
John,
You are so far over my head, that I don’t even have a clue as to what you’re talking about.

Sometimes even I don’t have a clue either. :grinning:

Jan, it will become more clear with time, and with the help generously offered by forum members here.

When you are ready we can resume.

John

1 Like

Download the file that John posted a link to above and save it in the following location:

If you installed Vcarve with the defaults it goes here for version 8.5, change the 8.5 to your version # if it is not 8.5. If you don’t have Pro then it might be in “Desktop” instead of “Pro” in the path below.

C:\ProgramData\Vectric\VCarve Pro\V8.5\My_PostP

When you generate your toolpath select “Grbl 2017 (inch) (*.txt)” as the post processor.

Then your G-code toolpath will be saved with the .txt extension.

I’m going to have to take a look at that when time permits.

2 Likes

Thanks Larry, please do. I traced it back over several versions of Grbl. Grbl only seems to balk when sending unparsed gcode lines.
John

1 Like

@JohnChamplain , can you give me some more information about this. I have a test file using G2 and G3 with F words in the line and it works fine here.

Here is a snippet:

G0 X22.9330 Y68.2811
G1 Z-0.1000 F360.0
G3 X175.4342 Y70.2404 I75.6307 J49.2305 F1200.0
G0 Z0.0250
G0 X158.7799 Y37.5849

Oh, sorry.

1 Like

Thanks Larry. Sending you an email with attachments.
This is likely to get lengthy, and I think easier to work out using email off forum. We can summarize results here later.
John

2 Likes

Ok gents,
For the last couple of hours I have been running Picsender with at least 10 different programs (air carves) without so much as a hiccup.
I have no idea what I did wrong yesterday,(not even a clue) ((please remember that I have only been doing this for ~4 months)) but right now (even as I am typing this) it is running perfectly.(little bit of a red face for previous rants)
At this point I think that I will pop for the full version, as its running MUCH better than UGCS ever did…
I really appreciate all of your efforts, and it is vey apparent the I have much to learn.
I look forward to tapping into your expertise and will remain in contact.

4 Likes