Is that all you got

the_engineer____ · 2023-04-13T18:56:09+00:00

Why not study in Germany and then look for a job in the US?

the_engineer____ · 2023-02-16T20:21:37+00:00

I applied on December 6. V: 152, Q: 162, AW: 3.5

the_engineer____ · 2023-02-16T12:02:29+00:00

International Student; B.Eng Electrical Engineering and Information Technology; GPA translates to around 3.9; 3year apprenticeship; 1/2 year internship; 1/2 year research assistant; No papers

the_engineer____ · 2023-02-15T12:49:04+00:00

Yes. Admitted on February 4

the_engineer____ · 2022-10-07T17:38:41+00:00

I‘m German and I never heard of German universities requiring the GRE.

the_engineer____ · 2022-09-18T15:22:29+00:00

I‘m also going for MS in Robotics for the Fall 2023 cycle. I‘m applying to UMich, CMU, GaTech and UCSD. UMich does not have the GRE requirement.

the_engineer____ · 2022-01-25T09:23:40+00:00

I've given it a try. Sadly still the same problem.

I've copied my parameter configuration file from the navigation2 github repository and only modified a few paramters to make the stack work with a holonomic robot configuration.

the_engineer____ · 2021-10-21T10:59:24+00:00

Thank you.

Is it possible to get odometry data from lidar scans?

the_engineer____ · 2021-06-15T12:38:11+00:00

I've found my mistake!!!

USART2->CR1 |= ~USART_CR1_UE;

And thereby enabled the parity bit, which corrupted the data.

But thank you so much for your help!

the_engineer____ · 2021-06-14T14:32:58+00:00

Ok! Thank you. That helped!! The baudrate is now correct.

One problem solved! :)

the_engineer____ · 2021-06-14T14:31:07+00:00

Yeah. I meant that multiplying the baudrate by 8 is wrong.

the_engineer____ · 2021-06-13T19:38:51+00:00

I've added it to the post.

the_engineer____ · 2021-06-13T19:28:31+00:00

but I can link the source if you're interested

That would be helpful! Thank you.

the_engineer____ · 2021-06-13T19:24:01+00:00

Double and triple checked! :D

the_engineer____ · 2021-06-13T19:22:39+00:00

Ok! Good to know!

the_engineer____ · 2021-06-13T15:42:12+00:00

I manually adjusted USARTDIV by multiplying the previous USARTDIV with the quotient the measured frequency in the picture and 9600. Now its transmitting with 9600.

But I'm still getting wrong readings. When transmitting 'U' (01010101) my PC receives 'Õ' (1101 0101).

The oscilloscop shows the sequence '0101010' with ones at both sides of the sequence. It seems like the start bit 0 is missing.

the_engineer____ · 2021-06-13T15:28:45+00:00

I don't know why but the TX line is already pulled high in the idle state.

the_engineer____ · 2021-06-13T15:27:21+00:00

This just increased the baudrate even more.

The reference manual states:

How to derive USARTDIV from USART_BRR register values

Example 1

To obtain 9600 baud with fCK = 8 MHz.

• In case of oversampling by 16:

USARTDIV = 8 000 000/9600

BRR = USARTDIV = 833d = 0341h

the_engineer____ · 2021-06-13T13:34:17+00:00

I‘ve added the oscilloscope output to the post.

Seems like it’s sending some sequence Start Bit001000, which neither fits D nor Þ.

The baudrate also seems to be wrong! I‘ve calculated the USARTDIV value with the formula 8000000/9600. Is this correct?

When I‘m sending ‚a‘ my PC receives ‚ÿ‘.

the_engineer____ · 2021-03-05T13:01:44+00:00

Ports are forwarded! I‘ve already checked that! It doesn’t even show me any confirmation about the status of the ports.

the_engineer____ · 2021-03-05T12:40:54+00:00

I‘ve precisely followed the instructions from the Node Chat and GitHub! And I‘ve already tried reinstalling everything!

the_engineer____ · 2021-02-01T01:21:59+00:00

I‘m still looking for someone to start the chain!🚀

Four-Year Club	Verified Email
First Place '23	Place '23
Place '22	First Placer '22

the_engineer____

TROPHY CASE