me to tell it where to install (it automatically chooses in the install wizard) and it always chooses rhino/4.0/.... when i type grasshopper into rhino 5.0, it says "unknown command grasshopper".
what's the trick for getting Gh into Rhino 5.0, PC platform (on a bootcamped Macbookpro)...?
Thanks!
Christina…
triangulate my mesh faces thus i was getting 7 points per polygon. 7 outputs needed. It works with 7 outputs even if 3 of them are not being used.
Problem solved!
Thanks so much for your help!
…
find a solution. At least it looks that way on my PC.
I lowered the number of decimal places to 1 (to save the time), and this is the closest result:
http://www.dodaj.rs/f/3Y/Ih/4QqtFuQy/proba.jpg
…
his is a clean new file with nothing but two points an the preview geometry. Clipping obviously inludes the two rhino points only.
Running Win7 x64
Dual ATI Radeon HD 6900 (I believe, Catalyst updated some days ago.)…
picture:
... and on a PC without anything attached to the serial port. When you open the port, start the read component and its timer, do you then get a stream of <empty> values in the log output? (hmmm... I suppose that's only reasonable - but still, you are also seeing this?)
I suppose that, because of the mutually exclusive behavior of both the spider and grasshopper (i.e. only one at a time can access the COM port), we can deduce that we are listening on the correct port.
Am I listening on the correct pin (if such a notion makes sense at all)? If I look back to the spider software, I see that 9 channels are listed and that it's only the measured value on channel 0 that changes when I press the load cell. Channels 1, 2, and 3 report OVERFLOW; 4, 5, 6, and 7 are pretty much constant at 0.000 to 0.005 V; and channel 8 says FFFF. I do not know how things like that work so I do not know if they reflect reading from the 9 pins on the D-sub 9 connector.
As for your BTW question: no, I don't need to record all of the sensor values. I suppose that the Out value on the Read component will always reflect the most current value and that's all that I need to get on with life. In the end, the idea is that we have 4 load cells in the 4 corners of a plate onto which a vertical pipe is fixed. Loads are then put on the top end of the pipe and we'll have to visualize both direction and magnitude of the bending moment that is calculated from the compression - tension readings from the load cells... We've done this on a scaled model and streamed load cell information into MatLab. Now we'll have to use a different datalogger and I was hoping to be able to do the post processing in Rhino.
wim…
will not be created in plugin folder of my Rhino 5 Beta as it does in Rhino 4 while it did in my last computer (pc,windows vista).
I copy/pasted the Grasshopper folder from Rhino 4 to Rhino 5 Plugin folder, but it seems like this folder is not functioning at all since when I drop any gh file for addons, like MeshEdit or Kangaroo or python, in the component folder, nothing new gets created in component ribbon.
Please let me know if you have any suggestion.
Thanks,
Naciem
…
ans to manipulate PC easily (I mean we have a couple of CNC routers... just no staff to run them... thanks middle management) Plus the Lexan is uncomfortably close to my tutors work (he using Correx). And Honestly unless it was sheet (rather then corrugated) then it wouldn't be the desired aesthetic.
I think if it was to change to PC then I would get rid of the nodes as we know them and just connect the PC to itself from the mid point of each line (fully realising the semi-monocoque style. This would forgo the acute angle annoyance.
I agree that the larger would lend itself to MERO style, but as it is with the extrusion being 4*3mm its tiny screws would drive me bonkers. I would use NX or something for a component based approach.
If it was going to take this to the next level then a rethink of materials etc would mean a more stable work flow/object/outcome, but now I'm past the point of no return (not as dramatic as that sounds). Although it does all seem to be falling apart at the last hurdle [dun dun dunnn!!] ;)
…
add another "trivial" constrain to the puzzle (for instance the PC sheets are 1.2*2.2m > meaning the obvious). This is addressable ONLY via the black bill (don't even think to use GH components for solving similar stuff).
3. One-off nodes are probably OK BUT for larger scales you'll need MERO type of approach > meaning assembly/component concepts > meaning dealing with instance Rhino definitions: blocks in plain English (don't even think to use GH components for solving similar stuff).
4. "Engulfing" type of strut extrusions are rather the best option (use aluminum in this case) > meaning profiles that can "wrap" the triangle content edge (be that "paper" or Lexan/PC).
5. The whole thing appears "easy" but on a pro level is rather quite challenging and obviously totally undo able without the black pill.
6. So: mesh relaxation <> adapter topology matters <> pack issues <> component design <> triangle content design <> cost <> you named it (for <> read "interact").
Such a "simple" case ... eh? …