QuotePB QuotePB QuotePB Seems Sbase do have level shifters i.e. SN74LVC1T45DCK at 0.15, 0.16, 0.18 I can not guess why it has problem with RRD displays. May it be incompatibility like inverted SCK levels (wrong CPOL) or time shifted MOSI to SCK (wrong CPHA)? BTW Sbase 1.2 schematics available The only thing I can confirm about Sbase 1.3 that level shifters IC at same places are present in 1.3by sdavi - Firmware - experimental, borrowed, and future
Quotesinned it looks like its using different pins for SPI functions on EXP2 header. You might have to jumper the SPI pins for SCK, MISO and MOSI: 0.15, 0.17, 0.18. Even thought it worked on Smoothiware, the LPC port only uses the hardware SPI pins, and the others are SW driven. sdavi might be able to help here. Looking at that pinout, seems they have wired up the external SDCard to use theby sdavi - Firmware - experimental, borrowed, and future
QuotePB heat.tempSensePins = {0.24, 0.23, 0.25}; heat.heatOnPins = {2.5, 2.7, 2.6}; fan.pins = {2.4, 2.6}; M307 H0 B0 S1.00 M305 P0 T100000 B4981 C1.632834e-7 R4700 M143 H0 S160 M301 H0 P16.2427 I0.6705 D98.3699 B30 M307 H1 B0 S1.00 M305 P1 T100000 B4981 C1.632834e-7 R4700 M143 H1 S280by sdavi - Firmware - experimental, borrowed, and future
Quote4lathe Sdavi, can we use tmc2208’s in uart mode with the current firmware? No, none of the UART or SPI stepper drivers have been ported.by sdavi - Firmware - experimental, borrowed, and future
The docs says the C param only applies when using P4 for M558. P9 says it's as P5, but instead retracts and deploys between probe points, and P5 refers to using the Z-Probe connector, which is set by using zProbe.pin the board.txt. If it's not configured, then the probe pin will be set to NoPin and won't work. Most of the LPC based boards have min/max pins for each axis. But we need to map theseby sdavi - Firmware - experimental, borrowed, and future
Quotedc42 No, you should NEVER configure a Z probe to be a Z endstop in RRF. Instead you should use a G30 command in homez.g and in the Z homing section of homeall.g. See . Thanks. Was too busy looking at the doc of 574. I just checked my config.g and have: M574 Z0 S0 Out of curiosity, when would you use the S2 of M574 ? Edit: I just checked the online configurator and it puts in M574 Z1 S2by sdavi - Firmware - experimental, borrowed, and future
Quote4lathe With Sinned giving me direction in a side channel, I managed to get the lcd and the rest of the printer working. The only thing that remains is the BLTouch acting as the z endstop. the BLTouch responds to all the m280 commands properly however when I do homez.g, the probe deploys but using my fineger to stop it, it does not trigger the z endstop. m558 p9 Try setting like this: boarby sdavi - Firmware - experimental, borrowed, and future
Quote4lathe jay_s did you ever get the skr 1.3 working? Sdavi, i used your board.txt above but get mo movement at all from the steppers. Is there something else to di to get tmc2130 working? I don't have any experience with the tmc2130 drivers or the SKR boards. Do you have any other normal style drivers without spi to test with so we can confirm that the stp/en/dir pins are correct?by sdavi - Firmware - experimental, borrowed, and future
Quote4lathe another issue. m280 p60 s10 works fine. in sys/deployprobe.g I have 1 command m280 p60 s10. however when I issue m401 I get Send: M401 Recv: Bad command: {\rtf1\ansi\ansicpg1252\cocoartf1671\cocoasubrtf500 Recv: Bad command: {\fonttbl\f0\fswiss\fcharset0 Helvetica Recv: Bad command: {\colortbl Recv: Bad command: \margl1440\margr1440\vieww10800\viewh8400\viewkind0 Recv: Error: G-Codeby sdavi - Firmware - experimental, borrowed, and future
Binary now updated to RRF v2.03. Download from Github. Be sure to read DC42s Whats New. There have been changes to the SDCard library (listed below), so it would be a good idea to make a backup of the config files etc on the SDCard before updating. LPC specific changes: Networking: Upgraded FreeRTOS+TCP to V2.0.11 Fixed a bug causing a buffer to not be freed if there was a socket error duringby sdavi - Firmware - experimental, borrowed, and future
Quote4lathe YES. Probe now deploying and retracting. M119 still only shows z: not stopped. Z probe: not stopped after m280 p60 s10 and me pressing and holding probe up. I don't know much about the new BLTouch, i've got a old one here i sometimes test to see if it's working in the port. The BLTouch webpage timing diagram shows there is only a very short pulse on zmin when its triggered, so its unby sdavi - Firmware - experimental, borrowed, and future
Quote4lathe I haven't tackled the tmc2130's yet. still working on the BLTouch. when I issue m280 p0 s10 I get servo index invalid. same for p1-p9. it wants to treat it as a servo on one of the pwm pins but the white and black wires of the BLTouch are attached to the z Endstop( this worked in marlin 2.0) and the servo wires are connected to the skr servo pins (2.0). again this worked in marlin 2.0by sdavi - Firmware - experimental, borrowed, and future
QuotePippy Does not the duets use SPI TMC drivers ? if so, could it not be added to your LPC port I wonder ? Never looked into it, but may be possible. I think the SKR1.3 doesn't use HW SPI pins for the drivers, so it would also need a software spi implemented. I don't have a board so unable to try it. Maybe someone here could port it over and test it?by sdavi - Firmware - experimental, borrowed, and future
Quote4lathe I have been getting some great help from a board member here but decided to ask if anyone had a board.txt for a bigtree skr v1.3 board. I've been running Marlin 2 on it in an ENDER 3 with bltouch that's pretty frankenstein'd out. I ran Klipper on it before that but both of these need work. I run a duet3d board on a couple deltas and really like that setup. thx for any help I startedby sdavi - Firmware - experimental, borrowed, and future
Quotejay_s Bigtreetech have released the SKR pro which uses a STM32F407ZGT6 clocked at 168MHz. Is there any chance of getting a build which would support this? Might perform better than the LPC based boards. Not here, this is just for LPC1768/9. It would need a different core etc ported to interface to the new microcontroller.by sdavi - Firmware - experimental, borrowed, and future
Quotesinned folks who are using the LAN module- what kind of throughput are you getting uploading gcode files? i seem to be topping out at ~ 80-100Kib/sec good ? bad? ok? Currently, up to 100K/s is normal. I recently found ChaN 2018 example code for SD card that used 16bit SPI transfersfor block transfers and makes use of the 8 frame SSP FIFOs on the LPC. So I redid the SDCard library based arby sdavi - Firmware - experimental, borrowed, and future
Quotesinned Has anyone set up a thermostatically controlled fan for hot end? If so, what pin did you use? I have not been able to get it work right with any of the available pins. I am thinking that the best way might be to actually use a 5V triggered MOSFET off of one of the servo pins. Any suggestions? EDIT: I am having trouble reconnecting the PS_ON pin and getting it to function. Anyoneby sdavi - Firmware - experimental, borrowed, and future
Quotesinned Quotesdavi To get everything to fit, the write buffer for the SDCard was reduced to 512 bytes - this also matched the library used for SDCard which only supports single block access (512 block size). I am confused- does this mean that the SD card in the Graphical LCD is functional? I thought that it was not available. sinneD Yep, that was implemented about a year ago when sharedby sdavi - Firmware - experimental, borrowed, and future
Quoteflydeprutten I mean timeouts when I load the page. As I can see, I get it on viewmodel.js, as it is the last file that is being requested, and chrome therefore gives a timeout, as it does not get downloaded in time. When I get home I will do a ping test, and then I could design a pcb that could act as a bridge between the re-arm and the ethernet module. this would remove that uncertainty. :by sdavi - Firmware - experimental, borrowed, and future
Quoteflydeprutten OK. Today I got my LAN8720 in the mail. I made a cable to connect it to my re-arm and it works. However, the problem is that it is insanely slow. My upload speed is approx. 100kb/s, and since the web server only allows one connection at a time, I get timouts in chrome. However, I can make it work in Firefox. i have a problem with that status.temps.heads is an empty variable inby sdavi - Firmware - experimental, borrowed, and future
Quotejay_s If I load this on an SKR v1.3, will I be able to set the driver current using SPI? No, currently there is no SPI stepper driver support compiled into the LPC port. It currently only supports manual and digipot for setting driver current, and only manual is supported for setting driver microstepping.by sdavi - Firmware - experimental, borrowed, and future
Quotesinned I am happy to report that the menu file from here - https://github.com/mudcruzr/Duet-Maestro-12864-Menu-Files work really well. I tweaked them a bit for my setup, but the basic framework is there. 90+% of a functional printer is in the menues. There are a few things that I am still trying to work through- 1. Octoprint consistently experiences a serial exception. I have looked aby sdavi - Firmware - experimental, borrowed, and future
Quotesinned Hi - sdavi, thanks for this and all your hard work ! small request/suggestions - put a link on the git page to here. it took me a while to find this page. i am trying to config REARM and could use some coaching. 1. can you confirm that the LCD info applies to the usual RRD Full graphic controller? I think so but I am not sure. //LCD Pins (only ST9720 SPI currently supported) aby sdavi - Firmware - experimental, borrowed, and future
Quotetripio2000 QuoteJoVo could it be that web control something cached? Now lot of hour later webgui is stable (I configured dual-z today - works also ) Last issue for me is Temperature (Chart) this is not a straight line - it has a lot of spikes up to 10 C ° most of them up to 5 °. For some test prints, the system was stopped due to incorrect temperature. PID was done. Hello, is there any sby sdavi - Firmware - experimental, borrowed, and future
Quickly looking at the schematic: Pins 34-39 on the ESP32 are input only pins so you'll need to swap those. In the current configuration, you should protect the ESP pins (not 5V tolerant) from the expander I2C and INT signals since it is powered by 5V. The schematic shows RX0 and TX0 pins tied together and used by the stepper module, but those pins (normally connected to the usb-uart chip oby sdavi - Next Wave Electronics Working Group
New binary updated to RepRapFirmware 2.03 Beta3. Also includes an LPC networking update when using DHCP to address an issue that prevented the networking from working again if the cable was unplugged and plugged back in (or the hardware for some reason dropped the link) or when renewing the DHCP lease.by sdavi - Firmware - experimental, borrowed, and future
Quotesvs072477 Hi, you wrote that you wanted to experiment with ESP 32. Is anything working? Yeah, it is getting close to working I think, only work on it now and again though. I've basically taken the whole Networking folder from RepRapFirmware and have it running on the ESP32 (only HTTP at this point). So most of the transfers between the LPC<->ESP (over SPI) are JSON status updates andby sdavi - Firmware - experimental, borrowed, and future
I've heard people say wood dust can clog up some filters/bags etc - I wonder if that has contributed to your motor burning out? Have you had a look at the Cyclone Dust Collectors? They connect inline with the vacuum cleaner and aim to remove most of the dust before it reaches the vacuum cleaner. Not sure if that helps in your situation but could be worth checking out.by sdavi - CNC Routers, Mills, and Hybrid RepRapping
Quotedot_bobYour binary is working on everything I throw at it so far. I keep you up to date if I see anything strange. Thanks for the extra testing. I've also been testing it with a number of different GCode over the weekend and no issues either. I even did some testing with apache ab to request M114 500 times during a print and with DWC running and it handled that as well. Fixed a typo in piby sdavi - Firmware - experimental, borrowed, and future
Looks like the main cause was "updating" the network driver memory allocation to match the other drivers in +tcp, so i've reverted back to the previous version. Ive run a couple of different test gcodes through and so far no issues. Updated Binaryby sdavi - Firmware - experimental, borrowed, and future