You are reading a single comment by @indianajones and its replies.
Click here to read the full conversation.
-
Fri 2019.10.25
'the real count is actually 67,786 bytes'
Two observations:
1) 67786 is greater than 65535 - might be a factor
2) From #15 available JsVars 3995 (understood that program may have grown in the last week)
67786 / 16 = 4237
What is the program usage, and/or free space before the data fetch? (on EspruinoWiFi not via Node.js)
@Gordon,
I have a minimal nodejs app that extracts the data from the audio mixer. I was way off in the total number of bytes - the real count is actually 67,786 bytes for the entire state of the mixer. Here is the code that successfully got the message dump (obfuscated IP address):
I've attached the file that represents the data dump (and there is no missing data from what I can tell). The data dump is a file of space-separated hex values, each representing a byte received from the mixer. At the very end, you'll see a few 'fe' single-byte messages, which is the MIDI ActiveSense byte sent once-per-second by the device. The fact that only 'fe' is being sent at the end of the data means the mixer has completed its dump of NRPN and SysEx data.
I dumped the messages as they arrived - no buffering or messing with the data. Each newline represents the end of the data for that particular message. If you need the file in a different format, let me know and I'll see what I can do.
Edit: how fast can the wifi go? For my project to work, it's gotta be pretty close to real network speeds. I saw 13Mbps was being mentioned on the internet - is that possible?
1 Attachment