kd4z / md380tools-vm Goto Github PK

Hi, in earlier version, bash history was saved, that is useful so people can search or arrow up the old commands quickly. Any way to bring that back?

Perhaps I'm the first to observe this... but the files needed by the script look to be missing.

When it gets to this line:
https://archive.org/download/TYTMD380FW2/TYT-Vocoder-MD380-D13.20.bin => dl/D013.020.bin Makefile_orig:60: recipe for target 'dl/D013.020.bin' failed make[5]: *** [dl/D013.020.bin] Error 22
...it all falls apart and of course no .bin files are created.

Did I miss a step or did the files on archive.org get removed?

Thanks! 73 -Gary, N4TXI
...

DMR works fine, but I lost analog Rx. TX works fine. I checked the codeplug and nothing was changed. Before I used the nosleep firmware DMR didn't work, but analog did. Now it's the opposite.

Thanks for your help

bash_aliases generates error when logging in

-bash: /home/pi-star/.bash_aliases: line 36: unexpected EOF while looking for matching `"'
-bash: /home/pi-star/.bash_aliases: line 46: syntax error: unexpected end of file

add " and it will work again

I am using the latest version of the virtual machine and virtual box. I am running it on mac sierra, 10.12.16. I have no trouble flashing the firmware. On trying to flash an update to the userdb, I am getting "operation timed out [Errno 110]" and the radio is left in "PC program USB mode". The error first happened on erasing. I got through the erasing cycle (I closed the VM, turned off the radio, and restarted the process) and it failed in the same way on writing the new user database. The third try, it failed on erasing.

I am able to read and write rdt files to the radio using tytera's CPS software. I was able to run the tytera flash tool, too, before flashing MD380tools. I am running V1.34 of the CPS. The tytera firmware on the radio before flashing MD380tools was 13.034.

One result is the userdb seems to be corrupted now, or at least partially erased. I am getting the callsign not found window, the one with the "update with glvusers, then flashdb" message when there is an active call. I do have "userdb" selected.

Any ideas where to start looking?

I have a scandinavian keyboard layout. When booting your VM, I cannot type equal sign, slash etc. Since I am not root (and dont have the root password) I cannot edit /etc/default/keyboard.

Can you inform about the root password in your VM Linux image so we can edit keyboard layout pse.
Also, what distro of of linux is it?

73

Hi Warren,

The 'user.bin' file is getting munged-up anytime a static.users file is included.

I first noticed the issue when I created one entry in the static.users file using this format (101,call1,name1,city1,state1,nickname1,country1) . The actual entry is:
3139370,W8FAA,John,Atwater,OH,John,USA
When the database is created, I do a lookup on the callsign with ./lookup W8FAA. Lookup returns two results. The first is my record as shown above. The second is (at the time of this post) a record for call CX1RK. This second record is the record for CX1RK from the database, but it has my record concatenated to the end of it.

SO, I removed my record from static.users and re-ran 'glvusers'. The user.bin file is still corrupt in the same place, but with different data. Something is wrong in the process that merges the data together.

Edit: Looks like CX1RK is the last entry in the original user.bin file. The issue is the addstatic script may not be adding a LF before inserting the static.users file.

73,
John W8FAA
[email protected]

The file says: Sorry, this file is invalid so it cannot be displayed.

Great work on the VM mate!
Regards,
Paulo CS7AGH

Hi!
I tried to install it on Debian (VM) and this step:
**cp md380tools-vm/root/.bash_aliases ~**
Didn't work for me.
The correct filename on Debian was .bashrc instead of .bash_aliases
73!

I get this when running glv. I can't identify how to resolve it. This is a Virtual Box installation.

Do not know if this is an issue u can answer but when I do the flashdb it clears the memory and says it is writing but after complete it is not there. It did not flash anything that I can find anywhere.

Hi there!

It looks after the last change on the md380tools, if you want on the submenu: "Date format" use the new option "TalkerAlias" it doesn't work.

Tried with the base md380tools by travisgoodspeed and it works.

Paulo - CT2JAY

Hello, Running MD380Tools VM version 4.53 with Oracle VM Virtualbox 6.1
Using a Retevis RT8 radio. I had no issue programming the firmware in (DFU) mode, with the 'flash' command. But failed to attach the USB device @00000004 : ffffffff Patched MD380 [200] or @00000008 - in either a USB2 port or USB3 port. Running the Oracle VM on Windows 10 which sees the device in the device manager as an STM Device in DFU Mode. The DFU mode does not change either actually in DFU mode or On (without using the Power / Up keys at switch on). In the Oracle Settings, USB, I have used the USB Device filters to pass over the commands from Win10 to the VM, with AnyRoad, @00000004 and @00000008 filters. What I am finding is that the 'Failed to attach the USB device' in every combination I try. My question relates to VM not seeing the USB device , is there a setting in Oracle VM which is preventing the Toolkit VM from seeing the radio ? I have resorted to using the TyteraFlashTool_v1_08c_BETA program in flashing the database. I would prefer to use this Toolkit VM. In the past this toolkit had no issue in flashing the database. Do I need to start again and download a fresh copy of the toolkit with Windows 10 USB drivers installed ? It may be Windows 10 is the problem and the USB drivers are not working anymore as they should ? Thanks, James

I've looked at the code myself, but I don't really understand the TypeError. Using Python 3.

`hans@G510:~$ glvusers
Archive: /home/hans/md380tools-vm/nicknames.zip
inflating: user.nicknames
Downloading data from RadioId.net...Normalizing...done
Downloading data from HamDigital.org...Normalizing...done
Downloading alternate data....done
Traceback (most recent call last):
File "/home/hans/md380tools-vm/merge_users.py", line 2256, in
enable_options = [upperFirst(x["name"]) for x in sorted(optionList)]
TypeError: '<' not supported between instances of 'dict' and 'dict'
Merging data...
Contact Merge completed.
RadioId count : 152226 records (8362895 bytes)
HamDigital count : 152038 records (5994772 bytes)
Alternate count : 0 records (0 bytes)
Nickname count : 4482 records
Records skipped : 4 records See /home/hans/merge.errors
** The Downloads for Contact information may have failed - run glvusers again
** before running flashdb, as the user.bin is not normal size.

Merged total : 0 records (0 bytes)
User.bin filesize : 0 bytes (not including header record)
Processing complete.
Run menu to return to the main menu screen `

With the latest experimental firmware I lose the display on the MD-380. It stays on for a moment during turn-on then goes off. Not able to see to access settings to deal with display. re-loading MFG firmware corrects issue but when re-loading experimental firmware same issue. At the moment you can either chose "flash" or "flashgps", any chance on a "flash" for the old vocoder?

The "flash" worked under 3.08 but not working now under 3.09.

Thank you!

"flash" command : Errno 13 Access denied ( insufficient permission )

73

This workaround does not seem to be working on my V5.01 radio. The RX meter still drops off after about 5 seconds. it seems to stay connected longer than before, but the radio still goes to sleep. Analog reception is deaf except when monitor is activated.

Here it goes two examples.

It should be Portugal. This are the lines of user.bin

Hope it can help.

Do you want to translate the menu and scripts messages to Portuguese?
Regards,

Paulo
CS7AGH