e-licktronic Forum

Dears, I just finished to build my new Nava, great kit.

I'm facing a strange behavior that I cannot understand (and solve) since I'm not an expert of Nava, neither an expert of the classic 909:

The tempo stays always stick to 0, if I go into pattern or song play mode there's not sequencer running, If I try to adjust the tempo, the data knob does not allow me to move from 000.
I tested the knob and it is working, in another menu section I clearly see it is working (for example moving a cursor from right to left and vice versa).

What can it be?
Of course I tried pressing play/stop, the Nava changes its operation mode but still tempo on 0.

Thank you,
Daryl.

No one can help?

Additional detail: I've updated the firmware with my JTAGICE3 through Atmel Studio 7, so the last firmware is on duty.
I preferred to use Atmel studio instead of atprogram through "command line" (that is not CMD), due to its capabilites to read fuses, dump memory etc. I know it's the same, but well, it's not.

Moreover, I just discovered I got 3 EPROMs with the same sound, an HiHat. Duh!

daryldee wrote:No one can help?

Additional detail: I've updated the firmware with my JTAGICE3 through Atmel Studio 7, so the last firmware is on duty.
I preferred to use Atmel studio instead of atprogram through "command line" (that is not CMD), due to its capabilites to read fuses, dump memory etc. I know it's the same, but well, it's not.

Moreover, I just discovered I got 3 EPROMs with the same sound, an HiHat. Duh!

Sometimes apparently insoluble problems are caused by the simplest reasons: bad contact. Try reheating all solder pads in the sequencer section and apply a bit of solder to each of them. I would also check continuity around X1 crystal.

Hey daryldee,

have you checked whether Nava is in external Sync mode?
It happened to us when we finished our sequencer part, we couldn't figure out why the sequencer wouldn't play and it was in external sync.

Hit shift + tempo to go to the Config page. Have a look at the case here if you don't know which buttons they are: viewtopic.php?f=24&t=797 .

The first highlighted Setting should be the Clock. If it's Ext, turn the encoder to set it to Int. Hit Enter to save.

You should now be able to hit Play Mode and turn the Encoder to a tempo.

(If that works out for you, you might want to go back to the Config page, Click the Encoder until you have selected Bpm, and turn the encoder to set it to something different than 255. Hit Enter again to save the default BPM your Nava boots up with).

groovelastig wrote:Hey daryldee,

have you checked whether Nava is in external Sync mode?
It happened to us when we finished our sequencer part, we couldn't figure out why the sequencer wouldn't play and it was in external sync.

Hit shift + tempo to go to the Config page. Have a look at the case here if you don't know which buttons they are: viewtopic.php?f=24&t=797 .

The first highlighted Setting should be the Clock. If it's Ext, turn the encoder to set it to Int. Hit Enter to save.

You should now be able to hit Play Mode and turn the Encoder to a tempo.

(If that works out for you, you might want to go back to the Config page, Click the Encoder until you have selected Bpm, and turn the encoder to set it to something different than 255. Hit Enter again to save the default BPM your Nava boots up with).

Good point and an even more simple solution...

hehehe yeah, the Occam's razor...

Aaaaaanyway, not... well, I wish yes, but I see a really strange behaviour in my Nava. :/

groovelastig wrote:Hey daryldee,

have you checked whether Nava is in external Sync mode?
It happened to us when we finished our sequencer part, we couldn't figure out why the sequencer wouldn't play and it was in external sync.

Hit shift + tempo to go to the Config page. Have a look at the case here if you don't know which buttons they are: viewtopic.php?f=24&t=797 .

The first highlighted Setting should be the Clock. If it's Ext, turn the encoder to set it to Int. Hit Enter to save.

You should now be able to hit Play Mode and turn the Encoder to a tempo.

(If that works out for you, you might want to go back to the Config page, Click the Encoder until you have selected Bpm, and turn the encoder to set it to something different than 255. Hit Enter again to save the default BPM your Nava boots up with).

Thanks groovelastig, this helped changing the Nava behaviour from "what are you looking to" into "I'm happily blinking and I can switch between play and stop".
You were right! now I can change the tempo, I played a bit with settings changing SYN from SLV (Slave?) to MST (Master?) and the PCh (??) from FRE to SYN and after changing SYN to MST now I got blinks and tempo.

The only thing is that nothing happens!
I really tried, but even following the manual there's no way to play a freaking instrument in sequencer mode.

I checked all the ICs, CAPS, resistors.
I checked the atmega1284p fuses and the clock source is set correctly (Full swing, slow rise, 256K) and the micro is working properly.
It seems there's something wrong with the software, I simply cannot do anything except going in tap mode, listening sounds and play with blinking buttons in Pattern or song mode. It is strange, all the buttons reacts properly, but not the software. Following the manual, many instructions do not correspond.

Atmel studio says the micro is not an atmega1284p but a atmega1284, the device signature does not correspond. Tomorrow I will read the datasheet to see if there's something that can make the difference, but I don't think so. Eventually I may program an IO testing firmware.

Please, tell me I simply don't know how to use the Nava

KlangGenerator wrote: Sometimes apparently insoluble problems are caused by the simplest reasons: bad contact. Try reheating all solder pads in the sequencer section and apply a bit of solder to each of them. I would also check continuity around X1 crystal.

Yes Klang, you are right, I gotta check again solders. I hope it is something like that.

daryidee,

Do you intialize the EEprom ?

Ehm, no...

Issues update:

1) Tempo stick to 0 was caused by the miss initialization of the eeprom
2) Strange Crash and Ride sound was caused by a clock issue, thanks Vincent to helping me out on this thing. At the end I have swapped 68K resistors with 6.8K and vice versa

For the records
Thanks to everyone!