Acompanhei seu desenvolvimento no xsimulador , e aqui no TH-cam! Parabéns pelo trabalho ficou incrível ! Queria muito que esse vídeo tivesse uma resolução um pouquinho melhor pois não consegui ver muito!
Thanks for sharing this information, it's incredibly helpful! I was curious about the Linux/Windows interface though. Do you run FlyPT Mover in the Linux VM, and play your game on Windows? How do the two talk to each other? Or is the VM only for the configuration of the ODrive? Thanks for the info!
@@stijnsprojects Brilliant! It is definitely a bit of a slog on windows, I am finding. Luckily I had installed a bunch of Python stuff earlier for school so the odrivetools setup was easy for me. THAT SAID your method looks nice and snappy so I will most definitely be doing this. Thank you again!
Great stuff Stijns I couldnt even work out how to compile the FW didn't even think of using a VM excellent idea. Have you tried the new GUI to setup the official new FW ?
Thanks, at first I used windows but it was such a pain go get everything installed, Linux is way better for this and not everyone can set up a second machine with Linux so VM is the way to go in my opinion also because you can switch between Linux and Windows when needed. I've not looked into the GUI yet.
why do you divide the ascii input code by the encoder cpr? from my understanding if flypt sent 511(middle bit) to your odrive it would go to 511/1600 turns? how to you accomodate the turns to length travled for an actuator? from the scale function? but if thats the case u cant even make a full turn if you at 10 bits and with linear actuators that doesnt make sense.
I did that because when I made mine, the units were different so I wanted to keep it the same. There are multiple ways to achieve the same functionality such as multiplication or division by a factor in firmware, using a microcontroller to change the value, maybe even multiplying or dividing by a factor in flypt. There have been many updates to the firmware and flypt since I made my sim.
In video you mention that position bit output in FlyPT "rig" module needs to be 18bit. How did you get the rig move in wider range if you use 18bit? I just get my rig works (thanks for the video) and now I am setting up FlyPT.
In the old firmware the USB move command were encoder pulses, in the new firmware, these are rotations, that's why I show in the video how to change the firmware that it's encoder pulses again.
@@stijnsprojects I do that firmware modification also. Or least I try because I had problems to get odrives connected to VM ware and ubuntu. First it works well, but after some time Ubuntu stops to recognize odrives or any usb device. Tried to figure it out but didn´t manage to do it. I made modificated hex file and then flash the odrives with windows. Are you sure that that is the only reason for my limited move problem with 18bit and I didn´t manage to do firmware modifications properly? Do you know is there any problems to use 19bit´s?
Hello, I'm not sure if I understand correctly but you can set min and max in flyptmover, you can find the information on the website or forum posts on xsimulator.net
Jij komt uit Nederland zie en hoor ik 😅? Toevallig in de buurt van Nijmegen? Ik ben ook al een tijdje bezig met een odrive 6 dof flypt mover rig. Goeie tutorial stukken beter dan die van silent chill ^^
België, het is niet makkelijk om hier een tutorial over te maken aangezien er altijd veel veranderd, maar ik hoop toch dat ik een aantal mensen hier al een berg werk en frustratie mee kan besparen.
@@stijnsprojects Ja mij is het idd met heel veel frustratie gelukt uiteindelijk en nog steeds een hoop issues hoor. Die odrives zijn zo complex.. En flypt is nog eens een heel stuk complexer wil je echt alle details goed instellen. Ben er maanden mee bezig geweest en nog steeds zijn mn settings vere van perfect... 😒. Maar ik geef niet op ^^
I have not watched yours but I know it's hard to make a tutorial about this, so many things change and in some way it's different for everyone, I just think that the more videos there are about this topic, the more people will figure it out
This is what everybody was waiting for, thanks!
No problem! Complete overview video coming soon.
Acompanhei seu desenvolvimento no xsimulador , e aqui no TH-cam!
Parabéns pelo trabalho ficou incrível !
Queria muito que esse vídeo tivesse uma resolução um pouquinho melhor pois não consegui ver muito!
Thanks for sharing this information, it's incredibly helpful!
I was curious about the Linux/Windows interface though. Do you run FlyPT Mover in the Linux VM, and play your game on Windows? How do the two talk to each other? Or is the VM only for the configuration of the ODrive? Thanks for the info!
The Linux VM is only for setting up the ODrive because it's a struggle in Windows, so Flyptmover and the game are both running on Windows
@@stijnsprojects Brilliant! It is definitely a bit of a slog on windows, I am finding. Luckily I had installed a bunch of Python stuff earlier for school so the odrivetools setup was easy for me. THAT SAID your method looks nice and snappy so I will most definitely be doing this. Thank you again!
@@stijnsprojects Are you on the X-Sim discord? I was wondering if I could ask you some questions about building the firmware.
Great stuff Stijns I couldnt even work out how to compile the FW didn't even think of using a VM excellent idea. Have you tried the new GUI to setup the official new FW ?
Thanks, at first I used windows but it was such a pain go get everything installed, Linux is way better for this and not everyone can set up a second machine with Linux so VM is the way to go in my opinion also because you can switch between Linux and Windows when needed. I've not looked into the GUI yet.
Eu tenho que fazer essa configuração pra cada porta USB ?
why do you divide the ascii input code by the encoder cpr? from my understanding if flypt sent 511(middle bit) to your odrive it would go to 511/1600 turns? how to you accomodate the turns to length travled for an actuator? from the scale function? but if thats the case u cant even make a full turn if you at 10 bits and with linear actuators that doesnt make sense.
I did that because when I made mine, the units were different so I wanted to keep it the same. There are multiple ways to achieve the same functionality such as multiplication or division by a factor in firmware, using a microcontroller to change the value, maybe even multiplying or dividing by a factor in flypt. There have been many updates to the firmware and flypt since I made my sim.
the make all command doesnt do anything for me, do i need to have the stlink currently connected?
You probably didn't install the required packages.
Are all Flypt games compatible with 6 dof?
In video you mention that position bit output in FlyPT "rig" module needs to be 18bit. How did you get the rig move in wider range if you use 18bit? I just get my rig works (thanks for the video) and now I am setting up FlyPT.
In the old firmware the USB move command were encoder pulses, in the new firmware, these are rotations, that's why I show in the video how to change the firmware that it's encoder pulses again.
@@stijnsprojects I do that firmware modification also. Or least I try because I had problems to get odrives connected to VM ware and ubuntu. First it works well, but after some time Ubuntu stops to recognize odrives or any usb device. Tried to figure it out but didn´t manage to do it. I made modificated hex file and then flash the odrives with windows. Are you sure that that is the only reason for my limited move problem with 18bit and I didn´t manage to do firmware modifications properly?
Do you know is there any problems to use 19bit´s?
I'm not sure, 18 is what worked for me but my project is already a few years old.
Hello, can you make a video on how to set safe min/max platform movement in firmware. thx
Hello, I'm not sure if I understand correctly but you can set min and max in flyptmover, you can find the information on the website or forum posts on xsimulator.net
@@stijnsprojects yes it can be set in flypt but you can also set the safe feature in the firmware (configuration).
Jij komt uit Nederland zie en hoor ik 😅? Toevallig in de buurt van Nijmegen? Ik ben ook al een tijdje bezig met een odrive 6 dof flypt mover rig. Goeie tutorial stukken beter dan die van silent chill ^^
België, het is niet makkelijk om hier een tutorial over te maken aangezien er altijd veel veranderd, maar ik hoop toch dat ik een aantal mensen hier al een berg werk en frustratie mee kan besparen.
@@stijnsprojects Ja mij is het idd met heel veel frustratie gelukt uiteindelijk en nog steeds een hoop issues hoor. Die odrives zijn zo complex.. En flypt is nog eens een heel stuk complexer wil je echt alle details goed instellen. Ben er maanden mee bezig geweest en nog steeds zijn mn settings vere van perfect... 😒. Maar ik geef niet op ^^
Jullie gebruiken niet silentchills firmware? Is daar een reden voor?
Sorry that you feel my tutorial was not helpful, I tried my best ............. im joking BTW :)
I have not watched yours but I know it's hard to make a tutorial about this, so many things change and in some way it's different for everyone, I just think that the more videos there are about this topic, the more people will figure it out