-
@justGuner What are you using to connect to the board? If you are using a Windows PC I would suggest using putty see: https://teamgloomy.github.io/putty.html We really need to see all of the output to work out what is happening. If you are connecting to the board via USB the baud rate is ignored.
I've not seen a module connected like that before. You seem to have a lot more pins connected between the module and the board than we would normally recommend (Our setup uses 11 in total I think you have 16 connected). I'm not sure if the additional ones could be causing a problem.
-
@gloomyandy yeah, I'm not gonna be able to try new things for about a week since I won't be near the printer...
I am connected to the printer over USB via pronterface
In terms of the pins used, I assumed that because on the official esp board there are 16 pins, all of them are connected. What are the necessary pins (on the esp) for the module to work properly?
-
@justGuner We don't have instructions for that board because most people simply use a commercially available module (if you get one get an esp32). The module you linked to may have all of the pins but I suspect some of them are not connected. You may be able to work out the connections from looking at the details of the homemade boards for the SKR Pro and mathcing it up with the skr 2 schematic. https://teamgloomy.github.io/skr_pro_connected_wifi_8266.html note that this does not include the UART connections, but I think you already have those working correctly.
I'd strongly recommend using putty rather than pronterface. Pronterface tends to try and interpret/change the commands and responses and generally "gets in the way".
-
undefined dc42 moved this topic from General Discussion
-
Here is a little update on the situation: after trying to solder some resistors to the esp according to this, I think I managed to damage the esp somehow, because after connecting it to the skr afterwards resulted in timeout errors no matter what. To make sure, I reverted to the previous method of wiring straight to the wifi header just like before, only to result in the same timeout error.
If I'm unable to fix this new issue by trying to resolder the wires again, I think I will just buy the btt esp module.
-
@justGuner I think all of the resistors that are needed are already on the skr2 board (see the schematic I linked to above). If you do get a module I'd strongly recommend that you get an esp32 version not an esp8266. Not sure if BTT do a esp32 but, Fly/Mellow certainly does. You will get much better performance from that and additional features.
-
@gloomyandy can you tell me what are some of the other features I get by going with the esp32? All I could find online was improved conectivity over the 8266
-
-
@deckingman Yeah but how many of those features can I use on the 3d printer itsels? For example as far as I know there isn't any bluetooth suport in rrf yet, and the sole reasong for buying an esp is to be attached to the printer, so I'm not thinking about using it in other projects
-
@justGuner The main "feature" is the improved upload speed. With the esp8266 the best I ever see is around 550KBytes/s with the esp32 I see up to 2.5MBytes/s with a STM32H7 based board, with a STM32F4 board I'd expect around 1.8MBytes/s. But that all depends on your WiFi signal SD card speed etc.
The other thing is that new features like enterprise wifi authentication and the MQTT support both need the latest 2.1 version of the WiFi firmware and that seems to run much better on the esp32. Basically there is not likely to be any new work on the esp8266 firmware going forwards (at least not from me). For the small extra cost I just don't think it makes sense to use an 8266.
-
I finally installed a esp32 from btt and it works just fine. Too bad I couldn't find an answer for the original question that started this thread. I might revisit this at some point in the future, who knows...
