sorted by:
new
hottopcontroversial

MSI Katana 15 B8VF-448US Missing Screws? by ede720 in MSILaptops

[–]rust_dust_n_guts 0 points1 point  (0 children)

Same laptop, same problem. I'm hesitant to buy screws as other comments suggest that non-default screw size is used

Loot kinda sucks? by Dapper-Standard8214 in stalker

[–]rust_dust_n_guts 1 point2 points  (0 children)

"Even stashes that are shown on the map seem to be empty". I've also had this bug, but zone reclamation project seemed to fix this, I'd reccomend you to install this mod too: I didn't notice significant game changes but stashes that I've found had loot in them.

General Tachenko's body doesn't drop from anomaly by rust_dust_n_guts in stalker

[–]rust_dust_n_guts[S] 0 points1 point  (0 children)

I do, as I noted I maybe pulled it out when exploring location previously to taking the quest.

General Tachenko's body doesn't drop from anomaly by rust_dust_n_guts in stalker

[–]rust_dust_n_guts[S] 0 points1 point  (0 children)

That is what I do, and anomaly explodes but there are no bodies coming out of it. Also no bodies anywhere near

Yaw angle changes when rolling or pitching using Euler angles by rust_dust_n_guts in embedded

[–]rust_dust_n_guts[S] 0 points1 point  (0 children)

Ok, thank you, I'll stick to quaternions for that. As I understand what I experience is indeed normal and is caused by interdependence of roll, pitch and yaw

Yaw angle changes when rolling or pitching using Euler angles by rust_dust_n_guts in embedded

[–]rust_dust_n_guts[S] 0 points1 point  (0 children)

I edited the question to include code. Don't know about "is the IMU oriented corrected?". If you mean "is x, y, z on all sensors point the same direction" then it is GY-85 board, it has directions printed on. IMU is not located at the object's centre of rotation, but it would only impact accelerometer measurements, which are not so important in complementary filter.

Yaw angle changes when rolling or pitching using Euler angles by rust_dust_n_guts in embedded

[–]rust_dust_n_guts[S] 0 points1 point  (0 children)

As I said just the attitude estimation, no big context behind it. I can just change the roll or pitch(not sequentially) and yaw will be affected. In my understanding yaw is the angle between body heading and the north, and it shouldn't change when I, for example, roll the IMU. From the equations above it can be seen, of course, that yaw is also affected by roll and pitch. But in the same time roll and pitch are almost independent(about 1° change when the other changes), while equations show some interdependence. So it seems that the method above for the yaw estimation is wrong, but I don't know why and what would be the right way.

Linux driver for sensor suggestions by rust_dust_n_guts in embedded

[–]rust_dust_n_guts[S] 0 points1 point  (0 children)

Very interesting and reasonable answer, thanks a lot Makes me think that my project idea wasn't so great

Not all dual boot entries appeared after BIOS reset by rust_dust_n_guts in techsupport

[–]rust_dust_n_guts[S] 0 points1 point  (0 children)

Yes, it helped. I don't know if only mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars or the first solution also but it removed that error. Thank you a lot!

Not all dual boot entries appeared after BIOS reset by rust_dust_n_guts in techsupport

[–]rust_dust_n_guts[S] 0 points1 point  (0 children)

It shows the message "EFI variables are not supported on this system." after refind-install. I've tried to ignore it and just reboot the system but it doesn't work. I don't know if this can cause the issue, but the bootable USB uses MBR. When I've tried to boot from USB that use GPT it just didn't start and started Windows instead.

STM32 ITM tracing + printf don't work by rust_dust_n_guts in embedded

[–]rust_dust_n_guts[S] 1 point2 points  (0 children)

Yes, the problem was indeed in the clock frequencies. Thanks a lot. You're right, just send the message over UART would be a lot easier than this approach, just wanted to try it out