non controler nat7210 scanned but no answer

[montagnard]

I am programming a nat7210 I follow the initialisation sequence of programming manual chapter 5. But when I lauch measurement and automation explorer and scan my device I get a DEC interrupt on my device.

During initialization I put in AUXE 0x3 and when I get DEC interrupt I put 0xF (val) in AUXMR. I don't know if it is good but it seems to work.

Moreover I get also ADSR interrupt but I don't know how to handle this kind of interrupts.
Futhermore after few seconds the mesurement and automation explorer fail to find a device.

I can't find any documentation about scanning algorithm for a nat7210 device. Could you send me that is the good sequence in order to be detected by automation and lauch explorer.

Regards

[ScottieB]

There's nothing that you need to do that is "special" for being detected in MAX.  As long as your device responds to at least 1 command that is written to it, it will show up as an instrument with "scan for instruments".  If it responds to *IDN? in compliance with SCPI and returns information about itself, then you will see that information in MAX as well.

I don't believe that MAX does a device clear (which would cause your DEC interrupt).  What addressing mode are you using?  If you're trying to just get a basic instrument up and running you should use "Impletementing one logical device: Normal Addressing" at the bottom of page 5-3.  If you're getting ADSR interrupts, I would expect you to be using "No addressing" mode and writing that mode to your ADMR.  Is that what you're doing?

Scott B.

GPIB Software

[montagnard]

I use normal addressing ie writing 0x31 to ADMR than writing myaddress (0x1) to ADDR1 (0x6) than 0xE0 to ADDR2 (0x6).

Il still get 0x85 for ISR2 and 0x8 for ISR1.

Regard

Bastien

[Collin M]

Can you verify you have the correct addresses for the registers in your firmware? I doesn't make sense to read 0x85 from ISR1, but it may make sense that ISR0 is 0x85.