Page 3 of 6

Re: er9x V2 = mbtx

Posted: Wed Nov 15, 2017 10:44 pm
by MikeB
Interesting, I can reproduce that sound on my M64 system. The sound is clearly related to the haptic output (I don't have a haptic fitted to my radios) as I changed from HAPTIC3 to HAPTIC2 and the number of "blips" reduced.
Odd that it doesn't happen every time.
Are you certain someting is on the beeper signal (seen with a oscilloscope for example)?

Mike.

Re: er9x V2 = mbtx

Posted: Thu Nov 16, 2017 3:09 am
by kmargos
I will try to measure in oscilloscope tomorrow. I'm sure it comes in the buzzer line, I remove the beeper wire and it does not happen anymore.

My other TX, which has the W020, uses the piezoelectric in series and controlled by a bc547, also the same occurs. But as it is connected to the BC547, it is possible to hear the noise in the piezoelectric.

See my other video with TX with W020.W020 Piezo noise



Marco.

Re: er9x V2 = mbtx

Posted: Thu Nov 16, 2017 12:40 pm
by kmargos
Hi Mike,

Oscilloscope video Noise in Oscilloscope


Image:

Re: er9x V2 = mbtx

Posted: Thu Nov 16, 2017 1:06 pm
by kmargos
DC analysis. haptic 3 (Beeper=NORM)

Re: er9x V2 = mbtx

Posted: Fri Nov 17, 2017 2:25 pm
by kmargos
Mike, in the future is it possible to configure PC0 (PB3), PC4 (PB4), PG5 (PB5) and PB7 (PB7) as extra switches on / off?

Marco.

Re: er9x V2 = mbtx

Posted: Fri Nov 17, 2017 3:59 pm
by MikeB
I think I can see what might be causing the problem.
I'll do a change to the source code and test it, but it may have to wait until tomorrow.

PB7, PC0, PC4 and PG5 are all available as switch sources, Are you asking for more switches as in "PB3" and "PB4" push buttons?

Mike.

Re: er9x V2 = mbtx

Posted: Fri Nov 17, 2017 8:22 pm
by kmargos
MikeB wrote: Fri Nov 17, 2017 3:59 pm Are you asking for more switches as in "PB3" and "PB4" push buttons?
Mike.
Yes!! more Switches. :D

Re: er9x V2 = mbtx

Posted: Sat Nov 18, 2017 4:48 pm
by MikeB
I think I have fixed the beeper sounding when haptic is running problem, I've just posted a mbtx3.zip on the first post with the fix in.
Adding some more switches as PB3 and PB4 is not a quick job, and, because of the extra code needed, I don't think it should be added to a M64 board.

Mike.

Re: er9x V2 = mbtx

Posted: Sat Nov 18, 2017 10:30 pm
by kmargos
mbtx3 no more noise !!

Thanks Mike !!!

Marco.

Re: er9x V2 = mbtx

Posted: Mon Nov 20, 2017 7:08 pm
by kmargos
Hi Mike ,


Is it later possible to compile a version for the M64?

Marco.

Re: er9x V2 = mbtx

Posted: Mon Nov 20, 2017 9:46 pm
by MikeB
The files mbtx-frsky.hex and mbtx-frsky-sv.hex (serial voice) in the zip file are for the M64.
Do you need a version that is without the frsky (telemetry) mod?

Mike.

Re: er9x V2 = mbtx

Posted: Mon Nov 20, 2017 10:59 pm
by kmargos
MikeB wrote: Mon Nov 20, 2017 9:46 pm Do you need a version that is without the frsky (telemetry) mod?

Mike.
Yes. My friend uses TX without mod. He wants only the serial voice module.

Marco

Re: er9x V2 = mbtx

Posted: Tue Nov 21, 2017 9:38 am
by MikeB
I'll try to build such a version of "V2", it may take a bit of time.

Mike.

Re: er9x V2 = mbtx

Posted: Tue Nov 21, 2017 10:34 pm
by kmargos
MikeB wrote: Tue Nov 21, 2017 9:38 am I'll try to build such a version of "V2", it may take a bit of time.

Mike.
Ok, take your time.

tks!!!

Marco.

Re: er9x V2 = mbtx

Posted: Wed Nov 22, 2017 3:46 pm
by kmargos
Hi Mike,

I opted to make the mod AIL an THR (FRSKY).

in M64 frsky-sv, I am giving the message "BAD EEPROM", I can not configure trim, pb1 and pb2 by hardware mode (V1 and V2).

Re: er9x V2 = mbtx

Posted: Wed Nov 22, 2017 10:05 pm
by MikeB
The first time your run er9x after flashing between V1 and V2 the EEPROM will show as bad.
If the EEPROM shows as bad every time you flash the firmware, check the fuse settings "Preserve EEPROM".

The M64 does not have enough flash to include all those hardware settings. You have to read the EEPROM into eepe (or eepeV2), make the settings there, then write the EEPROM back.

Mike.

Re: er9x V2 = mbtx

Posted: Thu Nov 23, 2017 12:54 am
by kmargos
Hi Mike ,
For M64, Frsky SV.
Bad EEPROM occurs after recording the EEPROM by program V2. Identical to the problem I mentioned earlier.
So I can not configure it.

Re: er9x V2 = mbtx

Posted: Thu Nov 23, 2017 11:42 am
by MikeB
This worked OK for me. My M64 radio doesn't have serial voice, it is on parallel, I just flashed it with mbtx-frsky.hex, let it create the EEPROM, then I could read it OK with eepev2, modify it and write it back.

Make sure you go into settings on eepev2 and change the processor type to M64 in TWO places.

Mike.

Re: er9x V2 = mbtx

Posted: Fri Nov 24, 2017 9:51 am
by MikeB
If you are still having a problem, use the option in eepeV2 to read the EEPROM to a file, then zip the file up and post it for me to look at.

Mike.

Re: er9x V2 = mbtx

Posted: Fri Nov 24, 2017 11:31 pm
by kmargos
It was a TX from a friend, I had to give it back. I did not have time to test.


Tks !!

Marco.

Re: er9x V2 = mbtx

Posted: Tue Apr 10, 2018 9:46 pm
by kmargos
Hi Mike,

My friend has a transmitter with atmega64, I installed the serial megasound. I can not get into Hardware to configure PB1 (ext1) and PB2 (ext2).
For both MBTX and R821. The trim (TH) in the Megasound board don't work to.

OBS.continues to appear the "BAD EEPROM" for MBTX.

Tks

Marco.

Re: er9x V2 = mbtx

Posted: Tue Apr 10, 2018 10:14 pm
by MikeB
Is the FrSky mod also done on this radio?
I'll try to post some updates tomorrow, I'll run some tests on them first.
When using the M64, you can only set hardware options from eepeV2, there just isn't enough flash to include it on the radio.

Mike

Re: er9x V2 = mbtx

Posted: Tue Apr 10, 2018 10:47 pm
by kmargos
MikeB wrote: Tue Apr 10, 2018 10:14 pm Is the FrSky mod also done on this radio?
I'll try to post some updates tomorrow, I'll run some tests on them first.
When using the M64, you can only set hardware options from eepeV2, there just isn't enough flash to include it on the radio.

Mike
I went back to the previous version "EEPEV1" and now PB1 (EXT1) and PB2 (EXT2) working. It should be some bug in version 2.
I have not yet made the modification to the FRSKY (keys) ... I just installed the serial audio.

Will you have the bug fix "minutes and minute"?

Tks!!

Marco.

Re: er9x V2 = mbtx

Posted: Wed Apr 11, 2018 2:56 pm
by MikeB
I've posted an updated mbtx (er9xV2).
I tested this on a M64 with frsky mod (telemetrez) and a parallel megasound board.
Using the included eepeV2 I was able to read and write the EEPROM, and change the setting of PB1.
It does include the minutes/minute voice fix for 1 minute remaining.

Mike

Re: er9x V2 = mbtx

Posted: Thu Apr 12, 2018 1:52 am
by kmargos
MikeB wrote: Wed Apr 11, 2018 2:56 pm I've posted an updated mbtx (er9xV2).
I tested this on a M64 with frsky mod (telemetrez) and a parallel megasound board.
Using the included eepeV2 I was able to read and write the EEPROM, and change the setting of PB1.
It does include the minutes/minute voice fix for 1 minute remaining.

Mike
Eepev2 continues with the error "bad eeprom" :( i used mbtx-frsky-sv.hex
i use M64 Fr sky mod (djt serial) and a serial megasound

tks,

Marco

Re: er9x V2 = mbtx

Posted: Thu Apr 12, 2018 2:12 am
by kmargos
See this print...data for EEPEV2 is 2017, november.

Marco.

Re: er9x V2 = mbtx

Posted: Thu Apr 12, 2018 9:49 am
by MikeB
That is the version of eepeV2 I was using.
I have just built a new test version and posted on the first post.
Please try reading the EEPROM from your radio with this one. If you still get a "Bad EEPROM Error", try using the "Burn" menu option "Read EEPROM memory to File", then post the resulting .hex file for me to look at.

Mike

Re: er9x V2 = mbtx

Posted: Thu Apr 12, 2018 1:45 pm
by kmargos
Hi, Mike

I did so, formatted the eeprom when the message "bad eeprom" appears, shortly after I loaded the eeprom in the EEPEV2 and then edited PB1 and PB2, timers, megasound and etc. And now it works. The working eeprom is attached.

Tks,

Marco,

Re: er9x V2 = mbtx

Posted: Thu Apr 12, 2018 2:01 pm
by kmargos
"The following on the MegaSound module:
XPB0 (EXT1 on V1)
XPB1
XPC0
XPD2
XPD3 - used for LV trim
XPD4 - used for LV trim
XPD7 (EXT2 on V1)
Note: Some of these may need the Megasound firmware to be updated to use them."

I can't see XPD7 or EXT2 in the EEPE2.

I think "LV trim" does not work.

Re: er9x V2 = mbtx

Posted: Thu Apr 12, 2018 4:39 pm
by MikeB
The LV trim mod is routing the left vertical trim switches to PC0 and PC4 (I didn't add this feature). It is not supported on the M64 for flash space reasons. If you have serial Megasound, then the left vertical trim switches need to be routed to the Megasound board.

I'll look into the switch configuration options on eepeV2 later tonight.

Mike