openrcforums

And the bowl of petunias goes to the punter who can guess whether the 'Keeps Resetting' problem went away, when I disconnected the, er, Reset pin of the MOSI interface (Embarrassed Emoji).

Mind you, it is terribly convenient to have a USB socket in the Tx instead of MIso/Mosi interface pins; anyone know of a way of SAFELY permanently connecting a USB interface to ER9X?

Doofer wrote: ↑Tue Jun 26, 2018 3:27 pm Anyway, have now returned to trying to get ID1 & ID2 to work - probably more bad soldering on the PCB. I guess that, in ER9X, there's nothing you can do with ID0/1/2 3-way that you can't do with another 3-way that just uses two other switches, but having lost two switches to TxRx, I'm running out of switches!

You shouldn't lose any switch. as Mike said, the switches that were on TX and RX, can (and should) be moved to the other pins. You do not lose any switch. Actually, by using Er9x, I believe you can use other unused pin(s) of the processor to connect an extra switch, or convert one of the existent 2 way switches to a 3 way switch..

Oh, and that dratted 'Pressing Menu just restarts ER9X with model one' problem is back. Apart from Menu somehow jogging a pwr connection, or mysteriously toggling Reset, any other way of resetting ER9X I should look for? I guess it could just be one of those 'running ER9X on something else' issues jhsa referred to...

As far as I remember, some people had problems when leaving the programmer permanently connected to the radio. an easy test to make sure that isn't the source of the problems you are describing, would be to disconnect the programmer from the radio and see if it still reboots..

João

Doofer wrote: ↑Tue Jun 26, 2018 3:42 pm
Mind you, it is terribly convenient to have a USB socket in the Tx instead of MIso/Mosi interface pins; anyone know of a way of SAFELY permanently connecting a USB interface to ER9X?

Mike will probably confirm this (or not), but one of the Er9x versions, perhaps the m128 one not sure, has a bootloader that allows you to flash the radio by using an FTDI adapter.. Only TX, RX and GND needs to be connected.. But i think you might have to power the radio with its own power..
As I said before, I haven't messed with this for quite a while now. I do still have a 9x radio with an M2561 chip (Doubles the RAM of the m128) with voice module, 2 way switch (ELE) converted to 3 position, and extra push buttons on the back of the radio.. Also self built hall sensor gimbals, but I did all this looong ago.

João

Yes, it all moves on so quickly. My brother is still using the Graupner MC24 transmitter he bought about 20 years ago! I don't find pots very useful, so have set up a 3-way switch (with a voltage divider on the centre contact) as P1, really useful for electric soarer throttle.

I will probably just fiddle with more diodes on that interface... it's SO nice to just plug in...

Had to re-solder another 4-resistor array 2mm long - ugh - and now all the switches work - apart from TRN which seems to be shorted to ID2 - although intrigued to see that when ID2 is 0, TRN reports 1, and vice-versa.

I am wondering if a 'rogue' TRN switch will cause any problems, since whether TRN is 0 or 1 my Tx reports it is permanently in 'Slave' mode. I have no problem with this, as long as it stays in one mode or another (no PPM IN connected).

Well the SmartieParts programmer stays permanently connected to a normal 9X and everything works OK!

Both the '128 and the '2561 versions of er9x now include the serial bootloader, accessed by powering on with botk horizontal trims held inwards.

Slave mode is detected pn PG1 (pin 34), it is pulled low when the radio is powered normally.

Mike

MikeB wrote: ↑Tue Jun 26, 2018 10:10 pm Well the SmartieParts programmer stays permanently connected to a normal 9X and everything works OK!

Mike

Mike, i remember that some USBASP programmers did cause problems if left permanently connected to the mainboard. Not the case of the smartieparts programmer of course..

João

OK, this one only offsets the display by 2 pixels.

Mike

Fantastic! No more funny pixels! Thankyou very much indeed for that, that's great.

I've bunged a 4066 inline with the USBASP lines (switching off when the USBASP is unpowered) - I'll see how this goes.
Hope to find some time to test the CPPM & telemetry this weekend.

(Still the flashing underscore top left, mind!).

Doofer wrote: ↑Thu Jun 28, 2018 10:49 am Fantastic! No more funny pixels! Thankyou very much indeed for that, that's great.

I've bunged a 4066 inline with the USBASP lines (switching off when the USBASP is unpowered) - I'll see how this goes.
Hope to find some time to test the CPPM & telemetry this weekend.

Cool As you also have the bootloader, perhaps you could give an FTDI adapter a try to flash the radio. it connects only to MISO, MOSI and GND. These adapters are normally smaller than the UsbAsp programmer..

João

Doofer wrote: ↑Thu Jun 28, 2018 10:50 am (Still the flashing underscore top left, mind!).

If I am not mistaken, that means there is configuration data waiting to be saved to the eeprom. stuff like for example the main screen you have on at the moment. If you give it some minutes, before you turn the radio OFF, or after you changed some configs, that flashing Character should go away, meaning that all was saved..

João

Okay, STM32 Tx Multiprotocol module set to '0' (cppm control, I hope), FrSky mod enabled, protocol set to FrSkyV, set F8V7-II receiver to bind and power up, press for a bit option 'Bind'.... and no binding.
I appreciate that binding can be, well, a bind at the best of times, so is there any simple way of detecting whether or not the MultiProtocol module is responding to the Cppm controls, as a first step?

0 is not PPM control.. it is serial.. And that should be the correct setting to use with Er9x.

Make sure you go to "Model Setup / Protocol", the select "Multi" as proto..

João

So there's nothing what on the 'protocol' page I need to adjust, I just select FrskyV and press bind?

Check the module's status on its LEDs.

jhsa wrote: ↑Fri Jun 29, 2018 2:48 pm 0 is not PPM control.. it is serial.. And that should be the correct setting to use with Er9x.

Make sure you go to "Model Setup / Protocol", the select "Multi" as proto..

João

basically you just press bind. But make sure the receiver is in bind mode..

João

Hmm. Rx in 'bind', screen shows 'binding', but 4in1 board red LED just keeps flashing every 2 secs.

https://github.com/pascallanger/DIY-Mul ... hooting.md

Check this..

It looks like you have the module in PPM mode, not serial.. To use the multi menus you need to set the module to use serial.

Something else you can try is just for a test leave the module in PPM mode, set the proto to PPM in protocol, set the rotary switch on the module to the correct protocol, and try to bind the receiver by pressing the bind button on the module..

João

It's set to '0' = serial.
Frustrating; initially I had TX in PPM, module set to 4 (FrsSky mode), and it could bind 'conventionally' (switch TX on while holding down button), so it works okay. I even have a 3-way slide switch selecting 4,5 & 7 (= FrSky, FrSkyX & DSM2), and FrSky & DSM2 could bind to FrSky & DSM2 receivers. Just the serial not working. Perhaps I should try to re-flash the module...
.

Okay, more info: With module set to 0 (serial) Red LED flashes 50/50 every second = "Set to serial but nothing detected on Rx". No change when I hit 'Bind' (no surprise). I did the switch swapping suggested by Mike, so Rx0 & Tx0 from pins previously assigned to AILsw & THRsw. Assuming Rx & Tx on the module could refer to the pins on the module, or the expected inputs, I've tried swapping them over, to no great effect.
So module isn't getting any serial input, despite being connected to pin 2 (and tried 3).

That is for telemetry.. The control serial is received on Pin 1 of the multi module.. the same as PPM..
And the module connects to the pin the radio sends PPM to the module.. PPM and serial use the same pin.

João

That's what I originally thought; so my writing is correct (ppm out to module ppm in). Seems unlikely ER9X firmware is faulty. I know the wiring is okay, as it works with both set for PPM.

So the remaining culprit is (possibly old) firmware as supplied by Banggood on the 4in1 module?

Can you download the eeprom from the radio, zip it and post it here?

João

The eeprom from the 4in1 module? I'll have a go

Arduino doesn't seem to have a Download option - any suggestions?

No, the eeprom from your radio Use eepe for that..

João

Oh dear. It downloads, but I get error 'File may be corrupted, old or from a different system. You might need to update eePe'. (eePe' reports it is the latest version 422). This doesn't give me an option to save what it has downloaded.
Oh, and I could only get this firmware to flash using the -F flag.
I then get 'Bad eeprom data' which I can only get out of by re-flashing.

Oh no, never use the -F option unless you want to brick the chip.

João

Please use eepe and try to read the fuses.

João

I had a lot of faith in MikeB!
Fuses: Low=A4 High = c1 Ext = ff