Progress! - Modbus Controlled Motor | MOT15

Подписаться 7 тыс.

Просмотров 1,9 тыс.

50% 1

Discussing some progress made in debugging communication issues, showing off basic closed loop control, and having some fun along the way! We’re developing a motor controller running on a PSOC4 MCU.
#Modbus #Motor #Microcontroller
-
Links:
Previous Video - • Choosing a C-Based Mod...
Docklight - docklight.de/
Modbus Test Program - www.se.com/us/en/faqs/FA180037/
E4E Code Repo - github.com/eeforeveryone/e4e-...
Support EE for Everyone:
Patreon - / eeforeveryone
YT Membership - / eeforeveryone
0:00 Introduction
0:50 Docklight com port debugger
2:50 Arduino Modbus Master Replacement
4:30 MODBUS preliminary register map
5:33 Motor Demo
6:30 Closing thoughts

Наука

Опубликовано:

4 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 2

@kickdrivesoftware 2 года назад

Ran into this because of the Docklight mention. On thing I like to throw in. The FTDI chipsets most certainly implement parity detection correctly. I wonder if this was an issue with parity detection at all, and not something related to voltage levels / "use two-wire-RS485 with extra GND yes-or-no". You mention TX Enable, so I assume actual motor connection is RS485, correct?

@EEforEveryone 2 года назад

Hello! That's bizarre. Yes, I wired the TxEn line from the ftdi module to the TxEn of an rs485 transceiver. Correct- the actual connection is rs485, with transceivers on all ends. The most bizarre thing that I saw in this whole debacle is that the ftdi module controlling TxEn appeared to receive extra data, while the two ftdi modules I was using to sniff via Docklight showed the correct and intended result. All three modules were hooked up to the same tx and rx pins, same PC, same ground.