-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to debug THC setup on STM32F4? #9
Comments
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?
The MX-tool in STM32CubeIDE allow to select PB8 as analog in, and does not raise complaints in code generation. Would it be advisable to route analog in to e.g. PA0 instead? |
Not according to the datasheet I have (xC variants), but it may work?.
These inputs (only ADC1 for F411) .
I think so. |
ah, good to know before I klick "order" at JCLPCB.... |
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. |
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 #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?
The text was updated successfully, but these errors were encountered: