Fusion Controls Not Working - Solved

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

ImGoingCoastal

Active Member
View Badges
Joined
Oct 21, 2018
Messages
229
Reaction score
132
Rating - 0%
0   0   0
I just wanted to post this here because it kicked my butt for 2 days and was driving me batty.

I upgraded from an Apex Lite to an Apex Classic (I had both so why not use the one with two probe ports?)

Anyhow, I configured everything and was able to link my classic to fusion just fine, could even see all the changes being made via the apex dashboard locally. I thought there was some sort of connection issue. Like I said, I could control the Apex locally but when I try to access it through fusion, nothing happens. I checked every connection I could think of. Flashed the system and reprogrammed it. EVERYTHING.

Finally found the issue. I was putting the wrong format for the names of my outlets! I never once saw anything about this until I tried to program the outlets through fusion.

Once I changed the name of the outlets it worked like a charm! I guess colons aren't allowed?

This might be stupid but I thought I'd post it up because in two days of searches I found NOTHING even close to this.

For reference, "1-1:T5_Front" wouldn't allow me to control the port but "1_1-T5_Front" would.

Hopefully this helps someone from going crazy in the future.




BLUF: If local works and Fusion doesn't, rename your ports to something simple and test.
 
Yes, there are a number of rules to keep in mind:
  • Names for Inputs, Outputs, Profiles, and Modules can only include letters, numbers, dash "-", and underscore "_".
  • Input names are limited to 6 characters.
  • Output names are limited to 12 characters.
  • Profile and Module names are limited to 11 characters.
  • Names are Case Sensitive in your programming, so be sure to match case in your code.
  • No duplicate names are allowed, regardless of type.
  • Custom names should not begin with a built-in command name, such as "If", "Feed", "Fallback", "OSC", "Set", "Sun", "Moon", "Defer", "Min", "When".
 
Last edited:
Great info; however note that Profile and Module names are actually limited to 11 characters.


Yes, there are a number of rules to keep in mind:
  • Names for Inputs, Outputs, Profiles, and Modules can only include letters, numbers, dash "-", and underscore "_".
  • Input names are limited to 6 characters.
  • Outputs, Profiles, and Module names are limited to 12 characters.
  • Names are Case Sensitive in your programming, so be sure to match case in your code.
  • No duplicate names are allowed, regardless of type.
  • Custom names should not begin with a built-in command name, such as "If", "Feed", "Fallback", "OSC", "Set", "Sun", "Moon", "Defer", "Min", "When".
 
Great info; however note that Profile and Module names are actually limited to 11 characters.

Thanks for the clarification. I edited my post above to correct it.
 

IF YOU HAD TO TAKE A REEFING EXAM, WOULD YOU PASS?

  • Yes!

    Votes: 32 45.7%
  • Not yet, but I have one that I want to buy in mind!

    Votes: 9 12.9%
  • No.

    Votes: 26 37.1%
  • Other (please explain).

    Votes: 3 4.3%

New Posts

Back
Top