Hi, I need to set up the KFX module to send the following RAW (decimal) string when a key fob button is pressed: ‘401863102341675096179874845349121290’
The base station software however only allows me to set up to maximum 9 bytes so I can not enter the entire command string.
Is there a way to set up the base station software to allow entering & sending more bytes?
Thanks for your help!
Hi,
This product wasn’t designed for this particular application, but the only way to increase the number of bytes sent would be to change the “Do Not Allow Multiple Commands” field to 1. You would then have 4 sets of 9 bytes.
Additionally you may be able to utilize the Release bytes, but they will only go out the serial port when the button is released so you would need to account for that when setting these values.
Hi Jacob,
Thanks for your quick reply. I tried with the “Do Not Allow Multiple Commands” field set to 1 but when I press the ‘set configuration settings’ button I get an ‘incorrect data entry’ error
These are bytes with a maximum value of 0-255 so to send a 771 as a string (assuming ascii encoding) you would need to send a value of 55 in the first field, 55 in the second field, and 49 in the third field etc.
Hi Jacob,
I’m not sure if what I’m trying to do is possible with the KFX
I have a device that I can send serial commands to when it is connected to my pc
ASCII format the command = Measure, stop
HEX format of the command= 4D6561737572652C2073746F700D0A
So now I want to set the KFX to send this command to my device when I press the key fob button (with the KFX and PR35-19 USB Configuration Adapter for NCD connected to my device)
I thought this would be possible with the ‘RAW’ setting but I’m not so sure anymore…
You will need to convert those hex values to decimal values and input them into Base Station. i.e. your first two hex values are 4d and 65 so these would be a decimal value of 77 and 101
I cannot guarantee this will work as its not the primary purpose of these key fobs.
Hi Jacob,
I managed to convert the ASCII string into decimals and was able to save it
(protocol = raw and ‘allow pultiple commands per button’ = 1)
With the KFX module in the USB Configuration Adapter, connected to pc via USB I can see the needed ASCII string in my serial capture software when I press the key fob button.
So far so good.
However, when I remove the USB Configuration Adapter and wire the pins 1, 2, 3 and 10 of the KFX module to a serial cable and correct power source, following to the PIN layout diagram below, it does not work.
I used an old PC with a real serial port to test and when I press the key fob button I do see some characters received in my serial capture software. However not the ascii command that I need.
This is what I’m receiving when I press the key fob button:
I realize that what I’m after (use a key fob to send a specific ascii command “Measure, start” to an instrument with a serial port) is not the primary purpose of the KFX module and I’m at the point of giving up but maybe you still have a magic tip for me that could make it work after all … 
thanks for your help.
So if you’re getting data at all then it sound like your pins are attached correctly. Gibberish usually means a bad baud rate or serial settings. Try baud rate 115200, data bits 8, stop bits 1, parity none.
those are the settings that I was using
What character encoding is your realterm using? The bytes above would need to be displayed as single byte ascii.
first screenshot is with the KFX module in the USB Configuration Adapter connected to PC via USB. When I press button 1 of the key fob I can see the incoming “Measure, start” message. (port settings can be seen in the lower right coner)
The next screenshot is with the KFX module pins 1, 2, 3 and 10 wired directly to a serial cable and correct power source, connected to a serial port of the pc. Exact same settings as the test above (except for the used port of course).When I press button 1 of the key fob I’m not seeing the expected input
PS1: I also tested with the pins 9 (DTR), 12 (CTS) and 16 (RTS) connected additionally to the correct RS232 pins but that makes no difference.
PS2: I also noticed that key fob button 2 (set to send a different command) works fine with the KFX module in the USB Configuration Adapter but gives no input at all with the KFX module wired directly to the serial cable
DTR and CTS are not used by the KFX.
Set your software to “Hex” in the lower left corner to see the bytes, you can also use “uint8” to see raw values from 0-255 (similar to the KFX setup software).