|
Re: unboxing the ubitx v6
Rafael,
For radio audio out to pc line in, a stereo cable will do. On the other way around use two stereo plugs but leave the mid section of the plug disconnected. The mid section on the mic input is the PTT, hence a mono plug will put the radio in tx continuously. Using a regular stereo cable can lead to erratic behavior, as the radio will understand some low voltage as PTT pressed. 73 de PU1OWL Rafael Pinto |
|
Re: Firmware up date!
Jon,
I will assume that the path in your first post is correct.? Then the window should contain: D:\uBitx V5\uBITX_CEC_V1.200\uBITXV5\UBITXV5_CEC_V1.200_NX.hex You can check this by clicking on the box with the ellipsis (three periods) and verify that the file is found. For my file locations the window looks like this: You will need to set the com port to match the one assigned by your setup, and set the baud rate to 38400.? I am not at my QTH, so cannot show you the actual settings for my computer. If you do change out the Nano, then you will need to recalibrate the uBITX.? The calibrations are stored in the EEPROM of the Nano.? Here is a video of how to do a stock calibration by Ashhar Farhan: You follow the same general steps with the KD8CEC software, the difference will be how to change the calibrations.? For me, I use the "yellow box" menu that comes up when you press the encoder.? You then need to go to the menu selection for "SETUP" and turn it on.? Press the encoder again, and then the BFO and Calibration settings are now listed as choices.? go through the three steps: 1 - Adjust the BFO to the lower side of the audio range (the 300 H line) to ensure that the lower frequency beats come through. 2 - Calibrate the rig to a known AM station (One of the WWV at 5MHz, 0r 10MHz works for me). 3 - Go back and readjust the BFO to center between the 300 and 3000 Hz bars. Between each setting you will need to press the PTT or the Encoder to save the stting, then power down the rig for 10+ seconds and restart to ensure the setting took.? Depending on the Nextion screen selected, the settings can be read on one of the screens.? That is a good way to verify that your change made it to the Nano. There is also a Memory Manager program that works with the KD8CEC firmware to save and restore the settings value. Hope this helps. 73 Evan AC9TU |
|
Re: WSJT-X 2.2.2
Does Serial.available work?
Thanks for letting me know. I just ordered some Nano Every's (should arrive Thursday). I went ahead and download the board setup for the Nano Every and tried to compile my sketch.? It looks like I need to redo my timer setup (I was writing directly to the timer setup bytes) and the board setup is missing the macro digitalPinToPCMskbit.? It's starting to sound like the software designers only worried about getting the high-level features working. 73, Mark, N8ME |
|
Re: WSJT-X 2.2.2
I didn't know that about serialEvent. I hadn't looked past the name.
So that really begs the question why my code is working. The only thing I see is that I am checking for Serial.read() to return -1 and ignoring that. The -1 return means that the read timed out, which doesn't make sense since you (and my old) code was only calling Serial.read() when Serial.available() indicated data was available. As a test, you could check your calls to Serial.read() for a -1 return. 73, Mark, N8ME |
|
Re: Different Nano's
I downloaded the Nano Every Board setup into the Arduino IDE and tried to compile my firmware sketch.
It failed on digitalPinToPCMskbit() which converts a digital pin ID to the appropriate bit in the output register. But more severely, it failed on the low level writes that I was using to set up timers: TCNT2 TCCR2A WGM21 OCR2A TIMSK2 CS22 | CS21 | CS20 Doing some online research, it looks like the timer setup is different. 73, Mark, N8ME |
|
Re: Frequency calibration on a lab
#bfo
#calibration
#frequency
Very good HAM setting, used only one instrument, but is not the best for laboratory setting, you not have any referent to the real frequency received; the error is very low, but is possible make something of better in a laboratory.
73 de
--?
IW4AJR Loris |
|
Re: WSJT-X 2.2.2
Dean,
My code is a little different. In setup(), it calls Serial.begin() and Serial.flush() like your code. My CAT handling is done in a Serial.event() function. This is called whenever there is a character available to read (or so says the documentation).? void?serialEvent(void)?{
??long?frequency;
??byte?temp1,?temp2;
??int?c?=?Serial.read();
??if?(c?>?-1)?{
????cmd_buffer[cmd_byte_ct++]?=?(byte)?c;
??}
??if?(cmd_byte_ct?==?5)?{
????cmd_byte_ct?=?0;
?
Then process the command. cmd_buffer is a 5 element byte array. cmd_byte_ct is a global variable initially set to 0. My original code was like yours in that it assumed that if Serial.available() returned 5 or more that Serial.read would always be able to read 5 bytes (I actually used Serial.readbytes(buffer, 5), but the way my program behaved, I'm not sure that was a valid assumption.? With a few hours testing WSJT-X versions 2.1.2 and 2.2.2 and with FLDigi (using hamlib) it seems to work, after a firmware upload or after a power cycle.? It was a little less reliable until I added the Serial.flush() in setup(). Thank you for that idea. 73, Mark, N8ME 73, Mark, N8ME |
Rafael Pinto [PU1OWL]
Mark Erbaugh
Loris Bollina