I have just plugged my grbl shield in for the first time, i have downloaded firmware, and have run the json serial port program. Chilipeppr finds my arduino but the status is idel. I have nothing plugged into the board nor have i put the drivers onto the board yet. Do i need everything set before i run chilipeppr?
i have not inserted the motor drivers onto the board yet
You should just be able to send a Gcode job and watch it work even if you don’t have drivers connected. You’ll just see stuff moving in the 3D viewer.
You need to match firmware with workspace at the moment. Grbl 0.9 use the grbl workspace. For grbl 1.1 use jpadie workspace. But note that this is not in final form.
Feel free to fork from either to fix the bugs.
@Justin_Adie the Jpadie workspace, fixes the DRO readout? Have not messed with it much but only thing I noticed when switching to 1.1. Are there other changes that were needed?
Hello @Brandon_Satterfield . Can you rephrase your question? I don’t understand what you are asking nor the context in which you are asking it.
Using GRBL .9 Chilipeppr/GRBL workspace all is well. Switched one of my boards to Sonny’s recent release of 1.1 all worked fine with the exception of the, position read outs coming back in the Axes window as a NaN. Improper term calling them DROs, apologies, coffee is setting in.
the messaging format is different between 0.9x and 1.1x. As is the jogging interface and support for some non-spindle interfaces.
Several other things were broken in Grbl too (e.g. seemingly random faults in auto-levelling, some issues with board import etc) that are fixed in jpadie. these may have also been fixed elsewhere.
i am at grbl 0.9. I am now getting this message “You must connect to your GRBL device using the GRBL buffer algorithm in this workspace. Connecting to any other buffer (default, tinyg, etc) will cause unpredictable behavior”
however i do see the gcode running and my arduino lights flashing etc.
that suggests you have not selected grbl in the sjps widget on the bottom right of the screen. you need to do this before you connect to the port.
@Justin_Adie are there plans to launch your workspace on the hardware fiddle page?
I’d like to create a link on the homepage to justin’s workspace and call it “Grbl 1.1 Workspace” or something.
i have now changed the drop down to grbl, the x,y,z position not changing and still says offline in the GRBL widget.
remember you have to connect to the port AFTER changing the drop down
also can you confirm that you have installed and started SJPS and that the ports show up in your SJPS widget.
i closed all programs and reloaded and it keeps the grbl in the drop down.
it shows the version and my computer name in the widget. There is no port number next to the GRBL in the widget above nor is the any info when you press the settings button in the widget. Also when the $$ is sent the the serial port console for the first time nothing is displayed.
Its working now, i had my baud rate set too high. I just went back to ardunio program for a sanity check and typed $$ in the serial monitor and all the settings came up. The baud rate in the bottom was 9600 not 115200.
Good job Jon B.
@jlauer gimme that thing brother :/). Moving all machines to GRBL.
The jpadie workspace is backwards compatible with grbl 0.9x so the ideal would be for the workspace and widgets to be pulled into the standard grbl variant.
But my workspace still has a logic/story flaw in handling units. When I have a few minutes I will revert all my attempts to harmonise units back to the old conversion routines. It’s deeply annoying but there are some ugly use cases that don’t lead to harmonisation of reporting, display and gcode.