Posts by BWUK

    Pigna:

    ..well yes I could but one end of the lead goes into RX1 or RX2 and the other goes into either the P2Bus port or the M link port. Not much to photograph really.


    Richard,

    I've repeated the update process and Terminal reported successful updates for both Rxs and the Mercury but with the same results. All still functions normally with M-Link. Since P2Bus is not crtitical for this application I'll continue on with M-Link and wait to see if the issues occurs with others.

    Thanks for help

    Bob

    Hi Richard,

    I have updated the Mercury again with the same result. I'm always concerned that I'm not connecting or setting the system correctly but in this case there's so little to get wrong! I'll update everything again and report back.

    Thanks

    Bob

    ..further update.

    Went to make sure that I had updated the Mercury correctly to v9 (which I had). So I had the mercury switched on- but without the Tx being on - and the same condition occured. All retured to normal when switching back to M-Link.

    Bob

    Hi Richard,

    Works normally when returned to M-Link but does not work properly with P2Bus. Am wondering if it could be gyro related? There's no discernable pattern to the way the control surfaces move - but they move uncommanded.

    Bob

    Hi Richard,

    Have successfully upgraded Core, Mercury and 2 PB26 -D to latest software to gain access to P2bus and new gyro features. Receivers are connected via the P2Bus ports and I have the Mercury set to P2Bus. However, I have no control over the servos. They power up and move randomly until I power down. Previously set up in M Link and working well. Software versions are: Core 1.4, Transceiver 1.5, Stickcontroller 1.3, Receivers 1.4, Mercury V09.

    Thanks for any help

    Bob

    Pete,

    You won't find better, and faster, support anywhere on the planet. I struggled as a beginner and received nothing but patience and good guidance. Just follow the rules of the forum and you will end up in the right place.

    Bob

    Hi Jack

    I had some problems with the jet tronic value a while back. Not entirely sure what you mean by 'leaving at factory setting'. You need to set the valve up so that it knows 'which way is up' so to speak. So air up the system and make sure the gear is in the down position - press the button on the valve next to the light that is on. Then move the gear to down and press the other button - the light should be on next to it at this point. Given that the sequencer is all set up then you are good to go.

    Richard I think is refering to a situation he helped me with a while ago. It seems that some of the older valves would sometimes create a situation where, no matter that the retract switch was in the down position, the gear would always go up when the tx was switched on - very annoying! This occured because the valve 'had a preference' for starting in a particular state without regard to instructions from the tx. Should this occur with you the solution is to swap the air lines over at the value i.e. just reverse them. Then make sure the sequencer is good and that should fix the problem. I think the newer valves do not suffer from this problem.

    Good luck

    Bob

    ..if you just move the Tx over the area of the model where the rx is located the Core screen will show an alert when you're close enough and you will see quite clearly on the screen that the signal has been lost. A very simple and effective solution evan if not on the function list!

    Bob

    Hi,

    Given that the Core takes some moments to close down and restart (not a complaint!) I'm wondering if there is, or could be, a failsafe test menu function that doesn't involve switching the tx on and off?

    Thanks

    Bob

    Hi Gary,

    Had a similar situation. In my case it turned out to be a bent pin which, once straightened, fixed the problem. Worth checking - just in case.

    Bob

    Hi Richard,


    I'm not trying to update the receiver. I thought I needed to follow this post from you. If I don't need it, what was your purpose in posting it?


    To use on or two M-Link receivers with a SRS prduct (iGyro, Mercury SRS, Cockpit SRS, Royal SRS...) you have to set the Data oputput of the receivers to "SRXL". To do that, you need a USB interface adapter from Multiplex or PowerBox.

    You can download the free software from the Multiplex Website: MPX Launcher When the program is installed - proceed with following steps:


    &thumbnail=1&thumbnail=1




    When using two receivers: set the Hold and Failsafe Time top 0.2s and 0.0s


    &thumbnail=1&thumbnail=1



    The receiver is now ready to connect to the PowerBox SRS.

    Hi Richard,

    Perhpas I should been a little clearer - I seem to have lost the title of my post. I'm not trying to update the receiver, I'm trying to connect it to a Mercury. To do this I have set the data output of the rx to SRXL. For this I need the MPX Launcher as per your post. The Launcher is not recognising the rx. This is my issue.

    Sor for the confusion.

    Bob