Analogue-sequencer

--- In analogue-sequencer@yahoogroups.com, Tom Adam <tom.adam@p...> 
wrote:
> Mmm, I think I uploaded the previous build a week ago and was 
thinking 
> on uploading to the latest one. But I first downloaded the sysex 
> (patterns and stuff). I than initialised all banks and send the 
sysex 
> back. Got the badblock X message...

Although I advise a pattern data dump/restore around a firmware 
update, it usually isn't needed.

Do you always get the bad block flag if you try sending the dump 
again ?
If you always get it around the same time, there could have been an 
error in the reception of the dump at your PC (or whatever you 
dumped to) when you made the dump, and that bad block is stored in 
the syx file.
When I finally get things sorted so I'm not building them myself, 
maybe I can get round to that 'proper' librarian utility that'll use 
the handshaking messages to guarantee a successful transfer...

> Strange thing is, when I uploaded 3981 all seemed OK.

Not all midi errors are caused by dodgy opto-isolators.
There are other factors, and if you have already done a successful 
update, it could well be one of those.
But for the most reliable midi reception, I'm now using 6N137 opto-
isolators, with no R3.

> Is there a way to 
> check what version I'm running, At start up it shows 398. Does 
this mean 
> 3980 or 398(I don't show you)?

If you hold FUNC+PAGE at power-on to enter firmware update, you'll 
see a 4 digit hex checksum.
The checksum is the only way to tell for sure which build you have 
running. But I don't have a copy of the 3.981 or 3.980 syx files 
here, or a note of what the checksums were. Can anyone else oblige ?

Cheers,
Colin f

(having email problems again - no colinfraser.com email received all 
day Tuesday...)