Has anyone got GCode parser to work with Orion board?


#1

Hi,does anyone maybe have a GCode parser or the correct pinout that works with the Orion board?The one on Github page seems to be for an older board.


#2

Hello Bleky,

these Threads might help:

It works perfectly fine for me now. Using this Layout:

int Y_STEP_PIN = 10;
int Y_DIR_PIN = 11;
int Y_ENABLE_PIN = -1;
int Y_MIN_PIN = 12;
int Y_MAX_PIN = 13;

int X_STEP_PIN = 9;
int X_DIR_PIN = 3;
int X_ENABLE_PIN = -1;
int X_MIN_PIN = 17;
int X_MAX_PIN = 16;

int Z_STEP_PIN = 15;
int Z_DIR_PIN = -1;
int Z_ENABLE_PIN = -1;
int Z_MIN_PIN = -1;
int Z_MAX_PIN = -1;
int Z_ENABLE_SERVO = 1;


#3

Thanks,will report back later if everything works how it should.


#4

Ok,the plotter is able to do the GRemote’s init sequence,it does all the limit switches pressing and releasing but it does not want to move using the up and down keys and so,what could be wrong?
@tec_support could you help?I used the pinout that you shown in the previous topic


#5

The moving, pressing and slowly releasing the two limit switches is part of the firmware init sequence. It’s not triggered by GRemote except for the fact that when you tell GRemote to open the port it causes the mainboard to reboot and repeat the init sequence.

I’ve seen with GRemote that the act of programming the position memory (the $1,2,3,4 command iirc), which Gremote does automatically and can’t be prevented, causes the board to no longer be able to respond to any commands. Not everyone has that problem and I haven’t investigated it enough yet to understand why this is the case but just be aware that the init sequence running means that main board is OK; it does not mean that GRemote is communicating with the board correctly.


#6

Did you use all the PINs you have in your Parser in your GRemote Settings?


#7

Ok,it seems to all work now,plotter moves using the keys,will try drawing something using GRemote now.


#8

I wasn’t aware that GRemote does anything with the pins. I do wonder if the fact that I’m using Ax pins instead of just the numbers causes the firmware memory commands to fail. Honestly though I’m not going back to GRemote and I don’t need the memory commands for what I’m doing so it’s pretty low on my todo list.


#9

Would be possible if it works without the Ax pins. Its really strange but maybe thats the solution. I just wanted to make sure everything works correctly with GRemote ill use python to communicate with the plotter anyway since i need the plotter for something else than drawing.


#10

I have a qustion,which kind of wire connection way of this code, use for the latest of assemble way?


#11