Cousin of OSW (Open Sim Wheel)

Ok who has had the best result with there setup and motor used so far

please read this thread - all the information you need is there

Ok it looks like this badboy or have my eyes failed me

This seems rather high

I want to build a wheel and I have several doubts, I read the problem of the gear effect by the magnets, I want to put a ratio of 6: 1 with a 20mm strap, would that gear effect also be noticed?
You have tested this engine and it has little gear, right?
https://es.aliexpress.com/item/350w...0.html?spm=a2g0s.13010208.99999999.384.1U1wrP
I would use this encoder 2500ppr
https://es.aliexpress.com/item/E6B2...8.html?spm=a2g0s.13010208.99999999.262.lEp23H
and two ibt2 in parallel, is there something that I have to rethink about my project?


And using two 150w motors together would give more smoothness than a large 350w? Could they attack the same pulley with a single strap?
https://es.aliexpress.com/store/pro...1553e91&transAbTest=ae803_1&priceBeautifyAB=0


There are also these engines but I think they need a lot of reduction, has anyone ever used them?
https://es.aliexpress.com/store/pro...1553e91&transAbTest=ae803_1&priceBeautifyAB=0

I suggest you use a single 350w motor but as direct drive.

If you dont like it buy another and go for a twin motor.

The encoder and ibt2 are good parts

I just discovered the post, I did not think it was as difficult to build a steering wheel with force feedback.

How do you calibrate a maximum rotation speed as well as the max power of force feedback?
Is it according to your feelings or did you use some data?

The software controls the forces that create ffb

Its all automatic you dont need to worry about it

I want a wheel with a lot of force so that it does not clipping ever, a 350w motor I do not think of enough strength and it will always be working at many amps, that engine is like yours? Does not have a gear effect?
To use with a pulley, is an engine or two better? I think that with two the gears will not be noticed so much because they are smaller, the amperes will also be better distributed in two ibt2 than using two in parallel, if one takes longer than the other in opening the other will receive all the amperage of a large motor, is my theory maybe this is wrong

I use a small diameter wheel so the torque is still quite high.

You can always use 2 motors or a more powerful one.

2 ibt2 is fine, one may work harder than the other but the overall effect will be the same

Just get in and build the wheel, you can modify it later if you need to

And to build there is some tutorial of the electronics? I want to use the STM32F407VET6, simply load the mmos code and it is wired and that's it? Electronics is what scares me the most

It's really great !

Personally I have a Logitech G27, it is good but its speed when it counterbrakes alone (during a drift for example) is a little slow, and it bothers me a little.

So, thanks to the software you use, can you change these values later?

To increase g27 speed you would need to make modifications to the H-bridge or build/use external, and connect a source with higher voltage and power.
Old example: G27 mod ARC Team
(Attention, only a source with more power could burn the original driver ...)

For a project based on arduino or stm32f407 you will need an H bridge as ibt2 and use some of the g27 hardware, but in that case it might not be worth using a working G27, maybe a dead.
For a considerable upgrade, will be necessary to abandon the G27 platform and build a direct drive or with better engines and pulleys.

Hello Fernando,

Sorry I have no experience using libraries .h like that..
Other errors now using the alpha..

Did you updated to use H-Shifter, check this, it working great!
github/functionreturnfunction/G27_Pedals_and_Shifter

Code:

ConfigHID:1: error: stray '\' in program
ConfigHID:1: error: stray '#' in program
brWheel:46: error: expected constructor, destructor, or type conversion before 'int'
brWheel.ino: In function 'void setup()':
brWheel.ino:120: warning: large integer implicitly truncated to unsigned type
ConfigHID.ino: At global scope:
ConfigHID:1: error: 'ufeff' does not name a type
ffb.ino: In function 'b8 HID_GetReport(Setup&)':
ffb.ino:97: warning: unused variable 'report_type'
ffb.ino: In function 'b8 HID_SetReport(Setup&)':
ffb.ino:121: warning: unused variable 'report_type'
ffb.ino: In function 'void FfbHandle_DeviceControl(USB_FFBReport_DeviceControl_Output_Data_t*)':
ffb.ino:520: warning: only initialized variables can be placed into program memory area
ffb.ino: In function 'void FfbHandle_DeviceGain(USB_FFBReport_DeviceGain_Output_Data_t*)':
ffb.ino:527: warning: only initialized variables can be placed into program memory area
ffb.ino: In function 'uint8_t FfbDebugListEffects(uint8_t*)':
ffb.ino:597: warning: only initialized variables can be placed into program memory area
ffb.ino:599: warning: only initialized variables can be placed into program memory area
ffb.ino:601: warning: only initialized variables can be placed into program memory area
ffb.ino:604: warning: only initialized variables can be placed into program memory area
ffb.ino:606: warning: only initialized variables can be placed into program memory area
ffb.ino:610: warning: only initialized variables can be placed into program memory area
ffb.ino:612: warning: only initialized variables can be placed into program memory area
ffb.ino:614: warning: only initialized variables can be placed into program memory area
ffb.ino: In function 'void FfbEnableEffectId(uint8_t, uint8_t)':
ffb.ino:650: warning: only initialized variables can be placed into program memory area
ffb_pro.ino: At global scope:
ffb_pro.ino:63: warning: only initialized variables can be placed into program memory area
ffb_pro.ino: In member function 'f32 cSpeedObs::Update(s32)':
ffb_pro.ino:91: warning: unused variable 't'
ffb_pro.ino: In member function 's32 cFFB::CalcTorqueCommand(s32)':
ffb_pro.ino:213: warning: unused variable 'err'
ffb_pro.ino: In function 'void FfbproSetEnvelope(USB_FFBReport_SetEnvelope_Output_Data_t*, volatile TEffectState*)':
ffb_pro.ino:399: warning: unused variable 'eid'
ffb_pro.ino: In function 'void FfbproSetCondition(USB_FFBReport_SetCondition_Output_Data_t*, volatile TEffectState*)':
ffb_pro.ino:418: warning: unused variable 'eid'
ffb_pro.ino: In function 'void FfbproSetPeriodic(USB_FFBReport_SetPeriodic_Output_Data_t*, volatile TEffectState*)':
ffb_pro.ino:432: warning: unused variable 'eid'
ffb_pro.ino: In function 'void FfbproSetConstantForce(USB_FFBReport_SetConstantForce_Output_Data_t*, volatile TEffectState*)':
ffb_pro.ino:454: warning: unused variable 'eid'
ffb_pro.ino: In function 'int FfbproSetEffect(USB_FFBReport_SetEffect_Output_Data_t*, volatile TEffectState*)':
ffb_pro.ino:502: warning: unused variable 'eid'
ffb_pro.ino:520: warning: unused variable 'is_periodic'
ffb_pro.ino: At global scope:
ffb_pro.ino:369: warning: 'void FfbproSendEffectOper(uint8_t, uint8_t)' defined but not used

Thank you!

I could not find the errors from my code, the warnings can be ignored, they are function allocations and unused variables, but the other errors I did not understand, it seems something like a compiler problem, maybe different version. Which IDE are you using? Are you using the core version 1.0.5?
I use the "visual studio 2017 community" with visualmicro extension to develop it.
If you use a different IDE tell me, I will try to reproduce the same error.

[Edit]
I could reproduce the error in the Arduino IDE, I dont know why, but it created a strange character at the beginning of the ConfigHID.ini file, just delete the character before the "#" solved here.

can anywhone confirm is fix the dead zone of center wheel ?

how many pulses does your encoder have ?

actually is EMRON 1000 ppr but i wait new encoder 5000 ppr

that is plenty of pulses - does your motor have magnetic resistance when you turn it with no power

umh...any suggestion ?