Forum Replies Created
-
Posts
-
I have now tested the display modules, all the segments tested OK including the dots. The problem therefore must lie elsewhere, and my knowledge of the matter ends well before being able to fix it.
I now have two suitable display modules anyway, I’ll try soldering them on the board as a last resort.
Yes, I understood that the test should be done with the original firmware. I now shuffled through the presets present on the device and on some presets the edit+button does lit up a totally different button when pressing the two buttons on the first column on the left. Very peculiar that it only occurs on some presets while others work fine, but this settles the case then. 0.5 % huh, lucky me!
Hi Christian,
I haven’t made any changes to the presets after pulling the device from the shelf and flashing Zaquencer. I tested the buttons by entering edit mode as you suggested, but could not reproduce the erroneous behaviour on any button. I then reflashed the demo and found out that occasionally the note pitch button enters the note pitch mode as intended, but more often it randomises everything or enters some other mode. I haven’t yet found out what mode that might be, because turning a knob then doesn’t seem to do much to the audio.I understand next to nothing about electronics, so is the hardware bug definitely a faulty display module, or could some other faulty component also result in this kind of behaviour? The author mentions that two segments on his display were dead. The segments all displayed correctly when I entered different modes and checked the display visually, but it is of course possible that some combinations don’t work properly. I’ll have to check both modules with my multimeter later.
Thanks for help, I’ll report my findings I’ve had the chance to test the display.
In fact the original firmware is 33 % larger and writes more blocks. Thanks for trying to help anyway. Anyone else want to pitch in and help me get this thing together?
I reflashed the device with original firmware 1.10 and all buttons and controllers worked as intended i.e. without any crosstalk, unresponsiveness or other issues, so it doesn’t seem to me that the problem is in the hardware. I then reflashed Zaquencer demo, but the problem persisted. I then tried flashing Zaquencer with Bome SendSX and got what appears to be a clean flash,
F0 00 20 32 7F 15 35 00 2F 00 F7 F0 00 20 32 7F 15 35 00 3F 00 F7 F0 00 20 32 7F 15 35 00 4F 00 F7 F0 00 20 32 7F 15 35 00 5F 00 F7 F0 00 20 32 7F 15 35 00 6F 00 F7 F0 00 20 32 7F 15 35 00 7F 00 F7 F0 00 20 32 7F 15 35 01 0F 00 F7 F0 00 20 32 7F 15 35 01 1F 00 F7 F0 00 20 32 7F 15 35 01 2F 00 F7 F0 00 20 32 7F 15 35 01 3F 00 F7 F0 00 20 32 7F 15 35 01 4F 00 F7 F0 00 20 32 7F 15 35 01 5F 00 F7yet still it does not work properly. Is there anything else I could try?
Couldn’t say really, the device has mainly been sitting on a shelf for the last few years until I finally found some sensible use for it.