wavestone-cdt / dyode Goto Github PK

Hello,

Could you let me know why you need 0.1uF capacitors around the optocoupler ?
Is it to smooth the input voltage ?

Thanks for your time

Can you please share your status which you set the for the DIP switches.
I guess its not working for normal ones (without DIP)

The case for DYODE v2 needs to be a bit taller.

The Dupont wires prevent the case from being correctly closed.

Hey there,

Thanks for your code. I'm trying to recreate your DYIODE light box but I can't make the HCPL works correctly.
Apparently, it requires 5V input (4.5 to 5.5V) but you power it with the 3.3V pi GPIO.
If I try to do the same thing, the optocoupler does not work and no signal is received.

Do I need to power it by 5V and add a voltage divider to get 3.3V on RX ?

Hi,

The link to the 'talks' gives an error (not found, 404).

Hi guys,

kindly share the details of media converter that works well with this project.

Thanks,
aj

hi, at first thank for this app.
i have problem to run dyode_out.py:
[root@CentOSOUT DYODE v1 (full)]# sudo python dyode_out.py
INFO:root:Loading config file
INFO:root:Configuration name : Dyode test
INFO:root:Configuration version : 1.0
INFO:root:Configuration date : 2016-05-04
INFO:root:Dyode input ip : 192.168.1.100 (08:00:27:9e:5d:fb)
INFO:root:Dyode output ip : 192.168.1.150 (08:00:27:9e:5d:fb)
DEBUG:root:Parsing "Partage de fichier 1"
DEBUG:root:Trying to launch a new process for module "Partage de fichier 1"
DEBUG:root:Instanciating a file transfer module :: Partage de fichier 1
DEBUG:root:Waiting for file ...
DEBUG:root:2017-12-03 16:30:17.712871
DEBUG:root:{'in': '/home/pi/in', 'type': 'folder', 'port': 9600, 'out': '/home/pi/out'}
DEBUG:root:9600
DEBUG:root:udp-receiver --nosync --mcast-rdv-addr 10.0.1.1 --interface eth1 --portbase 9600 -f 'manifest_Partage de fichier 1.cfg'
Process Partage de fichier 1:
Traceback (most recent call last):
File "/usr/lib64/python2.7/multiprocessing/process.py", line 258, in _bootstrap
self.run()
File "/usr/lib64/python2.7/multiprocessing/process.py", line 114, in run
self._target(*self._args, **self._kwargs)
File "dyode_out.py", line 28, in launch_agents
dyode.file_reception_loop(properties)
File "/root/dyode/DYODE v1 (full)/dyode.py", line 44, in file_reception_loop
wait_for_file(params)
File "/root/dyode/DYODE v1 (full)/dyode.py", line 69, in wait_for_file
files = parse_manifest(manifest_filename)
File "/root/dyode/DYODE v1 (full)/dyode.py", line 36, in parse_manifest
for item, value in parser.items('Files'):
File "/usr/lib64/python2.7/ConfigParser.py", line 642, in items
raise NoSectionError(section)

how can i solve it?

Hi,

Do you still have the scad file(or equivalent file) that I can make the edit on the v2 case hardware?

Thanks,

Thanks for share your project.
I built the v2 version using RaspPi3 and followed your steps but receive following error on Input Raspberry.
IP is the Input Raspberry

INFO:root:Loading config file
INFO:root:Configuration name : Dyode v2
INFO:root:Configuration version : 1.0
INFO:root:Configuration date : 2017-07-25
DEBUG:root:Parsing Automate Modbus 1
DEBUG:root:Trying to launch a new process for module Automate Modbus 1
DEBUG:root:Automate Modbus 1
DEBUG:root:{'coils': ['0-1'], 'registers': ['0-105'], 'port_out': 502, 'ip': '192.168.78.50', 'type': 'modbus', 'port': 9400}
DEBUG:root:Modbus agent : Automate Modbus 1
DEBUG:root:Modbus Loop
Performing an action which may throw an exception.
ERROR:pymodbus.client.sync:Connection to (192.168.78.50, 502) failed: [Errno 111] Connection refused
DEBUG:root:['0-105']
DEBUG:root:['0-1']
DEBUG:root:Register start number : 0
DEBUG:root:Register end number : 105
DEBUG:root:Number of registers to read : 105
ERROR:pymodbus.client.sync:Connection to (192.168.78.50, 502) failed: [Errno 111] Connection refused
DEBUG:root:Error connecting to 192.168.78.50
DEBUG:root:Modbus Error: [Connection] Failed to connect[192.168.78.50:502]
DEBUG:root:Data size : 25
^CError in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
Process Automate Modbus 1:
File "/usr/lib/python2.7/multiprocessing/util.py", line 325, in _exit_function
Traceback (most recent call last):
File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in _bootstrap
p.join()
File "/usr/lib/python2.7/multiprocessing/process.py", line 145, in join
res = self._popen.wait(timeout)
File "/usr/lib/python2.7/multiprocessing/forking.py", line 154, in wait
self.run()
File "/usr/lib/python2.7/multiprocessing/process.py", line 114, in run
self._target(*self._args, **self._kwargs)
File "dyode_in.py", line 24, in launch_agents
return self.poll(0)
File "/usr/lib/python2.7/multiprocessing/forking.py", line 135, in poll
modbus.modbus_loop(module, properties)
pid, sts = os.waitpid(self.pid, flag)
File "/home/pi/dyode_in/modbus.py", line 108, in modbus_loop
KeyboardInterrupt
modbus_send_serial(data, properties)
File "/home/pi/dyode_in/modbus.py", line 100, in modbus_send_serial
Error in sys.exitfunc:
Traceback (most recent call last):
File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
ser.write(encoded_data)
func(*targs, **kargs)
File "/usr/lib/python2.7/multiprocessing/util.py", line 325, in _exit_function
File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 542, in write
p.join()
File "/usr/lib/python2.7/multiprocessing/process.py", line 145, in join
res = self._popen.wait(timeout)
File "/usr/lib/python2.7/multiprocessing/forking.py", line 154, in wait
return self.poll(0)
File "/usr/lib/python2.7/multiprocessing/forking.py", line 135, in poll
pid, sts = os.waitpid(self.pid, flag)
KeyboardInterrupt
abort, ready, _ = select.select([self.pipe_abort_write_r], [self.fd], [], None)
KeyboardInterrupt

In your slides you say about "cutting the cable":

In theory, advanced attacks may allow to send information the other way around, for example by switching ports “up” and “down”

Could you elaborate on this? Are you referring to Auto MDI-X? Are you aware of any research on this?

Thanks,

Any assistance you can provide with media converter configuration? We can't seem to get the hardware layer to work.

Can you provide more information regarding what DIP switch settings you used for the media converters and what indicator lights should be illuminated?

Guys,
I have been trying to set your DYODE up. software setup seems fine and running but my converters Ultimode M-023M doesn not want to establish a correct link.
When I connect Tx to Rx and Tx to Rx the files are received but when I disconnect Tx cable from receiver converter and connect it to another converter to Tx socket the flow stops. Maybe the dead end converter needs to have some specific function?
Are there any specific parameters of TpLinks that you've used? I can try to buy and use the ones that you've used if neccecery.

Thanks in advance!