So I’m having 2 new issues, with an old controller. I’ve been building my monster kinda slowly (I’m a broke !@# ski lift mechanic.) Trying to run a Gremsy t3 v2 via sbus out from a standard carrier board. Serial 5 is reading full sbus, but only with a servo lead barely touching the pins. If you push it onto the pins, all signal is lost. This is the second bird this cube has been on, with hours and hours of successful, well tuned flight. The maiden on my heavy lift octa, was scary.
Tried with the servo rail powered via a Mauch power system Hybrid bec 5v, and unpowered. Testing with a ISDT BG-8s, and the gimbal software. Symptoms are consistant. So I just ran a sbus splitter from my X8r. I can control my gimbal, but my flight controller can’t.
My second issue is I randomly can’t flash firmware now. At first the cube was registering as an Omnibus f4. Windows 10 pro, so not my first driver issue by far… finally got it registering as an STMicro virtual com port. But on firmware flash, the board doesn’t reset, and reconnect. No response from board error. Tried 3 different computers, with different windows versions. Same issue. Yet, I can connect, and do anything else.
Honestly, my gen 1 pixhawk clone is far more reliable thus far. Is my cube dead?
I’ve tried the silabs drivers numerous times. windows vista is the only OS i have gotten to connect, and flash right. i can now load parameters, but it will not save any changes made. ive lost all my contracts, and my company is now in jeopardy. I’m seriously debating removing my cube entirely. I need consistency in my equipment. i cant say i can trust this fc anymore.
No, connection is a direct usb cable. I’ve tried several functional leads for sbus out. I’ve tried with the servo rail powered, via a mauch electronics 5v out. Power isn’t the issue. It’s bad signal pins in the board. I’ve been flying pixhawk flight controllers in multiple airframes for years. Side note, you can’t flash firmware over a sik radio connection anyway, so why would I try that?
As I have stated. It loses connection, it is in fact not broken, just not functioning. Maybe actually read the posts, and address the issues addressed, instead of assuming things. As a Chemical, biological, radiological, and nuclear ops specialist, I am in fact, not an idiot. I have tested your companies hardware, and found a layes in your PCB that is has a bad trace. That, is a failed product, and NOT “broken”.
Please actually address the issue.
Take responsibility for your product.
Please make up your mind as to what you are? If you would like to constructively engage in the community, that would be great! Each of my comments back to you was an attempt to assist you, I have posted three times now to RMA it. who is your distributor?
If you are from Paladin as you claim, then why the “i’m a broke ski lift mechanic” story?
me taking responsibility… RMA the equipment…
Where did you get the cube?
the SIK comment… two things, that was a cross post… and yes you can update firmware via a serial connection if you have all day…
My deepest apppgiea I got blown the hell up in combat, and was medically retired. So I am in fact, still a CBRN, however, due to a military discharge, I’m not active military. So I became a ski lift mechanic, but my destroyed body, I couldn’t hack it. So I opened Paladin UAV almost 2 months ago. Also, all firmware across the board, is current as of thursday the 29th. I’ll get screenshots, and a video of the issue when I return home.
All firmware is current. Working with gremsy to see if control over mavlink is even possible. Thus far, mavlink just locks the gimbal up. SBUS is the only control responding. How do we get this RMA ball rolling?