alan me too ,i want to speed him up a little.

@athena

how does a battleflipper recognice  a remote controller when they all are desame ? i gave them numbers  for visuel recognition .

battleflipper army

Hi there! It sounds like you’re building a Battleflipper Army and wondering how the robot can tell one remote controller from another when they’re physically identical-even if you’ve visually labeled them with numbers.

There are a couple of aspects to consider:

1. Physical vs. Logical Identification:
   The numbers you add on the remotes are great for our human eyes, but the Battleflipper’s control system (or its firmware/robot skill code) doesn’t "see" those numbers. To help the robot differentiate signals from each remote, you’ll need to add some form of logical or electronic identification.

2. Unique Configuration in Communication:
   Depending on what communication method you’re using (RF, IR, Bluetooth, etc.), the remote controller usually sends commands as data packets. Here are some ideas:

   • Customize the Transmission Code:
     If you can modify the code running on the remotes, consider incorporating a unique identifier (for example, a unique numeric code) into the data packets. Then the Battleflipper’s receiver or the corresponding robot skill in ARC can read that identifier and know which remote sent the command.

   • Channel or Frequency Separation:
     In some radio or wireless systems, you might be able to set each remote to operate on its own channel or frequency. This way, even though they look physically the same, the communication module differentiates them by the channel.

   • Pairing Mechanism:
     You could implement a pairing process so that the Battleflipper "knows" which remote controllers it should listen to by storing their unique IDs in a configuration file or global ARC variable. For example:

     // Example in ARC JavaScript
     var remote1ID = 101; // Unique ID for remote 1
     var remote2ID = 102; // Unique ID for remote 2
     
     // When a command is received, include code to check its ID:
     function onRemoteCommand(data) {
         var commandID = data.remoteID; // Assume your transmission includes a remoteID field
         if (commandID === remote1ID) {
             // Process command for remote 1
         } else if (commandID === remote2ID) {
             // Process command for remote 2
         }
     }
     

     In this simplified example, each remote embeds its own ID into the command data. The robot’s control logic then checks which remote sent the command before processing it.

3. Firmware or Skill Modification:
   If you’re using Synthiam ARC, you could create or adjust a robot skill to handle remote commands and incorporate the logic above. Check out our guide on creating robot skills for more details:
   Create a robot skill Overview

4. Next Steps:

   • Determine which communication method you’re using.
   • See if the remote controllers allow modifications to embed a unique ID.
   • Update the processing code (whether on the robot side or within the ARC robot skill) to check the incoming command’s identifier.

Does your current setup allow you to modify the remote controller’s code or configuration? Let me know what communication method or firmware you’re using, and I can provide more tailored guidance or sample code as needed!

#athena

here the answer from the seller . each controller needs a separt dongle .

Hello! Unfortunately, there isn't a specific manual available for this gamepad. However, it features a plug-and-play design, making it easy to set up. Simply connect the USB receiver to your device, and you're ready to go. If you have any specific questions about its features or usage, feel free to ask! do these have more then one signal ?

Yes, the gamepad features a dual controller setup, allowing for more comprehensive and immersive gaming experiences on PC, Android TV, and other compatible devices. This means you can connect two controllers to enhance your gameplay. If you have any further questions or need assistance, feel free to ask! how do i ad a signal to a robot for excample ?

To add a signal to a robot, you typically need to connect a compatible controller or device that can send signals. For example, if you're using a gamepad like the one we offer, you would connect the USB receiver to your device, and the gamepad will communicate wirelessly. If you have specific requirements or a particular robot in mind, please let me know, and I can provide more tailored assistance! lets say i have 4 wheel robots . does each robot need a dongle ?

Hello! For each of your 4-wheel robots, you will typically need a dongle or receiver to connect them wirelessly. This ensures that each robot can be controlled independently. If you have specific robots in mind, please let me know, and I can provide more tailored assistance!

Hi Nomad_6R,

Based on the seller’s response, here’s a summary that might help clear things up:

• Separate Dongle per Controller:
  The seller confirms that each controller requires its own USB dongle. This means if you’re using multiple controllers-for example, one for each of your 4-wheel robots-each robot will need its own dedicated dongle.

• Adding a Signal to a Robot:
  When we talk about adding a signal to a robot (for example, to trigger a function or movement), it generally involves:

  1. Connecting a Compatible Receiver:
     You connect the receiver (dongle) to your device so that the robot skill can pick up the wireless signals from the controller.

  2. Signal Processing in ARC:
     Within ARC (formerly EZ-Builder), you can use robot skills that are designed to process these input signals. If you need more specific behavior, you could even develop a custom robot skill that listens for specific data packets, which could include unique identifiers if you're programming in JavaScript or Python.

  3. Mapping the Signal to an Action:
     The robot skill then interprets the signal-mapping it to commands such as move forward, turn, or perform another custom action that you define. For example, you might develop a script like this:

     // Example JavaScript code snippet for handling a controller signal:
     var controllerID = getVar("$controllerID");
     
     if(controllerID == 1) {
       // Execute command for robot #1
       controlCommand("RobotSkill", "MoveForward");
     }
     else if(controllerID == 2) {
       // Execute command for robot #2
       controlCommand("RobotSkill", "TurnLeft");
     }
     // ... and so on for additional robots.
     

• For Your 4-Wheel Robots:
  If your goal is to control multiple robots independently, each should have its own dongle (or receiver) to ensure that signals from one controller are not mixed up with those from another. This makes it much easier for your ARC project to differentiate which robot is receiving which signal.

Does this answer your question?
Are you planning on handling all signals from multiple dongles within a single ARC project, or will each robot run its own ARC instance? Let me know if you need further clarification or any assistance in setting up the corresponding robot skills for processing these signals!