Cul self-construction, which chip? CH340G or FT232RL

---

Well, I have a MaxCube in operation for some time. He works very well with two thermostats and two window contacts.

Because I would like to add at some point other 868 MHz devices, I’ve tried me now building on a cul. Unfortunately, I’ve probably ordered the wrong Arduino Nano. I have now with the CH340G chip. Not the FT232RL. Does anyone know a way to operate the cul with the CH340G? If so, where can I find a HowTo?

If it doesn’t work, can I run an Arduino Nano with CH340G (Homeduino) in addition to an Arduino Nano with FT232RL (cul)?

I’m not really aware of what you are trying to do, but a quick look on ebay learns me you can order a Arduino Nano with a FT232RL chip. If the chip is your problem, wouldn’t it be the simplest to order a version with the other chip?
http://www.ebay.com/itm/Nano-V3-0-ATMEGA328P-FT232RL-FTDI-Micro-controller-Board-for-Arduino-/182355415015?hash=item2a753acfe7:g:iZAAAOSwu-BWOw99

@koffienl
Thanks, I was hoping there is a way. Now I must wait again until the item will be delivered.

maybe a dumb question, but why does the ch340 not work?

@leader21
I read it on different pages.

Here, see Bezugsquellen.
and here
and also here
Where the last probably on the same source of fhem is based.

ah ok, i see. the problem with the unique id and ch340 chips.
sure, sorry, haven’t thought about it.

@leader21
Will I have problems because the arduino (homeduino) also has the ch340 chip?
Or is it enough with an arduino with ft232 chip? So the arduino for the cul.

Hi.
the problem with the ch340 is the missing unique id.
The cul firmware must work normally. That is not the problem. But after a reboot the device path may change. And your pimatic config does not work.

ttyUSBX is not always the same.

I have three ch340 running on my raspberry pi.

With a simple udev rule, all chips have always the same name.
The identifier is now the physical usb port.

cat /etc/udev/rules.d/42-usb.rules
SUBSYSTEM=="tty", ATTRS{devpath}=="1.4", SYMLINK+="mysensor"
SUBSYSTEM=="tty", ATTRS{devpath}=="1.5", SYMLINK+="homeduino"
SUBSYSTEM=="tty", ATTRS{devpath}=="1.2", SYMLINK+="smarthome"

Create simply this file, reboot and it’s done.

The USB device on port 1.5 is now always reachable over:
/dev/homeduino

I have with the ft232 chip and my kernel some trouble. After some hours there are read errors. So I prefer the 340

Hello,

I have the same problem. My solution was the serial by path method.
See: Serial by Path
After that you must only connect your devices to the same USB-port.

Can someone explain what you can do with such a CUL? My German is quite bad …

@koffienl

See here cul firmware

For pimatic I think there a not a lot usages.
I want also to control my max! heating system. I am waiting for my CC1101 wireless chip for that.

@koffienl
the cul is a transceiver for RF communication, especially 868 MHz.
you need it e.g. if you want to connect to the homematic hardware or max! heating components directly.
for pimatic especially there is a pimatic-homegear plugin (for communication with homematic hardware) and the max-cul plugin for direct communication with the max hardware without gateway.

Is this something to incorporate into ESPimaticRF ?

well, i am no programmer but i guess this would be hard to achieve i guess.
you need a special transceiver and the cul fw.
feel free to have a look into the matter. it would be an outstandig feature of course!
maybe a @developer with more knowledge on homematic and CUL can help any further?

Yeah, don’t have anything of that kind stuff, can’t really say for sure it is something that fits in the ‘homeduino’ part of ESPimaticRF

Sorry for renewing a week+ old thread, but I have an issue that I hope a more experienced user can help with. I have two CH340g devices (Arduino Mega Clones) connected to a usb hub and both are connected to different ports; however, only one device is being recognized with the installed CH340g drivers. I am using Labview to interface with the Arduinos and thus require 2 active USB to Serial connections (2 separate COM ports) in order to communicate with both devices. I’ve gathered from this post that it might be impossible to uniquely identify multiple 340 devices because they all carry the same Serial ID. Have any of you ever encountered this issue? if so, did you come up with a solution? Any help and suggestions would be greatly appreciated!

Did you try this already?

/dev/serial/by-path/

It does require to use the same USB ports each time.

https://forum.pimatic.org/topic/42/tip-homeduino-usb/4

@rikki78 So it’s basically impossible to have two separate COM ports communicating with two CH340g devices? In that case, what if I replaced one of the Mega clones with an authentic FTDI chipped one? Would there be any issue when communicating with both the clone and the authentic one? From my experience you can have as many com ports as you want when communicating with the FTDI Megas, but maybe there’s a compatibility issue I’m not aware of?

@Kurobuta
What operating sytem are you using?

The problem with the ch340 is the missing unique id.

On Linux you can use the physically port for COM detection.
Like the devicepath “/dev/serial/by-path/”

On Windows i think you have a problem and you must use two different transciever chips.

@Kurobuta No it is not impossible, you have to address the USB ports in a different way. So instead of USBttyx use the /dev/serial/by-path/
Assuming you use Linux as OS