RemoteXY community — Arrays of devices - indirect addressing

Re: Arrays of devices - indirect addressing

2025-01-07T09:18:57Z

I have sorted the problem with the app crashing.

I had a page where I could see the called numbers.

I moved all of the indicators to the main page, but left the empty page in the configuration. That causes the app to crash on trying to connect. I deleted the page and everything works again.

Re: Arrays of devices - indirect addressing

2025-01-06T16:38:36Z

OK, so I think I've got this working.

Had an issue where the led that lit up was 1 greater than the *ledLinks[{variable}], and then I noticed that the links are addressed from 0. Changed my code accordingly, and think it's going to work, but I cannot test because every time I try to connect with the board, the app just shuts down. I've tried with both my iPad, and iPhone, they both do the same. Both can see the WiFi, so I don't know what the problem is.

I've shared link to the RemoteXY project, hope you can see if there is anything wrong with it.

https://remotexy.com/en/editor/d62dd980 … 692356677/

And here's the project code. Not complete just yet, bit of more work to do.... Note the GUI configuration is on another tab, and included. You can regenerate it from the shared project ?

// pRojeCt BINGO
// 
// License: Public Domain.

// Bingo number colours
#define bingo_blu 1
#define bingo_grn 2
#define bingo_red 3
#define bingo_yel 4
#define bingo_pnk 5

#include "RemoteXY.hpp" 
#include 

uint8_t topoftheshop;
uint8_t ball_called;
uint16_t called_number_sound = 1046;
uint16_t called_number_timing = 300;

uint8_t *ledLinks[] = {
  &RemoteXY.led_01,
  &RemoteXY.led_02,
  &RemoteXY.led_03,
  &RemoteXY.led_04,
  &RemoteXY.led_05,
  &RemoteXY.led_06,
  &RemoteXY.led_07,
  &RemoteXY.led_08,
  &RemoteXY.led_09,
  &RemoteXY.led_10,
  &RemoteXY.led_11,
  &RemoteXY.led_12,
  &RemoteXY.led_13,
  &RemoteXY.led_14,
  &RemoteXY.led_15,
  &RemoteXY.led_16,
  &RemoteXY.led_17,
  &RemoteXY.led_18,
  &RemoteXY.led_19,
  &RemoteXY.led_20,
  &RemoteXY.led_21,
  &RemoteXY.led_22,
  &RemoteXY.led_23,
  &RemoteXY.led_24,
  &RemoteXY.led_25,
  &RemoteXY.led_26,
  &RemoteXY.led_27,
  &RemoteXY.led_28,
  &RemoteXY.led_29,
  &RemoteXY.led_30,
  &RemoteXY.led_31,
  &RemoteXY.led_32,
  &RemoteXY.led_33,
  &RemoteXY.led_34,
  &RemoteXY.led_35,
  &RemoteXY.led_36,
  &RemoteXY.led_37,
  &RemoteXY.led_38,
  &RemoteXY.led_39,
  &RemoteXY.led_40,
  &RemoteXY.led_41,
  &RemoteXY.led_42,
  &RemoteXY.led_43,
  &RemoteXY.led_44,
  &RemoteXY.led_45,
  &RemoteXY.led_46,
  &RemoteXY.led_47,
  &RemoteXY.led_48,
  &RemoteXY.led_49,
  &RemoteXY.led_50,
  &RemoteXY.led_51,
  &RemoteXY.led_52,
  &RemoteXY.led_53,
  &RemoteXY.led_54,
  &RemoteXY.led_55,
  &RemoteXY.led_56,
  &RemoteXY.led_57,
  &RemoteXY.led_58,
  &RemoteXY.led_59,
  &RemoteXY.led_60,
  &RemoteXY.led_61,
  &RemoteXY.led_62,
  &RemoteXY.led_63,
  &RemoteXY.led_64,
  &RemoteXY.led_65,
  &RemoteXY.led_66,
  &RemoteXY.led_67,
  &RemoteXY.led_68,
  &RemoteXY.led_69,
  &RemoteXY.led_70,
  &RemoteXY.led_71,
  &RemoteXY.led_72,
  &RemoteXY.led_73,
  &RemoteXY.led_74,
  &RemoteXY.led_75,
  &RemoteXY.led_76,
  &RemoteXY.led_77,
  &RemoteXY.led_78,
  &RemoteXY.led_79,
  &RemoteXY.led_80,
  &RemoteXY.led_81,
  &RemoteXY.led_82,
  &RemoteXY.led_83,
  &RemoteXY.led_84,
  &RemoteXY.led_85,
  &RemoteXY.led_86,
  &RemoteXY.led_87,
  &RemoteXY.led_88,
  &RemoteXY.led_89,
  &RemoteXY.led_90
};


void setup() {
  // put your setup code here, to run once:
  RemoteXY_Init();
  randomSeed(analogRead(A0));
  called_number_indicators_reset();
  Serial.begin(115200);
  
  
}

void loop() {
  // put your main code here, to run repeatedly:

  RemoteXY_Handler();

  switch(RemoteXY.game_select) {
    case 0:  // 1-75
      topoftheshop = 75;
      RemoteXY.hide_76_80 = 1;
      RemoteXY.hide_81_90 = 1;
      break;

    case 1:  // 1-80
      topoftheshop = 80;
      RemoteXY.hide_76_80 = 0;
      RemoteXY.hide_81_90 = 1;
      break; 

    case 2: // 1-90
      topoftheshop = 90;
      RemoteXY.hide_76_80 = 0;
      RemoteXY.hide_81_90 = 0;
      break;    
  }

  if(RemoteXY.ball_gen) {
    RemoteXY.ball_gen = 0;

    // get a new random number
    // and test to see if ok
    do (ball_called=random(1, topoftheshop + 1));
    while (*ledLinks[ball_called] == 1);

    // called ball is valid, and new
    Serial.print("Ball Called ");
    Serial.println(ball_called);

    RemoteXY.called_number = ball_called;
    RemoteXY.called_sound = called_number_sound;
    delay(called_number_timing);
    RemoteXY.called_sound = 0;
    
    *ledLinks[ball_called - 1] = 1;
    
  }


}

void called_number_indicators_reset() {
  for (int i = 0; i < 90; i++) {
   *ledLinks[i] = 0;
   }
  }

Re: Arrays of devices - indirect addressing

2025-01-06T13:35:46Z

remotexy wrote:

yes, that's an interesting idea, maybe we'll do that in the future. There are more important tasks now. But I'll give you an example of how you can simplify your code. You can create a second array with references to variables in the RemoteXY structure and use it for cyclic operations.
struct {
    // output variables
  uint8_t led_03; // from 0 to 1
  uint8_t led_05; // from 0 to 1
  uint8_t led_01; // from 0 to 1
  uint8_t led_04; // from 0 to 1
  uint8_t led_02; // from 0 to 1

} RemoteXY;  

uint8_t *ledLinks[] = {
  &RemoteXY.led_01, 
  &RemoteXY.led_02,
  &RemoteXY.led_03,
  &RemoteXY.led_04,
  &RemoteXY.led_05
};

void loop() 
{ 
  RemoteXY_Handler ();

  for (int i = 0; i < 5; i++) {
     *ledLinks[i] = 1;
  }
}

It looks like that is exactly what I am hoping for, but you said "for cyclic tasks). Does this mean there's no relationship to the LED numbers, and the ledlinks just go through the RemoteXY array in the order they appear in the interface struct ?

If I have skillfully created my LEDs in the correct order, can I address them individually ?

Like....

void called_number_indicators_reset() {
 for (int i = 0; i < 91; i++) {
     *ledLinks[i] = 0;
  }
}

void called_number_indicators() {
   *ledLinks[ball_called] = 1;

  
//  if(ball_called == 1) RemoteXY.led_01 = 1;
//  if(ball_called == 2) RemoteXY.led_02 = 1;
//  if(ball_called == 3) RemoteXY.led_03 = 1;
//  if(ball_called == 4) RemoteXY.led_04 = 1;
....
//  if(ball_called == 90) RemoteXY.led_90 = 1;

Re: Arrays of devices - indirect addressing

2025-01-06T08:56:43Z

yes, that's an interesting idea, maybe we'll do that in the future. There are more important tasks now. But I'll give you an example of how you can simplify your code. You can create a second array with references to variables in the RemoteXY structure and use it for cyclic operations.

struct {
    // output variables
  uint8_t led_03; // from 0 to 1
  uint8_t led_05; // from 0 to 1
  uint8_t led_01; // from 0 to 1
  uint8_t led_04; // from 0 to 1
  uint8_t led_02; // from 0 to 1

} RemoteXY;  

uint8_t *ledLinks[] = {
  &RemoteXY.led_01, 
  &RemoteXY.led_02,
  &RemoteXY.led_03,
  &RemoteXY.led_04,
  &RemoteXY.led_05
};

void loop() 
{ 
  RemoteXY_Handler ();

  for (int i = 0; i < 5; i++) {
     *ledLinks[i] = 1;
  }
}

Arrays of devices - indirect addressing

2025-01-05T06:31:44Z

I'm tasked with creating a Bingo calling machine. Don't ask why, but it's there.

My code is sprawling out of control, because I have to address each "Called Number Indication" LED on the GUI independently.

So I have 90 statements to reset them, 90 statements to turn them on, 90 statements to map the internal array to the RemoteXY GUI, etc. etc. It is getting tedious to the extreme.

It would be great, and I have touched on this subject before, if we could have arrays of devices like Buttons and LEDs, addressing them by their index number. This would certainly make coding easier in many applications.

I don't see why this technique couldn't be extended to all of the GUI elements.