Jump to content

Joe Gamma

Members
  • Content count

    8
  • Joined

  • Last visited

  • Days Won

    17

Joe Gamma last won the day on January 21 2015

Joe Gamma had the most liked content!

Community Reputation

95 Excellent

About Joe Gamma

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  • Location
    San Jose, CA, USA
  • Interests
    Sleeping, when not wrestling DDR2.
    LED Art Installations, when available.
  1. TopoR 5.2.1 Comments and Questons

    Thank you, Elena. Given this forecast, I can't see that neither myself, or Joe, will be able to do a comparable tool within the same (or shorter) timeframe. I'm also confident that your team, given their many-year long experience of coding, will do an excellent job. I'd love if you would consider integrating this feature into TopoR itself (instead of an external tool), but any solution is ok. I would be happy to help out with any beta-testing when available! Thanx again! Great news! /Marcin Thanks for the update, Elena: I can just see Marcin and I finishing off a 90% effective tool, days before the real tool is posted! That's great news: especially since I now expect the bosses to crank up the work in the next couple months. Keep up the good work -- Joe
  2. TopoR 5.2.1 Comments and Questons

    Yes, I have read through both the TopoR and Eagle file format documents, and realized that I have quite a way to go before I grasp the whole concept. You see, I'm a GUI kind of guy, although I would say I'm a fairly good programmer. So before I embark on this journey that will easily consume 2-300 hours, I would need to know that we don't "re-invent the wheel" on each side... It would also be nice to know if there is any work being done from Eremex on this Eagle suport issue? I was in contact with Elena a while ago, but haven't had anything confirmed yet. Regards,Marcin I'll probably be upgrading my own Eagle to 6.x pretty soon (next 3 or 4 weeks). At that point, maybe we could team up on this. It's a pretty flat problem, so would not be hard to divide up the XML coding stuff. And maybe we could work out a deal with Eremex.... or maybe Maple would like to join the coding fun... -- Joe
  3. TopoR 5.2.1 Comments and Questons

    I'll have to check with the bosses. Classic American Intellectual Property policy applies here, unfortunately. Have you seen the Eagle 6.x XML data format yet? I suspect the export/import process will be ** MUCH ** easier now. Eagle->FST, then FST->Eagle. Naturally, now that I've burned hundreds of hours in getting export to DSN working, and translation to SCR... this ULP-to-DSN / FST-to-SCR conversion process will be inferior and obsolete. :angry: At this point, I'm on overload to finish the current design. Sorry I can't help immediately; I will examine this as soon as I can. -- Joe
  4. TopoR 5.2.1 Comments and Questons

    Sorry for late reply: project was interrupted by about 7 new "#1-priority" tasks. Back on track: 1. Thanks to the excellent Описание формата TopoR PCB, I wrote an application to convert FST to Eagle SCR. Using MS VC# 10 Express, the XML Namespace API(System.XML.Xpath) makes this task much easier. 2. re: Circles and Polygons: Of course, if I had read #8 in the help file Specifics section, on Coppers, this would not even be a question. The issue with filled circles is that the wires entering them are clipped at the circumference after Refine Wires and Freestyle... Just as the Help file describes. ... This is not really a problem, however: What appears to work: make an UNfilled circle, with wire width > radius. It's always poured, and maintains circular shape even at small sizes, in manual and FreeStyle routing. I can handle the Eagle polygon connectivity cleanup, a minor task at the end. One further question: On the Import side of the conversion, I should have translated the Eagle ULP to output directly to FST, instead of DSN (And I might still need to do that... ) For Keepouts, the DSN lines for placement and routing keepouts both create RoutingKeepout->Wires areas: (place_keepout(path "1#Top" 0.000000 408.000000 984.000000 344.000000 984.000000 344.000000 904.000000 408.000000 904.000000 408.000000 984.000000 )) (wire_keepout(path "1#Top" 0.000000 408.000000 848.000000 344.000000 848.000000 344.000000 768.000000 408.000000 768.000000 408.000000 848.000000 )) produces two rectangles: the place_keepout creates a 4-wire closed set of lines, the wire_keepout creates a 4-sided polygon (with hatched fill). The FST export of this is: <Keepout> <Role> <Trace> <LayerRef name="1#Top"/> </Trace> </Role> <Polygon> <Dot x="344" y="984"/> <Dot x="344" y="904"/> <Dot x="408" y="904"/> <Dot x="408" y="984"/> </Polygon> </Keepout> <Keepout> <Role> <Trace> <LayerRef name="1#Top"/> </Trace> </Role> <Line> <Dot x="408" y="848"/> <Dot x="344" y="848"/> <Dot x="344" y="768"/> <Dot x="408" y="768"/> <Dot x="408" y="848"/> </Line> </Keepout> ... The Via keepout works fine: it makes a "RoutingKeepout -> Vias, Layer: All" polygon. I can hack the FST file, to change the <Role> to <Place side = "Top"/>, and the polygon is created as a placement keepout, as expected. ________________ So, is my DSN placement keepout syntax correct? It looks like it's *close* to what your parser wants, but not quite. Many thanks, I am even enjoying this part... -- JLC
  5. TopoR 5.2.1 Comments and Questons

    Greetings from California! First, well done with the TopoR program. A unique concept, with a good (and improving) UI. I am using it with Eagle 5.11. One interesting feature for possible future updates: For circles, if the line width is 0, make the circle a filled area. The Polygon equivalent is a little difficult to draw, and results in an output that doesn't quite match the circle when imported back to Eagle. Keep up the good work, this tool is about to save me at least 3 weeks of time on one project. I do not understand why it is not used more in the USA. -- Joe
×