I am wondering if it is the switch. I had one customer return a switch that was doing this, and I confirmed the switch itself was intermittent. I have everything packed up at the moment preparing to move, but I will look into this as soon as I unpack everything.

Does the X24 give priority to RxPort, I want to connect 2 receivers and having one with a Cortex Pro and one without, so that if one of the receiver or the cortex failed, it will always be at least one receivers still active. If I connect both receiver through the Cortex and the cortex failed, everything will fail. But, the concern I have is if the X24 switch without priority on all receivers ports it mean that it will switch on and off of the gyroed one, making the flight unpredictable…

Thanks,

Recievers must be plugged in directly. You can not have anything between the Rx and the X24, no exceptions.

The X24 uses the first valid receiver's data, starting at the lowest Rx port number. If you had 4 receivers and never had a lost packet on Rx Port 1 then the data from the other receivers will have never been used. When packets arrive from the recievers (which occurs virtually at the exact same time), the data for each reciever is checked and marked as good or bad in the table that keeps track of each reciever's status. Once that is done, the computer goes through the list of recievers starting at Rx Port 1 and if the packet is good then that data is used. There is a time stamp, so the computer knows which receiver(s) have the most recent data.

We will have the X24 Pro available later this year (you will be able to update an existing X24), which will give you substantially better stabilization capabilities than the Cortex and any other gryo/flight stabilization system, and it's integrated into the X24's servo control.

Thanks Jim, when do you expect this new X24 to be release ? Is the gyros will be a physical addon to it (elseway how are we gonna be able to update our current x24) ? Thanks

Originally Posted by RobinLeblond

Thanks Jim, when do you expect this new X24 to be release ?

Jim said "later this year"......

He is adamant about not committing to any release dates so I'm surprised that he even said that .....

Case in point, the transmitter...... still waiting for ANY real status on when that might be released..... We've been waiting for it for over 6 YEARS !!!

Jim, my understanding is that because of the way the X24 prioritize/manage rx ports, if you put something between the receiver and the X24, it may create a delay leading the X24 to use the next rx port, I am right?

If yes, then if I use only one receiver/Cortex Pro combination it should work fine, more clearly:

X24 --- Cortex Pro Out --- Cortex Pro In --- Receiver

Meaning the receiver will be powered by the Cortex Pro and the later will be powered by the X24 (all of them sharing the same power bus).

Is this correct?

I don’t necessary need specifically a Cortex Pro, but your X24 Pro may get out after my project will be ready for this step (and I don’t want to delay it, it delayed all by it self way too much ;-) …).

But for sure, if your Pro version get out first I will be more than happy to use it!

JUAN : I did see it, I was just "trying" to get more precision from Jim... ;-)

Robin

Originally Posted by RobinLeblond

Jim, my understanding is that because of the way the X24 prioritize/manage rx ports, if you put something between the receiver and the X24, it may create a delay leading the X24 to use the next rx port, I am right?

If yes, then if I use only one receiver/Cortex Pro combination it should work fine, more clearly:

X24 --- Cortex Pro Out --- Cortex Pro In --- Receiver

Meaning the receiver will be powered by the Cortex Pro and the later will be powered by the X24 (all of them sharing the same power bus).

Is this correct?

I don’t necessary need specifically a Cortex Pro, but your X24 Pro may get out after my project will be ready for this step (and I don’t want to delay it, it delayed all by it self way too much ;-) …).

But for sure, if your Pro version get out first I will be more than happy to use it!

JUAN : I did see it, I was just "trying" to get more precision from Jim... ;-)

Robin

I'm sure you also saw Jim state, "Recievers must be plugged in directly. You can not have anything between the Rx and the X24, no exceptions" . Even if you could , wouldn't doing so defeat your original intent of having a "backup" receiver??

You can not ever have anything plugged in between a reciever and the X24. There is a very narrow window of time that is allowed between recievers, and adding anything except a long extension is not allowed.

I don't give release dates, and I no longer even announce what is being worked on because then people expect a release date. The X24 Pro (and the ability to upgrade an existing X24 by sending it back to us) was made known at the beginning of the X24 announcement, so it's not a secret. However, there is no release date.

Thanks Jim.

Juan, yes it would defeat the original intent of having a backup receiver, but it was just a temporary solution while waiting for the Pro version.

Originally Posted by brettc

Jim,

I've been trying to pin down this problem with the main switch. I tried it all different ways at the house, and it worked perfectly. I took it to the field today, flew it, and it wouldn't shut off. I cycled the power, and it still won't turn off. After 15-20 min unpowered, I turned it on, and the switch works again. After another flight, I put in the pin, and it shuts off. Pulled the pin out, put it back in, and again, it won't turn off. Let it sit unpowered, turn it back on, and it won't turn off.

There doesn't seem to be a lot of consistency with the functionality of this switch. Do you have any ideas? Is this a failure? Do you have any ideas as to why it's doing this? Is there anything I can try that would help?

Did this ever get sorted out?? ............

It was never reported again. Are you still having this issue? Does it occur with ALL of your X24's?

Originally Posted by JimDrew

It was never reported again. Are you still having this issue? Does it occur with ALL of your X24's?

I had the issue a couple of times on only one X24.....then it started behaving normal.........helped a friend who was having the "Issue" on a regular basis......one day, I convinced him to change the orientation of his RFU antennas (I was not in agreement with his set/up).....the switch issue never happened again.........I obviously have NO idea what's going on!
Thanks Jim
Ed

I would be interested to learn how antenna orientation would have any effect on the switch function.....????

That's very odd. Maybe you have a problem with the switch cable? Moving antennas would not affect a switch. Moving the cable around in the process of re-orienting the antennas could be why it suddenly works.

I feel the need to elaborate a little more.....we did shuffle switches & cables from air-frame to air-frame with no effect on the "Issue"....(we have seven X24 equipped air-frame's between us).....I became more interested in HIS "Issue' when he mentioned that his engine, non-commanded, momentarily went to idle a couple of times (In flight), & so I'm thinking Fail/Safe.....that got me to looking his set/up over & therefore the "New" antenna orientation......no more switch "Issue" & no more engine momentarily going to idle.....like I said, I have NO idea whats going on...........just wondering if a Fail/Safe condition may somehow confuse the soft/switch function internally in the X24?? .....