Node Module in subtype

[Massetstephane]

Hi! I'm testing the mod and the Module Node in subtype :

                        MODULE
			{
				IDENTIFIER
				{
					name = ModuleEnviroSensor
				}
				DATA
				{
					sensorType = TEMP
				}
			}
			MODULE
			{
				IDENTIFIER
				{
					name = ModuleScienceExperiment
				}
				DATA
				{
					experimentID = temperatureScan
					experimentActionName = #autoLOC_502067 //#autoLOC_502067 = Log Temperature
					resetActionName = #autoLOC_502064 //#autoLOC_502064 = Delete Data
					xmitDataScalar = 0.5
				}
			}

It's ok for ModuleEnviroSensor, sensorType value modified as well by Subtype. But for ModuleScienceExperiment i have problem for the experimentID value

in wiki :

Any other values can be used to identify the module, e.g. engineID, experimentID

seem 's experimentID is not considered as DATA , it's possible to use this parameter as DATA in module DATA to have possibility to switch experimentID between barometerScan, temperatureScan for example. experimentActionName work resetActionName work xmitDataScalar work

But maybe it's not possible to use name like engineID, experimentID or finished by "ID".

I'm using and testing the mod on a Pitot airplane sonde Here

Steph.

[Gordon-Dry]

@MODULE:HAS[@DATA:HAS[#experimentID[temperatureScan]]]

[Massetstephane]

HI !

@Gordon-Dry

@MODULE:HAS[@DATA:HAS[#experimentID[temperatureScan]]]

It's a ModuleManager tag ?, it's work inside part.cfg, in SUBTYPE { MODULE{ etc, for B9Partswitch module ?

Looking the WIKI page i'm not sure, the switch work in Editor (VAB or SPH), i choose on the part the type of sensor

I will test anyway thank !

Steph.

EDIT Tested in the part cfg do nothing in module B9Partswitch but no error 👍🏼 , i think is about Dynamic-Modules And it's a module code i think, But well, that's okay I manage to manage the module "ModuleEnviroSensor" perfectly. I activate it I choose the sensorType, and it is indeed deactivated when I choose the option without sensor.

[blowfishpro]

You want to put experimentID in the IDENTIFIER block, it's one of the things that identifies the target module, not one of the things you're trying to change

[Massetstephane]

HI ! @blowfishpro thank, yes i understand now, I tested experimentID in node DATA (see first post), so the two tags experimentID and ModuleScienceExperiment are the tags used to recognize the module.

So it is not possible to detached experimentID for use as data in node DATA.

It would have been nice to be able to control the parameter of experimentID, to change the type of experience. experimentID = gravityScan , or experimentID = seismicScan for example.

Steph

[blowfishpro]

It's also just possible the module doesn't take well to it being changed. It's done in sort of a hanky way and not every module takes to it well.

[Massetstephane]

hi !

@blowfishpro ok thank 👍🏼 , it works well, anyway I control the module its function and it deactivates well when I choose the version without sensor it's perfect love the possibility with B9PartSwitch.

It's the first time I've used it, I use it to change the function of the module ModuleEnviroSensor, Between : ACC, TEMP, GRAV , PRES and no sensor (parameter sensorType ) and I vary the texture of a small indicator on the part. it is a part that is placed on the nose of aircraft cockpits to simulate a pitot tube, I have programming knowledge but not enough to make my own module for the moment.

Steph