Posts made by timothyz

@timothyz
Ok, well, I just found the answer:
A list of the UART ports are here https://teamgloomy.github.io/board_txt_stm32.html#uart-useable-pins---stm32h7-based-boards
Board.txt Configurables Applicable to STM32 | RepRapFirmware for LP...
Details of each item that can be configured in Board.txt and which build they are applicable to
However in 3.5 and below we only support 2 UART connections. 1 for a WiFi module and 1 for a screen or other device
In 3.6 this has been increased to 3. 1 for WiFi and 2 for other devices
Looks like PB6 and PB7 are available on the EXP headers

Hi,
I am having issues with the AUX 2 serial not loading right with board.txt with an octopus pro. Here is my baord.txt (with 3.5.3)

board.txt:
//Config for BTT Octopus Pro v1.0 F429 Version
serial.aux.rxTxPins = { PA_10, PA_9 }
serial.aux2.rxTxPins = { PD_6, PD_5 }

Here is where the error is in config,g:
M575 P1 S1 B57600 //This works fine, using for CNC pendant, works great actually.
M575 P2 S7 C"RS485" B9600 // Error in console: Error in start-up file macro line 49: in file macro line 49: M575: parameter 'P' too high

Any hints on what could be the issue, I searched here and the Team Gloomy Discord and could not find anything wrong with my config.

@Dennis_kim HF020 Pulse Driver Speed Motion Controller

It's an external board, but it is the best solution to make it act like a spindle, could be controlled with a digital output/heater/fan output. I believe @dc42 said that this was potentially a feature to be added in 3.5, but I think it might not be ready in time (as well as feed hold, which is also useful in places where you have a spindle).

@T3P3Tony @dc42 I have been trying to figure out the best way to make M260 also be able to be used to send and receive bytes over UART to enable expanding spindle control capabilities. I think there should be a separate parameter set that would tell it that it is going to use a uart channel instead of an i2c channel, and then would it be best to use B for both?

@OwenD I didn't know you could declare an array that way! It won't work if I do it as one line, but this is perfect. I must have missed this in the documentation.

Thanks again.
I will make a new post once I have created something useful.

Hi,
I am trying to implement additional tool management capabilities for a CNC router and I am curious how long the new arrays can be? I am trying and I can't seem to declare an array that is longer than 10 or so values. Is this a limitation of the gcode parser max line length? Is there any way to multi-line this?

Thanks,
Tim

I don't know if I could be any more excited to see this post! Excellent work, will be super beneficial to the community using Duet/RRF controls on CNC machines. I was actually starting to develop some integrations for tool management in DWC but I am curious to see how you integrated it on your system. Regardless, blown away by the polish and the thought that went into this and I hope you get plenty of interest and win the most innovative machine award.

Thanks for sharing and I hope you get the attention you deserve, and I am excited to see stuff like this being done with RRF!

@jay_s_uk It's so close to being capable I can taste it, maybe to start, we could allow M118 to optionally send data instead of pure strings. Though, I really don't grasp the deeper functionality of M118 so I'm not really sure. It may be best to change M260, but dc42 always seems to know the inner details and how to make things work.

@dc42
Just some food for your thought, another open source project has implemented RS485 communication to spindles in a CNC controller called the CNC xPro v5. RRF is definitely better developed overall, and it could be very powerful to port that feature. I am guessing your daughter board would be using a MAX485 style uart to RS485? I have one of those modules and could test if you were to implement it.

This is a board I have that I am planning on hooking up to a spare UART: UART to RS485 Board

The CNC xPRO V5 has a list of spindles that they have already integrated and you would be able to use those for references in your implementation (src/spindles folder). Obviously an RRF implementation would allow for the interface of way more than VFDs, and I think if done right could make it a very capable tool for more industrial hardware.

@avdoverflow I think the proper solution is to make a change to the interface to allow the commands to be buffered such that any commands in the buffer that are non motion commands could be executed on the fly/mid move? dc42 will need to confirm the possibility of this. I am very excited to see move segmentation added, does this mean that it will be possible to track the distance to go until the end of a move in DWC? If so that makes it one of the last fundamental features of a fully formed cnc controller.

@dc42 Glad we caught it before the stable release, thanks man! Excellent work as always

@dc42 It shows the CNC view in DWC, I can try sending an M450 to confirm.

I also have no M451 in my config, and there is an M453.

Is there any other prerequisite to read this style gcode?

@timothyz

Tom's gcode looks the same as mine, starts off with a G0 or G1, then on the following lines has the individual X, Y or both X and Y on one line. Reprap firmware seems to be ignoring all lines without the G1 or G0 preceding it. See below:

G90
G21
G0X145.682Y79.693Z12.700
G1Z-1.270F203.2
Y91.765F508.0
X146.122
Y79.693
X145.682
X144.094Y78.105
Y93.352

Now, even in CNC mode this is not getting parsed properly, @dc42 Would you be able to take a look at this, or should I put it this in as an issue on github? I can confirm this is not parsed on both 3.3 and 3.4RC2.

Thanks,
Tim

I think this is isolated to the specific software we used, other programs have been just fine that put in normal G-Code commands the beginning of every line.

Everything about my machine works, I was just seeing if carbide create got better results. The path looks good but the gcode it pukes out doesn't look great to reprap firmware.

Again, everything works when the gcode is normal but with gcode missing the command (G1) it ignores the line even in cnc mode.

It may be that the code generated is missing even more traits required for rrf to read it. Not sure.

I will copy and paste some test gcode a little later

@tomartig

I am having the exact same issue with similar gcode on firmware version 3.3. It only does the z commands and no xy commands.

Also running in cnc mode seemingly successfully, but it is not playing nicely here.

Anyone have any ideas?

@zapta
That's understandable, with this really being focused to the hotend, I guess I would be able to connect a fan outputs to another fan outputs if I wired them to two pin connectors. Looking at the size of everything, there really isn't much difference so I'll probably buy some more microfit 3.0 connectors (they are basically the same size as nanofit, weirdly enough).

I just thought I would bring/post about a connector I found that Molex makes that I think would work well for hotend connections, as well as elsewhere on my printer. What does everyone prefer to use for their hotend heater thermistor, and fan connections out by the extruder? I know the Voron guys like the microfit 3.0, and Lulzbot had the normal dupont style pins, some people use JST on daughter boards.

Molex makes some crimpable wire to wire connectors that are kinda cool (available on digikey). They call them ditto connectors since there is only one kind of crimp and one kind of housing (no male and female, but insertion is one way). Here's a video: https://www.youtube.com/watch?v=R-sWcdPl7Dc

They make 2.5mm pitch connectors, so pretty compact for what they are: https://www.digikey.com/en/products/detail/0368770004/WM10902-ND/5114214?itemSeq=354314114

Any thoughts? Is there any connector that is ideal that I just haven't heard about?

Thanks in advance.
-Tim

@bricoletout
Just wanted to make sure you know about this printer: https://www.projectr3d.com/shop/p/daedalus

It checks all of your boxes and is ready to go!

I want one

@Phaedrux I am running 3.1.1 and it seems to be working very well (I was having issues with the much older version of DWC).

Do you think that the newer version of DWC could cause this even with no client connected?

-Tim

@dc42 That's the thing, I did not intentionally reset the board before sending the m122, that was how it was when I walked up to the machine in the morning. The power up was immediately following the reset if I read the timing correctly.

This is one of those silly Fusion3 F400s, I will disconnect the paneldue and reset button connected to the expansion connector and try again, also will see if I can scrounge up a brand new sd card.

Anything else I can do to debug? Doesn't M111 need a PC connected via usb to receive the debug messages?

-Tim