logo elektroda
logo elektroda
X
logo elektroda

[Solved] How to configure OLED 0.66 I2C with esp8266_deauther on WeMos D1 mini?

Ch4ist0 3864 34
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #31 17993121
    Ch4ist0
    Level 6  
    kaczakat wrote:
    Maybe being a hacker is not your calling?


    Maybe it isn't but I haven't mentioned it once so I don't know where such questions come from....

    PS. I've never been a hacker and I probably won't be because computer science is just my hobby and education, if I were I wouldn't be cluttering up such posts....

    And as for my question, I know the subject of deauth attack very well and I can do it perfectly myself in unix system, I use WeMos D1 module not to bring my laptop....
  • ADVERTISEMENT
  • Helpful post
    #32 17993349
    rb401
    Level 39  
    Ch4ist0 wrote:
    I use the WeMos D1 module to avoid lugging my laptop around with me....
    .

    If you need this as a useful tool and you don't have much strength or time to fight with the software (where you would have to accept some compromises to the original anyway), some simple but effective solution to your problem came to my mind.

    I took this display from D1 and a normal common OLED I2C 128x64 0.96" and noticed that the width of these boards is identical.
    What's more, I took the "universal" for D1 and it turned out that here not only the width agrees but also the position of the leads on the OLED board with the free points on the universal (exact as if they were made for this application):


    How to configure OLED 0.66 I2C with esp8266_deauther on WeMos D1 mini? .


    Here so "dry" put together:


    How to configure OLED 0.66 I2C with esp8266_deauther on WeMos D1 mini? .

    and here in comparison with the OLED for the D1.
    Only the pins on the sides are covered from above, but this does not harm anything, because no board is inserted above the display:

    How to configure OLED 0.66 I2C with esp8266_deauther on WeMos D1 mini? .

    That is, from such a universal and a simple Arduino OLED module, you can literally make, in 15 minutes, a decent display module for D1 128x64 by soldering this module to this board and stress-free pulling the four wires from the bottom to the corresponding D1 bus signals (+3,3V, GND, SDA and SCL). And fit within the dimensions of D1.
    Upload a ready-made 128x64 OLED and you're done.

    Alternatively, you can solder a goldpin socket (e.g. a piece like the one supplied with the universal) to the universal to simply insert the display into it. This will, however, increase the board gap to somewhere around 10.6mm compared to 2.6mm when soldered directly. If it doesn't make any difference, it is probably better to use this socket, especially as such sockets will be left over after the job is done if you buy a universal with a choice of connectors included:

    How to configure OLED 0.66 I2C with esp8266_deauther on WeMos D1 mini? .
  • ADVERTISEMENT
  • Helpful post
    #33 17993402
    khoam
    Level 42  
    @Ch4ist0
    The advice of colleague @rb401 makes perfect sense. Use the kind of display envisaged in this project. Instead of playing "hacker", as one juggernaut here tried to describe you, don't try to make changes to the code by force. In a while, a new version of the program will appear and you will again wonder what you have to change in "your" version of the source code - this makes no sense if you do not want to actively participate (as a programmer) in the esp8266_deauther project.

    Moderated By gulson:

    3.1.9. Do not be ironic or malicious towards the other side of the discussion. Respect dissent and other opinions on the forum.

    .
  • ADVERTISEMENT
  • #34 17993444
    kaczakat
    Level 34  
    khoam wrote:
    The advice of colleague @rb401 makes perfect sense. Use the kind of display envisaged in this project. Instead of playing "hacker", as one juggernaut here tried to describe you, don't try to make changes to the code by force. In a while a new version of the program will come out and you will again be wondering what you need to change in "your" version of the source code - this makes no sense if you do not want to actively participate (as a programmer) in the esp8266_deauther project.
    .
    I see you're drinking at me again, but I noticed this 10 posts ago:
    kaczakat wrote:
    You can add support for this geometry yourself, but there is no guarantee that it will work properly, the texts may be too long, the number of lines may look funny too.
    .
    But it's cool that an expert is proposing the same solution as me - juggler/amateur, just for what? Are you gaining posts? And what do you think the deauther project is for:
    How to configure OLED 0.66 I2C with esp8266_deauther on WeMos D1 mini? .
    Even if it's improvised attacks on your own network that's what playing "hacker" is all about.
    Helpful post? Buy me a coffee.
  • #35 17994645
    Ch4ist0
    Level 6  
    Hello, topic to be closed...

    I bought a larger display OLED 0,96" 128x64 SSD1306 I2C such as is dedicated by default for ESP8266 Deauther 2.1.0 .

    As colleagues above wrote it would be too cumbersome to rewrite the software for a 0.66" screen...It is possible but I chose the simpler way.

    Thanks to all for your participation and help :) .

Topic summary

The discussion revolves around configuring a 0.66" OLED I2C display with the esp8266_deauther software on a WeMos D1 mini. The user encountered issues with display compatibility, as the software was designed for a 0.96" display, leading to incorrect rendering of information. Participants suggested using the U8G library and the Adafruit_SSD1306 library to support the 64x48 resolution of the OLED. The user was guided on how to install libraries, modify the A_config.h file, and compile the project. Ultimately, the user decided to switch to a 0.96" OLED display, which is natively supported by the software, to avoid the complexities of modifying the code for the smaller screen.
Summary generated by the language model.
ADVERTISEMENT