Yes, it works fine with the Lowrider.
1 Like
I wonder if anyone has the same issue like me.
Using SKR Pro 1.2 and tft35 as recommended.
The PP adds notes in the code that should display and you could resume afterwards.
Like: power on router, remove touchplate…
The pause functions do work fine, but the messages don’t display. A bit annoying as I always seem to forgot why it paused:)
I found a post about this on github, where someone mentions this only works on simple lcd’s and not on tft’s.
So, anyone using this feature successfully?
Ok, so the M0 message isn’t showing anything on my tft35. When I manually add M117 before the M0 command I obviously get a brief echo of that message.
Wonder if this is a bug or something that needs to be activated in the V1 tft bin files.
@Flyfisher604 are you aware of this? Is there some kind of fix, if not how could we add a M117 before each M0 command?
I assume you are using the touch interface and not Marlin? I think this has to do with minimal firmware support for the Big tree tech TFT, but @vicious1 should know.
1 Like
Add it to the starting and tool change gcode in your CAM program.
1 Like
correct, I only use touch, as I removed the serial cable to increase airflow in the TFT box but also since I prepared for RRF on SKR (but to busy to continue that for now).
well that´s been set up by the PP in Fusion 360, so that´s why I asked @Flyfisher604 if we could add it as on optional setting in the PP.
In the meanwhile I found this ancient topic. So it´s not my specific setup. But there seems to be no followup on this matter.
@Olivier, I’m not sure if something may have changed in the firmware but I can confirm the messages were being displayed. I’m running firmware that is a couple years old though, so I can’t comment on what is happening now.
Can anyone with newer firmware comment on what they see when the messages are to be displayed?
1 Like
ok, don´t update then! 
on my V1 FW update do get something like this (would have to take picture, have stolen it from the other post)
I recently upgraded to the Jackpot board (GRBL). I have mostly been using vcarve, but would really like to use Fusion 360 more since I use it for CAD. I was able to get @Flyfisher604 PP to work with my SKR (Marlin) board in the past. I started looking for GRBL post processors and stumbled upon a post that this PP also works for GRBL. Great! Except when I post processed, it did not add my touch plate probing. When I dig into the PP code, I found this:
// Is Grbl?
if (fw == eFirmware.GRBL) {
writeComment(eComment.Important, " >>> WARNING: No probing implemented for GRBL");
}
Why is probing not implemented in GRBL? Can I comment the lines in the code out so it is enabled. I just want it to add the G38 line and then G92 Z0.5 with pauses to attach and remove the probe. The fusion PP is pretty complicated for a hack like me, so I don’t want to do anything that will break something. Any issues with this?
@staffordj when coding the PP I had no access to a controller that used GRBL. I relied on what I could determine online and what others confirmed worked.
Implementing probing in GRBL appeared to be deferent then Marlin. As I didn’t know the answer I left it out. G92 in some GRBL implementations was marked as deprecated and it seemed the G38 needed to be a G38.2 or maybe a G38.3. Bottom line is I didn’t know and I had no test platform to determine what was correct. Remember this was 3 years ago, Jackpot didn’t exist.
If the correct GCode sequence can be determined then I can look at adding this functionality. But there may be a delay as my PP development environment needs to be refreshed (not needed in several years) and I’m currently working on other projects. That said, if the correct GCode sequence can be determined then it can be added.
2 Likes
Note, by default the PP uses a G28 to probe. This is Marlin specific. By setting probe4_UseHomeZ to false in the configuration it will use a G38.3 which should work (a G38.2 may be safer though, but that’s not in the code).
It won’t do any probing though if it is in GRBL mode so you will need to comment out the if.
I haven’t tested any of this. If this works let me know and we can work to make the code correct and put out a new release.
2 Likes
Assuming you are just probing at the beginning of the job, you can author your probing as start code and have the PP automatically insert the code.
1 Like
Edited: I had the wrong gcode
I had forgotten that you can use a file for start and end code. I will give that a try. @Flyfisher604 if you get back to this, here is the start code I have been using. My system is a MPCNC primo using a 0.5mm touch plate to set z height.
G21
G90
G94
G92 X0 Y0
M0 (MSG Attach probe)
G38.2 Z-80 F200 P0.5 ( probe down set thickness )
G1 Z10 F900
M0 (MSG Remove probe)
I am looking for beta testers for an updated F360 post processor that better supports GRBL/FluidNC/Jackpot. Changes are primarily related to start up, probing and ending GCode. Still need to review tool changes.
If you are interested and are using GRBL then reply here and I will reach out and provide access to the beta post processor.
1 Like
Hi. Very interested. I’ve just started with the jackpot board after a struggle with Klipper. I generally draw in fusion or Vcarve
I’m at the point where I have a workflow and I can make “Cartesian “ items but I’m also very interested to use that 6th driver on the Jackpot for a rotary axis. I like Fusion but I think I’ll have to use Vcarve for wrapping.
I would love to test it
@MarkC and @staffordj, it will likely be next week before I pull a Beta together.
Please comment on if you are currently using my F360 post processor, are you hand editing the GCode currently to get it to work with the jackpot board or using the file insert ability, and any additional functionality you think would be useful.
1 Like
I am using your post processor with start and end code files inserted by the post processor. The start and end code is similar to the code in my post above.
Thank you, Don for contributing the post processor and for your plan to improve it.
I have the Same answer; I use start and end files.
Maybe not relevant to your plan but FYI
I’m close to a solution for easy substitution of a rotary axis in place of X. I don’t need to unplug anything. Ryan’s latest config file had pins and values for the 6th motor driver, just commented out.
So I commented out the two drivers for X and uncommented the 6th driver. I renamed it X instead of A. I saved this as “rotaryconfig”.
All I need to do is switch the config file and restart and I can flip from xyz work to AYZ rotary . I had to reduce the max speed to prevent the motor losing steps. Next increased the steps/mm to get a full revolution when I call for 360 degrees on X. Checked it through 100 revolutions.
Next I want to set up a probe for the rotational zero position.
I would prefer to use fusion for CAM either way but I think there’s a paywall to use wrapping or 4 axis. I also have Vcarve as a backup.
I will post more details when I get it all working smoothly.
1 Like
@MarkC and @staffordj can you reply and attach any files you are inserting in the GCode to override header, footer, tool change, or probing functions.
Having these will allow be to see if the pp should be generating different GCode by default for GRBL.
Thanks in advance.