New Controller NCMate4 about fluidnc HOT 13 CLOSED

Thank you everyone for your valuable help! I am done with the design for now, I implemented these changes:

• AHCT shift registers included
• Included ESP32 WROOM 32 16GB module directly to board
• Solder pads for driver configuration on the backside
• Added 4 RC Servo outputs (and therefore removed JTAG

I am going to order 5 assembled boards. If somebody has genuine interest in deep testing, I will give one or two away for free, please get in touch with me if you like to get one.

)

Schematic_NCMate-4_2021-12-06.pdf

from fluidnc.

That looks good with a nice mix of features. I don't have time to do a detailed review of the schematic. Just make sure you use the 74AHCT595D (T version) of the I2SO chips for the TTL version.

You should ask follow up questions on Discord. We like to keep the open issue count low.

https://discord.gg/Hnaxr99q

from fluidnc.

74HC595 does not meet specs at VCC = 5V. Vih is 0.7 * VCC = 3.5V, above the ESP32's output voltage. That is why we use AHCT.

from fluidnc.

FluidNC does not currently support ESP32-S.

from fluidnc.

Thank you for the comment for the HCT version, this is a flaw indeed. BUT - in this respect - HCT does not support 3.3V supply, so the 3.3V/5V VCC switch seems a bit odd. Will hook everything to 5V and remove VCC.

Why you think the ESP32S module is not supported? It is the same chip as the WROOM 32. However, I think about soldering a module to the board directly, instead of using a development board.

from fluidnc.

I think you are OK with the ESP32 socket. It looks like you have laid it out correctly. I would suggest using ESP32 DevkitC V4 modules.

The 3.3V/5V Vcc is required for use with Trinamic drivers when the diag pin (StallGuard) connected back to the ESP32. It works fine for me.

from fluidnc.

It is not recommend to mount the ESP32 antenna over the PCB. Most people will hang it over an edge.

Not as good....You can remove the PCB under the antenna. You can remove the copper under the antenna.

The 16M chip is OK with stock FluidNC. It will not use all of the memory. If you custom compile with a custom partition scheme, you can use all of the memory. We may publish a recommended 16M scheme soon. OTA updates would need to be tested. I suspect they would need to be compiled with the same scheme.

I found the JTAG to be marginally useful or productive with a combination of interrupt driven stuff and RTOS tasks .

from fluidnc.

Moving those things to the back side is nice. It is much cleared back there and easy to read.

The FluidNC logo is here. It would be nice if you could include it.

https://github.com/bdring/FluidNC/wiki/FluidNC-Logo

I have been playing with a new external driver only version of the 6 Pack. It uses the 16M chip and includes some stock features as well as a few module sockets.

from fluidnc.

I am aware of the wifi "issue". I have removed all the copper in all layers in this area for now, did not find the space to move it to the edge. The next Version will have it. Also, one is free to solder the module with the connector for the external antenna. But yes, thank you for mentioning.

Of course I will put the Logo!

from fluidnc.

Moving those things to the back side is nice. It is much cleared back there and easy to read.

The FluidNC logo is here. It would be nice if you could include it.

https://github.com/bdring/FluidNC/wiki/FluidNC-Logo

I have been playing with a new external driver only version of the 6 Pack. It uses the 16M chip and includes some stock features as well as a few module sockets.

Do you consider include a TTL serial port? (external LCD..)

from fluidnc.

Got mine

from fluidnc.

Dears,
thank you for your help during developing my first controller. It was a big help, and despite the signal integrity issues mentioned in #245 the controller is working and drives an actual machine just fine. However, I did not want to stop here, and improve my development with some learnings I made in the first prototype. Mainly I want the signal integrity issue to be solved, but also wanted to allow 48V input, a better silk screen and a more compact form factor. I am almost there, but would appreciate just a very quick expert look on how I try to solve the signal integrity (see pictures below):

• All I2S signals are routed shorter, and have a proper ground plane flowing around the whole trace length
• I included a 0-Ohm series resistor at the source (ESP32), which could be replaced later to achieve some basic impedance matching if required

Any comment on this approach and overall over the new controller will be appreciated, thank you!

Some info on the new controller:

• 80x100mm
• Smaller 3.81mm detachable connectors
• 48V (60 in theory) max input voltage
• Full pinmapping on bottom silkscreen
• All configuration with solder jumpers on bottom side

from fluidnc.

The red-side ground island between PWM and IN_1 is probably unnecessary, since the blue-side ground return path is mostly unbroken.

from fluidnc.