Nice idea with the BL-temp.
What if it will not shown as value all the time, but as a setable threshhold is reached some warning might be shown.

CaScAdE meinte

FrankT meinte

Is it possible to get a BL-Ctrl temperature on the OSD
(one is enough )

Possible of course.
But the overhead would be quite huge.
And: I do not have any BL-Ctrl that supports Temperature, so I cannot test the stuff.

The Temperatures are shown somewhere in the Navi-LCD, right?

No in FlightCtr [15]

/Frank

CaScAdE meinte

The Temperatures are shown somewhere in the Navi-LCD, right?

Das scheint nicht im Abo zu stehen - geht also nicht ohne besonderen FC-Patch...

mabomiko: Nicht im Abo, aber man kann ja das LCD abfragen und parsen... Auch das von der FC.... Aber das wird umstaendlich...

Frank: We could get the data by parsing the FC-LCD-Stuff, but we would have to swtich the NC-Debug port to forward stuff to the FC, get the LCD-Page, switch back and re-request the normal OSD-Data again. That would cause a lott of lagg... I am doing something similar to access the PPM-Channel-Values while using OSD-Data with a different software, not a good solution...
We should talk to the Developers and ask them to include the info in the OSD-Dataset.
Or the NC should redirect the stuff directly when the destination address is not itself, but the last time I tried that it was not working well.

CaScAdE meinte

mabomiko: Nicht im Abo, aber man kann ja das LCD abfragen und parsen... Auch das von der FC.... Aber das wird umstaendlich...

Frank: We could get the data by parsing the FC-LCD-Stuff, but we would have to swtich the NC-Debug port to forward stuff to the FC, get the LCD-Page, switch back and re-request the normal OSD-Data again. That would cause a lott of lagg... I am doing something similar to access the PPM-Channel-Values while using OSD-Data with a different software, not a good solution...
We should talk to the Developers and ask them to include the info in the OSD-Dataset.
Or the NC should redirect the stuff directly when the destination address is not itself, but the last time I tried that it was not working well.

Oke, thank you for looking at it.

//Frank

I am trying to install the USBProg on my windows vista 32bit laptop so I can change to my EPI to C-OSD.

I downloaded version 01 of the software but Libusb drove my computer crazy. It crashed and was unable to recover until I uninstalled the program.

I then downloaded the software (version 0.2.0)

I plugged in the programmer without the jumper (j2). I have a solid green LED and a flashing red LED.

Windows states 'USB device not recognised' .'unknown device' is listed in device manager under Universal serial bus controllers.

I have tried to manually direct it to the driver (programfiles\USBprog\driver) but I get the message 'the best driver software for you device is already installed'. When I click on driver details I get ' no driver files are required or have been loaded for this device'.

I have tried uninstalling the device several times without any sucess. Please help!!

Regards

Fergus

Hier fliegt wohl keiner im minimal-screen, hm?
Ich habe mal die Statistik-Anzeige repariert. Wenn man im minimal-mode geflogen ist, kamen im Stats-Screen sehr wüste werte.

@CaScAdE: ich habs gleich mal ins SVN geworfen.

Fergus meinte

I have tried uninstalling the device several times without any sucess. Please help!!

Never tried Vista and only had some problems with x64 Hosts.

I am using
AVR_ISP_mkII_Clone_Driver.zip
USBASP_Win32-Win64_v0_1_12_1.zip
which are pretty old but they were working ever since here... Dunno where I got them but they are in my usbprog folder

shaddi meinte

Hier fliegt wohl keiner im minimal-screen, hm?
Ich habe mal die Statistik-Anzeige repariert. Wenn man im minimal-mode geflogen ist, kamen im Stats-Screen sehr wüste werte.

@CaScAdE: ich habs gleich mal ins SVN geworfen.

Guter Punkt. Hatte den nicht mit gepflegt. Vielen Dank
Wollte das eigentlich mal zusammenfassen damit das nicht immer doppelt Platz braucht... Aber... Naja... Zeit :/

Thanks I tried the AVR clone driver but get the same message - 'the best driver software for you device is already installed'. How do I force vista to use a different driver?

I will do a blind shot in the dark.
Let's see what happens...

Thanks. Automatic update is on and the system is up to date. Manually updating the driver always gives the same outcome 'the best driver software for you device is already installed'. Even though when I click driver details tab it says 'No drivers are installed for this device'.

Try unistall the driver?
And when plugging in the device again select the "I have a disk" part?
Did not do much with Vista, but back in XP there was...
Something similar to force drivers vista?

No i have tried those steps as well without sucess. Is there another device I can use from a laptop to flash the boards?

You did try the driver posted here: http://www.mikrocontroller.net/topic/112224 ?

As far as I know there are people using Vista along with the USBProg, so it has to work...

Yes I have tried that driver also. If I try to manually update the driver in device manager I always get the same result - 'the best driver software for you device is already installed'. Yet when I check the driver details in the driver tab for the device it says no driver is installed!

I just tried to 'add legacy device' in device manager but that did not help either. The programmer still shows up as unknown device.

When I uninstall the device I do not get the option to also remove the driver as is usual in vista. This I think is because no driver is being associated with the device. After uninstalling then reconnecting I get the message 'USB device not recognised'

I have uninstalled and re-downloaded the software several times. rebooted and have the same problem each time. I have also tried connecting in AVRstudio but it fails to connect.

If you can recommend an alternative programmer for the EPI I will buy it. I do not have access to a serial port so I can't as I understand it use a SERCON.

ps. Thanks for your continued help CaScAdE

There are a lot of programmers out there... Cheap to expensive... But I really recommend USBProg.

A inexpensive workaround you can try is to install VirtualBox and Linux inside and use the USB-Prog from within... Not the best solution but it costs nothing

Anyone willing to flash the boards with the latest C-Firmware for me if I pay return shipping and a nominal fee if required?

Fergus meinte

Anyone willing to flash the boards with the latest C-Firmware for me if I pay return shipping and a nominal fee if required?

Hi Fergus,

I can do that for you, but I guess you better find someone in your own country to cut on P&P. Unless you live in Belgium as I do

Arachnida

@ CaScAdE,

Now that H&I officially support AeroSim, don't you think it would be a nice idea to implement your C-OSD layout in the simulator?

In the past I found the Spanish programmer very kind and helpful, and as his simulator is aimed towards FPV enthusiasts I think it will be liked by a lot of EPI OSD users!

Cheers,
arachnida

arachnida,

Thanks for the offer. I doubt I will find another epi owner in Ireland haha. Shipping to Belgium will not be too bad. Is there a private message function on this site? alternatively have you an email I can reach you on?

Fergus meinte

arachnida,

Thanks for the offer. I doubt I will find another epi owner in Ireland haha. Shipping to Belgium will not be too bad. Is there a private message function on this site? alternatively have you an email I can reach you on?

Looks like you already found the PM function

arachnida

Falls jemand ne FC mit ACT DSL dran hat, kann der mal die in ACT DSL RSSI und C-OSD gepostete FC-ONLY FW von heute morgen testen? Bitte? :-)


Edit: kopter2011 hat berichtet, dass es geht...

Ist es bei euch auch so, daß kein Empfangsausfall piepen kommt wenn das EPI mit C-OSD an der FC hängt und der Sender ausgeschaltet ist? Leider erschwert das u.U die Ortung bei einer nicht optimalen Landung Ist das gewollt? Kaum ist das EPI abgeklemmt, schon piepts.

Ich fliege FC 1.1 am Summensignalempfänger und EPI mit C-OSD-20101115-0800-pal-fconly

Moin KaBiKopter, das ist nicht intendiert aber wohl kaum vermeidbar. Das OSD nutzt den Debug-Datensatz in der FC-ONLY-Version. Wenn der angefordert ist, dann gibts kein Piepen. Ist wie wenn das MK-Tool an ist, dann ist auch kein piepen...