hardillb
-
Gesamte Inhalte
12 -
Benutzer seit
-
Letzter Besuch
Posts erstellt von hardillb
-
-
Thanks for the link to the device identifiers.
Rather than posting zips of code changes here, a pull request on github would be great so we can track the changes.
Thanks
-
It's not been packaged for npm just yet
but you can npm install direct from github with the following:
npm install hardillb/node-red-contrib-tinkerforge
If you run this in /home/pi/.node-red it will end up in the right place
I have only done a Ambient light v2.0 node as that's the only hardware I have available to test. But it should be pretty simple do v1.0 node if somebody can let me know the deviceIdentifier.
-
I've been working on some Node-RED Tinkerforge nodes
Feel free to kick the tires
https://github.com/hardillb/node-red-contrib-tinkerforge
All feedback welcome.
P.S. A guess about the error you had will be that you probably need a use the v2 Ambient Light Object if you have a v2 bricklet
-
Having read the description again more closely I now assume that the RS485 extension can only be used to communicate with other RS485 Extensions to combine stacks.
If I want to talk to 3rd party RS485 Modbus kit then I'll have to use a USB RS485 adapter on a RED Brick and a separate bus.
-
Can anybody point me at some examples of using a RS485 Brick with a RED Brick?
Specifically I was looking for examples of connecting to none Tinkerforge modbus devices
Thanks
-
That seams to have worked.
Thanks
-
Hi,
Python 2.7.10
And I got the following after adding the line:
<configparser.ConfigParser object at 0x7f5340581750>
Traceback (most recent call last):
File "/opt/shared/projects/tyyrell/brickv-2.3.4/src/brickv/plugin_system/plugins/red/red_tab_settings_network.py", line 1056, in slot_network_connect_clicked
iname_previous = self.network_all_data['manager_settings'].get('Settings', 'wired_interface', '')
TypeError: get() takes exactly 3 arguments (4 given)
-
A totally fresh SD card image and stacking with the RED Brick on the bottom seams to be working now.
Does stack order matter?
Also I don't seam to be able to get brickv to bring up the network interface. When I hit the "connect" button I get the following error on the console:
Traceback (most recent call last):
File "/opt/shared/projects/tyyrell/brickv-2.3.4/src/brickv/plugin_system/plugins/red/red_tab_settings_network.py", line 1054, in slot_network_connect_clicked
iname_previous = self.network_all_data['manager_settings'].get('Settings', 'wired_interface', '')
TypeError: get() takes exactly 3 arguments (4 given)
I'm using a src build of brickv on Fedora 22.
I can bring the interface up manually from the command line.
-
Just to add some more info.
- Master Brick + the Ethernet Extensions works fine
- RED Brick + Ethernet Extension no sign of any network interface
- RED Brick + Master Brick (Ambient + Motion) brickv doesn't show the master brick when plugged into the RED Brick
- RED Brick + Master Brick + Ethernet + Master brick. brickv shows only the RED Brick when usb attached to RED Brick, When connected to master brick it shows ambient light, motion and ethernet (not RED Brick)
RED Brick is running v1.8 card image
Components:
RED Brick v1.0 (fw 2.0.2)
Ethernet Extension v1.1
Master Brick v2.1 (fw 2.3.4)
Ambient Light v2.0
Motion Detection v1.0
- Master Brick + the Ethernet Extensions works fine
-
I've got a RED Brick and a Ethernet Extension (POE) and when I assemble then stack I can not see any networking options.
The Brick View doesn't list any network interfaces and ifconfig -a only list lo and a tunl0 adapter, not tf0.
I can't see anything obvious in the dmesg output. Any suggestions?
I have serveral sets of hardware and I can't get any of them to work.
Broken apt-get dependencies
in General Discussion
Geschrieben
I'm trying to upgrade my RED-Brick with apt-get and I'm getting dependency issues with perl.
I'm on jessie so should still be getting updates:
I've tried clearing out the apt-cache but no joy.
Any ideas?