Yahoo Groups archive

Casio CZ/ VZ/ FZ - Pro Series

Index last updated: 2026-04-28 22:42 UTC

Message

Re: VZ sysex bulk data transfers and error messages

2004-09-05 by steve_the_composer

--- In CZsynth@yahoogroups.com, "phonophobie" <sidstation@h...> wrote:
> Last night i tried to send sysex banks from midiOX to my VZ10m too.
> I was getting an ERROR message all the time. ( vz said something
> about midi error/ Check system ).

Here are the error messages I have been getting when sending VZ sysex 
data to the VZ-8m. (See my previous message about channel and data 
type matching.)
---------------------------------------------------------------
Message: --TRANS ERROR--- | CHECK SYSTEM!
Problem: Data channel <> VZ receive channel
Solution: Change VZ channel to match sysex file data.

Message: --MIDI ERROR--- | RECEIVE ERROR
Problem: Data type transmitted <> Data type expected
Solution: Select proper data type when loading data type into VZ.
---------------------------------------------------------------
To see the channel and size of data, you can use debug [PC].

EXAMPLE [VZCard9.syx]:
F0 44 03 00 70 70 02 F7
F0 = system exclusive data coming
44 = Casio product ID
03 = VZ line
00 = VZ-1 format data [02 = VZ-8m format data]
70 = channel 1 [7N where N = 0->F meaningchannels 1->16]
70 = open communication
02 = INT 64 voices + 64 op-mems
F7 = end of sysex transmission.

F0 44 03 00 70 74 . . . [data] . . . F7
74 = data is coming next

other codes for the 6th byte:
71 = close
72 = ok
73 = error
---------------------------------------------------------------
For the VZ-8m, I have the following SYSEX data sizes [received from 
VZ]:

65661 = FULL [Voice + Op-Men + Total]
65644 = VC+OP [Voice + Op-Mem]
43094 = VOICE
22672 = OPMEM

The VZ files posted in files are 55958 which I assume is the VZ-1/VZ-
10M VC+OP size.
---------------------------------------------------------------
Hope this helps.
--Steve

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.