"Roving" Controller Detection Failure

[John Dowson]

I am not sure what can be done if the parking brake is being given the same GUID as one of your rudders... 

Can you try changing the ids assigned to your Parking Brake using the JoyIDs program. These are the current entries:

Quote

N, x00, x16D0, x3530, Parking Brake, -1, 5, 0, {NULL}, {F73B09B0-4B37-11EE-8008-444553540000}, {F73B09B0-4B37-11EE-8008-444553540000}, Y, Y
N, x00, x16D0, x3530, Parking Brake, -1, 12, 0, {NULL}, {FB5D7920-D8A3-11EE-8001-444553540000}, {NULL}, N, N

Try changing to use ids 13 and 14 (instead of 5 and 12). It would be better to remove that first entry completely, as the GUID for that entry is the same as the one for your Fulcrum One yoke, but if it is removed it will probably just get re-created.

Once you have changed the ids, run FSUIPC7 and re-attach your files again.

Have you installed any specific drivers for the Parking Brake, or do you just use the windows default drivers?
If you have installed specific drivers, try uninstalling them and using the standard windows drivers instead.
Also, who makes this Parking Brake - do you have a link?

 

[John Dowson]

Can you also add custom logging (Log->Custom) with a value of x200000 - this will log further information around the acquisition of HID devices.

[vanislepilot]

2 hours ago, John Dowson said:

who makes this Parking Brake - do you have a link?

https://www.desktopaviator.com/Products/Model_2400/index.htm
 

It’s a plug and play device, so I didn’t install any drivers manually. I’m assuming Windows drivers.

I will give your steps a try later today after I return home.

Many thanks 

Troy 

 

[vanislepilot]

Looks like I'm back in business, John! I connected the parking brake again and noticed that JoyID was registering it as controller 13 upon connection. Assuming this was the status quo leading to the problemc, I decided to skip the 13 slot and I swapped it into 14.

Ran FSUIPC with your debug code and this is what I get...

As far as I can tell, everything is looking good now! Thank you again for all the effort you've put into helping me - it's greatly appreciated!

Regards,

Troy

FSUIPC7.ini FSUIPC7.log FSUIPC7.JoyScan.csv

[John Dowson]

10 hours ago, vanislepilot said:

As far as I can tell, everything is looking good now! Thank you again for all the effort you've put into helping me - it's greatly appreciated!

Great!

Do you have two VPC Panels or just the one? The HID scanning reports two of these, but only one is acquired:  

Quote

Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk?

,,, HIDscanning completed

...
N, x00, x3344, x0259, , -1, -1, 0, {NULL}, {NULL}, {F73B30C0-4B37-11EE-800B-444553540000}, Y, N
N, x00, x3344, x0259, , -1, -1, 0, {NULL}, {NULL}, {F73B30C0-4B37-11EE-800C-444553540000}, N, N
...

,,, REGscanning completed
...
N, x00, x3344, x0259, VPC Panel #1, -1, 4, 1, {NULL}, {F73B30C0-4B37-11EE-800B-444553540000}, {F73B30C0-4B37-11EE-800B-444553540000}, Y, Y
N, x00, x3344, x0259, VPC Panel #1, -1, 12, 0, {NULL}, {F73B30C0-4B37-11EE-800C-444553540000}, {F73B30C0-4B37-11EE-800C-444553540000}, N, N
 

The 2nd one looks dodgy (N in ValsOk? column) so maybe there is only one of these devices and that can be ignored...

John

 

[vanislepilot]

Just the one VPC panel. What do you recommend in terms of “ignoring” it? Disabling that entry somehow or just continuing as is?

Thanks!

Troy

[John Dowson]

4 hours ago, vanislepilot said:

Just the one VPC panel.

Ah, ok then. Must be the device also returning a non-usable GUID for some reason.

4 hours ago, vanislepilot said:

What do you recommend in terms of “ignoring” it? Disabling that entry somehow or just continuing as is?

Just ignore. Your files look good!

Regards,

John