Tones Tidbits

Because I use them so infrequently I forget...

Base current flows out of base, Emitter is +ve supply, collector is output

If the NC pin associated with the ICPORT (pin 34) is not pulled to 5V, PORT D, PORT E, SPP & something else are all disabled. Writes to those registers are ignored, contents stay at zero...

It's poorly documented. It's extremely hard to follow. It's very difficulty to modify successfully. Damn, it's even hard to compile it without even makign any changes!

It's rarely updated to take into account the fact that the new IDE won't compile the existing code.

radix -hexadecimal

add wave \ {sim:/testbench/DUT/FIFO/WE } \ {sim:/testbench/DUT/FIFO/RE } \ {sim:/testbench/DUT/FIFO/WCLOCK } \ {sim:/testbench/DUT/FIFO/RCLOCK } add wave -divider <1st> add wave sim:/testbench/DUT/FIFO/WE add wave -divider <2nd> add wave /testbench/* add wave sim:/testbench/DUT/* add wave sim:/testbench/DUT/ADC_SM0/* run -all

If a trigger doesn't work properly, stop and re-start in "Measurement Configuration"

Help files:

C:\Program Files (x86)\Common Files\dSPACE\HelpDesk 2014-A\Print\ControlDeskNextGenerationBasicPracticesGuide.pdf

Page 549/1016...

"Specify the variable you want to use for triggering. Select it in the Variable Browser and drag it onto the platform trigger in the tree or the Variable Mappings list in the platform trigger configuration."

Also...

Page 546/1016

"Pretriggering and posttriggering of data captures"

"With triggered measurement, it is possible to perform pretriggering and posttriggering. You must specify a trigger delay for the start trigger for this.

A pretrigger time is a period of seconds for starting data capture

before the start condition is met. A pretrigger time must be defined as a negative delay for an enabled start trigger. For example, with a delay value of -0.5, ControlDesk will actually start the data capture 0.5 seconds before the start condition is met.

A posttrigger time defines a period of seconds for delaying data

capture after the start trigger is invoked. A posttrigger time must be specified as a positive delay for an enabled start trigger. For example, with a delay value of 1, ControlDesk will actually start the data capture 1 second after the start condition is met."

Use

`ifdef MODEL_TECH  if it doesn't work, check the source file is included in the .do file

In just about every way, this is one of the worst pieces of software I've ever had the misfortune to use. It crashes, it won't autosave, it barely works anyway and it's limitations are so plentiful it's hardly worth it...

It's now been the downfall of 4 keyboards and a monitor, with plenty more damaged...

Proteus Ares PCB is obviously completely and unbelievably awful... You probably know that if you're reading this.

Thanks to http://www.slideshare.net/Mashood/pcb-design-using-proteus-18385708 I realise that the answer to my problem is trivial - Auto Trace Style Selection was turned on by default (not by me, because it prevents the software working usefully). turn it off, and one can select any trace width...

Auto-trace style selection prevents routing by changing from a narrow track to a wider one, then failing DRC and not allowing a route to be placed... How stupid!

On PIC32MX764:

JTAG default is on for release, off for debug - so output pins RB10 RB11 RB12 RB13 only work in debug

To turn off JTAG: