er9x development

Post by **MikeB** » Tue Dec 08, 2015 9:30 am

I think the problem might be the mainboard is trying to talk to the MegaSound at the same time.
You prevent this by switching on with the two horizontal trims held inwards. This causes the display to show either "Stopped" (M64/2561) or "Bootloader" (M128). You may be doing this.

The diode is needed to allow the serial connection to be shared between the radio and the PC.

It's a while since I did this, I'll need to hook up and try it.

Mike.

Post by **jhsa** » Tue Dec 08, 2015 11:33 am

Pino, try to connect another schottky diode on the the other FTDI line, but reversed in relatiion with the first one.. My arduvoice does need two diodes. One on each line as far as I remember.. it's funny how quickly we forget how we did things as there is so much information flowing here (and to keep in mind) all the time..
I hope this helps

João

LTMNO · Post by **LTMNO** » Tue Dec 08, 2015 1:00 pm

Thanks for the posts.. I will try that.. I am for sure using the BOOTLOADER mode..
That being said, when I plug into the FTDI to the radio in BTLDR mode i see activity on the TX line coming from Serial.
If I plug in the USB... jack then that goes away, no activity visible...

To note, I was using a 1n4001 diode... was that a bad choice?

Post by **jhsa** » Tue Dec 08, 2015 1:21 pm

There is more voltage drop on the 1N4001.
You can try connecting another one just like I have posted above. As I said, I had to do that on my ArduVoice module. The FTDI pictured on your post above is an original. I have to say that according to my experience the clones work better

João

LTMNO · Post by **LTMNO** » Tue Dec 08, 2015 1:26 pm

The thing is that is works on the on my other 9x radio... same setup... same ftdi...
There I am using a Glass Tube Diode.. whatever you call those...
I have one here too.. tested that.. same results... once I start to see the 1515151 instead of the 0606060 i know its not going to work.

hmmm

Post by **jhsa** » Tue Dec 08, 2015 1:29 pm

Sorry, what did you test? Adding the second diode to the other FTDI line?

João

LTMNO · Post by **LTMNO** » Tue Dec 08, 2015 1:48 pm

I was testing just another diode... i am going to test 2 now.. but i was reviewing this diag again..

I think I might have this wrong... as shown previous in this thread...
Just checking now..

LTMNO · Post by **LTMNO** » Tue Dec 08, 2015 2:20 pm

Alright, did the testing some more, checked the wiring again... It is setup just like the diagram above with 2 diodes.
Same result, I loaded multiple files, I have it in BTLDR mode.
I can read and write Models...
I take it over to my MAC... works no problem.

Really strange eh? Does the SD Serial work on the latest build of eepe for Windows?
Can you test it?

This link on the er9x.com sight is for r415 even though it says r418 (WINDOWS) and it offers to download r418?
http://www.er9x.com/eePeInstall.exe

This one is for r419 (WINDOWS)
http://www.er9x.com/p419/eePeInstall.exe

This one is for r411 (MAC)
http://www.er9x.com/eepe.dmg

I did test r415 and r419 which are available to me... they both don't work on Windows... the MAC r411 however does work.

Oh Also, once you load r415 for windows and it offers to download r418, you download it and then it offers to save and install the package...
This error occurs...

Post by **jhsa** » Tue Dec 08, 2015 2:46 pm

Pino, my suggestion wasn't to test with both diodes like on the diagram above. What I suggested was to connect a diode on both FTDI lines. The second one being connected reversed..

João

Post by **jhsa** » Tue Dec 08, 2015 2:59 pm

Like this:

Post by **MikeB** » Tue Dec 08, 2015 3:57 pm

I've tested as much as I can (after Windows mucked about with my USB-Serial drivers!). All just works for me.
However, I don't have any MegaSound installations that use non-inverted, logic level serial connections to the PC. They all use a 3.3V supply for the mega128, and have the transistor inverters in so I can use a "real" RS232 adapter.
I don't have an FTDI device either. I do have an Arduino USB2Serial device.
My original design does include the extra diode in the logic level connection.

Mike.

LTMNO · Post by **LTMNO** » Tue Dec 08, 2015 4:03 pm

Yeah, I was just thinking.. I have a usb to serial 3.3 and 5.5 adapters. But what is the point as it works in MAC and not in Windows. This features is really for just updating voice files.. i only add a few when I have a new model. So not really that important. The only thing that I can think is different is that I have a V4 MegaSound in the new radio and I think the other radio has V3. they are wired identically. They look the same around the Pad 7/8/5/6/2.

I am not sure if there are resistors on the bottom side of the v3 like there are in the v4.

Post by **jhsa** » Tue Dec 08, 2015 4:08 pm

I have a FTDI (clone) permanently installed in the radio and connected to my ArduVoice board, and all work as it should. Just tested with the latest eepe 419

João

Post by **MikeB** » Tue Dec 08, 2015 4:31 pm

The "Cannot open folder" error is due to googlecode blocking downloads of .exe files. I had to use a .zip file, then eepe can't run it directly to do the upgrade. You have to save the .zip, extract the .exe in it, then run the .exe to do the install.

It is the same code running on the different versions of eepe for different PCs. I don't think I've changed anything in this area for a long time. I'm using a r419 of eepe.

I can only think there is some timing not quite right, that is different on different PCs (your/mine/windows/MAC).

Mike.

LTMNO · Post by **LTMNO** » Tue Dec 08, 2015 5:10 pm

Yeah, its okay.. really... I have sealed the radio, its the best working stock M128 one I have out of all of them minus that... The sound is crisp, clear and no hum or hiss. The Sticks are solid as in there is no jitter what so ever for Stock Gimbals, everything is 100% on ANA. I am going to get oLRS running on it.
Now, for eePe, I did what you said, downloaded, extracted and ran the EXE. It then loads eePe and asks to download r418 again.

I just grabbed r419. That works fine but i am using Mac now.. so doesn't really matter there either.

Happy to keep testing for you.. but if no one else is having the issue... then its stops with me.

Here is plug for Steven at SmartieParts... I have to say, the 2-3 days it takes to setup a radio rather than just buying the Xtreme and just screwing it in.. is well worth the $60+ IMO.

Heading to the Airport, have a great day. Back in a few days to play again. Thanks again!

LTMNO · Post by **LTMNO** » Tue Dec 08, 2015 7:44 pm

I had a few hours to kill here at the airport, got me thinking... could the quality of wire used to connect everything make a difference?
I have 20/22 gauge for the working system on windows and then i have 28 guage on the one that is not working?
I dunno, just reaching here... I know I was going to leave it alone, but just thinking out loud?

Post by **MikeB** » Tue Dec 08, 2015 11:10 pm

I don't think the wire size will make any difference.

Mike.

LTMNO · Post by **LTMNO** » Thu Dec 10, 2015 1:37 pm

Thanks, understood... just thought the impedance if any, but I have a funny suspicion there is something different with my V3 and my v4 Megasound. I think there are a couple of Resistors on there and perhaps they are doing something to prevent this to work. I have pinged HC1969 to see what that is.

andrewju · Post by **andrewju** » Tue Dec 15, 2015 9:50 pm

Mike,

I think you fixed it already in some earlier version, but now I see this issue again in the latest eePe revision 419:
When I go to File --> Preferences and set MCU = 2561, eePe still offers to download er9x.hex instead of er9x-2561.hex
Not a big deal, but may be worth fixing again.

Thanks!

gerhardp · Post by **gerhardp** » Tue Dec 15, 2015 11:43 pm

MikeB wrote:The "Cannot open folder" error is due to googlecode blocking downloads of .exe files. I had to use a .zip file, then eepe can't run it directly to do the upgrade. You have to save the .zip, extract the .exe in it, then run the .exe to do the install.

It is the same code running on the different versions of eepe for different PCs. I don't think I've changed anything in this area for a long time. I'm using a r419 of eepe.

I can only think there is some timing not quite right, that is different on different PCs (your/mine/windows/MAC).

Mike.

Sorry to interrupt, Mike,

Does r419 of eepe have the printing fix that we talked about a while ago?

I am on r418 with eepe, just wondering. It didn't prompt me to download r419 of eepe, probably due to the server switch.
But it is prompting me to download r819 of er9x. I am on r818 with that. Is there a doc with changes for er9x r819?
Thanks Gerhard

Post by **MikeB** » Tue Dec 15, 2015 11:55 pm

eepe r419 isn't formally released, it is downloadable manually from the right side on http://www.er9x.com.
I can't remember if it has that fix in, probably it does.

Changes to er9x are in the file "changelog.txt" found here: https://github.com/MikeBland/mbtx/tree/ ... radio/er9x.

Mike.

gerhardp · Post by **gerhardp** » Wed Dec 16, 2015 12:00 am

Thanks Mike.

Post by **MikeB** » Wed Dec 16, 2015 10:14 am

andrewju wrote:I think you fixed it already in some earlier version, but now I see this issue again in the latest eePe revision 419:
When I go to File --> Preferences and set MCU = 2561, eePe still offers to download er9x.hex instead of er9x-2561.hex

Even if you change the processor, you still need to change the setting on the line above for "Version to Download".
For whatever reason, when eepe was first written (before I started on it!) there were (and still are) separate settings for downloading and burning, so 2 places to set the processor. I have combined the two settings into one dialog to make it more clear.
It would probably be good to sort them all out, although I believe some people use eepe as a "front end" to AvrDude for flashing AVR processors that are not the 9X (e.g. '328 on the MegaSound board). This does require the 'burn' processor is different from the download processor.

Mike.

Post by **jhsa** » Wed Dec 16, 2015 11:32 am

Unless you make "Profiles" available.

Then you can have only one setting for both. Just load a different profile for a m328 for example. You could point the version to download to a zip file with the latest versions of the voice module files..

João

andrewju · Post by **andrewju** » Thu Dec 17, 2015 11:52 am

Oh, right! 'Version to download'... Ok, confirmed to work properly.

But why do we have both 'Version to download' and 'Processor' under the File --> Preferences window? Does 'Processor' make any difference if the previous line defines specific version that I would like to get?
In my experience, neither of the above are related to the 'burn' options (avrdude configuration), as avrdude settings are located under Burn --> Configure window.

P.S.:
Yes, I'm also one of those using eePe as a frontend to avrdude on a regular basis. And I sometimes miss a simple button that would allow me to BACKUP an Atmega - saving both firmware and eeprom to a file (or to two files - even better), and then another button to RESTORE it back if there is a need. Ideally, eePe should not even try to 'understand' the eeprom content in this case. Simple backup & restore of whatever currently is in the Atmega.

Otherwise, for example, when reading a stock eeprom with eePe, it gives an error that the eeprom is not understood and then deletes the file from the temp folder. So I have to manually copy the file from the temp folder in order to keep it. And I often find myself using avrdude from the command prompt and saving the file to where I need it, rather than browsing through 'temp' folder with Windows Explorer.

KAL · Post by **KAL** » Thu Dec 17, 2015 12:20 pm

Please have a look at AVRDUDESS

A really nice GUI for avrdude.

Klaus

andrewju · Post by **andrewju** » Thu Dec 17, 2015 12:22 pm

Good point, I'll look into it!

Post by **MikeB** » Thu Dec 17, 2015 12:48 pm

In the "burn" menu are options to "Read EEPROM to file" and "Write EEPROM from file". These just do as they say, read or write without checking the contents.

Mike.

ReSt · Post by **ReSt** » Thu Dec 17, 2015 2:17 pm

I also do use eePe to flash opentx as due to my modifications opentx every time wants tor format my eeproms

Reinhard

gerhardp · Post by **gerhardp** » Thu Dec 17, 2015 2:23 pm

MikeB wrote:eepe r419 isn't formally released, it is downloadable manually from the right side on http://www.er9x.com.
I can't remember if it has that fix in, probably it does.
Mike.

Mike,

I have downloaded and installed eepe r419. It does not have the printing fix, THR and ELE are still reversed.
See below.

: r419_prnt.JPG (27.87 KiB) Viewed 12398 times

Gerhard

openrcforums

er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development

Re: er9x development