You can use pretty much anything to communicate with Grbl — the issue is that 1.1 uses different responses than Grbl 0.9 and before, so communication / control programs have to be updated to accept that.
Forgive me if I’m being super obvious, but in addition to updating to CM4.09 did you also reflash your board with Grbl 1.1, or is it still running the old Grbl 0.9? If so, please disregard, if not check here:
Ok, so it seems that I did flash and need to undo it.
For what it’s worth, I don’t recall seeing that long post with all the warnings, and being so used to the frequent “click here to update” habit, I assumed it would just be another update. Yes, I am responsible for my gear and knowing what I’m getting into and should read the fine print. I’m a novice and will learn from this. Maybe a clearer warning on the “beta” status of products, and if they are optional or not.
I do appreciate the hard work from the team on chasing problems.
Flashing Grbl 1.1 and installing Carbide Motion 4.09 are two different processes, but both need to completed in unison to have it all work. Carbide Motion is the software on your PC/Mac and Grbl is the software on your controller card. Carbide Motion 3 works with Grbl 0.9, Carbide Motion 4 onwards works with Grbl 1.1. Following the link I posted above will guide you through the whole process.
Also as Will stated you can go back to CM3 Grbl 0.9 if need be, I’ve done it several times now. Just a very little bit trickier than going forward to 1.1 and CM4.