FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

News:

Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support


New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Pages: [1] 2 3 ... 10
 1 
 on: January 18, 2022, 08:13:07 PM 
Started by MattHousley - Last Post by MattHousley
Hi,

My name's Matt, and I'm from England. I've been professionally involved in serial control in the broadcast industry for over 20 years, utilising FTDI chips for RS232 and RS422 control. However, I've joined the group as an Amateur Radio hobbyist. I'm developing using the Mikroe Click USB Adapter https://www.mikroe.com/click-usb-adapter, that utilises the FT2232H to control various modular add-on boards that they supply. The first one I'm looking at is the https://www.mikroe.com/irda-3-click "IrDA Click 3" board for communication to an old Psion 5mx. Mikroe, unfortunately supply now software or documentation for their 'Click USB Adapter' other than a circuit diagram https://download.mikroe.com/documents/starter-boards/other/click-usb-adapter/click-usb-adapter-manual-v102.pdf, so this is where I'll be looking for help from the community.

Look forward to talking with you!

Cheers

Matt

 2 
 on: January 18, 2022, 06:44:27 AM 
Started by Susaninfes - Last Post by Susaninfes
Start New Topic
**
medecin en vacances comment faire : https://www.maquestionmedicale.fr
consultation par internet : https://www.maquestionmedicale.fr
docteur en ligne : https://www.maquestionmedicale.fr
medecin en ligne : https://www.maquestionmedicale.fr
medecin conseil en ligne : https://www.maquestionmedicale.fr
**
consulter un medecin en ligne

 3 
 on: January 14, 2022, 09:09:58 PM 
Started by jaypdx - Last Post by jaypdx
I haven't received a resolution via email yet, but I'm thinking I can open each attached FT260 and read the configuration EEPROM via the FT260_I2CMaster_* commands.  I should be able to figure out where the serial number is stored by comparison with FT_PROG.  This only works because I have an external EEPROM on my board... I'm not sure how one would read the serial number stored inside the chip.  Is this a reasonable approach?  How does FTDI recommend differentiating between multiple FT260's connected to a system?

 4 
 on: January 14, 2022, 01:27:16 PM 
Started by ilya79 - Last Post by sbell
Hi, just curious, what was the outcome of this?

 5 
 on: January 14, 2022, 08:38:45 AM 
Started by jaypdx - Last Post by FTDI Community
Hi Joseph,
You have already contacted us by email.
Feel free to post any resolution here to help other community users

Regards
FTDI Community

 6 
 on: January 13, 2022, 06:46:44 AM 
Started by jaypdx - Last Post by jaypdx
Do the D2XX functions work for HID devices like the FT260?  When I call FT_ListDevices(&numDev, NULL, FT_LIST_NUMBER_ONLY), it returns numDev=0 with my FT260 EVM attached (though FT_PROG can see it just fine).

 7 
 on: January 11, 2022, 05:06:26 PM 
Started by jaypdx - Last Post by jaypdx
How can I read the SN from my application?

 8 
 on: January 11, 2022, 04:57:26 PM 
Started by jaypdx - Last Post by FTDI Community
Hi
You can use the FT Prog utility to read/ program the serial for these parts
https://ftdichip.com/wp-content/uploads/2021/05/FT_Prog_v3.12.11.594%20Installer.zip

Regards
FTDI Community


 9 
 on: January 10, 2022, 03:04:58 PM 
Started by jaypdx - Last Post by jaypdx
I have multiple FT260's attached to my PC and I'd like to use the serial number to tell them apart.  How can I read the serial number of each?  I don't see a function in libft260 that does this.  If this isn't possible, is there some other way to uniquely identify each FT260 attached to the system?




 10 
 on: January 06, 2022, 12:33:23 PM 
Started by knut - Last Post by knut
Update: It works now. :)


In case anyone finds this thread and is curious, there are the commands I ended up using in the initialization (after opening the device):

FT_ResetDevice(ftHandle)
FT_SetLatencyTimer(ftHandle, 16)
FT_W32_GetCommModemStatus (ftHandle, &modemStatus)
FT_SetDataCharacteristics(ftHandle, FT_BITS_8, FT_STOP_BITS_1, FT_PARITY_NONE)
FT_SetFlowControl(ftHandle, FT_FLOW_NONE, 0, 0)
FT_SetDtr(ftHandle)
FT_SetChars(ftHandle, 0, 0, 0, 0)


(Of course, there is also some code around these, including checking return values, etc. These are just the FT_ function calls.)


Pages: [1] 2 3 ... 10