Anybody who's built the kit.. is PLA strong enough to print with? Or should the parts be made of ano
Anybody who's built the kit.. is PLA strong enough to print with? Or should the parts be made of another material
RIf you mean the gimbal? PLA will last a few months, but will eventually fail (in many areas). I have just reprinted in PETG and it definitely seems like it will last much, much longer (if not forever).
GExcellent. Thanks.
HIs there a 3D printed box for the base instead of doing it out of wood or sheet metal??
HDisregard, I found Walmis .step files for the 8mm ply. This can be tried with a 3D print as well.
GThose of you who built the kit... what should I use for a power supply?
S350.4W 24V 14.6A Single Output Switchable Power Supply 24 Volts 14.6 Amps Features • AC input range selectable by a switch • Withstand 300 VAC surge input for 5 seconds • No load power consumption • 1U low profile • High operating temperature, up to 70°C • Protections: Short circuit / Overload / ...
G
GGot everything coming together slowly. Can't wait
YSlowly is the word. That will make it taste that much better, right?
Yat least that's my hope 
AThe !info command appears to not give a response anymore btw
A(At least for my email)
FWorking for me
WFixed!
SHaving what I hope is a stupid me issue, but my TM Warthog grip seems to only register the trigger and it lights up everything in the VPForce software. Yes, I've verified it's plugged in correctly (tried both extension cable, and directly to the grip) and verified the buttons work by plugging it back into it's old base. I ran the debugging profile too and it just spammed the FF line with button trigger presses showing 00 00 repeating. This is NOT using the passthrough port you installed, was trying to just use the native interface. I also tried power cycling/unplugging USB. Everything else seems fine and during a test flight the base functioned as expected.
SShort logfile capture if relevant.
samples.csv1.61MB
WWe figured out that the USB voltage on the hub was too high - 5.6V, hence the grip didn't register the 3.3V signaling correctly. When plugged directly into PC it works correctly.
STo build on this, I believe this hub was previously faulty its not an issue with the Rhino or hubs in general. I was just running out of shit to plug shit into.
PIf anyone can help out with the install process for the DCS Telemetry app that'd be cool. I have python installed & the .zip file downloaded from Walmis's github but I'm lost as to what to do with the cmd prompt stuff, I'll be online for a while if anyone is keen to help? Cheers
W- open up windows explorer, navigate to the source files.
- Hold shift and right click on a blank area
- Click
open powershell here - enter
in powershell promptpip3 install -r requirements.txt - and then
python main.py
P
Pright clicking in this window & typing in the powershell window "pip3 install -r requirements.txt" gives me an error
P
Wtry pip instead of pip3
Pok
Palright, looks like for some reason the installer for python that I got from their site didn't install correctly for this to work, instead I did what Skypickle told me to do in cmd type python & it lead me to windows store, once I did the python install again through the store this time the commands you gave me worked
DI haven't read everything but, would it not be possible to add the base in the simshaker software?
It would be easier then to make profil with different effect
It would be easier then to make profil with different effect
WNo, it's not that simple
POk Walmis what next? Do I put the export .lua file just in the DCS.openbeta folder? or is it in a specific folder?
DBecause of them not wanting you to do it or because of the way the effect is generated being different
DI mean, with a soft between the simshaker app and the base translating app input to input that apply on the base
DIt couldn't?
WYeah, simshaker is very simplistic at it's core and the logic of the control is very different
DSo no way to translate those input into rhino input?
DOr making a similar app for the rhino maybe?
WThat app above is that exact thing 
Wjust run
python main.py
VYep app is great, the only downside is having to run so many apps and exports in the first place for something that should be working natively in the sim
WI'll try integrating auto launch inside the lua script
VAnd as winwing has shown us the exports can greatly impact performance if done wrong, luckily Walmis' script seems to have little to no impact which is great
Pyou mean that one?
Wya
SBTW, I installed npm for windows, built teleplot, got it running, with this showing in the cmd window:
STeleplot server started
Open your browser at 127.0.0.1:8080
Send telemetry with a "key:value" UDP packet to 127.0.0.1:47269
Example:
BASH: echo "myData:1234" | nc -u -w0 127.0.0.1 47269
Open your browser at 127.0.0.1:8080
Send telemetry with a "key:value" UDP packet to 127.0.0.1:47269
Example:
BASH: echo "myData:1234" | nc -u -w0 127.0.0.1 47269
SI opened a browser then started DCS.
STelemetry started appearring in the TelemFFB window
SBut teleplot was not doing anything
SThe TelemFFB cmd showed this:
S2023-02-01 12:22:47 - INFO - Open Rhino HID FFFF:2055
2023-02-01 12:22:47 - INFO - Using 127.0.0.1:47269 for plotting
2023-02-01 12:22:47 - INFO - Listening on UDP :34380
2023-02-01 12:25:16 - WARNING - Aircraft definition not found, using default class for AH-64D_BLK_II
2023-02-01 12:25:16 - INFO - Creating handler for AH-64D_BLK_II: <class 'aircrafts.Aircraft'>
2023-02-01 12:22:47 - INFO - Using 127.0.0.1:47269 for plotting
2023-02-01 12:22:47 - INFO - Listening on UDP :34380
2023-02-01 12:25:16 - WARNING - Aircraft definition not found, using default class for AH-64D_BLK_II
2023-02-01 12:25:16 - INFO - Creating handler for AH-64D_BLK_II: <class 'aircrafts.Aircraft'>