PlanetZ forums - scopeusers.com

This is germain to those who are configuring systems with multiple CW boards, for example several Pulsar2s, or a P2 and a Luna.

Problem: the wrong board is showing up as the primary board (listed first in settings, loads hardware modules first).

Sol'n: Crack open cset.ini in Pulsar/App/Bin and insert tags to the effect of the following

e.g. "...

[board0]
boardid=1

[board1]
boardid=0

..."

This assumes you have two boards, and want to switch their order of appearance. Clearly, the important element is tagging the desired board with a "boardid=0". It's also essential to have a tag for *all* boards in the system if you have a [board#] tag for *any*. Thus,

"
[board1]
boardid=0
"

by itself (with out the complementary [board0] tag) will *not* work. Pulsar will yell at you when it tries to initialize in this case. Simple enough.

Now go make something that arouses ears. -E.

Darn nice 2nd post there!! WHOO!

Changing the board order is something I have been telling people to do to achieve lower latency, so it is nice to see it spelled out clearly here.

Why change board order? A multi-board Creamware setup will use the PCI interface of board0. If you have eg: a Pular1+Luna2, you know that only the Luna2 has ULLI. You can get the best performance and lowest latency if the Luna2 is board0. (You can still use ULLI settings without changing anything, but you might get crackles) In previous versions to V3, changing this setting in CSET.INI could give you that lower latency setting without clicks.

I'm curious now if V3 optimizes the CSET.INI for you, or if this will still be necessary...

<font size=-1>[ This Message was edited by: subhuman on 2001-11-03 00:26 ]</font>

Thanks for this excellent tip! Adding these lines actually helped me with communication error problem when loading some devices, namely Zarg's Rotor and the new Prophet plus demo. I've got 2 PulsarI boards. So experimentation is always the key when working with Pulsar . Happy New Year everybody!

gedas