I just can’t figure out what setting is being made once I open the manufacturer’s control program that allows LabVIEW to communicate. Home Questions Tags Users Unanswered. It just seems strange that I can ping the chip but not get it to send signals to the relay board. I only ever use 2. Minions Thanks for this. Page generated using Genpage – Version: I can connect, get a handle, get the device details serial number, etc , get the modem and queue status, etc.
|Date Added:||22 June 2013|
|File Size:||36.10 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Fdi rate setting and reading if the device is open by multiple processes the baudrate read results are undefined. Tests the following ioctls: I haven’t tested this myself so I reproduce Kuba’s documentation slightly edited he added to the patch below: I can connect, get a handle, get the device details serial number, etcget the modem and queue status, etc.
The driver is no longer marked experimental because many people have used it and it seems to behave as 245f. They have also provided sample devices for driver testing. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
NOTE This hack is now out of date as the driver version 1. Even if you could, it’d be possible to effectively unprotect it by removing the chip and replacing it with an unprotected version. FTR is frdi IC. Message 3 of 4. Sign up using Email and Password.
FTDI R Relay board
The driver is marked experimental at the moment. Message 1 of 4. Use the most up to ftvi linux kernel. I only have to do this if the computer has been restarted and can open and close my program as much as I like as long as I don’t restart the computer. Acknowledgements FTDI for making the specifications for the device available, and providing me with their new product.
I bought it from Dick Smith in New Zealand. The original device I have is called the USC Please see the driver source for details or the description below. See the script for the loopback plug assumed 245rr.
Sign up using Facebook. Most Active Hardware Boards: I have also included a perl script for use with testing a serial port with a loopback plug. Message 2 of 4.
Every so often I will update this webpage though. The program tests simple writes of any size using simple data. I just can’t figure out what setting is being made once I open the manufacturer’s control program that allows LabVIEW to communicate. I know that I am connected to the board because I can get the device details but it will not accept my write command until I first use their program to connect to the board.
Instrument Control (GPIB, Serial, VISA, IVI)
I am worried about my own working process, not a third party action. Run it with -x for help. But I’m going to change that because it isn’t experimental any more.
Sign up or log in Sign up using Google. You will need to fix broken.