I would like to use an Arduino Due board. I have flashed grblHAL onto it. Initially I connected it to UGS, and it is alive and well. But, I would much prefer to use it with gSender. gSender does not see the com port at all. Checked Device Manager, no issues, it sees the board as COM5, Arduino Due. AI tells me this is an issue with the Due not properly identifying itself to gSender.
Any suggestions?
@TReischl Welcome to the group, Ted.
I’ve moved your question to the gSender category. It will get more traction here.
I’ll start off with a question. When you try t o connect with gSender, what version of gSender are you using? You are selecting grblHal to connect, yes?
Thanks for the response. Spent about 4-5 hours trying to figure it out. Finally determined that grblHAL was NOT flashed on the board properly and unfortunately never will be. That is because there is no proper build available on GitHub anymore. Had AI help me on this, very disappointing to say the least. So, the bottom line is that gSender is not seeing the port because there is no grblHAL there to respond to it. Or something like that. . . . looking at a FluidNC board now.
@TReischl Since you have little to lose, I wonder is you could flash the sienci version of Hal onto the Due. I know absolutely nothing about this. It’s just a question.
I assume that nothing here is what you need??
Not possible, the Due is based on an Atmel SAM3X8E processor- the SLB on a STM32F412 which is very different.
However, it is possible to create firmware for the Due via the Web Builder or by compiling from source.
That may or may not be true, being able to build via Web Builder. Web Builder keeps insisting that a “board” must be selected. There is no “board” with an Arduino Due. Now, whether or not that messes things up is beyond my pay grade.
What I do know is that a Mega with grbl has no problem being recognized by UGS and gSender. That is not the case with the Due board. They both “see” the com port the board is on, but they fail to “connect”.
You know what though? You got me thinking, there is a Mega 2560 board listed. I am going to give that a go this morning and see what happens. Off I go. . . .
That did not work. Here is what happens:
Notice it looks like it has connected, has found grblHAL, but it remains “disconnected”. The same thing happens in UGS.
As far as building from scratch? It seems that all the stuff for the Due has been deprecated, files that it needs are not available, etc. Now, that could just be my not understanding GitHub. To the average person, GitHub is well beyond comprehension.
What AI tells me is that there is no “board” required for the Due. AI is not always right. I wonder why the Web Builder lists the SAM3X8E but shows no “board” for it? Or does not allow a blank selection?
@terjeio: Since you maintain Web Builder, what do you suggest? I used it to do the earlier build.
Just for grins, also tried the cmcgrath, no go. Also saw a post about using Ramps Smart, that did not work either.
I could use a bit of education here.
I am no electronics guy by a long shot. It seems to me that the Due is connected to the computer. See? I can actually see the cable, so I know that the Due is directly connected, no intermediaries. UGS and gSender talk to the Due. The Due is not talking back to them, has nothing to do with “boards” to my way of thinking.
For instance, I can hook up a Mega 2560 and that talks to UGS and gSender without being hooked up to anything else.
So, from my viewpoint Web Builder is not building a proper .bin that includes communication with the Due.
I also know that after trying to find all the files to do a scratch build, that is not possible.
I have been working with this issue for over a month, off and on. All over the internet the sages claim that the Due will work with grblHAL. Yea, ok, uh huh.
