Works fine! Thanks Pat for Manual an Allard for the Sketch.

73 de Matt, DH2LAB

On Fri, May 26, 2017 16:32, KC8WBK via Groups.Io wrote:

Scan works great, I like the scan configuration menu.

Good to hear this Paul, glad you like it!

73 Allard PE1NWL

Scan works great, I like the scan configuration menu.

A lot of Linux distros have outdated Arduino software (at least this is true for Ubuntu and its variants which seem to be stuck at version 1.0.5!), so I recommend downloading directly from the Arduino website.
--
Darren, W9ZIM

开云体育

开云体育

Sorry for the delay Noel,

I was working offline with a client and now is that I has time and $ to get online... hi hi hi

Please check the examples bundled with the lib, once you loaded the lib on the Arduino IDE you can go to examples and inside Yatuli you willl find two examples "shuttletune" and "optionselect"

The first is a use case for testing the tuning and it's wired in a way that you can test it with your raduino hardware, the second is to show how to make an option select mechanisms just like if the volume control was a rotary encoder.

For you question, in the setup segment of the shuttletune example you can find this initialization.

========%<=============================
void setup() {
??? // initialize serial communications at 19200 bps:
??? Serial.begin(19200);
??? Serial.println("Example init...");

??? // Init the lib
??? St.init(APin, 6900000, 7500000, 100, 10000);

??? // 6.9 to 7.5 Mhz
??? // 100 Hz steps
??? // 10 kHz steps on edges

??? // Set 7.100 Mhz as the start freq
??? St.set(7100000);
}
========%<=============================

St.init(APin, 6900000, 7500000, 100, 10000);

That's translated to this:

St.init(analoPin, lowF, highF, normalStep, edgeStep);

In this case you can read it uses A7, from 6.9 to 7.5 MHz, 100hz normal step and 10Khz steps on edges of the range.

If you dont's set any starting point it will be calculated from the lower end and the actual wiper position.

The start position of the pot is fixed with a separated function, you can use:

St.set(7100000);

To set the initial value of the pot to 7.1 MHz in this case, of course, it can swing a little down or up due to jitter in the analog read, in this case in +/- the normal step, so you can set it to 7.1MHz and get 7.9999 MHz or 7.1001 MHz but most of the time it will get right on spot.

I coded the set() function separated from the init procedure just because it makes sense on my related project, and if you plan to use the lib just for option selection you can live without the set() function.

The init() function is not exclusively of the setup() part in the code. Mind this:

You has a setup like the raduino, but you need to change a setup option (USB shift, IF, etc) you entered the SETUP mode (the way to enter is not important at this time) and you are presented with a option menu: (yatuli has shifted to operate on dir() rather than value, and you get option select features)

"?????? IF????? "

Once you rotate the Dial you can get other options like:

" ? USB shift ? "
" Si5351 ppm "
.....

Now you press one "OK" button, and you entered the IF option for example; by enterig into this sub-menu you are runing a code like this under the hood:

St.init(APin, 11000000, 13000000, 10, 1000); // move the IF from 11 to 13 MHz in 10 Hz / 1Khz steps
St.set(IF);

And shiftted to movement functionality of the yatuli lib.

By doing that now you can move via the "dial" the value of the IF and it will start on the actual IF, all with just one instance of the yatuli lib, one you can reach the point you want just press again the "OK" button and it will reset the lib to operate on the tune freq value under the hood.

And you will be back to the menu select.

You can make this with? as many variables you has, for instance in the raduino I can tell: USB shift, IF, VFO stating freq, Si5351 PPM, etc...

Remember this is only the initialization procedure, you will need to include a check() on your loop() and test if the value has moved to act.

See the examples, they are commented in excess to help other to understand the general idea.

I'm coding a new raduino firmware based on this lib and my Si5351mcu lib for a friend, so far so good, I used a homebrew/breadborad version of the raduino hardware with a ATMeg168 instead a bigger ATMega328 of the read hardware; I has about 70% of the 16Kb filled by now with almost all the funationality of the amunters code. (I'm missing the CW code, but has a "HD" smeter/TX_power bar ;-) )

The real drawback is I don't has much free time do get into it and it get coded in weekend's? / midnigths style...

73.

hi i have tried to follow the instructions - all is well until "configure the port" it only offers com 1 and com 2 not usb

and the upload fails

terry gm4dso

Linux is largely the same.? You can find some information here:

Only catch at the moment is that version 1.8.2 has a bug in the installation script, so you'll want to install the hourly build (it's on the download page).

Once the software is installed and you've added your user to the appropriate group then follow the OP's instructions for the rest.
--
Darren, W9ZIM

If you don't want to use the function button for your mobile radio, then
why not install a small push button internally (inside the enclosure).
This will still enable you to set everything to your liking, but it will
prevent the user from accidentally changing some of the settings.

Alternatively, you can change the "factory settings" that are hardcoded in
the function factory_settings() starting at line 1302.

In the setup() routine, at line 1437 is some code that reloads the factory
settings under certain conditions:

if ((digitalRead(CAL_BUTTON) == LOW) || (digitalRead(FBUTTON) == LOW) ||
(old_version != raduino_version)) {
factory_settings();
}

You could change the "if" condition so that the (revised) factory settings
will be reloaded each time when you power up the rig:

if ((digitalRead(CAL_BUTTON) == LOW) || (digitalRead(FBUTTON) == HIGH)
|| (old_version != raduino_version)) {
factory_settings();
}

73 Allard PE1NWL




On Fri, May 26, 2017 03:40, KC8WBK via Groups.Io wrote:

I have a mobile radio built that I do not intend to add a function

button to. It is a radio that I want to keep simple and I don't want the
user to be able to switch to USB or CW by mistake.??

I would like to be able to set the functions in the sketch by

commenting, uncommenting or changing values so that the radio starts up
with the same values/function settings every time.

The settings that I would like to modify are VFO drive setting, LSB

frequency offset and Scan range.

Can I replace line 165 with

int LSBdrive = 2;?? ???

I found USB_OFFSET but did not find a LSB_OFFSET.?? Can I calibrate LSB

with a line of code somewhere??? Apparently it is offset using

calibrate()?

Can I replace line 195 with

int TUNING_RANGE = 300; // tuning range (in kHz) of the tuning pot?? ???

i have got the instructions for windows from pat griffin but i prefer to use linux. i have got win 7 but i do not like connecting windows to the internet cos of the wiced nasties.

has anybody got similar instructions for linux

terry gm4dso

Mike,

I put my first board through the analyser and found the IF filter around 1.8-2K as I remember.
If you adjust the BFO in one direction the audio will sound sharper but less bassy and vice-versa.
Check the BFO and replace the fixed cap with a 22pf and add a 40pf trimmer next to it.
Or you could put just a 70pf trimmer. You could tell at what BFO freq. you are getting the best quality.

Cheers
Raj, vu2zap

after a bit of research i discovered that the usb mini comes in two flavours a and b, the bitx40 uses the b flavour.
i eventually found one and it worked !!

maybe i should have know !!!

terry

On Thu, May 25, 2017 at 09:03 pm, Soundararajan Ra. wrote:

There is a confusion in instruction? page.

Line number 15 function button red wire

line number 66 function button orange wire.

Please clarify how t.o connect function button it is A2 or A3 Red or orange.

Soundar,

these are two different things:

• CAL wire, connected to pin A2 (red wire)
• Function Button, connected to pin A3 (orange wire)

The red CAL wire was used for calibration only (for basic BITX40 board with no extra mods and without function button).
It is kept in the code for backward compatibility so that the software always works even without the extra mods.

But if you wire up the Function Button then you don't need the red CAL wire anymore as the calibration can also be performed from the FB menu.

Hope it's more clear now.

73 Allard PE1NWL

from source code:
#define FBUTTON (A3)

Hi Mike,
The muffled audio is more likely due to the crystal filter passband rather than the mic amp. I've noticed this on another station myself.
Moving the 12 MHz oscillator (BFO) up in frequency could be a solution to allow more high frequency audio modulation through the filter. The filter bandpass is centred on the lower side of the BFO.
Scope for experimentation!

Cheers,
Gerard - VK2IO