Which is the best GitHub for for GCodeParser?

[tMonation]

So i just want to share you my Setup:

Here is just a picture so you can see in which port i plugged in the diffrent cables.
The Board is an Orion based Board.

The Pin Layout in the Parser looks like this:

It looks like you plugged the Y Motor in Port 2
And X Motor in Port 1.
Im using this Setup since i had problems with mDraw when i chose the other Layout.

The same settings i used in GRemote under the tab Settings.
Im not sure what the -1 on the different int means i just copied the PIN-Layout from another forum Post.

Also when i send the G01 X200 Y200 via Arduino Monitor i get an oë as an OK Message i saw that in GRemote too
GRemote also gave some kind of error in the cmd line

So in Arduino Monitor the OK is oë and in GRemote the OK goes by oÙ maybe there is a problem with the character encoding.

In the Universal GCode sender you dont get an OK at all you just see:

**** Connected to COM13 @ 115200 baud ****

{“gc”:“G01 X200 Y200”}

This could be why i sometimes get Problems when sending more commands because sometimes i send the code and nothing happens…

Is there any way that i can send more than 1 command via the Arduino Monitor?
If there would be an ability to load a file it would be good.

Also is there a command where i can get to X 0 Y 0 in the bottom left corner (view like image)

I also found out for me that if i enter a command from the fish file G02 and G03 arent working G01 is working…
even without the I13.839709 J-13.234108 values on the G02 and G03 commands arent working.
Also i cant get the G90 or G91 commands to work.
Seems like there are only some commands that work and not all the GCode commands.

Edit: So i fixed the strange ok by changing Serial.println(“ok”); to Serial.println(“o”); in the process_string file but still i cant do any absolute movement just G01 commands.
Also i can now send code from GRemote and even Send a file from GRemote with arrow keys working aswell

[charlieb]

Wow! I wonder if the “o\n” makes some strange character in unicode that’s throwing everything off. I’m using Arch Linux and all I see is “ok”. I changed the sources to Serial.print(“ok\n”) but it didn’t make any difference. I’ll try changing it to “o” tonight.

The universal sender’s command table tab shows the G… command but the “done” column never gets a checkmark.

The ardiuno serial monitor is very basic which is nice because it makes no assumptions and requires nothing but it also provides no facilities.

[tMonation]

Yeah i just tried it and had luck
Its pretty cool now that GRemote finally works.
Now i will test the fish file again and give feedback.
If you need any Infos let me know im still 2 hours at work

Edit: Okay the fish file does work however im not able to control the Servo i need to look into maybe a problem in the Parser.

[charlieb]

I’m really interested to hear if the fish works. The circle command (G02/3) is supposed, looking at the code, to go to a location and draw a circle there but I’ve only ever got it to just draw a circle in place.

[tMonation]

Would be awesome to hear if it works for you with the “new” Serial print function.
Ill try to fix my Servo next week on Monday.

[charlieb]

I tried your “o” thing and it didn’t work so I took a look at the GRemote code and it is waiting for “OK” not “ok”. I fixed that in the firmware and now I’m getting through the GRemote startup sequence but I still don’t have a responsive plotter at the end of GRemote’s command sequence.

It would appear that the memory setting codes ($1 X…) cause the plotter to no longer be able to move. If I don’t issue any of those commands then everyone’s happy.

Next, for the universal sender the choice of TinyG is not such as good one. It does allow commands to be sent because the application does think that the tool is initialized but the response (at least in 1.0.9) is expected to be in json format. A simple “OK” is not good enough. You can fake the sender into accepting that the firmware is grbl by sending “Grbl 0.9” instead of “start” at the end of initialization (in the setup function). Then the sender will correctly parse the “OK” or even “ok” that the firmware sends back.

I had to put the sender into single command mode (settings->sender settings->enable single step mode) because the firmware can’t handle multiple gcode commands at the same time.

It’s also become clear to me that my servo is setup wrong because it’s up when its supposed to be down (for the fish) and its still up when it’s supposed to be up. I though Z34 was up but I guess it’s supposed to be down. Yup, it was wrong. I set it to Z34 then removed the white arm from the servo and put it back on so that it was perfectly horizontal with the pen down.

It’s currently and correctly drawing the fish!

[charlieb]

It’s a bit small and perhaps a blunt pencil wasn’t the best choice but it looks pretty damn good to me.

[tMonation]

Looks Great thanks for Sharing your results and new Information with me. Ill try your new results on monday with my setup.

[system]