-
| Hi, a midi device I've made, receive and read sysex message with this function : void OnMidiSysEx(byte* pData, unsigned length) {
  std::string myString((char*)pData, length);
  String message = myString.c_str();
  ChaineMemoire = message;
}Everything is ok with ios app I've developped to send message to my device now I wanted to send sysex with another device I made using this code : #include <MIDI.h>
MIDI_CREATE_DEFAULT_INSTANCE();
void sendsysex() {
   uint8_t sysex[] = {0xF0, 0x65, 0x73, 0x73, 0x61, 0x69, 0x0A, 0xF7};
   MIDI.sendSysEx(8, sysex, false);
}
void setup() {
  MIDI.begin();
  // put your setup code here, to run once:
}
void loop() {
  sendsysex();
  delay(5000);
}and the message don't seems to be received. what do I do wrong ? | 
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
| Your message does contain the SysEx boundaries (0xF0 and 0xF7), so you'll need to pass  void sendsysex() {
   uint8_t sysex[] = {0xF0, 0x65, 0x73, 0x73, 0x61, 0x69, 0x0A, 0xF7};
   MIDI.sendSysEx(8, sysex, true);
} | 
Beta Was this translation helpful? Give feedback.
-
| HI,
same thing, message doesn’t seem to be read.
I’ve tested wiring, cables etc. everything is fine.
thx !…  Le 19 févr. 2023 à 11:08, François Best ***@***.***> a écrit :
 Your message does contain the SysEx boundaries (0xF0 and 0xF7), so you'll need to pass true to the last argument of sendSysEx:
 void sendsysex() {
    uint8_t sysex[] = {0xF0, 0x65, 0x73, 0x73, 0x61, 0x69, 0x0A, 0xF7};
    MIDI.sendSysEx(8, sysex, true);
 }
 —
 Reply to this email directly, view it on GitHub <#322 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA3KNRUGPXCICERKSCRIBXLWYHWIVANCNFSM6AAAAAAVAUOVGY>.
 You are receiving this because you are subscribed to this thread.
 | 
Beta Was this translation helpful? Give feedback.
-
| ok merci !
c’etait un faux contact ……  Le 19 févr. 2023 à 11:21, François Best ***@***.***> a écrit :
 Could you use a MIDI monitor to inspect what is sent by the iOS app (and understood by your receiving device), and what is sent by your emitting device, and find the difference?
 —
 Reply to this email directly, view it on GitHub <#322 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA3KNRQRFPOLHN5P3GGAGYTWYHXZVANCNFSM6AAAAAAVAUOVGY>.
 You are receiving this because you are subscribed to this thread.
 | 
Beta Was this translation helpful? Give feedback.
-
| Voila 😂.Le 19 févr. 2023 à 21:55, François Best ***@***.***> a écrit :
Le coup classique. 😅
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> | 
Beta Was this translation helpful? Give feedback.
Your message does contain the SysEx boundaries (0xF0 and 0xF7), so you'll need to pass
trueto the last argument ofsendSysEx: