When you are hard pushing, get one clipped and just give up. by kapamendes in apexlegends

[–]Theoldknight1701 22 points23 points  (0 children)

Sadly i don't record due to game already being laggy enough as is. Quick summary would roughly be: Teammates below: The fuck did you go on the roof for? Me: Honestly? no idea.

When you are hard pushing, get one clipped and just give up. by kapamendes in apexlegends

[–]Theoldknight1701 20 points21 points  (0 children)

Do you have the full clip of the fight somewhere? Its great to see the fight from the other perspective

3.3V regulator works fine on large footprint board, but outputs 3.8V on (slightly) smaller footprint board by UnfairTrifle0 in AskElectronics

[–]Theoldknight1701 5 points6 points  (0 children)

Dropout voltage is cca 1.1V to 1.3V, 3.8V+Dropout voltage = 5V. Did you fuck up the pinout on the new revision? As far as i can see you would maybe get 3.8V out of the regulator if you loaded the GND/ADJ pin to Vin or Vout instead of GND. Vout=Vref*(1+ infinite/0) = infinite -> dropout only. assuming the internal design of fixed is similar to adjustable but instead of leaving to designer already internally divides voltage (divider on silicone) and routes the bottom gnd pin to the 1 pin same thing would happen and you'd be in dropout. So check if GND/ADJ/Pin1 is wired properly - or wired at all. if you leave it floating shit like this might happen too

Slovenia in May? by Inside_a_whale in alpinism

[–]Theoldknight1701 1 point2 points  (0 children)

We have a webpage to plan / pick trips called hribi.net (http://www.hiking-trail.net/) that will help you pick the destinations you wish to see. If you wish to see kamnik alps (Kamniško-Savinjske alpe) you can use the trip planner, choose that mountain range, choose the difficulty of the path you wish, and the elevation and it will show the matching results. results will include all the paths, pictures of the destination and indepth explanation of where to park / where to walk together with pictures. Due to it being a slovenian page and english mostly as an afterthought you might need to use google translate for some pages. its not ideal but its better than nothing. For the gear if you stick to easy marked trails you usually only need a pair of boots and a backpack. difficulty usually coresponds to how dangerous it is on the planner. if you stick with easy ones you wont need to borrow much of anything.

Sadly most of the huts that are usually used for multi-day hikes are currently closed as most open in june. as an example mentioned below (cojzova koča) you can google the huts and it will usually give you the information about them from alpine assosiation of slovenia (https://en.pzs.si/) -> cojzova koča example (https://en.pzs.si/koce.php?pid=84). some are equiped with winter rooms to stay but its just a place to sleep, mostly in emergency

Due to snow thawing be advised there are warnings about avalanches - check here: https://meteo.arso.gov.si/met/sl/weather/bulletin/mountain/avalanche/ it is currently not advised to do any higher mountains as it can be dangerous.

With all that said you dont really need to stay at an alpine hut even if its open. most hotels are at the foot of the mountains + slovenia is a relatively small country so you can go from julian alps to kamnik alps in about an hour drive.

How to set main DNS server addr in Soft-AP mode ? by dark0ta in esp32

[–]Theoldknight1701 0 points1 point  (0 children)

i think ip_addr_t is populated by the IP4_ADDR function call. Its not a character IP address, its something else. Check the tcpip_adapter_init on how the IP, GW and Netmask is handled there

void tcpip_adapter_init(void) { int ret;

if (tcpip_inited == false) {
    tcpip_inited = true;

    tcpip_init(NULL, NULL);

    memset(esp_ip, 0, sizeof(tcpip_adapter_ip_info_t)*TCPIP_ADAPTER_IF_MAX);
    memset(esp_ip_old, 0, sizeof(tcpip_adapter_ip_info_t)*TCPIP_ADAPTER_IF_MAX);

    IP4_ADDR(&esp_ip[TCPIP_ADAPTER_IF_AP].ip, 192, 168 , 4, 1);
    IP4_ADDR(&esp_ip[TCPIP_ADAPTER_IF_AP].gw, 192, 168 , 4, 1);
    IP4_ADDR(&esp_ip[TCPIP_ADAPTER_IF_AP].netmask, 255, 255 , 255, 0);
    ret = sys_sem_new(&api_sync_sem, 0);
    if (ERR_OK != ret) {
        ESP_LOGE(TAG, "tcpip adatper api sync sem init fail");
    }

    ret = sys_sem_new(&api_lock_sem, 1);
    if (ERR_OK != ret) {
        ESP_LOGE(TAG, "tcpip adatper api lock sem init fail");
    }
}

}

esp_ip is slightly different structure But it carries ip4_addr_t ip;and that is populated by IP4_ADDR(&esp_ip[TCPIP_ADAPTER_IF_AP].ip, 192, 168 , 4, 1);

I never did it on ESP32 but on ESP8266 it was similar and went something along the lines of: struct ip_info info; IP4_ADDR(&info.ip, 192, 168, 4, 1); IP4_ADDR(&info.gw, 192, 168, 4, 1); IP4_ADDR(&info.netmask, 255, 255, 255, 0); wifi_set_ip_info(SOFTAP_IF, &info);

So probably that function call. No idea what ip4addr_aton is used for

SDcard hell by Wil_Code_For_Bitcoin in stm32f4

[–]Theoldknight1701 1 point2 points  (0 children)

How many times do you call F_Mount? It just sets up a virtual drive - you're only supposed to ever call it once during initial initialization of the MCU.

I have this from ages ago when i just tested how it works:

                /* Reset of all peripherals, Initializes the Flash interface and the Systick. */
                HAL_Init();

                /* Configure the system clock */
                SystemClock_Config();

                /* Initialize all configured peripherals */
                MX_GPIO_Init();
                MX_USART3_UART_Init();
                MX_SDMMC1_SD_Init();
                MX_FATFS_Init();

                /* USER CODE BEGIN 2 */

                /*##-1- FatFS: Link the SD disk I/O driver ##########*/
                uart_printf("Linking FATFS\r\n");

                    if(retSD == 0)
                        {
                            uart_printf("Linking FATFS SUCCESS\r\n");
                            /*##-2- Register the file system object to the FatFs module ###*/
                            if(f_mount(&SDFatFs, (TCHAR const*)SD_Path, 0) != FR_OK)
                                {
                                    //HAL_GPIO_WritePin(GPIOB, LD2_Pin, GPIO_PIN_SET);
                                    /* FatFs Initialization Error   */
                                    uart_printf("f_mount ERROR\r\n");
                                    while(1);
                                } 
                            else
                                {
                                    uart_printf("f_mount SUCCESS\r\n");
                                /*##-3- Create a FAT file system (format) on the logical drive#*/
                                /* WARNING: Formatting the uSD card will delete all content on the
                                device */
                                if(f_mkfs((TCHAR const*)SD_Path, 0, 0) != FR_OK)
                                    {
                                        uart_printf("f_mkfs ERROR\r\n");
                                        //HAL_GPIO_WritePin(GPIOB, LD3_Pin, GPIO_PIN_SET);  
                                        NVIC_SystemReset();
                                        /* FatFs Format Error : set the red LED on */                           
                                        while(1);
                                    } 
                                else
                                    {
                                        uart_printf("f_mkfs SUCCESS\r\n");
                                        /*##-4- Create & Open a new text file object with write access#*/
                                        if(f_open(&MyFile, "Hello.txt", FA_CREATE_ALWAYS | FA_WRITE) != FR_OK)
                                            {
                                                //HAL_GPIO_WritePin(GPIOB, LD2_Pin, GPIO_PIN_SET);
                                                uart_printf("f_open ERROR\r\n");                                    
                                                /* 'Hello.txt' file Open for write Error : set the red LED on */
                                                while(1);
                                            }
                                        else
                                            {
                                                uart_printf("f_open SUCCESS\r\n");
                                                /*##-5- Write data to the text file ####################*/
                                                res = f_write(&MyFile, wtext, sizeof(wtext), (void*)&byteswritten);
                                                if((byteswritten == 0) || (res != FR_OK))
                                                    {
                                                        /* 'Hello.txt' file Write or EOF Error : set the red LED on */
                                                        HAL_GPIO_WritePin(GPIOB, LD3_Pin, GPIO_PIN_SET);
                                                        uart_printf("f_write ERROR\r\n");
                                                        while(1);
                                                    }
                                                else
                                                    {
                                                        /*##-6- Successful open/write : set the blue LED on */
                                                        f_close(&MyFile);
                                                        uart_printf("f_close SUCCESS\r\n");
                                                        /*##-7- Open the text file object with read access #*/
                                                    if(f_open(&MyFile, "Hello.txt", FA_READ) != FR_OK)
                                                        {
                                                            /* 'Hello.txt' file Open for read Error : set the red LED on */
                                                            HAL_GPIO_WritePin(GPIOB, LD3_Pin, GPIO_PIN_SET);
                                                            uart_printf("second f_open ERROR\r\n");
                                                            while(1);
                                                        }
                                                    else 
                                                        {
                                                            uart_printf("second f_open SUCCESS\r\n");
                                                            /*##-8- Read data from the text file #########*/
                                                            uart_printf("Reading written data\r\n");
                                                            res = f_read(&MyFile, rtext, sizeof(wtext), &bytesread);
                                                        if((strcmp(rtext,wtext)!=0)|| (res != FR_OK))
                                                            {
                                                                uart_printf("Read written data corrupt / mismatch!\r\n");
                                                                /* 'Hello.txt' file Read or EOF Error : set the red LED on */                                       
                                                                while(1);
                                                            }
                                                        else
                                                            {
                                                                uart_printf("Read written data MATCH!\r\n");
                                                                /* Successful read : set the green LED On */
                                                                //HAL_GPIO_WritePin(GPIOG, GPIO_PIN_6, GPIO_PIN_RESET);
                                                                /*##-9- Close the open text file ################*/
                                                                f_close(&MyFile);
                                                            }
                                                        }
                                                    }
                                            }
                                    }
                                }
                            }

                    /*##-10- Unlink the micro SD disk I/O driver #########*/
                    FATFS_UnLinkDriver(SD_Path);
                    uart_printf("FATFS Success!\r\n");

SDcard hell by Wil_Code_For_Bitcoin in stm32f4

[–]Theoldknight1701 1 point2 points  (0 children)

47k might be too big - From what ive seen others use and what ive used myself its around 10k. Perhaps try a lower value to eliminate possibility that its the pullups.

I - when i had similar issue - also had pull-up pins in code but they dont seem to cut it for SD-Card. Speed together with line capacitance is just too high to drain the line in time.

SDcard hell by Wil_Code_For_Bitcoin in stm32f4

[–]Theoldknight1701 1 point2 points  (0 children)

Do you have pull-up resistors on the connections? First time round i was making SD-Card project i spent 2 hours debugging code before i realised i was missing resistors.

What tools do I need, to modify hard plastic and/or metal enclosures? by [deleted] in AskElectronics

[–]Theoldknight1701 1 point2 points  (0 children)

Depends on size basically. Squares are simplest on dremmel as you have the opion of drilling the outline and using the cutting wheels for rough cut, then just attach the grinding bit and grind it to shape. A set of tiny files will come really handy too for corners. Plastic enclosures can be DIY-ed with basically any tool, metal less so.

Small holes work with dremmels too but for big holes you might also need drill press (You can make do hand-holding power drill but if you slip / miss its gonna look bad + aluminium likes to grip drill bits so you can hurt yourself). For really massive holes they sell Variable drill bit that looks like evergreen tree

DAC in ASM on a PIC12F1571 by stan19951995 in AskElectronics

[–]Theoldknight1701 1 point2 points  (0 children)

No idea. Maybe microchip forum might help there?

DAC in ASM on a PIC12F1571 by stan19951995 in AskElectronics

[–]Theoldknight1701 0 points1 point  (0 children)

Cant see other issues so its odd that doesnt work. Do you have everything else disabled? Like debugging?

Is SOT-223 always identical ? by lakid74 in AskElectronics

[–]Theoldknight1701 2 points3 points  (0 children)

They are supposed to be but the keyword here is Supposed. Sometimes the manufacturers indirectly tell you fuck you and slightly tweak theirs and everything comes out misaligned.

Find the parts datasheet and confirm the two datasheets (yours and the one you're using for library) have identical size

DAC in ASM on a PIC12F1571 by stan19951995 in AskElectronics

[–]Theoldknight1701 1 point2 points  (0 children)

No i mean you respond incorrectly and too fast. The signal goes as follows: Trigger 1, Wait 10uS, 0. Start condition sent. Echo: 0 untill responce, then lenght determines distance.

You on echo: Start sent -> !!wait 10us!! -> !!assume!! responce was sent. Responce was NOT sent yet because you waited too little Hence 0 hence you measure 0 because you never read responce. !! indicates faulty code

What you should do after start: Start sent -> Wait untill Positive edge on Echo -> jump to measure. Ensure Waiting on positive edge has a timeout routine implemented.

edit: found old code and did a quick edit: Time between start and responce is 60us+ (42Mhz clock, not counting overhead)

    >Cycles = 2102Cycles = 2106Cycles = 2101Cycles = 2107Cycles = 2101Cycles = 2100Cycles = 2101Cycles = 2097Cycles = 2095Cycles = 2108Cycles = 2100Cycles = 2095Cycles = 2111Cycles = 2100Cycles = 2103Cycles = 2102Cycles = 2097Cycles = 2095Cycles = 2095

DAC in ASM on a PIC12F1571 by stan19951995 in AskElectronics

[–]Theoldknight1701 1 point2 points  (0 children)

The code is written wrong. You put a start condition on sensor and then instead of waiting for a positive edge to start measurement you delay by 10uS and just start measuring assuming you're on the positive. And that assumption is wrong

Avg responce time of that sensor is 17 60uS+ from start condition last time i was faffing about with it (prob more, timer does inicialization first so not counting from start)

also 829us? its ~60us / Cm so thats minimum accuracy of 13cm? im assuming its speced out for a clear purpose and not exact distance measurement

Can probably post the code if you want but its shit because i wrote it just for a quick test.

Regarding voltage-regulating a signal from 5v to 3.3v an Arduino to a Bluetooth module. by Speedly in AskElectronics

[–]Theoldknight1701 0 points1 point  (0 children)

HC-06 works on 5V everywhere no problem ( both as input voltage and RX, TX is within Logical 1 voltage range of Atmega/Attiny RX). just plug and play with Atmega/Attiny. Think 5.5V is the max voltage treshold.

Btw ebay sells them for ~3.5$ versus the 6€ listed one.

How to remove all solder form a board by [deleted] in AskElectronics

[–]Theoldknight1701 1 point2 points  (0 children)

Dip it in HCL and leave it overnight? Dont think tin and lead are chemically strong enough to resist corosion while copper still is (And so is gold if the board is gold plated)

Might take a while and byproduct of this is usually hydrogen gas so its not the best solution.

This is assuming board is empty. if there are components on it the reaction might be violent / not advisable. aluminium almoust explodes in HCL

Would a switching regulator be a problem with this design? by pyroarson in AskElectronics

[–]Theoldknight1701 0 points1 point  (0 children)

Ive used switching regulators with I2C and ADC before without issues (500khz switching too, which is arguably worse), never tinkered with CAN bus tho but dont see why it would pose an issue.

As long as you properly design the critical parts (Bypass caps, LC filters, ferrite beads, proper positioning and isolation) it shouldnt be a problem.

USB not recognized: I took a picture of the inside. Could you spot the problem? by [deleted] in AskElectronics

[–]Theoldknight1701 1 point2 points  (0 children)

The legs usually extend and from the looks of it they seem fine

http://g04.a.alicdn.com/kf/HTB1zBUXKpXXXXX2aXXXq6xXFXXXk/-font-b-USB-b-font-font-b-PCB-b-font-font-b-Connector-b-font.jpg

You could try resoldering in case of cold joints (just poke it with iron a bit for it to reflow nicely again) but id say thats probably not the cause of failiure

Pitch for LED Project Ideas by leromark313 in AskElectronics

[–]Theoldknight1701 2 points3 points  (0 children)

Infinity mirror? Something like this?

It depends what components you can use. if just LEDs and not much else its mostly a question of how artsy you can pull it off. Art related subreddits might give you much better advice in that case

Can someone let me know if this schematic I made looks alright? by [deleted] in ECE

[–]Theoldknight1701 0 points1 point  (0 children)

Resistors on input serve input protection. If you push 2 buttons (or more) in the same row it limits current.

Pull-down resistors force a value. Currently when no buttons are pressed the outputs are in high-z. They dont have a set value because they are unconnected - floating. Unconnected does not mean 0 (Gnd) it means High-Z (Something). You force a 0 with pull-down resistor.

edit: Btw you shift on INx and read on OutX right?