GoodQbuy USB Programming Cable Cord for Yaesu Vertex/Standard Horizon Radio HX370E VX-6R VX-7R VX-7E HX750 VX-120 VXA-700 1-pin 3.8 out of 5 stars 21 $21.99. 1 FIF-12 USB PROGRAMMING INTERFACE The FIF-12 is the Interface Unit which allows cloning of channel data to Vertex Standard transceivers, and/or re-writing of the firmware on some Vertex Standard transceivers, using the USB port of a personal computer.: Check with your Vertex Standard Dealer for applicable models.
- Vertex Standard Port Devices Driver Windows 7
- Vertex Standard Parts
- Vertex Standard Port Devices Driver Windows 10
- Vertex Standard Port Devices Driver Ed
Overview: This document provides the steps needed to configure CWSerenade to integrate with Vertex O® Series so that Vertex calculates tax for orders during order entry, pick slip preparation, and billing.
Compatibility: CWSerenade version 3.5 or later is compatible with Vertex O Series® 6.0.
In this topic:
• Before You Start: Taxability Considerations:
• Mapping Data from CWSerenade to Vertex
• Creating the Product Class
• Configuration Steps:
• Setup within CWSerenade
• Set up Data within Vertex
• Configuration Files
• Vertex wsdl (Web Service Definition Language) File
• VertexWS.xml File
Vertex Standard Port Devices Driver Windows 7
• Default Values by Company XML File
• Warehouses XML File
For more information: See CWSerenade/Vertex Interface for an overview on the integration.
Before You Start: Taxability Considerations
Mapping Data from CWSerenade to Vertex
Before you start the configuration steps described below, it is helpful to note the information in CWSerenade that maps to corresponding values in Vertex.
If you specify a Company in the Default Values by Company XML File, it overrides the actual company code.
Used if the Pass Entity Code to Tax Interface (F69) system control value is selected and you do not specify a company code and division code in the Default Values by Company XML File. Set up with the company taxpayer as the parent, and configure all required data at the entity-level taxpayer.
The entity on an order is determined by the division assigned to the source code on the order header.
If you specify a Company and a Division in the Default Values by Company XML File, the Division specified overrides the entity code.
item class (WICL)/ long SKU department (WLSD)/ long SKU division (WLSV)/ long SKU class (WLSC)
Assigned in CWSerenade to the item/SKU (MITM). Used to map to the product class in Vertex in order to apply tax exceptions. See Creating the Product Class, below.
customer class (WCCL)
Assigned in CWSerenade to the customer. Maps to the customer class in Vertex to apply tax exemptions.
• You can also flag individual customers as tax-exempt in CWSerenade, and specifying an Exempt certificate number and Exempt expiry date.
• If the customer on an order is assigned to a customer class in CWSerenade that does not correspond to a matching class in Vertex, Vertex calculates tax as if there is no customer class assignment.
Creating the Product Class
Purpose: In order to set up product classes for taxability purposes, you can map your company’s item class, long SKU department, long SKU division, and long SKU class combinations to product classes (taxability drivers) in Vertex. The particular categories mapped, and the order in which they are mapped, is user-defined, so that you can select the product class hierarchy that best matches the way you group and classify items.
Identified where? The Product_Class_Concatenation_Type in the Default Values by Company XML File identifies the sequence in which to concatenate the four product class code components, with leading zeroes included.
What components can you include?
Identified as Element Number:
item class (WICL)
long SKU division (WLSV)
long SKU department (WLSD)
long SKU class (WLSC)
The setting of the Product_Class_Concatenation_Type identifies the order in which to send these elements to Vertex in order to indicate an item or SKU’s product class.
You set the Product_Class_Concatenation_Type to 2341. This setting indicates to concatenate the product class elements as: long SKU division (2) + long SKU department (3) + long SKU class(4) + item class (1).
You enter an order for an item with the following assignments:
• long SKU division: XYZ
• long SKU department: 4
• long SKU class: 6543
• item class: FD
Vertex receives a product class assignment for the item of XYZ00046543FD. Note that leading zeroes are included (for example, the long SKU department of 4 is included as 0004).
Setup considerations: As a way to simplify the setup process, you can set the Product_Class_Concatenation_Type so that your most commonly used components are included first. For example, if you always use item class (1), sometimes use long SKU department (3) and never use long division (2)) or long SKU class (4), you can set the Product_Class_Concatenation_Type to 1324. Then when you set up product classes (taxability drivers) in Vertex, you only need to specify the item class (1) and long SKU department (3), as the integration concatenates those two values and leaves the rest of the product class blank.
Setup within CWSerenade
System Control Values
• Use Generic XML Tax Interface (J10): Must be selected to have CWSerenade communicate with Vertex.
• Use Standard Tax Calculation if Tax Interface Fails (J13): Select this value to have CWSerenade use the standard tax calculation if it does not receive a response from Vertex. If you select this value, you will need to set up tax rates at the SCF level (WSCF) and/or the postal code level (WZIP).
• Pass Entity Code to Tax Interface (F69): Select this value to pass the entity associated with the source code on the order header to Vertex, provided you do not specify a Company and Division code in the Default Values by Company XML File. If you select this value, then you can set up product class or customer class tax exemptions at the entity level in Vertex.
• Tax Included in Price (E70): Must be unselected if your company integrates with Vertex.
• Send Tax to Vertex as Quote not Invoice (L11): Indicates whether billing should send a quotation or an invoice request message to Vertex when processing a shipment or a return.
• When you change a system control value, stop and restart the background jobs (MBJC) and exit and re-enter CWSerenade to have your changes take effect.
• It is not necessary to set up the Tax on Freight (B14) or Tax on Handling (B15) system control values.
TAX_INT Integration Layer Job (IJCT)
For the TAX_INT job: Set the Communication type to Web Service and set the WSDL Document Name to calculate-tax-60.wsdl. See Vertex wsdl (Web Service Definition Language) File for more information.
Because the TAX_INT job is always in INTERACT status, you do not stop or restart the job for your change to take effect.
Note: The TAX_INT job does not require a process queue.
Important:Integration with Vertex will not work if you hide the TAX_INT job.
Additional Setup in CWSerenade
Create a customer class for exempt customers: Use Work with Customer Class (WCCL) to set up one or more classes of customers who are tax exempt, and then assign customers in CWSerenade to the appropriate customer class. You can then set up the customer class(es) as tax exempt in Vertex. Similarly, set up product class exemptions and individual product (item) exemptions in Vertex. See Set up Data within Vertex for more information on setup steps in Vertex.
Note:If the customer on an order is assigned to a customer class in CWSerenade that does not correspond to a matching class in Vertex, Vertex calculates tax as if there is no customer class assignment.
Set up individual customer tax exemptions: Use Work with Customers (WCST) to set up individual customers as tax exempt, including specifying their Exempt certificate number and the Exempt expiry date, or setting this information up for the customer in specific states or provinces. CWSerenade passes this information to Vertex when a tax exempt customer places an order. It is not necessary to assign these customers to a particular customer class in order to flag them as tax exempt to Vertex.
Assign items and SKU’s to a product class hierarchy: Use Work with Items/SKU’s to assign items and SKU’s to the categories you use to identify product classes in Vertex, as described under Creating the Product Class.
Note:It is not necessary to set up tax rates or other settings at the SCF level or the postal code level if you are using the generic tax integration with Vertex.
Set up Data within Vertex
Use the Sales Tax option within the Vertex Taxability Manager:
Set up company and entities as taxpayers in Vertex:
1. Set up a taxpayer for each company to integrate with Vertex. The taxpayer Code should match the company code and should be zero-filled (for example, company 3 in CWSerenade = taxpayer Code 003 in Vertex). Assign the taxpayer to the appropriate jurisdictions, such as all U.S. states.
2. If you are sending entity information to Vertex, add a taxpayer for each entity for the related company, where the company taxpayer is the parent to the entity taxpayer. For example, if you are adding entity 100 for company 3, select taxpayer 003 in Vertex as the parent for taxpayer 100. Again, assign the taxpayer to the appropriate jurisdictions, such as all U.S. states.
3. If you would like to set up product class exceptions, use the Taxability Driver option in Vertex:
• Input Field = Product Class
• Code = the concatenated product class, as determined through Creating the Product Class
• Taxpayer = your company and, optionally, entity
• Taxability Driver is... = the taxability rule for the product class
• Optionally, any other settings as needed
4. Set up product classes for freight, additional charges, and handling and map them to the appropriate delivery charge categories:
Line Item Type
OF (Order Freight)
LD (Line Duty)
LH (line handling)
Note: If the S/H exclude tax? flag is selected for an additional charge code, then a line that uses this additional charge code for special handling is not subject to line handling (LH) tax. See Establishing Additional Charge Codes (WADC) for background.
AF (additional freight and shipper item charges)
LF (line freight)
If you use the integration with Vertex to calculate taxes, then the settings within CWSerenade to control tax on freight and handling (such as system control values and settings at the SCF and postal code level) are not used.
5. Optionally, set up customer class exceptions in Vertex.
Note:If the customer on an order is assigned to a customer class in CWSerenade that does not correspond to a matching class in Vertex, Vertex calculates tax as if there is no customer class assignment.
Use a text editor to edit the following files.
Important:MICROS recommends that you make a backup copy of each of the files discussed below before making any changes. Also, it is important that you do not make any changes in these files beyond those outlined in these instructions.
Vertex wsdl (Web Service Definition Language) File
Purpose: The wsdl file controls web service communication and other settings between CWSerenade and Vertex.
File location and name: The wsdl file you use for integration with Version 6.0 of Vertex is named calculate-tax-60.wsdl file, and is typically located at C:Serenadeserverconfcwdirectcpproperties on your CWSerenade server, where C: is the root drive.
Configuring the wsdl file:
• Search for localhost and replace each instance in the file with the name or IP address of the server running Vertex.
• Make sure that the port defined for the CalculateTaxWSService is correct. Typically, the port uses https rather than http and does not designate a port.
• Make sure that all other URLs that point to the Vertex server designate a port of 8095.
• Do not change anything else in the file.
Vertex Standard Parts
• Save the wsdl in the same folder where the manifesting wsdl is stored, typically at C:Serenadeserverconfcwdirectcpproperties on your CWSerenade server, where C: is the root drive. Delete the current copy of the calculate-tax-60.wsdl bin file if there is one.
Upgrading the wsdl file: If you need to upgrade your Vertex integration to work with Version 6.0, rename the calculate-tax-40.wsdl file to calculate-tax-60.wsdl.
Note:After making any change to the wsdl, you need to restart CWSerenade to have your changes take effect. See Restarting CWSerenade for more information.
Purpose: Use this file to specify the user ID and password to use for connection to Vertex.
File location and name: This file is called VertexWS.xml and is in the same folder as the wsdl.
Configuring the VertexWS.xml file: You need to enter a valid UserID and Password with access to Vertex. The user ID you specify should be assigned to the Vertex partition that includes the data that will be required by CWSerenade.
The password entry here is encrypted. If you change the password as part of your PCI standards, you must follow the instructions below.
Note:After you change the VertexWS.xml file, you need to stop and restart CWSerenade. See Restarting CWSerenade for more information.
Changing the Vertex user ID and password: To change the Vertex user id and password used for connection to Vertex:
1. On the CWSerenade application server, advance to C:SerenadeCWSerenadeVertexconfig and double-click the runthis.bat file
2. At the Vertex ID/password Configurator window, enter the user ID used for connection to Vertex and click OK.
3. The program next asks for the Vertex password. Enter the password for the user ID and click OK.
The program updates the user ID and password in the VeretexWS.xml file.
Note:The password is encrypted so it will not be clearly visible in this file.
To have this change take effect, restart the SERENADE service.
Repeat these steps for each CWSerenade application server.
Default Values by Company XML File
Purpose: Use this file to specify default values to send to Vertex for each company that will use the tax integration.
File location and name: A copy of this configuration XML file is required for each company that will use Vertex. The files are typically located under SerenadeserverconfcwdirectcppropertiesxsltVertexWS on your CWSerenade server. The company number in the file name should be zero-filled; for example, the file name for company 49 is DefaultValues_049.xml.
Sample files: Your CWSerenade installation includes a sample default values XML file for company 49 and for company 51. You can use these samples as starting points to build default values XML files for your companies.
Configuring the file: Each entry in the file is labeled by an ID, for which you enter the corresponding Value:
Default Value ID
Optionally, use this field to enter an override company code to pass to Vertex that differs from the actual company number. See Configuring the Division and Company Codes for more information.
Optionally, use this field to pass a division code to pass to Vertex. See Configuring the Division and Company Codes for more information.
Indicates the sequence of the item class, long SKU department, long SKU division, and long SKU class to use when creating product classes (taxability drivers) for exceptions to default tax rules. See Creating the Product Class for setup considerations, and see Set up Data within Vertex for setup steps in Vertex.
The tax area ID to send to Vertex in order to identify your call center’s location. You can determine a location’s tax area ID in Vertex Central Home under Tools > Tax Area ID Lookup.
This information is required by Vertex.
This information is required by Vertex. You also use the Warehouses XML File to indicate the tax area ID of each warehouse where you make shipments.
Configuring the Division and Company Codes
These fields in the Default Values by Company XML File enable you to override the Company and Division specified in the QuotationRequest, InvoiceRequest, and DistributeTaxRequest messages that CWSerenade sends to Vertex.
• If you do not specify a Company here: Regardless of whether you specify a Division here, CWSerenade passes:
• Company: The actual company code.
• Division: If the Pass Entity Code to Tax Interface (F69) system control value is selected, this is the entity code related to the source code on the order header. If the Pass Entity Code to Tax Interface (F69) system control value is not selected, no Division is passed.
• If you specify a Company here but not a Division: Regardless of the setting of the Pass Entity Code to Tax Interface (F69) system control value, CWSerenade passes:
• Company: The Company code you enter here.
• Division: None.
• If you specify both a Company and a Division here: CWSerenade passes the Company code and Division code you enter here.
Changes effective immediately: Changes you make to the default values by company file take place immediately. It is not necessary to stop and restart CWSerenade.
Warehouses XML File
Purpose: This file provides the list of warehouses from which you ship merchandise, so that Vertex can apply the appropriate tax rules for the shipping location.
File location and name: Like the default values by company XML file, a copy of this configuration file is required for each company that will use Vertex. The files are typically located under SerenadeserverconfcwdirectcppropertiesxsltVertexWS on your CWSerenade server. The company number in the file name should be zero-filled; for example, the file name for company 6 is Warehouses_006.xml.
Sample files: Your CWSerenade installation includes a sample warehouses XML file for company 49 and for company 51. You can use these samples as starting points to build warehouses XML files for your companies.
Information in this XML file
First WarehouseValue element: The first WarehouseValue element at the beginning of the file indicates that the file provides a list of warehouse ID’s and their corresponding tax area ID values:
Do not change the default element.
Default warehouse tax area ID: The first warehouse entry in the file should indicate a warehouse ID of 000 and your company’s default tax area ID. For example, if the tax area ID is 220250100, the first entry is:
For each warehouse: For each warehouse where you will be processing shipments, enter the ID that identifies the warehouse code in CWSerenade, and enter the tax area ID of the warehouse. For example, if warehouse 3 has a tax area ID of 140430510, enter:
Example: The following example defines tax area ID’s for warehouses 1, 2, and 3:
Note:Make sure that the Default Warehouse (A04) is one of the warehouses included in this file.
Changes effective immediately: Changes you make to the warehouse XML file take place immediately. It is not necessary to stop and restart CWSerenade.
|PC Manifest Interface Setup||Contents||SCVs||Search||Glossary||Reports||Database||Solutions||XML||Index||Using Microsoft Internet Explorer® for CWSerenade|
No pics yet, but here is a page about the radio: http://www.qsl.net/yo4hfu/Yaesu.html It's very simple. Which I like.
I really took a gamble because you can't directly enter frequencies into these radios and they MUST be programmed with special software. To make things worse, a google search told me 3 things:
1) they require an old, slow computer running MS Dos, and the software won't work in a Dos Window on newer computers,
2) they require an old fashioned serial port, which new computers don't have and
3) there are absolutely no tutorials online about how to program them! I aim to fix that last item. Because I was able to do it, on a laptop with no RS232 serial ports, running Windows 10.
Things you need to program this radio with a modern computer:
1) A USB programming cable designed to program THIS radio, with drivers. I found one on ebay for $18. The cable has a USB plug on one end (NOT an RS232 serial port!), and an RJ45 plug on the other end (to plug into the microphone jack) What this cable does is trick Windows into thinking a USB port is now a regular old fashioned Com port.
2) DosBox, a free DOS emulator. People use it for playing old Dos games in newer computers: https://www.dosbox.com/ You can run this on Windows, Linux, or Mac
3) The original programming software. Fortunately it's really old and I was able to find it free on the internet. I found 2 versions. The one I used that worked, I found here: http://www.mediafire.com/?3mn0mbz01aa The software you need is called 'CE5'. There are other versions, like CE6 and CE11, but you need CE5.
First, plug the USB programming cable into your computer. Then insert the driver disk, go to the folder that has your operating system (mine is Windows 10) and install the drivers. (On my driver CD, most of the text in the file names and folder names was in Chinese.) Next, (in Windows) go to Device Manager and find what Com port the USB cable is set up on. In my case it was port 3. Remember this number, and also remember that if you move the cable to a different USB port the com port may change and you'll need the new number.
Download the programming software and put all the files in a new directory on your C drive. I made a folder called 'CE5'.
Download and install DosBox. Fiddle around with it and learn how to mount the CE5 folder so you can access it. Then find your Dosbox configuration file, which is a text file. Mine was located here: 'C:Users[my-name]AppDataLocalDOSBox' The name of the file is 'dosbox-0.74.conf'. Open the file in a text editor (I use Notepad++ for things like this but you can use Notepad) and add these lines to the bottom:
mount c c:ce5
The second and third lines aren't necessary, but they will get things ready for running the program. The 2nd line mounts your CE5 folder (Linux users will know what I'm talking about) and the 3rd line moves you to that directory. If you don't have those 2 lines in the config file, you will have to type them in every time you open Dosbox.
Then, run DosBox from the regular Windows start menu. You will be in your new CE5 folder (but it will appear that you are in the root drive of C.) Then type 'CE5' to run the software. You can mess around in the software and see what's what, and see the different options. It will say 'Com 1' somewhere, but you've redirected Com 3 (or whatever Com port you're using) to Com 1.
I messed around for awhile trying to read from the radio and write to the radio, and honestly, sometimes it worked and sometimes it didn't. But I kept at it and made it work. Here is what seemed to (mostly) work.
First, see if you can read from the radio. Do this by pressing F5 and follow the directions. When it works, your channels currently in the radio will be shown in the program. Mine only had 2 channels programmed and they were commercial channels I couldn't use, in the 430 MHZ range.
Then, change the channels to whatever you want, and add more if necessary. It MAY be very important to not create a brand new channel file, but to MODIFY the file that you got from the radio.
Here are the GMRS channels I put in:
I turned off all the options for CTCSS, DCS, etc. For simple 2 way comms you don't really need those and I don't like them. On the other hand, I'm not sure. Do I need these for this radio? There is no squelch knob.
Then press F4 to save the file. Give it a name, like GMRS8. (Because, 8 channels).
Then press F6 and see if you can write the new channels to the radio. I wasn't able to do it this way. I had to:
Turn off the radio and unplug the cable from the radio, turn the radio back on
Restart Dosbox and press F3 to load the file I had saved
Press F6 to write the file to the radio
Vertex Standard Port Devices Driver Windows 10
Vertex Standard Port Devices Driver EdI did have to try it a few times, but in the end I got it working. The radio now has 8 channels. So if it doesn't work at first, If you get the 'unable to communicate' error, just keep trying, and try different things.