Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to execute different .ino codes for different Arduinos #478

Closed
rinon13 opened this issue Feb 23, 2023 · 1 comment
Closed

Unable to execute different .ino codes for different Arduinos #478

rinon13 opened this issue Feb 23, 2023 · 1 comment

Comments

@rinon13
Copy link
Contributor

rinon13 commented Feb 23, 2023

Description: When two different .ino codes are copied to two different Arduinos, the 1st Arduino's .ino code is overwritten by the 2nd one.

Steps to Reproduce

image

  1. Connect as shown above or take circuit from Gallery (Two Arduinos)
  2. Copy .ino code to first Arduino
void setup(){
	pinMode(13, OUTPUT);
}

void loop(){
	digitalWrite(13, HIGH);
    delay(1000);
	digitalWrite(13, LOW);
    delay(1000);
}
  1. Copy .ino code to second Arduino
void setup(){
	pinMode(12, OUTPUT);
    digitalWrite(12, HIGH);
}

void loop(){
}
  1. Check the .ino code of the first Arduino
  2. The .ino code of the first Arduino would have been overwritten by the second one
  3. If a different .ino code is copied/written to the first Arduino, the second one's code would also get overwritten

Expected Behavior: The .ino code of the respective Arduinos should not affect the other Ardionos. Different n number of .ino codes should be able to be written for n number of Arduinos.

Video of the process mentioned above:
Arduino_Parallel_Execution_Issue.webm

Additional information: The LED of Arduino 2 blinking even though the code does not provide any LOW input is a bug. (Already mentioned in Issue #476 ).

Version and OS:

  • OS: Ubuntu 22.04.1 LTS
  • Browser: Firefox 110

Tested on:

  • develop
  • simulation.iitbx.in
@firuza
Copy link
Collaborator

firuza commented Mar 4, 2023

Fixed in #479

@firuza firuza closed this as completed Mar 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants