Scyto Posted November 27, 2015 Posted November 27, 2015 If i can choose packet format 2 or 14 is there any reason i should choose one over the other? In my experience these are not common formats (i tend to use the BIN and HTTP formats for dashbox and btmon.py respectively) so just wondering on the choice. I am happy to use either as my dashbox is connected to com2. (PS i started posting in the right forum this time
io_guy Posted November 27, 2015 Posted November 27, 2015 No pro/con to either. I just chose a couple somewhat easy formats to integrate. Http tends to have a little extra overhead and bin is a PITA to code.
Scyto Posted November 27, 2015 Author Posted November 27, 2015 Cool, i tested both 2 and 14 and they both work a.ok on my system on v0.2.3.
ppitkin Posted November 27, 2015 Posted November 27, 2015 Io_guy, Would there be any way to have your node server pick up the SEG feed that comes out of the Dashbox? In my setup my Gems both use the wired network configuration to talk to the dash box and so I can't use com 1 for the node server. Peter
io_guy Posted November 27, 2015 Posted November 27, 2015 I have no idea of what comes out of the dashbox. If you have details, send them along.
Scyto Posted November 27, 2015 Author Posted November 27, 2015 ppitkin Yes there would, the dashbox can be wired to both com2 and com1 of the GEM and expose both packet formats. On mine i have the the COM2 of the GEM connected to my COM1 of the dashbox, you can get the data from http://dashboxip:8001for the dahsbox COM1 (8002 for dashbox COM2). I actually tried this at first with nodelink as my GEM was not connected to ethernet or wifi - the dashbox was my interface and unit that sent to SEG. However the packet format that is on the dashbox COM1 will be same packet format used on GEM COM2 - namely format #5 bin48-net-time. If you changed the packet setting to another format it would stop sending data to the dashbox. Also GEM COM2 supports less options - only packet formats 0,1,2,4,5,7,8,9,10,11 - none of which nodelink currently supports anyways. So options: extend nodelink to support bin48-net-time and keep connected like i have connect just the transmit line of GEM COM1 to dashbox COM2 - this IIRC keeps the ethernet/wifi working and allows the send of the packet (i have never tried this, but it is something ben at brultech once mentioned in a post to me). If i has another one of the cables i could try.... let me see what i can find on amazon, the GEM COM1 format would still need to be something that nodelink understands, so if you are using a 3rd packet format say for btmon.py you would be SOL The one advantage of supporting bin48-net-time over COM2 > COM1 is that this leaves GEMIP:8000 open and free, so connecting with web browser wouldn't interrupt data collection by nodelink ppitkin - out of interest why do you need to do what you need to do?
io_guy Posted November 27, 2015 Posted November 27, 2015 NodeLink supports 2, which can be sent over COM2. What am I missing? If life is easier with bin48 I'll add it.
Scyto Posted November 27, 2015 Author Posted November 27, 2015 NodeLink supports 2, which can be sent over COM2. What am I missing? Nodelink might work (as the i think the dash box outputs the stream raw on that port) but the dashbox would stop recording data - it requires the bin48-net-time. That said, i can access the web page of the GEM on dashbox:8001 - so let me double check packet format on that port - --edit-- confirmed it gets a gem decode error.
Scyto Posted December 7, 2015 Author Posted December 7, 2015 I noticed the version changes - want me to test the changed packet format / routing via the dashbox?
io_guy Posted December 8, 2015 Posted December 8, 2015 Sure. I still need to do some work on bin48. It unfortunately sends all 32 channels regardless of what you enable in packet send, so right now you'll get 32 nodes in the ISY. It also doesn't include power so I calculate it myself. All in all a crappy format.
ppitkin Posted December 8, 2015 Posted December 8, 2015 Scyto, Sorry for taking so long to reply. I'm afraid you totally lost me with all your com1 com2 connections. I have two gem's feeding into a single dash box. As far as I'm aware, according to Ben, there is only one way to get this setup running when using the wired ip network connection. I used to have my dash box sending the data to SEG for monitoring and display purposes - I really like the GUI. Dash box needs a lot of work before it can come the with SEG. What I wanted to do was have the dash box send the data to node link and this to then display the data in ISY as a node Well actually two nodes which mimick the two gems. So 64 channels plus voltage. I don't use the pulse counter or temperature sensors yet. I know it is possible to have the dash box update ISY parameters but I wanted it to be de splayed as a device in the ISY.
Scyto Posted December 9, 2015 Author Posted December 9, 2015 You have your gems connected to the dashbox using the com port leads right?
ppitkin Posted December 9, 2015 Posted December 9, 2015 Scyto, No, I use a network connection (RJ45) not the rs232 leads. The two gems and the dash box are connected via a network switch.
Scyto Posted December 16, 2015 Author Posted December 16, 2015 Oh then the solution i am refering to won't work for you. The point is that when the GEM is connected via the RS232 leads to the Dashbox the Dhasbox proxies the GEM. So for example one sets packet format for outgoing COM2 on the GEM to BIN48-NET-Time; this port is then say connected to the incoming COM1 port on the Dashbox. At this point the dashbox is decoding the packet format AND it is making the GEM available on the the <dashboxipaddr>:8001. so the idea would be to use that with nodelink. This is one of the theoretical advantages of using com connection over IP connection as you have effectively multiple ways of reading the packet format. It also means you can put out one packet format on the IP address of your network and another different format out over the COM port but still make that accessible to otger machines a) this isn't an option in your scenario and b ) it doesn't seem to work (i just tried) and i am getting this for the bin48-net-time: 2015-15-12-15 17:42:13 - GEM Decode Error - Unknown Format [gem] I will checkin with Ben and ask if the packet format is fully exposed or not via the DB.
Scyto Posted December 16, 2015 Author Posted December 16, 2015 To be clear i have decoding of the bin48 working when i point at the GEM directly.
ccclapp Posted February 15, 2016 Posted February 15, 2016 Oh then the solution i am refering to won't work for you. The point is that when the GEM is connected via the RS232 leads to the Dashbox the Dhasbox proxies the GEM. So for example one sets packet format for outgoing COM2 on the GEM to BIN48-NET-Time; this port is then say connected to the incoming COM1 port on the Dashbox. At this point the dashbox is decoding the packet format AND it is making the GEM available on the the <dashboxipaddr>:8001. so the idea would be to use that with nodelink. This is one of the theoretical advantages of using com connection over IP connection as you have effectively multiple ways of reading the packet format. It also means you can put out one packet format on the IP address of your network and another different format out over the COM port but still make that accessible to otger machines a) this isn't an option in your scenario and b ) it doesn't seem to work (i just tried) and i am getting this for the bin48-net-time: 2015-15-12-15 17:42:13 - GEM Decode Error - Unknown Format [gem] I will checkin with Ben and ask if the packet format is fully exposed or not via the DB. Hi I have gem and DB connected via com 1 gem into DB with the rs232 cable. I believe this requires BIN48-NET-Time. My gem does not have Ethernet or wifi ie cable connection only. I'm about to setup nodelink. I expect to prefer energy channel nodes over variables on ISY. I would also like to try having nodelink send to SEG ( even though DB can do it ). I'm a little unclear if this configure is working or if nodelink needs to go direct to gem ( which I can't do without wifi/Ethernet on my gem). Do you mind clarifying ( I'm sure you said it above, but I don't follow your conclusion fully) Thanks
io_guy Posted February 15, 2016 Posted February 15, 2016 To my knowledge the DB doesn't put out the right format for NodeLink (I have no idea what it does). The GEM/DB will send a limited amount of data to the ISY. If you pick up the GEM network module, you can put the DB on COM2 and hook NodeLink up to 1, You can then get full V5 data into the ISY and send info to SEG or Emon.
ccclapp Posted February 15, 2016 Posted February 15, 2016 To my knowledge the DB doesn't put out the right format for NodeLink (I have no idea what it does). The GEM/DB will send a limited amount of data to the ISY. If you pick up the GEM network module, you can put the DB on COM2 and hook NodeLink up to 1, You can then get full V5 data into the ISY and send info to SEG or Emon. Yes I may have to do that, but was hoping to avoid another add-on and connection point Also can you or others clarify, with gem to nodelink is the dash effectively rendered obsolete, or does it still do something unique ( besides its own dashboard, which SEG Emon will replace)? I guess it holds a lot of historical data. Would this be held in the RPi if no dash? Thanks
io_guy Posted February 15, 2016 Posted February 15, 2016 I don't use a dash. It's purpose would be to store historical data. I store on Emoncms, which could also be installed locally if desired.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.