Видео

@@LukiPigna18 hola gracias, en el video muestro la placa originaria de OpenFFBoard, basada en el STM34F407xxx, también como driver para el motor estoy usando VESC mini 4.20, un motor de hoverboard y encoder magnético MT6835, actualmente es lo q uso el día a día en el simulador jejeje

@@blessingmwewa8529 I don't remember well, but if I remember correctly, odrive and odesc are not identified the same way. I'm sure that by the time I'm answering you've already managed to connect to it, but it takes a process to make it possible for you to be able to make the configurations; it's good that you join the OpenFFBoard discord and enter the odrive room there we will answer faster and more efficiently. Discord ID:704355326291607614 LINK: discord.gg/openffboard-704355326291607614

@@subary5056 Yes, in both, but my recommendation would be that you use ODESC with FFBeast, since all the programming in odesc to use it in EMC or OpenFFBoard the configuration in CMD is a bit complicated, you have to configure each parameter independently

​@@GinjersonAbreuyou can ask what to do to protect the PSU, although there is a brake resistor connected to odrive

@@subary5056 To be honest, the least option is the braking resistor, it comes specifically for its purpose, but if possible you can change it for one with more capacity, this way you will avoid overheating, and the other option is to place a rectifier diode at the PSU output, positive line, remember that the capacity of this diode will be according to your current, for example if your constant current is 15A then it is best to put 20A or 25A, remember to increase from 25% to 50% of the capacity in that case, the reason is to avoid heating or in its worst scenario burn the diode, remember that there are also current peaks, which sometimes can reach up to 100% above the constant, ah, the rectifier diode will prevent in a certain way a return of voltage to the PSU, in combination with the braking resistor in the Odesc is a good option, there are other external options which are not controlled by software as in odesc, but for now with odesc alone it is enough, you just adjust the load what do you need for braking in FFBeast if that's what you use. regards.

@@GinjersonAbreu Thanks for the answer, but can I see your odrive settings?

hello, I've set up odrive, everything is connected and it works in emc, but for some reason, in ac, ffb works in the center, everything is fine, but you turn the steering wheel and there's just a spring there​@@GinjersonAbreu

@@subary5056 I could help you with that, but I'm short on time right now, so I suggest going to the Discord of these authors, you'll get a lot of help and answers, since they're always active; you can search on Google or RUclips for: FFBeast and OpenFFBoard, you'll get the links to enter their discords.

@@subary5056 Yes, in both, but my recommendation would be that you use ODESC with FFBeast, since all the programming in odesc to use it in EMC or OpenFFBoard the configuration in CMD is a bit complicated, you have to configure each parameter independently

@@dashensingh6823 greetings broth, I tell you that you should not have any type of problems with the rotation in FFBeast, as long as you follow the configuration to the letter, I have some odesc working and the only difficulty is the PPR of your shrink, knowing how to calculate them when entering the information in the ffbeast app, the normal thing is that if your shrink has a resolution of 8192 you multiply that value x4 and the result is what you are going to place in the corresponding box, in any case if you do not know the resolution, you configure the turn to 360 degrees and from the intermediate point of the wheel, whether left or right, you turn it has to stop exactly at 180 degrees on both sides, if the ppr value is higher you will see that the wheel will lock and will continue to turn equally if the ppr is lower, so then you have to play with that value until you have the correct result.

@@Ameen-v8f The solution I got was to use the logiteth g27 drivers, it is the unique software of the g27, then in the gimx configurator map all the buttons and turns, selecting g27 for PC in the emulation list that is in the same configurator.

​@@GinjersonAbreuThis is my alt account I could not explain how thankful I am it was the only issue that was affecting me you are a legend thank you so much ❤️

@@cristianscarfi utilizo este controlador de motor: flipsky.net/collections/v4-series/products/mini-fsesc4-20-50a-base-on-vesc-widely-used-in-eskateboard-escooter-ebike Y también FFBoard para la gestión de efectos ffb con una resistencia de carga junto al módulo hecho por la misma comunicada que se encuentra en el discord de FFBoard.

@@christianendara3200 hola, la verdad que no es algo para perderse, en el Discord de FFBeast está todo documentado, puedes integrarte, pero un adelanto, solo es conectar el motor al ODESC y el ENCODER al mismo, calibrar con la aplicación FFBeast y listo, pero entraras en calor cuando visites el Discord. Gracias por tu comentario, saludos desde República Dominicana.

@@GodWhipping muy pronto estaré haciendo uno pequeño, pero el esp32 le he cargado el código para Ble-gamepad, hay muchos tumorales en RUclips sobre el mismo.

@@rochacxbob Hi friend, there are many videos on RUclips explaining how to create it, it is very easy.

@@LaNonni You can use a GIMX adapter, which you can build yourself, or use the Emuwheel software, all the details about each can be found on RUclips!

@@zero-zs4mg No, OpenFFBoard…!

@@Raimundoraimundo1992 es simple, un ESP32 con una batería 18650 y un módulo de carga para el, y conectado por la entrada de 5v, el modulo de carga que utilizo es de un powerbanck.

600 is more than enough for DIY wheels!

@@SHADOWLEGENDDRAWS I Use this: MT6825 PWM/SPI, a.aliexpress.com/_mqSxqEs

@@SHADOWLEGENDDRAWS I Recommend it.!!

Hello, I saw a message from u before, I thought I responded to it; but regarding this, the truth is that I would have liked to make an explanatory and uncut video at the time, the truth is that currently I have completely switched to FFBeast and OpenFFBoard, so I invite you to try using FFBeast with your ODESC in Its improved version is much more comfortable and easier, with that topic I would be happy to help u if you need it.

It doesn't work that way, it is linked to the processor Id, you have to install the EMC, then it generates an Id and you send that Id to the developer so that he can then send you the .Lic file

@@GinjersonAbreu thank for reply..god bless and more fun diy..keep sharing..always watching

Well, I can say that to do it, you have to program the odrive or odesc independently of everything, just with the motor, configure the parameters and adjust them according to the need of the motor you are using, the voltage used, the braking resistor that you are using in at the moment, make calibrations together with the encoder until everything is correct, but no less important, make the adjustments for each parameter carefully so as not to damage the board, it is also necessary to adjust the CAN BUS for its operation with EMC which goes hand in hand to use it With the STM32F407VET6, where you will load the EMC Firmware, it is easy to work with the EMC application, but with the control board for the motor, you have to spend time until you understand its operation well and know what each command used is for, and so on. do not abuse them. I hope I can help you in some way with the information.

To be honest, that face has already passed into history, it is better to invest in a controller like Odrive or Odesc 4.2, I recommend forgetting the hoverboard controller.

Pues es fácil, EMC te da el plano donde detalla todo para hacer las conexiones, Qq utilizar y etc. Gracias por su comentario.

@@GinjersonAbreu Ya he mirado el esquema, pero soy muy malo con el tema eléctrico y no me aclaro del todo. Pero entiendo que básicamente es pasar la señal pwm al driver odesc. O algo parecido. Y así poder utilizar la stm32f401 con la v1.08 y el programa EMC pro

@@rc-simracing no, realimente necesitas un CAN BUS, lo adquieres en eBay, no recuerdo el modelo, pero el esquema te muestra el modelo, solo sigues las líneas de conexiones, podrías escribirme priv a mi ws y te oriento mejor, si ya tienes todo entonces será más fácil; Ws: +1 829-966-9544

my. or figuration is simpler than you think, I have everything in pro, without driving aids, brakes or anything to see aids in the game, active ABS and driving mode in simulation, then the FFB is a configuration recommended in some video of RUclips, one that is related or similar to the steering wheel you are using, whether DD or with Pulleys; Also play with its parameters so that you understand the effect that each parameter causes and put it to your liking. thank you for your comment.

Hola! Gracias, honestamente puedo ofrecerte una lista de lo Qq he utilizado, dime que quieres saber exactamente y te puedo especificar, también puedo recomendarte un una comunidad donde puedes nutrirte de sus ideas, proyectos y sabiduría, también el creador ofrece todo lo necesario para manejar el software lo cual es gratis, el hardware que es de paga, pero si quieres un poco más de menor costo también tienes otras opciones. Este es tu enlace de invitación a OpenFFBoard: discord.gg/openffboard-704355326291607614

Can I use any similar board except odrive or mks ?. Because this boards are not available in India locally.

Hello, to be honest, I no longer use Odrive, but the information necessary to start using Odrive and program the parameters necessary for the operation of the engine can be found on the Odrive page, after all to make the connections and learn a little more about EMC, it would be to contact the creator of EMC to buy his product if you don't have it yet and in the same obtain the necessary documents, you can also visit the OpenFFBoard discord, the guys there will help you without problems, you will also get everything which is software for your project (free), if you have Odrive you go to the Odriver-support channel; last recommended option! discord.gg/invite/openffboard-704355326291607614

Sorry for insisting but could you just mention the links in this video you posted please?

@@Kleberdasnevesoliveira-ye3tt facebook.com/EMCDeveloper?mibextid=LQQJ4d

@@GinjersonAbreu hey u mentioned u are no longer using o drive did u change board of u pulled out of the project

@@emiljanduka51 I changed from odesc to the Vesc, for the reason that it broke down while playing ATS, the micro controller melted inside, now I use the Vesc, always active without problems; active project, you can see some recent videos. hanging from the canal.

To control the brushless motor use a Flipsky Vesc 4.12 mini controller and the signal is via CAN BUS. thank you for your comment.

Hello, I'm sorry for the delay and I'm sorry to say that I don't have a guide for the process, the truth is that everything was on the fly, trial and error, but I can say that the guide to configure your Odrive on your engine is knowing the specifications of your engine . , adjust the parameters in odrive so that everything is fine and then connect the odrive with STM32 via can bus, you can get a complete guide to adjust the parameters in odrive together with the can bus on the official ODRIVE website, it is easy after that you understand every point.

Well, I can give you some idea since I don't remember well, it has been a while since the last time I used Odrive together with EMC, now I use VESC, but in the EMC guide for STM32f407vet you will be able to see the CAN BUS pins, which are PB8/PB9. They connect directly to the CAN Module and the pins that connect to the Odrive, it is simple when you have it in a graphic, EMC on FB can give you the updated guide by accessing Google Drive, you can download everything and there you will find what you need, I hope I have helped in some way, If even after 6 days of delay due to not responding you have not managed to make progress.

Well, I can give you some idea since I don't remember well, it has been a while since the last time I used Odrive together with EMC, now I use VESC, but in the EMC guide for STM32f407vet you will be able to see the CAN BUS pins, which are PB8/PB9. They connect directly to the CAN Module and the pins that connect to the Odrive, it is simple when you have it in a graphic, EMC on FB can give you the updated guide by accessing Google Drive, you can download everything and there you will find what you need, I hope I have helped in some way, If even after 6 days of delay due to not responding you have not managed to make progress.

@@GinjersonAbreu oh, thank u

Hi, AMT103

@@syafiqzainal2174 hey, i use this now:: MT6825 PWM/SPI, a.aliexpress.com/_mqSxqEs

I don't remember the version used at that time, but it was the most recent, the one indicated in the instruction manual.

@@GinjersonAbreu thanks . I have now force feedback . But index Z not work yet. I vill see again. But thanks

Can you post your Vesc config? @@GinjersonAbreu

@@lubl5631 I would gladly do this if the settings were universal, but it wouldn't be possible for you to use my conf since each motor and voltage you use is a different setting and parameters.

do you have encoder connected directly to wheel because i cant get good results of FOC @@GinjersonAbreu

Sorry for the delay, I hope you have had a solution at this point, but for this you must consider that the encoder has a Z point, if it is well connected, then you will be able to see its movement in the Vesc application, for this you have to activate the viata option in real time, I hope you are already familiar with it, there you will see how the line moves as you turn the steering wheel, every time you turn the vesc off and on the Z point resets and you have to get it manually, a suggestion before To assemble everything completely, it would be good for you to know where the Z is and place it in the center of your steering wheel.

Amigo tienes WhatsApp, me podrías hacer el favor de regalarme el diagrama

😍

hola, de donde eres? -respondiendo a tu pregunta, la utilizacion del encoder fue algo complicado, pero su coneccion es directa al VESC, EN ESE MOMENTO estuve utilizando un ENCODER de impresora y para solucionarlo tuve que mandar un pulso negativo al pin Z ya que no viene con PIN Z el ENCODER de impresora, y asi encontrara el centro, eso cada vez que encendia el equipo, por eso estaba dando un resultado invertido.

Hello, first of all I would like to know if you have managed to configure ODESC or ODRIVE, since the correct operation of it depends on that, then make it work with EMC, it is only to select the last option in configuration and driver, which is ODRIVE, and if If you use ENCODER together with CAN BUS, mark ENCODER otherwise, if you use ENCODER in the STM32 do not mark, remember that you must learn ODRIVE first then everything will be easier.

@@GinjersonAbreu do you have this odrive programming saved? In fact, I've never used ODrive, but I know that in terms of values it's more affordable than VESC.

@@GinjersonAbreu do you have project update?

​@@1djval I can tell you that I have the configuration, but the configuration in all cases is individual, it is more complex even in the VESC, since everything is manual, believe me, it is not to discourage you but it took me time to understand many parameters since it was there by then very pine. but I can tell you something, is that ODRIVE for some reason stopped working at a time when I was playing ATS, and then it never did anything else, it didn't connect either, I totally lost it, but if you insist on wanting to use ODRIVE I can recommend a developer that it already has everything fine to use, but only with its software, otherwise I can help you with many things if you decide to use VESC, it is what I am using and it works great for me, of course at the hardware level it is almost as complicated as the ODRIVE in its manual programming, but in the end everything is fine.

@@1djval I'm still in the aesthetic phase, it's all the same that is presented in the videos but with the exception of the ODRIVE, it's gone, now it's a VESC.