Here is my code : http://ge.tt/89oox98?c
I would like to give me some hints to manage the problem with the clock as i had describe in post 618.
I would like to give me some hints to manage the problem with the clock as i had describe in post 618.
I think your problem is because you used the "case else" for this subroutine
Select Case Command
Case 16 : Call Vol_up
Case 17 : Call Vol_dw
Case 13 : Call Mute
Case 12 : Call Poweronoff
Case 62 : Call Menu
Case Else : Call Datetime
End Select
End If
The compiler translate it into an assembler code and it looks then completly different.
To make things worser this "select case works" different with other compilers.So I'm not sure how your compiler does translate it.
I would try a different approach like this:
Call Datetime
Select Case Command
Case 16 : Call Vol_up
Case 17 : Call Vol_dw
Case 13 : Call Mute
Case 12 : Call Poweronoff
Case 62 : Call Menu
End Select
End If
In this way the routine Datetime is separated from other routines.
Select Case Command
Case 16 : Call Vol_up
Case 17 : Call Vol_dw
Case 13 : Call Mute
Case 12 : Call Poweronoff
Case 62 : Call Menu
Case Else : Call Datetime
End Select
End If
The compiler translate it into an assembler code and it looks then completly different.
To make things worser this "select case works" different with other compilers.So I'm not sure how your compiler does translate it.
I would try a different approach like this:
Call Datetime
Select Case Command
Case 16 : Call Vol_up
Case 17 : Call Vol_dw
Case 13 : Call Mute
Case 12 : Call Poweronoff
Case 62 : Call Menu
End Select
End If
In this way the routine Datetime is separated from other routines.
When i'm increasing the volume with rc5 remote control and because the control sends low pulses i'm getting the clock between the numbers on my lcd
I have the volume : 15 , if i want to change the volume from 15 to 20, i'm holding the volume up button on the RC5 and start increasing but while i'm holding the button i'm getting the time between the numbers like 15-time-16-time-17-time-18-time-19-time-20... I'm try to fix this.
In general, i want the time to be on the screen only when i'm not using the remote control, when i'm increasing or decreasing or changing the balance of my speakers i want the time to be "hide"
I have the volume : 15 , if i want to change the volume from 15 to 20, i'm holding the volume up button on the RC5 and start increasing but while i'm holding the button i'm getting the time between the numbers like 15-time-16-time-17-time-18-time-19-time-20... I'm try to fix this.
In general, i want the time to be on the screen only when i'm not using the remote control, when i'm increasing or decreasing or changing the balance of my speakers i want the time to be "hide"
Last edited:
Code:
Dim Time_call As Byte
If Pwr = 1 Then
Getrc5(address , Command)
If Address = 0 Then
'************************************************
Time_call = 5 ' <<<<<<<<<<<< set to 5 or more
'************************************************
Command = Command And &B01111111
End If
Select Case Command
Case 16 : Call Vol_up
Case 17 : Call Vol_dw
Case 13 : Call Mute
Case 12 : Call Poweronoff
Case 62 : Call Menu
End Select
'**********************
If Time_call > 0 Then
Decr Time_call
Else
Call Datetime
End If
'**********************
End If
the one I designed does have all that: The LCDuino-1 Display I/O Processor (also search the delta1 and delta2 for the attenuator and input selector). all open source and with a huge amount of functionality.
follow the links on amb.org for lcduino and firmware or download (link on left hand side of menu area). a zipfile is created and a link is mailed to you.
Online calculator for logarithmic relay-attenuators
Hi,
I have made relay-based attenuators for many years now, with logarithmnic behavior. That means: each step provides an extra attenuation with a fixed number of dBs, like 1dB.
That is unlike 'R2R' attenuators that provide a linear voltage scale, which is undesired for audio.
During these years I have received many questions on dimensioning the resistors in such attenuators. Sorry that I waited until now to create an online calculator to do so...
The calculator includes rounding of ideal resistor values to E-series values, and computing the undesired effect of attenuator inaccuracies due to such rounding. See:
Logarithmic Attenuator Calculator
Hope this helps our community!
Hi,
I have made relay-based attenuators for many years now, with logarithmnic behavior. That means: each step provides an extra attenuation with a fixed number of dBs, like 1dB.
That is unlike 'R2R' attenuators that provide a linear voltage scale, which is undesired for audio.
During these years I have received many questions on dimensioning the resistors in such attenuators. Sorry that I waited until now to create an online calculator to do so...
The calculator includes rounding of ideal resistor values to E-series values, and computing the undesired effect of attenuator inaccuracies due to such rounding. See:
Logarithmic Attenuator Calculator
Hope this helps our community!
Many thanks, Jos !
Your project was the source of inspiration (the Bible 🙂 ) for our project presented here by Danzup.
Regards,
Tibi
I am looking this thread a long time and very interested in Jos work for a long time.
I just remember REVOX B285 that uses Analog Device AD7528 and AD7118 AD convert to control audio volume with 0,1dB of resolution.
This was an aplication of R-2R attenuator where the audio signal is applied in AD voltage reference pin. Of course the log beharvior is done by software.
regards
I just remember REVOX B285 that uses Analog Device AD7528 and AD7118 AD convert to control audio volume with 0,1dB of resolution.
This was an aplication of R-2R attenuator where the audio signal is applied in AD voltage reference pin. Of course the log beharvior is done by software.
regards
fwiw, I have not found the need for 'log behavior' when the steps *are* already logarithmic (ie, they are spaced by db).
one of my attenuators was relay based at .1db spacing and I used that as a 'trimmer' box (for subwoofer level matching, in one install). .1 is too fine for everyday use, though.
half db is just about right. no matter where I am on the range, half a db is a nice little bump up or down. to find the sweet spot while listening, half db gets you there and each step is noticeable but not too much.
to move fast, I have 2 sizes of steps: large steps and native steps. native steps are what the engine, itself, does (half db in most cases). large steps are what the user can define and when you map alternate arrow keys to those functions you move quickly and without delay. I usually set my bigsteps to be 3.5db; that seems about right to speed thru a fast vol-change sequence but not over-run or under-run too much. once I'm near where I want to go, I then use the main arrows and go by half a db at a time.
and so, with that scheme, I never found the need to have 'non uniform' db spacing. the key is to have enough steps. 64 steps is not enough and you have to play games. but modern controls often will go 96 to 0 (and above) and in half db or better steps. with that granualarity, you can totally forget about so-called log mappings. not needed anymore.
one of my attenuators was relay based at .1db spacing and I used that as a 'trimmer' box (for subwoofer level matching, in one install). .1 is too fine for everyday use, though.
half db is just about right. no matter where I am on the range, half a db is a nice little bump up or down. to find the sweet spot while listening, half db gets you there and each step is noticeable but not too much.
to move fast, I have 2 sizes of steps: large steps and native steps. native steps are what the engine, itself, does (half db in most cases). large steps are what the user can define and when you map alternate arrow keys to those functions you move quickly and without delay. I usually set my bigsteps to be 3.5db; that seems about right to speed thru a fast vol-change sequence but not over-run or under-run too much. once I'm near where I want to go, I then use the main arrows and go by half a db at a time.
and so, with that scheme, I never found the need to have 'non uniform' db spacing. the key is to have enough steps. 64 steps is not enough and you have to play games. but modern controls often will go 96 to 0 (and above) and in half db or better steps. with that granualarity, you can totally forget about so-called log mappings. not needed anymore.
R/2R Nixie/LCD Versions
Hi
Volume Controller Nixie version was finished in april. It was successfully tested.
Two LCD versions are also finished, there is one small difference as an option.
Options:
- volume control R/2R -127dB...0dB
- passive board control, bass&treble, 4 steps in 5dB from 0dB to +20dB
- Nixie PWM (brightness)
- IN-13 VU PWM (brightness)
- Nixie underleds PWM (brightness)
- RC5 learning and control + encoder control
- Fade-out on Mute, fade-in on UnMute
- UnderNixie leds fade-in & fade-out in Mute.
- 6 Inputs selection
- old-school option "-20dB" in one go
- variable volume control speed
First LCD version backlight goes down automatically if no RC5 button pressed and if encoder do not use.
Second LCD version has backlight brightness control via RC5.
Now the case is underway.
More info here
Tube preamp_Nixie version
in russian language
Links to video - how it works
IN-13.mp4 - YouTube
All Options.avi - YouTube
LEDs up_down manual.avi - YouTube
Mute_UnMute.avi - YouTube
Great THANKS to Kim (FarmTech) for help me to implement this idea - the volume R/2R controller with Nixie...
Hi
Volume Controller Nixie version was finished in april. It was successfully tested.
Two LCD versions are also finished, there is one small difference as an option.
Options:
- volume control R/2R -127dB...0dB
- passive board control, bass&treble, 4 steps in 5dB from 0dB to +20dB
- Nixie PWM (brightness)
- IN-13 VU PWM (brightness)
- Nixie underleds PWM (brightness)
- RC5 learning and control + encoder control
- Fade-out on Mute, fade-in on UnMute
- UnderNixie leds fade-in & fade-out in Mute.
- 6 Inputs selection
- old-school option "-20dB" in one go
- variable volume control speed
First LCD version backlight goes down automatically if no RC5 button pressed and if encoder do not use.
Second LCD version has backlight brightness control via RC5.
Now the case is underway.
More info here
Tube preamp_Nixie version
in russian language
Links to video - how it works
IN-13.mp4 - YouTube
All Options.avi - YouTube
LEDs up_down manual.avi - YouTube
Mute_UnMute.avi - YouTube
Great THANKS to Kim (FarmTech) for help me to implement this idea - the volume R/2R controller with Nixie...
Attachments
linuxworks, bargraph style can be change without any prob. I used some other stiles for tests, but yours bargraph style I like more...
🙂
🙂
Nice work!
But I don't know why so many people use atmel microprocessors.What's good on them or better said what's better then by other?
I use only Microchip PIC's and i'am happy with them.I tried also atmel, but it was much more complicated then PIC's, for me at least.
But I don't know why so many people use atmel microprocessors.What's good on them or better said what's better then by other?
I use only Microchip PIC's and i'am happy with them.I tried also atmel, but it was much more complicated then PIC's, for me at least.
Last edited: