![]() I was having a little trouble understanding how your drive numbers it's register addresses in the manual you posted, and 7680 is just the decimal version of the hex number(s) listed in your manual and was my best guess at what to use. = what would this be? each read/write that MB2HAL does needs a unique number this is it This thread has a link to an unsigned driver. If anyone knows anything some help would be appreciated. I am trying to get it to work on my windows 7 64 bit system but cannot find drivers that work anywhere. HAL_TX_NAME=run = is this for linuxcnc's side? It can define a unique name for the hal pin that is created I have a USB to serial adapter that is a 'HL-340'. MB_TX_CODE=fnct_16_write_multiple_registers = is this a standard function in modbus to be able to write values to the vfd? yes NELEMENTS=1 = What is this? The number of register addresses in this block (can be more than one) Ok, could you explain what the diffrent codes would translate to in my VFD manual? i'm having a hard time seeing the connection.įIRST_ELEMENT=7680 = What is this? This is the register address you are reading or writing to #Example: mb2hal.00.01 (transaction=00, second register=01 (00 is the first one)) #The pins are named based on component name, transaction number and order number. #fnct_16_write_multiple_registers: creates a floating point input HAL pins. #fnct_15_write_multiple_coils: creates boolean input HAL pins. ![]() #fnct_04_read_input_registers: creates a floating point output HAL pins. #fnct_03_read_holding_registers: creates a floating point output HAL pins. #fnct_02_read_discrete_inputs: creates boolean output HAL pins. #REQUIRED: Modbus transaction function code (see specifications). Have use a lot of different brands of USB-Serial-Adapters and some just don't work for certain things.MB_TX_CODE=fnct_16_write_multiple_registers I would lean more towards #1 or #2 being the problem. I would uninstall the old driver first, reboot, then try this one. It would install and look fine, but would get consistent output to the serial device. I have had problems when the right driver was not installed. Try This Driver as it looks like the adapter is based on the Prolific chipset, which a lot of USB-Serial-Adapters use.USB-Serial-Adapters internals are much faster with data than a normal serial port, and I've seen on occasion where turning those values down can help alleviate problems. After you check/change the settings in device manager for the com port, on the "Port Settings" tab, go to "Advanced" and turn the "Receive Buffer" and "Transmit Buffer" down to the low setting.Not knowing what scales you have, it's hard to know. Some serial scales when viewing from a terminal window, require a command entered for them to return the weight.What brand of scales are these? Have you talked to the manufacturer to make sure those com port settings are indeed correct? Device Manager-Ports(Com & LPT)-Properties of your Com Port-Port Settings tab Have you checked the Com port settings in device manager? The adapter probably installed at a default settings of 9600/n/8/1, where you need 2400/E/7/2 (2400 baud rate, even parity, 7 data bits, 2 stop bits) The adapter in device manager should read 2400/E/7/2 as well. See if you can find a computer with a real serial port, and check the scales there. Try the same adapter on another computer maybe a different OS if you can. Some of those adapters the drivers/chip-set can be weird and not allow some types of devices to work correctly. Have you used that USB-Serial-Adapter on other computers with no problems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |