openrcforums

rperkins wrote: I was really looking for the member lists.

I found it under the 'quick links' icon which is located on the upper left hand side of the 'non mobile' layout

not an issue at all but if you wanna run it down. http://openrcforums.com/forum/ucp.php when in control panel there is a tab on the right hand side labeled UCP_BLOG the link on that tab http://openrcforums.com/forum/ucp.php?i=248 gives this error Cannot find module ./includes/ucp/ucp_blog.php I was ...

Thanks for the upgrade. I'm in :-) If I notice anything major out of whack I will post. Those little tweaks we make are the hardest part to track. For the most part I try not to do them anymore because they get lost or just dont function the same . thanks again. hopefully this will address some of t...

She passed away.
viewtopic.php?f=48&t=6987

gruvin wrote:The pic arrived broken for me, sorry.)

sorry, you had to click 'view raw file'. I fixed the link above so it will work. But I have no idea what type of mod he has on his radio or if it was one of the mods listed in the gruvin makefile

Did I miss something? He says his speaker is connected to the speaker port on the G9 board. That should just work, sound options in the menu not withstanding. I dont know the details of his mod. He just said it didnt work in the first post. Then I found the options for gruvin9x and also viewed this...

cant talk about Tray flying with thinking about Flaps.

If it's the G9X 4.x board, then you just need to wire your speaker to the speaker socket, instead of where the piezo used to be. You can put the piezo back if you still have it. Then you can have loud beeps for some things (say alarms) and the speaker for others, like trim-up down and menu nav soun...

Here he said he has a version 4.2, so sounds like this should work for him

viewtopic.php?t=7804#p104322

Here is the gruvin src makefile which has this option # gruvin: BEEPER. Values = BUZZER, BUZZER_MOD or SPEAKER # (without a mod, BUZZER can make PPM jack output switch from output to input at random) # SPEAKER mode actually works on the stock radio, using the stock beeper. Sort of sound OK(ish). BEE...

Here is the Makefile if you were going to compile your own version of opentx. within this file is a section titled 'build options'. I am not familiar with these options but upon a glance did not see what I think you are looking for. I would imagine every option possible for opentx would be listed in...

you're welcome. glad you got it working.

just getting ready to take my nap and thought of this.

open your terminal like you do when you have been manually flashing your radio. type this command I dont even know if mac has this command but if it does it will tell you which version of avrdude is working for you.

Ok this makes more sense. I see a mismatch but it isnt at 0x0100 it is at 0x0000. So same type of error but probably caused by something else. also I notice that when you manually flash you are installing opentx 2.1.3 and when you use companion it is grabbing 2.1.511111 . it also looks like companio...

the output of that flash looks good. I am surprised it doesnt work maybe you have 2 versions of avrdude on your computer. I notice from the other thread you are using /usr/local/bin/avrdude. the output here is using your $PATH to find avrdude. I would check the entire computer for multiple versions ...

I know a couple years your first couple posts had to be moderator approved. Is that still the case ? If so then howare new spam accounts gettimg their spam onto the forum without moderator approval ?

There's two -p's in your command. Remove the -p m64 one and things will go better. But who cares, now? ;-) FYI . the last -p takes precedence . thanks for checking in. I know nothing about the gruvin/opentx. Hopefully he will start a new post to use the gruvin in companion and you guys can help him...

you're welcome. glad you got it going. It will work with companion now that your usbasp's have been updated. As far as which setting to use in all the various places within opentx to make it work, that is beyond my comprehension. It is important to realize that using the gruvin board with opentx pro...

ok lets try to flash with the firmware you posted in this thread http://openrcforums.com/forum/viewtopic.php?f=95&t=7804#p103772 be sure that you have unzipped the hex file and it is in your current directory run this code, it should all be on one line. the filename is long but I think I got it ...

my bad. I was thinking Australia and now I looked closer and see Austria

Koarl wrote:And programmer number 2

This one looks good also.

One quick question .
Do you want your firmware in German ? I think you downloaded a german firmware. we are going to test with it either way.

I'll have another response soon

Koarl wrote:Thanks!
Here is the output of programmer 1

that is good. that programmer is updated

3.0.14 is the latest of the 3.0.x version
https://www.phpbb.com/downloads/3.0/

here are some public exploits for 3.0.12
https://www.cvedetails.com/vulnerabilit ... .0.12.html

I have no idea how serious these are or if there are others.

this forum is on 3.0.12 http://openrcforums.com/forum/styles/prosilver/style.cfg # # phpBB Style Configuration File # # @package phpBB3 # @copyright (c) 2005 phpBB Group # @license http://opensource.org/licenses/gpl-license.php GNU Public License # # # At the left is the name, please do not change t...

lets go ahead and reflash both of your usbasp's so we are sure that you are using an updated one. hook the usbasp's together and put the jumper on the one on the end. be sure you are in the directory with firmware.hex. firmware.hex should be the romulo firmware you downloaded from this thread earlie...

has the site been compromised ?
I believe it has happened to a couple other sites hosted by Rob in the past ?
are you on the latest version of phpbb ?

and how did you flash them both at the ' first flashing attempt ' . you realize the only usbasp that is updated is the one that you are shorting out the programming jumper ?

It really drives me nuts. Should I buy another programmer? No. You dont need a new usbasp. You already have 2 of them Are both your programmers the same ? Did you update them both ? Do you have them clearly marked so that you dont get them mixed up ? depending on your answers i think you are ready ...

http://openrcforums.com/forum/viewtopic.php?f=95&t=7804&p=104751#p104740 According to this post you have updated yout usbasp properly. It is confusing because within the same post you added output from trying to read the firmware from the radio whike using wrong parameters.. look at the link...

On eepe, there is an option under the BURN menu or "Review Output". This lets you look at and copy the Avrdude output. Mike. That is a good option to have. This poster is using opentx and I imagine it is still true that opentx uses companion and er9x uses eepe and that it is not the best ...