Show all posts by user
Page 1 of 8
Pages: 12345
Results 1 — 30 of 213
A few things, this problem is almost certainly a problem with the TFT software not with RRF. There is no notion with RRF of a UART based device (like the TFT) connecting so the disconnect/connect is almost certainly just changing something on the TFT side of things. I'm not sure if the author of the TFT firmware you are using monitors this forum or not, so you may not get any help. I don't use a
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@srs5694 Firstly please if you can use the discord server for discussions like this. I only check this forum now and again so you will get faster responses over there.
Without knowing what versions of things you are running it is hard to be sure what is going on. I would be surprised if there is a general problem with responses. I have seen no problems when using a PanelDue to list files etc. I'
by
gloomyandy
-
Firmware - experimental, borrowed, and future
The BTT SKR Mini E3 uses an STM32F1 processor which is not supported.
The BTT SKR SKR E3 Turbo uses the LPC1769 processor, but RRF does not currently have a built in configuration for this board. We are currently working on adding support for it, it will also need a different adapter board to allow it to be used with an ESP8266 WiFi module (again this is currently being worked on).
The BTT ESP01S
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@DeltaDroid I'd say there is very little chance it will work and a small but real chance you will damage something. I really wouldn't advise just flashing the firmware.
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@Crunch69. No the GTR ribbon cable interface is pretty useless all it has connected is power and one UART connection, we need more than that for the SBC. The M5 is not currently supported (because among other reasons I don't have one!). We are trying to get hold of an M5 for testing/development and if/when we do I'll take a look at it. But I'm pretty busy at the moment merging the LPC and STM cod
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@fenixsz, you will almost certainly get more help if you use the LPC discord server (see the LPC Wiki for details). The M911 command you are trying to use requires that the main board is able to monitor the supply voltage, the BTT SKR boards do not have that feature. When using the BTT UPS it sends a trigger value to the board and it may be possible to configure RRF to use this trigger, but it is
by
gloomyandy
-
Firmware - experimental, borrowed, and future
I have just uploaded beta test versions of an experimental STM32F4 port of RepRap Firmware V3.1.x+. The firmware files can be found here:
This port is an enhanced version of the RepRap Firmware LPC176x port and much of the documentation/features etc. applies to both.
Currently the following boards are supported:
BTT SKR Pro V1.1BTT SKR Pro V1.2BTT GTR V1.0 (The expansion board is not currently
by
gloomyandy
-
Firmware - experimental, borrowed, and future
If you are still getting the same error then you still have the same problem. Did you restart vscode after changing the path? Can you run mkdir in a vscode terminal window? Do you have some sort of command line environment (like git-bash)? You should be able to run the make command in that environment (but you may need to make sure that the compiler is setup correctly for use in that environment)
by
gloomyandy
-
Firmware - experimental, borrowed, and future
Looks like your system does not have a mkdir command installed (or at least there is not one in your path). You either need to install mkdir on your system or edit the makefile and set MKDIR appropriately.
Is there a reason why you are building your own version of the firmware?
by
gloomyandy
-
Firmware - experimental, borrowed, and future
Folks I've just upload a new release 3.1.1-14, this contains a fix that will hopefully resolve problems with fans not running. It also contains a change to the Ethernet build that disables the LCD support because of the lack of available RAM. The release can be found here:
by
gloomyandy
-
Firmware - experimental, borrowed, and future
I'm pretty sure I have a fix for the fan problem (something relate was reported the other day with thermally controlled fans). It's a little complex to describe what is going on an is related to the way that the PWM frequency is set at the same time that an initial speed is also being defined. I'll try and put together a release with the fix in it in the next few days. But for now setting a non-z
by
gloomyandy
-
Firmware - experimental, borrowed, and future
The WiFi is not MKS. it is a separate nodemcu module (ESP8266) that you hook up either using and adaptor board or make up your own wiring loom. It connects to the main board using SPI and the connection is pretty fast. The details are here: not for everyone, but at least a couple of folks (in addition to me) have it working with the SBase.
Yep the download should take less than 80 seconds over
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@MKSA we have had a few folks try the SBase board now and it seems that for virtually everyone the DWC load time is approx 80 seconds (as is mine), not fast but nowhere near as slow as you get. So there must be something different about your board/network/whoknowswhat that is triggering the extra slow download. The extra ADC filtering is present in this build but it is off by default, there is a
by
gloomyandy
-
Firmware - experimental, borrowed, and future
The original 3.0 thread was getting a little old (and long) so we have decided to create a new thread for V3.1.x (which includes the current 3.1.1 versions). We have also included a number of links to information which will hopefully help anyone trying to use this port.
History
The original LPC port of RRF firmware was created by Sdavi and details of that can be found here and here , a huge th
by
gloomyandy
-
Firmware - experimental, borrowed, and future
Just to be clear, it does not look like you have a problem with either the WiFi board or the SKR. However you do have a problem with the board.txt file. Either there is a problem with the content that is causing an error as it is being read, or you have it in the wrong place (it should be in the /sys folder and must be called board.txt), we can't tell because you did not post a complete directory
by
gloomyandy
-
Firmware - experimental, borrowed, and future
Also please note that there is currently no support for the 2130 SPI interface. So you will have no way of setting current etc. via software. You will also probably need to set the number of smart drivers to 0 to stop the firmware trying to talk to them via the UART interface.
by
gloomyandy
-
Firmware - experimental, borrowed, and future
You are not running the latest RRF version, but it should still work, the current release is 3.1.1-12 (see here ). Please post the output from M122 p200. Please post a picture of your board and wifi module so we can see how you have it connected. Did your WiFi module come with firmware installed? If not have you installed the correct firmware (what version did you install and how did you install
by
gloomyandy
-
Firmware - experimental, borrowed, and future
Well it certainly works with the SKR V1.4. but the RRF WiFi support will not work with the esp-01. I suppose you might be able to hook up the rx/tx lines from an esp-01 to the SKR UART and feed gcode in that way using something like esp3d, but I'm not aware of anyone doing that and you really miss out on most of the advantages of rrf by doing that, so I'm not sure it makes much sense.
by
gloomyandy
-
Firmware - experimental, borrowed, and future
Please post...
* A picture of your board and WiFi module so we can see how you have it set up.
* The contents of your board.txt file
* The output from M122 P200
Have you flashed the WiFi firmware to your WiFi module?
What stepper driver modules are you using, they are currently all reporting errors.
by
gloomyandy
-
Firmware - experimental, borrowed, and future
Page 1 of 8
Pages: 12345
