Show all posts by user
Page 1 of 12
Pages: 12345
Results 1 — 30 of 341
Ah right. I haven't used cmake much before, I looked at it briefly for the LPC port couple of years ago but didn't like it so stuck with makefiles (which fortunately didn't need much maintenance over the years).
I did an initial partial port of RRF v2.01 for the ESP32 quite a while ago. Just enough to get it the main part running, loading configs from sd, connecting to WIFI with dwc and IO ex
by
sdavi
-
Firmware - experimental, borrowed, and future
Yeah I'm not a fan of the eclipse setup either which is one reason why I didn't use it when I did the LPC port of RRF.
I notice that every source file is individually listed in the sources in the cmake version. So every time a new file is added, renamed or moved the makefiles will need updating - personally I think this would get a bit frustrating to update them every time that occurs.
What c
by
sdavi
-
Firmware - experimental, borrowed, and future
This is what my duet reports on my 230x270x6.35mm ATP-5 piece. Note that I also have a piece of PEI stuck on mine:
Number of points: 180
Probe area: 346.5 cm²
Maximum deviations: -0.204 / 0.004 mm
Mean error: -0.058 mm
RMS error: 0.038 mm
That's flat enough for me.
by
sdavi
-
Mechanics
Looking at the datasheet it says "0.381 mm or better". Looks like you have to go over 12.7mm where they'll guarantee 0.127 mm or better. I wonder what the tolerances are for the MIC6 plates most are using?
by
sdavi
-
Mechanics
Quotegloomyandy
@SDavi as an extra data point, I have an SBase (as I think does Jay_S) and have not been able to reproduce the slow download of DWC (and I've tried it on a couple of different routers and over powerline adaptors), in all of those cases DWC downloads in about a minute for me. I have however seen the problem (that I think you have a fix for) of the connection sometimes connecting at
by
sdavi
-
Firmware - experimental, borrowed, and future
QuoteMKSA
@sdavi An other issue, still related to the TFT32 communication, strange but dangerous:
From DWC (works but takes about 15 minutes to load as already mentioned), system works. I can home, set T°, print ....
BUT from the TFT32 when I set the hotend to say 130° (in fact any temp) , the T° keeps rising, never stopping ! I had to cut the power in an emergency as it was going beyond 350°
by
sdavi
-
Firmware - experimental, borrowed, and future
Quotehobbymods
Was that "Calm Aluminium"?
I got them to cut me a piece of 1/4" (which is 6.35mm) for my Zortrax conversion. Mine is "Vista Metals ATP5" as well. I don't know if that's better or worse than MIC6, but that's all I could find as well.
It wasn't perfectly flat by the way, but still pretty good compared to any other plate I've used and heats nicely.
Yeah that was the place. Mine ha
by
sdavi
-
Mechanics
Quotehobbymods
Yes, you are lucky to be so well equipped and supplied. The US must be awesome for niche hobbyists.
There's no such thing as cheap cast plate in Australia, but I do have access to a water jet cutting guy who takes care of me. I don't have anything that would cut or machine aluminium to the tolerances required, which is why I've opted for a frame kit.
I do have the gear to make r
by
sdavi
-
Mechanics
There are a number of feed and speed apps out there that you tell it what material you want to cut, what bit you want to use etc and it can calculate values for spindle speeds, feedrate, plunge/ramp speeds, depth of cut etc etc. Some of them will even warn you about potential issues such as tool deflection, rubbing etc.
by
sdavi
-
CNC Routers, Mills, and Hybrid RepRapping
Quotegloomyandy
@SDavi, one problem that I've seen a couple of times with the LPC and USBCDC is that of sending zero length packets. The CDC spec requires that if you send data that ends with a full packet then you must send an additional zero length packet to terminate the transmission. If you don't do that then some systems (Windows for sure) will not pass on the data until either you send anot
by
sdavi
-
Firmware - experimental, borrowed, and future
Quotegloomyandy
@SDavi My USB changes are fairly minor, more cleaning things up and a slightly more efficient way of using the buffers. I did consider switching to using DMA, but I wasn't convinced that how I would do it would really save that much time and would need more memory (for DMA buffers) or delay things more. I came to a similar conclusion on the UART side of things, but it seems like y
by
sdavi
-
Firmware - experimental, borrowed, and future
Quotegloomyandy
Hi SDavi,
that looks like some interesting improvements. I've also made some updates in similar areas and you may want to take a look at my changes, they are on a separate branch to the main 3.1.1 version of my repo. I'll be pushing some more changes later today (mainly USB updates), so watch this space!
I also have been working on some new USB code but it is probably a while be
by
sdavi
-
Firmware - experimental, borrowed, and future
Over the last few weeks, I have been looking at improving the core code and speeding things up a bit. See the attached binary (RRFv3.1.1 build with Ethernet support) if anyone is interested in testing out an early build with these new changes (make sure you using the pin naming scheme as mentioned in the first post of this thread). With the extra memory requirement in V3.1, the ST7920 is no long
by
sdavi
-
Firmware - experimental, borrowed, and future
QuoteDrDitto
Thanks to all.
I will make a deep research.
At the moment I will work changing the new Open source mks tft firmware. Because the one that all mention at the messages did not work. It shows no images for the button.
You could also run the original TFT firmware (configured to use Marlin mode) and setting the aux serial in RRF to use "raw" mode with M575 in the config.g (i.e. M575 P1 B
by
sdavi
-
Firmware - experimental, borrowed, and future
QuoteDrDitto
oK
I Recompile all with no network
This is the new M122
and all data but LCD Shows nothing
--
LCD works in marlin as a RRD Full Graphic LCD
but not in my setup
Your board.txt contains errors (it is using the "old" settings), so some of the configuration such as the software SPI pins etc etc are not read by the firmware. Always check with M122 P200 to ensure that the board.txt setti
by
sdavi
-
Firmware - experimental, borrowed, and future
QuoteDrDitto
Thanks for the support
I Use no WIFI just LCD
I am using this menu repo
and actually is at sd
UltimateDuetMenuSystem-master
But I see just a bllank screen
I just tested the UltimateDuetMenuSystem on my setup with RRD Full Graphic LCD and is working correctly for me.
Also make sure to check the menu files are located at sdcard:/menu/ as the firmware expects to find the file /menu
by
sdavi
-
Firmware - experimental, borrowed, and future
BTW, DC42 has already added the raw serial mode support as of 3.01-RC11.
by
sdavi
-
Duet
For those waiting for the non-paneldue UART mode in RRF3 to use TFT32, ESP3D, etc etc, these should hopefully be working again as of 3.01-RC11 as DC42 has just implemented UART "raw" mode. I've just done some testing with 3.01RC11 on the LPC port and is working well for me. This replaces the need for the old "lpc.uartPanelDueMode" board.txt setting that was used in LPC-RRF2.
To use raw mode,
by
sdavi
-
Firmware - experimental, borrowed, and future
Quotedarchap
; Z-Probe
M558 P4 C"Zmin" H5 F600 T6000 ; set Z probe type to switch and the dive height + speeds ALSO TRIED ZSTOP
G31 P500 X0 Y0 Z15.9 ; set Z probe trigger value, offset and trigger height
M557 R80 S20 ; define mesh grid
Note that my zprobe is not inverted. Ie if i config my x endstop as this M574 X2 S1 P"Zmin" a
by
sdavi
-
Firmware - experimental, borrowed, and future
Quoteosterac
I tried to search for the forum post you mentioned but couldn't find anything
I think this is the one dc42 is referring to:
Quoteosterac
and I haven't been able to find a full schematic of the duet 2 PCB.
by
sdavi
-
Duet
Quotegloomyandy
@dc42 @sdavi not sure if you are looking at this thread but... I'm in the process of updating to RC4 but have hit a couple of problems. There are a number of new items that have been added to the object model, but some of these are causing compilation errors when built with some of the options we use for some of the LPC builds. In particular the object model reference to "powerFai
by
sdavi
-
Firmware - experimental, borrowed, and future
Quote7ambrion
i have purchased thirdparty max31865 and it looks like its have a lot of pins need i all of them or its just a one signal pin? and how about 430 resister, will it work with this gcode?
M308 S1 P"e0temp" Y"rtd-max31865" R430
It uses SPI, so you need to connect the MISO, MOSI and SCK to SSP0 on the LPC, and the ChipSelect pin to a spare LPC pin. The P param for the 31865 is the ch
by
sdavi
-
Firmware - experimental, borrowed, and future
Quote7ambrion
hei guys! is it someway to run pt100 on this port? I have tl amplifer so what i need to write here?
M308 S1 P"e0temp" Y"??????"
Supported sensor types in RRF can be seen here: .
I have a PT100 working on the port, but its with a MAX31865.
by
sdavi
-
Firmware - experimental, borrowed, and future
QuoteMKSA
@jay_s @sdavi
Note that what puzzles me is that once DWC is loaded and I have control, I can transfer a gcode file of about 10MB (4 times the script file size app.9fed7e58.js that takes 15min !) in about 10s !
What about downloading that same gcode from the LPC? (in DWC right click on the gcode file and select download) Maybe when sending from LPC it is slow?
@jay_s Maybe you can look
by
sdavi
-
Firmware - experimental, borrowed, and future
@MKSA
Hmmmmm, that is strange - I don't see anything out of the ordinary there. Based on those snippets, it looks like its working properly (on the LPC), but for some reason just very slow when loading up the web files.
I tested on mine (v3.01) connected directly to laptop with a static address and can confirm that part of networking is still working quickly.
Since the upload speeds etc are
by
sdavi
-
Firmware - experimental, borrowed, and future
From memory, the last time I did fixes for networking I applied it to the V2 branch as well. The initial load on mine is only about 6 seconds to fully load and display DWC2.
When it's up and running, what are the speeds like when upload and download a gcode file?
Enable debugging for Networking: M111 P1 S1. Attempt to connect, when its working you should see accepted connections and data qu
by
sdavi
-
Firmware - experimental, borrowed, and future
Quotegloomyandy
Hi @sdavi I now have my rPi and SKR V1.4 board talking to each other (at the default 2MHz SPI speed). Which is pretty cool. Great work (again!). Hopefully tomorrow I can try a few more things out and perhaps even hook it up to my printer control board and test things there. I'm not sure that I have a very consistent rPi setup at the moment as I'm using the released rPi duet3 boot
by
sdavi
-
Firmware - experimental, borrowed, and future
Quotegloomyandy
Hi @sdavi, thanks for uploading the files. I'm hoping to make a start on trying this tomorrow at some point. But I'll need to get my pi running the Duet software and hook things up. Did you have to make any changes to the pi software side of things (for clock speed or buffer size etc?). Did you include any resistors in the connections between the pi and the LPC (like the ones that
by
sdavi
-
Firmware - experimental, borrowed, and future
Quotegloomyandy
That sounds pretty simple. I was a bit concerned because the Duet 3 seems to use a fairly substantial ribbon cable, so wasn't sure if it needed extra signals etc. What speed are you running the SPI connection at? I assume it is slower than the Dueat 3 uses? Are you seeing and SPI errors?
If you can make your changes available at some point, I'll merge them into my build and give
by
sdavi
-
Firmware - experimental, borrowed, and future
Page 1 of 12
Pages: 12345