January 27, 20206 yr On 1/25/2020 at 3:34 PM, koohejie said: With the new update it worked! We are happy! Thank you very much! Our product has had this feature for nearly a year with no feedback so far, so I'm glad to read it works at last!
April 29, 20206 yr Currently working to use SmartCopilot to synch RXP GTN 750s between Laminar C172s. I have included the following per previous entries above: [GTN_750_1]UseSharedTouch = true 2) configure SmartCopilot to share this dataref:RXP/radios/indicators/shared_touch/GTN_750_1=0 And also these commands: #REALITY XP GPS commands RXP/GTN/DTO_1 = 0 RXP/GTN/HOME_1 = 0 RXP/GTN/VOL_PUSH_1 = 0 RXP/GTN/VOL_CCW_1 = 0 RXP/GTN/VOL_CW_1 = 0 RXP/GTN/FMS_PUSH_1 = 0 RXP/GTN/FMS_OUTER_CCW_1 = 0 RXP/GTN/FMS_OUTER_CW_1 = 0 RXP/GTN/FMS_INNER_CCW_1 = 0 RXP/GTN/FMS_INNER_CW_1 = 0 RXP/GTN/CDI_SOURCE_1 = 0 RXP/GTN/OBS_MODE_1 = 0 RXP/GTN/TAWS_INHIBIT_1 = 0 RXP/GTN/MARK_ON_TARGET_1 = 0 RXP/GTN/TOGGLE_WINDOW_1 = 0 RXP/GPS/MASTER_DEVICE_0 = 0 RXP/GPS/MASTER_DEVICE_1 = 0 RXP/GPS/MASTER_DEVICE_2 = 0 Mouse clicks on the master GTN flow to the slave GTN but not consistently. For example, a click on the master GTN home button does not transfer to the slave. Any suggestions?
April 30, 20206 yr I received the following from Roman at SmartCopilot: If you issue the command by your LUA script, does it also gets transmitted to another pilot? If yes, you can attach these commands to X-Plane keyboard hotkeys and use it with keyboard only. HeinzXP note: I tried this and the HOME and DTO commands execute correctly on Master and Slave. It looks like these commands are working only in one direction: if the user issues the command, it will trigger the button event like in your example. It is also the main reason why the devs add these commands to control the plugin from external hardware. However, when the user triggers the button itself, the command is not being issued. You need to contact plugin developers and ask if they can make it work in both directions. It is minimal modification. Otherwise, there is no chance to capture the button events. Best regards, Roman.
May 1, 20206 yr Hi, I'm not sure to understand what difference is Roman making when talking about: a) "issuing a command" which is triggering a button event and: b) "triggering a button" which is not issuing a command. because: c) the GTN is not issuing anything at all. Therefore, whether any command (like "RXP/GTN/DTO_1") gets intercepted in computer A and transmitted to computer B for execution on computer B should be a feature of his program, regardless who the issuer is (a plugin, a shortcut key, a mapped hardware button, a Lua script etc...). These are RXP own commands, but you can also use stock X-Plane GPS commands (you'll have to configure both GTN for this) and see whether his solution is passing around the stock commands instead? The only thing for which there is no command is the 'RXP/radios/indicators/shared_touch/GTN_750_1' dataref, which his solution is supposed to be sync between the 2 computers.
May 2, 20206 yr Thanks for the reply Jean-Luc. After further testing I concluded the 'RXP/radios/indicators/shared_touch/GTN_750_1' dataref only updates when I click on the touch screen area of the GTN display. The dataref change is correctly passed from Master to Slave. When I click on a bezel button like 'HOME', the dataref does not update. The result is an action on the Master GTN but none on the slave GTN; at that point they are out of sync. As a work around I started using a no-bezel popout and mapped the bezel button commands to the keyboard. These commands flow as expected between Master and Slave.
May 2, 20206 yr This is expected: This dataref is only for the touch screen (like its name "shared_touch" implies). It has been added as a 'hack' to help using this tool to sync 2 X-Plane instances for anything related to the touchscreen only, because any other command is supposed to be synced by the tool you're using (like it is already syncing any command). NB: it is not a master/slave relationship. Provided you configure your tool to sync both ways, it will work both ways for the GTN too!
May 10, 20206 yr Hi everyone ! I am also trying to get the GTN 750 to sync using smart copilot. @Jean-Luc : Pourriez-vous me dire comment configurer les fichiers pour que ça fonctionne "de base" comme je peux le lire dans le thread ? Je serais aussi ouvert à aider dans le projet.
May 10, 20206 yr 10 hours ago, Maillouski said: Hi everyone ! I am also trying to get the GTN 750 to sync using smart copilot. @Jean-Luc : Pourriez-vous me dire comment configurer les fichiers pour que ça fonctionne "de base" comme je peux le lire dans le thread ? Je serais aussi ouvert à aider dans le projet. I almost got it working. The only issue I see, the -D-> and HOME buttons when used on the 2D panel of the GTN 750 do not replicate to the other computer. However, when pressing the same buttons from the 3D model of the GTN 750 present in the C172SP model modified to have the GTN750 in the dash that I downloaded, they do work. Maybe I just need to add the proper dataref of the 2D panel in the smartcopilot configuration file ? Where to look at? -- Je crois avoir réussi, sauf un léger problème : Les boutons -D-> et Home ne se transmettent pas si on les utilisent à partir du panneau 2D du GTN 750. Cependant, ils fonctionnent si on les utilise à partir du modèle 3D dans le tableau de bord de l'avion C172SP que j'ai trouvé, modifié pour afficher le GTN 750 dans le tableau de bord. Où est-ce que je pourrais trouver les datarefs correspondants au panneau 2D pour que je les ajoutent au fichier de configuration de smart copilot ? Edited May 10, 20206 yr by Maillouski
May 11, 20206 yr The 3D buttons might work because they are sending XPlane commands, which are intercepted by the GTN plugin. SmartCopilot is then also syncing these commands between the two instances because they are XPlane commands. However when using the 2D window, these are mouse clickspots solely intercepted by our plugin and interpreted locally, with no other 'backing' dataref or command to 'sync'. This is interresting a discussion and it was too late to implement any addition to the 2.5.25 update we've just released, but now that I know the 'touchscreen' dataref is working ok, I'll see to add a broader "Shared GTN" option, maybe next update, which will also provide the means to pass the commands from the 2D windows. No promises though.
May 11, 20206 yr 11 hours ago, RXP said: The 3D buttons might work because they are sending XPlane commands, which are intercepted by the GTN plugin. SmartCopilot is then also syncing these commands between the two instances because they are XPlane commands. However when using the 2D window, these are mouse clickspots solely intercepted by our plugin and interpreted locally, with no other 'backing' dataref or command to 'sync'. This is interresting a discussion and it was too late to implement any addition to the 2.5.25 update we've just released, but now that I know the 'touchscreen' dataref is working ok, I'll see to add a broader "Shared GTN" option, maybe next update, which will also provide the means to pass the commands from the 2D windows. No promises though. That would be very nice!
August 7, 20205 yr Hey Jean, Highly enjoying flying vfr with a friend in PilotEdge. Just wondering do we configure GTN #2 the same way? [GTN_750_2]UseSharedTouch = true 2) configure SmartCopilot to share this dataref:RXP/radios/indicators/shared_touch/GTN_750_2=0
March 9, 20224 yr I did want to ask, it seems that I am having an issue with the GTN's being improperly synced up. It seems when typing in waypoints it doesn't always work, is this a bandwidth issue?
Archived
This topic is now archived and is closed to further replies.