Open wolfgangr opened 4 months ago
Set $367 to 0 or 1 to claim an aux input for the arc ok signal.
Ok, I'll try that in the next build.
Just busy designing a breakout, I encountered another possible problem:
Is PB8 possible as analog-in? If I undestand the datasheet (STM32F411xC STM32F411xE; "Table 8. STM32F411xC/xE pin definitions" ) correctly, may be it's not? ADC are assigned as follows:
PA0 ... PA7 is ADC1_0 ... ADC1_7
PB0 ... PB1 is ADC1_8 ... ADC1_9
PC0 ... PC5 is ADC1_10 ... ADC1_15
The MX-tool in STM32CubeIDE allow to select PB8 as analog in, and does not raise complaints in code generation. What's the reliable source? And, above all, what's implemented in grbl-HAL right now for STM32F411?
Would it be advisable to route analog in to e.g. PA0 instead? just to be on the safer side of live...
Is PB8 possible as analog-in?
Not according to the datasheet I have (xC variants), but it may work?.
And, above all, what's implemented in grbl-HAL right now for STM32F411?
These inputs (only ADC1 for F411) .
Would it be advisable to route analog in to e.g. PA0 instead?
I think so.
ah, good to know before I klick "order" at JCLPCB.... Is it worth to dig into the code to enable more than one ADC? I've put two analog input circuits on my current pcb draft. Is there any application at all in grbl yet for a second ADC?
Is there any application at all in grbl yet for a second ADC?
Not that I am aware of except that is will be available for M66 and the value can be used in expressions (G-code).
Ok, that's worth a trial. Had some space left on my board, so I kept a second anaolog input circuit there.
I try to build a Plasma cutter with a STM32F411 "blackpill" .
It skd looks like working a bit, but does not really match the expectations from documentation and source code. The pattern is similar to https://github.com/grblHAL/Plugin_plasma/issues/8, but not related to sth like MCP3211 :
I messed around with preprocessor conditionals, but in the end, after configring an analog input, I found that obviously at least some thc functionality is implemented.
Some details:
some blind dry run exercises (not all input is echoed)
Pinout:
upper end of configuration: This is what worries me most - many variables listes in
thc.c
and in https://github.com/grblHAL/Plugin_plasma are missingMy gut feeling tells me that quite some stuff might still be broken... Ho can I pin this down?