You can just submit the .brd file and get boards made but they'll lack some of the silkscreen because they only print the tNames layer. I'll put the CAM job into git tonight when I get home that exports the proper layers. You run that from EAGLE then zip up the 8x .ger files an 1x .xln file that it generates.Originally posted by D Peart:
To order them I just need to submit the Eagle files from Git to Dorkbot? I think that is where you said you got them made.
I decided to not put it in git because this varies per boardhouse, but here's the CAM job I use:Originally posted by Bryan Mayland:
I'll put the CAM job into git tonight when I get home that exports the proper layers.
Welcome and I do actually! Check the bottom of the v2 wiki page here:Originally posted by Dave S (GeoDave):
When I load 192.168.200.1, I get a blank page. The title and little heatermeter logo does show up on the top bar. I do not have a heatermeter hooked up to the routers serial port. I looked at the page source and it looks like only part of the code for the page was uploaded. I am not stressed that it isn't working because I was well prepared to brick the router. Any ideas on fixing it?
Yeah right? Also, using the same component I think I can make a software-initiated reset that isn't quite as hacky out of the same part. So that means there will be 8 less parts in total, two of which were unique.Originally posted by D Peart:
Always ways to improve on things.
Welcome and I do actually! Check the bottom of the v2 wiki page here:
https://github.com/CapnBry/Hea...ading-LinkMeter-1to2
There's a... thing... in the OpenWrt build system that messes up the configuration file and disables linkmeterd. You get a blank page because the web server throws an error (this is fixed in git sorta). There's a pretty good change that if you ssh in and run that uci batch command and restart lucid, the page will come up.
Can you clarify what you mean? What are you editing?Originally posted by John Bostwick:
...I just put the same port info back into the router and all is fine for another hour or two. Its like it forgets how to access heatermeter...
Originally posted by Bryan Mayland:
Oh you in trouble now! I have pseudo-killed many routers (I have like 5 in my 'lab') but I've always managed to get them going again. The problem is usually trying to figure out A) their IP address B) what format image they want.
Usually in the bootloader the IP address is 192.168.1.1 and they won't take a TRX image, only the custom BIN image specific that device. If it is getting past the bootloader and starting to boot, OpenWrt has a nice feature where you press any button and it goes into a recovery mode (the lights on the device stay blinking) where you should be able to telnet (or ssh I forget) into it to reflash. For the standard image that 192.168.1.1, for LinkMeter custom firmware it is 192.168.200.1.
If all else fails and you have an USB FTDI cable you can just jack into the serial port on the broken device and see what it says is wrong. Just connect the TX line through a couple of resistors to drop the 5V to 3.3V:
<pre class="ip-ubbcode-code-pre">
FTDI TX --\/\/\/--|--\/\/\/-- GND
4.7k | 10k
| Router RX
</pre>
Also connect GND and RX of course. EDIT: If you just want to see what it is saying, you don't need that resistor kajigger, just hook up RX and GND.
Can you clarify what you mean? What are you editing?Originally posted by Bryan Mayland:
<BLOCKQUOTE class="ip-ubbcode-quote"><div class="ip-ubbcode-quote-title">quote:</div><div class="ip-ubbcode-quote-content">Originally posted by John Bostwick:
...I just put the same port info back into the router and all is fine for another hour or two. Its like it forgets how to access heatermeter...
I am still working on fixing the WRT150N. No progress yet. There is no DMZ light on the WRT150N.