Sponsored Content
Operating Systems OS X (Apple) The Alternate DC board for AudioScope.sh. Post 302947884 by wisecracker on Tuesday 23rd of June 2015 02:28:20 PM
Old 06-23-2015
The Alternate DC board for AudioScope.sh.

Hi guys...

Well I have entered an area of partial insnity... ;o)
Below is a photo of the 'ALTDC' board for AudioScope.sh...

I have decided to incorporate all three methods for obtaining DC into this MBP via the MIC input.

1) VFO.
2) CHOPPER.
3) COUNTER.

The controller for the COUNTER is not yet done but this board can now do 1) and 2).

I have started properly coding for the VFO section first but and I have decided just to do an accuracy of 4 bit depth for this. That is 0 - +2V to an accuracy of 0.125V.

I have an example basic piece of code that checks ranges of values so as to create each of the 16 values possible. The problem is it is ugly and 16 conditional "if"s is not the way to go. Again I can't find any info how to create a look up table where each lookup is a range of values. The EXAMPLE code below DOES work mighty fine but looks so ugly and primitive.

Any other ideas guys?
Code:
#!/bin/bash
# lookup
while true
do
	read -p "Number, 100 to 499:- " num
	if [ $num -ge 100 ] && [ $num -le 199 ]
	then
		echo "1) $num"
	fi
	if [ $num -ge 200 ] && [ $num -le 299 ]
	then
		echo "2) $num"
	fi
	if [ $num -ge 300 ] && [ $num -le 399 ]
	then
		echo "3) $num"
	fi
	if [ $num -ge 400 ] && [ $num -le 499 ]
	then
		echo "4) $num"
	fi
done

This simulates 2 bit depth but looks SOOO ugly...

Now the photo...
Top Left:
The CHOPPER with the option of the diode DC offset removing the blue link.

Bottom Left:
The 9V PP3 input to 5.1V supply.

Middle:
4 transistor VFO used for the first part of the DC code.

Top Right:
The VFO test circuit using the two black links connected and transistor input for measurement when links disconnected.

Bottom Right:
3 terminals, top terminal multivibrator output for 3) and for detection.
Middle terminal for the DC input.
Bottom terminal is one of the ground terminals.
To keep this simple it took some working out...

Enjoy. Bazza...
The Alternate DC board for AudioScope.sh.-dc2jpg
 

9 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Board Maintenance

Just a remark now the board has grown to considerable proportion. I see too little of an active hand(s) maintaning the boards, clipping away dead posts, moving posts that were created in the wrong forums etc. It's a bit tiring to see alot of threads ending in: this has been covered before, do a... (7 Replies)
Discussion started by: patvdv
7 Replies

2. What is on Your Mind?

AudioScope has had a magazine review. <shock>

Hi Admin and Staff... Thanks for hosting AudioScope.sh on this site. I have had the biggest surprise of my life today. This months issue of the UK Linux magazine "Linux Format" have done a small piece on the project. Issue April 2014, LXF 182, page 65... This I never expected and I... (1 Reply)
Discussion started by: wisecracker
1 Replies

3. OS X (Apple)

AC to DC trigger pulse for AudioScope.sh.

Hi all... Has _below_ ever been done in UNIX shell scripting before? (I have done this easily in Python but this is using purely the shell.) The DEMO version IS built and has been tested. Pre-amble... I now need at least one control pulse for the AudioScope.sh when in PURELY audio I/O mode,... (2 Replies)
Discussion started by: wisecracker
2 Replies

4. Shell Programming and Scripting

Experimental awk audio converter for CygWin and AudioScope.sh

Development machine:- Standard MBP 13 inch, OSX 10.7.5... GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin11) Copyright (C) 2007 Free Software Foundation, Inc. Scenario:- Audio capture for AudioScope.sh for CygWin without ANY third party installs. I am trying my hardest to get a... (6 Replies)
Discussion started by: wisecracker
6 Replies

5. How to Post in the The UNIX and Linux Forums

Board not present

Can please somebody tell me what could be the reason for the following error (Unix Motorola Server): /usr/etc/ce3/s374: Board at address 0xff10000 not present - Entry skipped. /dev/lpc2: I/O error I already replaced the board 374 on the server, but I have the same problem. Thank you! (1 Reply)
Discussion started by: dma
1 Replies

6. What is on Your Mind?

AudioScope...

Boy oh boy, with only a MONO mic input to use AudioScope gets much more difficult when the ALTDC board is included. It needs, so far, two hits at the MIC input with a single hit at the HEADPHONE audio output. The first at the highest practical resolution for the AC component and the second... (0 Replies)
Discussion started by: wisecracker
0 Replies

7. OS X (Apple)

The DC Control and Timer boards for AudioScope.sh...

Hi all... Apologies for any typos... For those intersted in the AudioScope the next construction is finished. I have not been totally idle but working out the hard stuff to be able to be very simple to build. It is a single transistor simple timer that lasts for about 1.2 to 1.8 seconds.... (2 Replies)
Discussion started by: wisecracker
2 Replies

8. UNIX for Advanced & Expert Users

Has AudioScope found a bug in bash 4.4.5?

Using AudioScope.sh on Ubuntu 17.04 from a live DVD disc I came across an error. Consider the code below it is a MUCH shortened version of the KEYBOARD input in AudioScope. #!/bin/bash bash --version uname -a status=0 KEYBOARD() { read -r -p "Enter QUIT or EXIT to quit:- " kbinput if ||... (11 Replies)
Discussion started by: wisecracker
11 Replies

9. OS X (Apple)

AudioScope Project.

AudioScope Project. (Apologies for any typos.) For the few following...... AudioScope.sh... Now at Version 0.60.00. Well this baby has come a long way since its inception in January 2013. It is now at Version 0.60.00. It is MUCH more Apple centric now with a new OSX Sierra minimum _silent_... (7 Replies)
Discussion started by: wisecracker
7 Replies
I2C_REGISTER_BOARD_I(9) 				      I2C and SMBus Subsystem					   I2C_REGISTER_BOARD_I(9)

NAME
i2c_register_board_info - statically declare I2C devices SYNOPSIS
int i2c_register_board_info(int busnum, struct i2c_board_info const * info, unsigned len); ARGUMENTS
busnum identifies the bus to which these devices belong info vector of i2c device descriptors len how many descriptors in the vector; may be zero to reserve the specified bus number. DESCRIPTION
Systems using the Linux I2C driver stack can declare tables of board info while they initialize. This should be done in board-specific init code near arch_initcall time, or equivalent, before any I2C adapter driver is registered. For example, mainboard init code could define several devices, as could the init code for each daughtercard in a board stack. The I2C devices will be created later, after the adapter for the relevant bus has been registered. After that moment, standard driver model tools are used to bind "new style" I2C drivers to the devices. The bus number for any device declared using this routine is not available for dynamic allocation. The board info passed can safely be __initdata, but be careful of embedded pointers (for platform_data, functions, etc) since that won't be copied. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 I2C_REGISTER_BOARD_I(9)
All times are GMT -4. The time now is 08:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy