Topics

Help needed with KD8CEC memory manager

Bill
 

Hi to all,
 I have just uploaded ver 1.061 with success, I think! I am trying to use memory manager to set up for reverse beacon function. ( i at least wanted my call sign to display on power up). I have absolutely no coding experience just so you know. I have memory manager downloaded, and have entered some very simple info. When I hit encode, I get an error message about filling in boxes on left. I am lost. Another question is what baud rate is correct?? If all I wanted to do right now is display my call sign, I would still have to use this program, correct? I can follow instructions but am on a steep learning curve! Thank You for your help! Bill A.

Bill
 

I have gone back to the Hamskey website and tried to follow the directions for the memory manager. My problem right now is that nothing happens when I click "read from ubitx", although I did get it to work at one time, and was able to create a back up file, which I can load into the manager. I have made some changes and hit write to..., after hitting encode. A green bar will slowly run across the screen untill finished. Each time it will show o successful. So it seems I cannot read or write from this program right now. Any thoughts?

a.vision
 

That's exactly what I am getting  I can't understand why any help greatly appreciated thanks .



Sent from my Samsung Galaxy smartphone.

-------- Original message --------
From: Bill <allerthomes@...>
Date: 09/08/2018 04:24 (GMT+00:00)
To: BITX20@groups.io
Subject: Re: [BITX20] Help needed with KD8CEC memory manager

I have gone back to the Hamskey website and tried to follow the directions for the memory manager. My problem right now is that nothing happens when I click "read from ubitx", although I did get it to work at one time, and was able to create a back up file, which I can load into the manager. I have made some changes and hit write to..., after hitting encode. A green bar will slowly run across the screen untill finished. Each time it will show o successful. So it seems I cannot read or write from this program right now. Any thoughts?

Bill
 

Could this problem be from the hex file that was uploaded? Does anyone have an easy to find source for the proper updates in hex file format? My display did change from a single line to 2 lines after the 1.061 installation, so I thought it was correct.

Bill
 

When I hit read read from ubitx, I get an error message with the time followed by; error receive length = 1/1027. What does this mean???

Ralph Mowery
 

When I got that error it was because I used the wrong baud rate.  Try another .


On Thu, Aug 9, 2018 at 9:26 PM, Bill <allerthomes@...> wrote:
When I hit read read from ubitx, I get an error message with the time followed by; error receive length = 1/1027. What does this mean???

Bill
 

Yes, I have tried the different baud rates to no avail.

Rich AE4OK
 

Hello - I am also getting error receive length = 1/1027. I have tried almost every possible combination of firmware and MM. I was successful with 1.097beta over the summer, then tried the I2C meter. At one point I lost the ability to communicate via Memory Manager to EEPROM. I use linux ans I am able to upload .hex and use the IDE to read all EEPROM values. For Memory Manager I need to use wine. I've used it successfully in the past this way. I was able to calibrate and save settings etc.

Can someone please help guide me to the best solution.
Thanks,
Rich

Mike Short
 

I have had the same error.  

Mike

On Sat, Nov 24, 2018 at 3:59 PM richard_a_morrisey via Groups.Io <richard_a_morrisey=yahoo.com@groups.io> wrote:
Hello - I am also getting error receive length = 1/1027. I have tried almost every possible combination of firmware and MM. I was successful with 1.097beta over the summer, then tried the I2C meter. At one point I lost the ability to communicate via Memory Manager to EEPROM. I use linux ans I am able to upload .hex and use the IDE to read all EEPROM values. For Memory Manager I need to use wine. I've used it successfully in the past this way. I was able to calibrate and save settings etc.

Can someone please help guide me to the best solution.
Thanks,
Rich

Woody
 

Rich,  FWIW - That is the error I received (using windows) after my Nano got fried.  Would connect, but data transfers failed.
Good Luck!
Woody   KZ4AK

On 11/24/2018 21:59, richard_a_morrisey via Groups.Io wrote:
Hello - I am also getting error receive length = 1/1027. I have tried almost every possible combination of firmware and MM. I was successful with 1.097beta over the summer, then tried the I2C meter. At one point I lost the ability to communicate via Memory Manager to EEPROM. I use linux ans I am able to upload .hex and use the IDE to read all EEPROM values. For Memory Manager I need to use wine. I've used it successfully in the past this way. I was able to calibrate and save settings etc.

Can someone please help guide me to the best solution.
Thanks,
Rich
_._

AndyH
 

I just got a string of 'receive length...' errors when trying to read the raduino in my uBITX.  I had the raduino in the radio.  Once I removed the raduiono from the radio so that the only connection was the USB cable, comms were fast and I could read from and write to the nano.

Andy, KG5RKP


On Sat, Nov 24, 2018 at 03:59 PM, <richard_a_morrisey@...> wrote:
Hello - I am also getting error receive length = 1/1027. I have tried almost every possible combination of firmware and MM. I was successful with 1.097beta over the summer, then tried the I2C meter. At one point I lost the ability to communicate via Memory Manager to EEPROM. I use linux ans I am able to upload .hex and use the IDE to read all EEPROM values. For Memory Manager I need to use wine. I've used it successfully in the past this way. I was able to calibrate and save settings etc.

Can someone please help guide me to the best solution.
Thanks,
Rich

paul_hvidston
 

I've determined that with my just received V5 board, I cannot use the CEC memory manager when the nano is plugged in to the raduino. Seems to work fine with just the bare nano connected to a USB cable to the computer. The only difference that I can see is that the 3.3 volts generated by the CH341 chip gets plumbed to the Si5351 and may be causing the USB interface to have problems. The CH341 does not specify a current output limit, and does not even suggest that any external devices should be powered by it. Measuring the 3V3 voltage with, and without the raduino attached yields about 3.6 volts, so not sure what that says. For now, I simply remove the nano so I can connect the USB port.

Paul/N6MGN

Russ KR0EHM
 

I’ve noticed this same problem.
I recently wired up the back port of my case to the usb on the nano and thought that was it, but it only works when the rest of the radio is powered off. Once the nano is running only on USB power the connection works like it should.

paul_hvidston
 

Yes, exactly right, knitnerd. Thinking about Andy's post too, I was out doing further testing. I determined that the USB cable has to be attached, and powering up the Nano to be successful. If the Nano is already powered up from the uBITX board/power supply, the communications fail. I've been looking through the CEC source code to see if I can track it down. I recall serial not working right on UNO's if the USB cable was not already attached at the point of "Serial.begin()," but need to look at some of my older project code to see what the issue was and how I worked around it. I'm just glad it appears to be a firmware issue that we can easily remedy.

I had been avoiding powering the entire Raduino from the USB port on my notebook since it may overcurrent and shut down the port. I would usually just pop off the Nano and reprogram it so I never saw the problem until I wanted to correct the CW behavior. Being mainly a CW op, the default behavior of displaying the RX instead of TX frequency is a show-stopper.

Thanks to Andy and knitnerd for helping narrow down the failure mode!

72 de Paul/N6MGN

Evan Hand
 

I have a v5 with a 3.2 " Nextion and CEC version 1.2.  I do not have the Memory Manager version as I am on the road for business right now.  With the above I have been able to directly connect to the Nano with the MicroUSB cable direct to the Nano port.  When I read about running cables to the rear panel, I wander if there is another factor in the mix, like a case with rear connectors and/or aux boards for ease of wiring.  To really know where the issue is,  we need to list all of the non-HFSignals mods in addition to the CEC mod so that the problem can be clearly defined.  I have read of multiple threads where the issue was traced to a case mod that gets between the uBitx board and the rest of the world.

With the above understanding, PLEASE be sure to list ALL non-stock mods so that we can compare apples to apples.  It may be that there is a know issue with something as simple as a wiring error on a case kit that has come up in the recent topics.  This type of problem can only be solved if all of the information about the rig is known. 

Now to better articulate my setup, It is all stock EXCEPT for the CEC/Nextion display AND a power drop resistor on the 12 volt line feeding the 5volt regulator on the Raduino board.  There is a know power issue with running the stock Raduino board with more than a 2.8" Nextion display.  The total power required is more than the regulator can handle with more than 12 volts suppiled to the the main board (the PA can be higher with out this issue).  I also added two 1n4xxx diodes between the 13.8 volts supplied by my power supply and the RED wire on the uBITX board.  This was done to keep the voltage supplied to the main board close to 12 volts (i have since measured 11.9 volts under power).

I have gone to this level of detail to explain my setup to give you an example of the level of detail that is needed for us to help.  We have not all used the same setup when building our rigs.

Apologize on being long winded on the need for details, however it is for your best interest.  Wrong information can lead to wrong diagnosis and ultimate board failures.

73
Evan
AC9TU

Mike WA0YCN
 

Evan,

I have a Nextion waiting to be installed, but I’m working on finishing with the stock 2 line display and software from HF Signals first.  Watching all these discussions, I’m fearful I will make a mistake programming and not be operable for a while.  I purchased a spare Nano, wondering if I could pull the one that came with the ubitx, put the new one in, then be able to put the original Nano back in if there’s a problem. Am I oversimplifying things?  :)

Thanks,

Mike

paul wegwert
 

Mike,

Did just that today. I obtained 3 Nanos as spares, programed one to CEC's ver. 1.20 . Removed the original Nano and replaced it with no problems. I put the 'stock' Nano in a protective container and marked it as ubitx 5.1 just in case.

Have fun,

Paul 
KD9JYV

paul_hvidston
 

For exhibiting the USB serial issue, can't get much simpler than my setup. I'm running a brand-new V5, completely stock, no mods, CEC 1.2 F/W, USB cable direct from Nano to a Windows notebook. The voltage concerns with the uBITX V5 board appear to be primarily the LM386 version (some cannot tolerate >12V), and the dissipation of the Raduino 5-volt regulator. I run 13.8 Volts, and since the LM386 is socketed, if it smokes I'll replace it with a a known higher voltage version (LM386N-4).

Since I have a bunch of Nano's on hand, I plan on loading up the W0EB/W2CTX ubitx_V2_00R F/W in one and playing with it.

72 de Paul/N6MGN

Evan Hand
 

Mike,

The short answer is yes you can.  The long answer is two fold; 
1 - Be sure to get a Nano with the header pins supplied separately and solder them in on what is usually the back side of the Nano.  Check with orientation of the one supplied.
2 - When you program the Nano with the CEC software, the calibration parameters will not be saved.  These are stored in the EEprom, not the flash memory.  You will need to go through the CEC calibration procedure, which is different that the stock procedure. The CEC procedure goes back to the original way of using receive and zero beating a know signal.  The BFO is the same, just remember that the value will be different due to the change in crystal filter. 

Because of point 2, most get frustrated that the Nano reprogramming did not work.  The significant thing is that the BFO is most likely off, and the receiver has very little sensitivity (it is aligned outside of the 11.0555 pass band - check for the exact frequency, I do not have it handy at the moment and the grey matter is getting old).

You can then swap between the two as long as you also change out the display.

73
Evan
AC9TU    

Niels Jalling
 

If you first load the nano with the original ubitx v5 software (from github) and then load the CEC software the frequencies are not way off as they are after just loading the CEC.
PS I compile allways from source.
73
Niels
OZ9NY