VBar Control - Hobbywing Integration
Posted by R@VBar
|
March 30, 2020 09:30AM |
Hi zusammen, hi Andy,
ich finde es jetzt frech, wenn HW Kunden sagt, das sei nicht ihr, sondern Mikados Problem.
Sie haben in sofern recht, dass wir die App für die Classic noch machen müssen, aber durch ihren vorzeitigen Firmwareergu- Release _ohne_ irgendeine Absprache (kommt mir vor, wie während fast der ganzen Entwicklung ...) lassen sie uns jetzt blöd da stehen.
Vielleicht die Retourkutsche, dass wir immer gesagt, haben, der Ball ist in HW's Spielfeld (war er ja auch, aber sie haben das Spiel jetzt eben einseitig für beendet erklärt).
Mal abgesehen von den Problemchen, die Frühupdater zu haben scheinen, was man so im Netz liest.
Also, kommt Zeit, kommt App. Wir werden Euch sicherlich nicht hängen lassen, aber es muss halt noch ein paar Tage, eher Wochen länger so gehen wie 'bis gestern' ... was ja auch ging
//
I find it bold of HW to tell customers, it's not their but Mikado's problem.
They are right in a way that we still have to make the App for the Classic, granted, but by their premature firmware-eja... release _without_ any accord (seems to me: like during the whole time of development) they make us look as if we didn't get the thumbs out of our butts.
Maybe this is tit for tat, for us repeating the ball was in their field (which it was, but now they declare the game closed unilaterally).
Not to speak of the issues early updaters seem to have, according to posts on the net.
So, the App will follow once it's ready. We won't leave you out int the rain, but for now it has to work as it did until now, for the next couple of days, more like weeks.
— Eddi
Born to fly ...
forced to work.
ich finde es jetzt frech, wenn HW Kunden sagt, das sei nicht ihr, sondern Mikados Problem.
Sie haben in sofern recht, dass wir die App für die Classic noch machen müssen, aber durch ihren vorzeitigen Firmwareergu- Release _ohne_ irgendeine Absprache (kommt mir vor, wie während fast der ganzen Entwicklung ...) lassen sie uns jetzt blöd da stehen.
Vielleicht die Retourkutsche, dass wir immer gesagt, haben, der Ball ist in HW's Spielfeld (war er ja auch, aber sie haben das Spiel jetzt eben einseitig für beendet erklärt).
Mal abgesehen von den Problemchen, die Frühupdater zu haben scheinen, was man so im Netz liest.
Also, kommt Zeit, kommt App. Wir werden Euch sicherlich nicht hängen lassen, aber es muss halt noch ein paar Tage, eher Wochen länger so gehen wie 'bis gestern' ... was ja auch ging
//
I find it bold of HW to tell customers, it's not their but Mikado's problem.
They are right in a way that we still have to make the App for the Classic, granted, but by their premature firmware-eja... release _without_ any accord (seems to me: like during the whole time of development) they make us look as if we didn't get the thumbs out of our butts.
Maybe this is tit for tat, for us repeating the ball was in their field (which it was, but now they declare the game closed unilaterally).
Not to speak of the issues early updaters seem to have, according to posts on the net.
So, the App will follow once it's ready. We won't leave you out int the rain, but for now it has to work as it did until now
, for the next couple of days, more like weeks.
— Eddi
Born to fly ...
forced to work.
|
April 04, 2020 11:05PM |
|
Re: VBar Control - Hobbywing Integration April 15, 2020 12:54AM |
Avalable for old VBC
Many THX
Many THX
|
April 15, 2020 11:24AM |
|
April 15, 2020 02:01PM |
|
April 15, 2020 02:25PM |
|
April 15, 2020 02:30PM |
|
April 15, 2020 03:09PM |
|
April 15, 2020 03:38PM |
Hi,
since Battery ID is a must have (in my opinion ;-) on helis where it fits, that would be the way to go.
Reason why it could not work properly alone is, on legacy VBars, we are using the Spektrum Satellite ports, which were designed as ... receiver inputs, with the required circuit and electric requirements. They are a design from 2012 and before after all.
Our telemetry items are designed in a way so they act per our own specs—same specs which we also provide to parties like YGE, Scorpion, Kontronik, HW.
Now comes the 'but' ... they do their own thing, use or abuse their own hardware and connectivity, means, there could be technical reasons why it does not/properly work with legacy VBars (at least with existing ESCs, only updated), or shortcomings in the implementation of the specs.
If you do new hardware, like YGE, Scorpion, Kontronik with TelMe module and their latest ESCs, you can make it work (but still there may be shortcomings).
If you only do software for existing hardware, like HW, you might have to live with the hardware at hand ... benefit for the customer, no new ESC required, just an update, but also possible downside, if it has limitations.
If you connect a 'shaky' device to a Mikado Sensor, that sensor can improve the signal to the VBar (also: legacy VBar), like it will most likely work on a VBar NEO, where the former or combined Telemetry/Spektrum Sat ports are designed differently.
Bottom line, you can go NEO, you can use a different sensor as a signal relay/enhancer in between, or you have live with it the way it was before ... sorry for that ... but at least it didn't cost you money, and the ESC didn't go bad either, just so you can still fly.
Cheers
Eddi
Born to fly ...
forced to work.
since Battery ID is a must have (in my opinion ;-) on helis where it fits, that would be the way to go.
Reason why it could not work properly alone is, on legacy VBars, we are using the Spektrum Satellite ports, which were designed as ... receiver inputs, with the required circuit and electric requirements. They are a design from 2012 and before after all.
Our telemetry items are designed in a way so they act per our own specs—same specs which we also provide to parties like YGE, Scorpion, Kontronik, HW.
Now comes the 'but' ... they do their own thing, use or abuse their own hardware and connectivity, means, there could be technical reasons why it does not/properly work with legacy VBars (at least with existing ESCs, only updated), or shortcomings in the implementation of the specs.
If you do new hardware, like YGE, Scorpion, Kontronik with TelMe module and their latest ESCs, you can make it work (but still there may be shortcomings).
If you only do software for existing hardware, like HW, you might have to live with the hardware at hand ... benefit for the customer, no new ESC required, just an update, but also possible downside, if it has limitations.
If you connect a 'shaky' device to a Mikado Sensor, that sensor can improve the signal to the VBar (also: legacy VBar), like it will most likely work on a VBar NEO, where the former or combined Telemetry/Spektrum Sat ports are designed differently.
Bottom line, you can go NEO, you can use a different sensor as a signal relay/enhancer in between, or you have live with it the way it was before ... sorry for that ... but at least it didn't cost you money, and the ESC didn't go bad either, just so
you can still fly.
Cheers
Eddi
Born to fly ...
forced to work.
|
April 24, 2020 05:52PM |
Sorry, only registered users may post in this forum.