Page 4 of 5

Posted: Mon Aug 13, 2007 11:44 am
by babamoog
Here is a way to test your sysex delivery system.

If you have two midi adapters, then loop them together, either with a cable or an external midi device that has 'Thru' capability. Then you can send the sysex out one port, and use Midi-Ox to record the rx'd version.

Check the sizes of the files as a first check to see if they are different. If same size, then use a program like WinHex to do a byte by byte compare.

Posted: Mon Aug 13, 2007 12:36 pm
by Ghost
Hi Babamoog, thanks for the help.

I've just connected my Uno to the MIDI in/out of the Saffire box, and set the input device in MIDIOX accordingly. When i send the 1.03c file via SyxLoader it is showing activity in the Input monitor window of MIDIOX (huge amount of pink text) but i can't see any way to check the filesize etc..

When i turn on logging, it does'nt seem to actually record anything to the midilog.txt file in the MIDIOX directory, not sure whats wrong.

Can you explain how to log the transfer?

Posted: Mon Aug 13, 2007 2:19 pm
by babamoog
I don't know Midi-Ox that well, so maybe someone else can explain how to record a sysex file.

I will check it out later, but someone else might know right now.

But if you can see data going out and data going in, then you are nearly there. Just need to record it to a file.

Posted: Mon Aug 13, 2007 3:49 pm
by babamoog
OK, here is how to record a sysex file in Midi-Ox.

Select Actions/Send/Sysex File.

Then cancel the file selection.

Now you will see the Sysex View and Scratchpad window.

Then select Sysex/Receive Manual Dump.

Now you will get a small window that waits and counts the bytes coming in.

Send the sysex file and you should see the byte counter change.

After the file has been sent, select done. Now Right Click in the Display Window and select Save As. The Display Window is the lower window in the Sysex View and Scratchpad window.

Posted: Mon Aug 13, 2007 4:35 pm
by Ghost
Thanks a lot babamoog, looks like we could be on to something now!

After completion the dump reads 119856 bytes recieved. The readme for the update says that the 1.03c OS is 119857 bytes, so for some reason it's one byte short.

Maybe this is the what is causing the problem?

EDIT: i just repeated the dump twice more to be on the safe side, and sure enough it is coming up 1 byte short every time.

Posted: Mon Aug 13, 2007 6:11 pm
by babamoog
Well, that's what the PC exe says it is sending. But I've just downloaded the 1.03C sysex and the length is 119856.

Now use WinHex to do a byte compare of the results with the original. Get it here:

http://www.x-ways.net/winhex/

Now, open both the original and the rx'ed sysex files using the File/Open menu.

They should both appear, under different tabs.

Now select Tools/File Tools/Compare. You should see both files listed as 1st file and 2nd file.

Select OK to do the comparison. You will have to select OK twice, as the first time it fills in the compare length. If the files are the same, a little window pops up to say so, otherwise a difference report is written to a text file that you can view with notepad.

Posted: Mon Aug 13, 2007 6:33 pm
by Ghost
Ok i have just done as you suggested, and WinHex found no differences between the 2 files.

So i guess this suggests that there is no problem with my computer/drivers etc.. after all, and the LP must be faulty ? :(

Posted: Mon Aug 13, 2007 7:31 pm
by babamoog
OK, you've taken your delivery system out of the picture now. But it sounds like it could have been a problem originally if you did not get the Midi-Ox buffer settings correct.

Let tech support know, I'm sure this info will help them.

But my advice is to try an earlier version, now that you know your delivery system is ok now. Could be the C version is having a problem with your unit.

Posted: Mon Aug 13, 2007 7:39 pm
by Ghost
First flash was actually attempted with the executable tool, that's when it 'hung' and just never worked again. I figured it was probably the best idea at the time since i never used any kind of Sysex programs before :(

Hopefully Amos or Steve will see this and tell me whether i should try to send it in for repair under warranty or perhaps there is some other file i might be able to try.

Thanks again for your help, i really appreciate it. Sucks that my LP is still out of action, butat least i know now that my computer is not the problem.

Posted: Mon Aug 13, 2007 7:44 pm
by babamoog
OK, if the first attempt was with the exe, then it appears your machine has a problem with the C version. Try an earlier version if you have one, preferably using the exe.

Posted: Mon Aug 13, 2007 7:52 pm
by Ghost
I've tried flashing with 1.03b a few times, it still hangs after the update but when i restart the LP manually afterwards the startup screen will show momentarily (with 1.03sb), but then the screen returns to 'SEND FIRMWARE SX' after that.

Are there any older revisions than 1.03b i could try? I looked on the Moog site and also Googled but nothing came up.

EDIT: i have only tried flashing 1.03b using SyxLoader/MIDIOX though, i don't have the .exe version of that OS.

Posted: Mon Aug 13, 2007 8:01 pm
by babamoog
OK, post a mangled e-mail address and I'll send you a B exe. Might be a while as I'm not at home.

Posted: Mon Aug 13, 2007 8:05 pm
by Ghost
Cheers! sent my address in PM :)

Posted: Tue Aug 14, 2007 9:30 am
by Ghost
Thanks for sending me those files last night baba, unfortunately neither of them have got the LP up an running :( When i try to install 1.03a/1.03b i get the startup screen briefly when i turn the LP on, but then it resets to the SEND 'FIRMWARE SX' again.

I'll wait on Amos/Steve to comment now before i contact CS for a return. Maybe they have some magic program i can run to clear the memory in the LP.

Posted: Tue Aug 14, 2007 9:35 am
by Amos
Hi Ghost,

Did you not get my email from Monday? I haven't heard back from you.

I think I know exactly what the trouble is. If you haven't heard from me, email again to amos at moogmusic dot com. Thanks!