bdring / psoc_grbl

PSoc5 Port of Grbl CNC Controller

PSoC_Grbl

PSoc5 Port of Grbl CNC Controller

This is a port of the amazing Grbl CNC Controller firmware to the Cypress PSoC 5 CPU. Grbl is targeted at the Atmel ATMega328P and ATMega2650 8 bit CPUs. The PSoC 5 is a much more powerful CPU and is a mixed signal processor.

You can read more at this blog post.

psoc_grbl's Issues

LCD problem CY8CKIT-059

To work with the port P3[6:0]
It is necessary to delete on the prototype CY8CKIT-059,capacitor C7 pin3_2

hardware feed hold and cycle start issues

1. with ENABLE_SAFETY_DOOR_INPUT_PIN not defined,
   CONTROL_PIN_INDEX_FEED_HOLD and CONTROL_PIN_INDEX_CYCLE_START defines don't match hardware.

2. control_isr_handler doesn't correctly ifndef the "bit_true(sys_rt_exec_state, **)" statements.

error build release

In the compilation mode, debugging all is well no errors
When you try to compile a project in Release
There were 28 errors
Read this link, solved the problem
(https://community.cypress.com/docs/DOC-12152)

display doesn't update when sys.suspend is true

don't know if this is also grbl behavior ...

enter feedhold with '!' or feedhold signal.

add this to end of protocol.c protocol_exec_rt_suspend()

if (exec_lcd_status) {
lcd_report_realtime();
exec_lcd_status = false;
}

Stepper drives continuously

Hi

I'm running this PSoC_Grbl repository on a CY8KIT-059 and I'm having some issues. I have a TB6600 driver and a nema 23 hooked up with X_step on pin 2.0 and X_dir on pin 2.0, running cnc.js or chilipeppr with a proven g-code file (fusion 360 grbl post processor), running the g-code the stepper moves at a constant speed continually.. it does not stop or change directions. I have tried numerous grbl settings to no avail.

Additionally, both mentioned g-code senders have issue with the position reported by PSoC_Grbl. Chilipeppr displays XYZ position NaN whilst cnc.js stays at 0. Which g-code senders are proven to work? Is there an issue with my setup? How do I get it running correctly?

Also, occasionally upon soft resetting PSoC_Grbl the alarm state is triggered. I don't know why.