TRX-manager uses the ChikatAX DLL Active X for many Internet related functions. Unfortunately, the author of this DLL does not ensure a backward compatibility between the various versions of this DLL. Since V4.7.8 TRX-manager checks for the version of the registered DLL and prompts a warning in case of a mismatch which avoids a crash. To fix this problem you can copy the ChilkatAx-9.5.0-win32.dll from the TRX-manager's program folder to the System32 (32 bit systems) or SysWOW64 (64 bit systems). You need the administrator rights to perform this operation. An other solution is to reinstall the last TRX-manager patch which forces the installation of the required version.
In principle, RTS/DTR/CTS/CTS pins (required for CW/PTT keying or by some serial protocols) should be supported by USB Drivers but not always properly: in some (rare) cases, the cable is not even wired for these lines !
Trx Manager Serial
Under WINDOWS VISTA/7/8 the PROLIFIC adapters are prone to malfunctions with TRX-manager and all applications using MSCOMM32.OCX. Some applications may run (with latencies or only in one direction) while some others not at all... This situation may come from a fake Prolific driver not supported by the manufacturer (who writes the driver). In such case, under Windows 10, these "old" adapters do not work at all.
1) The best way to synchronize TRX-Manager and any device (an amplifier...) or any software (a logging program, PowerSDR-IF...) which requires CAT data is the TRX-Manager's SYNCHRO mode: TRX-Manager will behave like a Kenwood or ICOM transceiver on its synchro ports (TRX-Manager provides TWO synchro ports). Synchro mode requires either a null-modem cable and two free serial ports or a "pair" of virtual ports created by a serial port emulator (like Eterlogic's VSPE). Please see for more information in the HELP under SYNCHRONIZATION.3) Y Cable : generally this method does not work very well... not recommended4) ICOM CI-V System (ICOM Rigs). This protocol works with TRX-Manager to synchronize some ICOM compatible device.5) LP Bridge by Larry N8LP LPBridge can synchronize much more than one device or software but may slow down the CAT control and has some (slight) limitations with TRX-Manager. LPBridge requires you set up TRX-Manager with special settings (see Help)6) DDE or OLE Links between programs. DDE is an outdated method (Windows 3.1), slow and uninstable and not used in TRX-Manager. OLE is much more reliable. TRX-Manager provides an OLE link with LOGic, Swisslog and some other programs...
1) USB interface produce RF Noise... So In practice, in the HAM shack, it is always preferable to connect your radio using its RS232 port and a real RS232 port on your computer: the one on the motherboard (*) or an additional COM Port using a PCI based serial communication card.
(*) Despite the fact that most computers are delivered without any com port today, most of the motherboards provide a serial-port header. You have to connect a bracket with one or two com ports that occupies a slot space on the back of the case.
- You are not required to switch to the new folders structure!- TRX-Manager will automatically copy temporary and utility files located in the TRX-manager's main folder to the new \Misc subfolders (located in ProgramData\TRX-manager and in AppData\Local\TRX-Manager),- BUT TRX-Manager does NOT move your personal files (i.e files created using the Open/Save buttons, your LOG or SWL database, your MEM files and generally all files located in the TRX-Manager's subfolders...). Consequently, almost all files located in the TRX-Manager's subfolders will NOT be moved and will stay in the Program files\TRX-manager's folder and TRX-manager continues to write Program Files!. It is up to you (but strongly recommended) to transfer these files to the new location (AppData\Local\TRX-manager's subfolders) and to configure TRX-Manager accordingly.- Once this option is effective, you can NOT go back!
X-VGA monitor (in preference to a S-VGA) 1 serial port for radio interface (Com 1-16) or an USB/Serial adapter Level converter (except FT-847/920/1000MP/DX9000 TS-570/870/2000/480) 32 bits connection to Internet (optional) TNC or multimode controller + serial port (optional) Rotator interface + serial port (optional) a free parallel port for the band decoder (optional) 150 MB of free disk space are required to run the program. 124 MB RAM a 1024*768 / 16 bits color display RS 232 interface and cable Supported rotator interfaceRelated:
You cannot download any crack or serial number for TRX-Manager on this page. Every software that you are able to download on our site is legal. There is no crack, serial number, hack or activation key for TRX-Manager present here. Our collection also doesn't contain any keygens, because keygen programs are being used in illegal ways which we do not support. All software that you can find here is freely downloadable and legal.
For Sales Transaction, I'm trying to run / build an integration that uses the Serial Numbers section. The integration is mapped to pull the serial numbers from the source file, but when I try to run the integration, I get this message: DOC 1 WARNING: Serial Number '[insert serial number here] 'does not exist. When I check GP, my batch is uploaded, as well as the trx header info, but there is no line item info at all!
Yes, the source files are separated into 3: the header, line and serial. I'm not sure if I need to be grouping the line file or serial file a certain way, but the line items aren't pulling up in the Sales Trx window. Just blank in the grid where line items usually are.
Hope this helps in understanding what is going on. I have not looked at it directly, but I would look to see if I could load the serial numbers in Inventory via the Inventory Trx - IM as the first pass. Then the second pass would be to do the Sales Transactions.
Thanks Warren, when I went through the Sales Trx window manually in GP, and tried to enter a serial number, it asks me 'do you wish to add this serial number'. I can click Add and it'll allow me to insert that new serial number. So I am wondering if there is some way to get past this message in IM, as it seems like that is the message that prevents the integration from importing the serial numbers.
Yea, sometimes there is a dialog box that the IM designers did not anticipate that throws things off. I have run into that before on other windows. I looked at the SOP IM and there is not an option to add the serial number.
So I followed your suggestion and have built an Item Trx integration to pull in the serial numbers. However, there seems to be an issue pulling in large quantity values. Items with a qty of 1 integrated perfectly, but other line items with quantities of 300 and 1800 did not import correctly --they imported with a qty of 0 and no serial values (since quantities were imported as zero). Do you know anything about importing line items in the IV Trx integration for large quantity values? Any ideas on this one? Thanks.
1) Install the dual serial port driver from Yaesu website. See manual here: =9515&FileCatID=42&FileName=USB%5FDriver%5FInstallation%5FManual%5FENG%5F1610%2DB0.pdf&FileContentType=application%2Fpdf
7) Set the rate to 38400 in TRX-manager (setup menu) and select FT-891. Also select correct COM port (on my PC it was COM5. It may be different on yours).Remember: unless you set CAT RTS to DISABLE (see above) you will not get data thru and you will mess around in the TRX-manager menus while the problem was a setting in the FT-891 menu.
Sometimes, one serial port just isn't enough! When trying to communicate with multiple serial enabled devices, while also sending info back to the main serial window, a few extra RX/TX ports can be a welcomed thing. This example makes use of one of Arduino Mega's 3 auxiliary serial ports, routing any incoming data read on that connection straight to the main TX line, and, in turn, to the main serial window for you to view.
After checking the data sheet of whatever serial enabled device you choose to use for this example, make sure that it is both properly wired and powered. Connect the RX pin and TX pins of your device to the TX1 and RX1 pins of your Mega, as shown in the schematic below.
Most devices supported by OpenWrt have or can be modified to have a serial port. These serial ports typically provide a console to the bootloader and, when the firmware has booted, a console to the running system. A console to the running system will let you correct a misconfigured network, for example. Console access to the bootloader will often allow one to fetch and flash new firmware and may be the only way to do so on some routers if the firmware is not functional.
Most routers come with an UART integrated into the System-on-chip and its pins are routed on the Printed Circuit Board (PCB) to allow debugging, firmware replacement or serial device connection (like modems).
Once OpenWrt starts running, it is generally possible to enter failsafe mode with a terminal program attached to the serial port. Either in failsafe mode, or with OpenWrt running in normal mode, it is generally possible to enter commands the same way one would if using ssh over a network. One advantage is that if you've somehow configured your router so that the network or ssh isn't working, you can still access your router to manage it.
While a functional serial port can't protect you from a damaged bootloader or other low-level problems, it can be used to resolve many user-configuration errors, including, with luck, when the cat pulled the plug on your router as you were flashing it:-/
For low-level developers, or those that choose to flash their own bootloader, accessing the JTAG port may be the next step, as the serial port requires functional software (either the bootloader or a running system) to be useful. JTAG access falls into the realm of expert use. It is mentioned here mainly as a reminder that flashing a bootloader, no matter how many have been successful before you, is a risky endeavor that a serial port may not allow recovery from errors. 2ff7e9595c
Comments