I wanted a way of listing connected devices that have been served an IP Address using the command line on my DG843GT ADSL2+ router with DGTeam Firmware. This firmware allows ssh login and the ability to change the noise margin amongst other things.
I began by looking at the link for attached devices on the admin webpage of the router. This URL http://192.168.1.1/setup.cgi?todo=nbtscan&next_file=devices.htm was examined and the command nbtscan was noticed.
This was tried on the command-line but it didn't seem to do anything , nbtscan --help didn't help either.
I thought it must be something to do with arguments so I tried nbtscan 192.168.1.1 (my routers IP Address) this listed the attached devices so it's a result.
I haven't written a script using expect to get and extract this info automatically yet but it's on my todo list.
Example of the command and its output xx added to anonymise my MAC addresses
# nbtscan 192.168.1.1
192.168.1.3;UNKNOWN;00:xx:83:2D:xx:BA
192.168.1.10;TORE;00:1F:xx:C8:xx:B5
192.168.1.12;UNKNOWN;00:1B:xx:07:xx:A3
192.168.1.13;DEB;D6:56:xx:FE:xx:57
192.168.1.22;DAD;00:30:xx:46:xx:2E
A place to where I can record my Technical stuff that should be accessible from anywhere. It is mainly technical stuff I find interesting and I suppose it can be looked on as a modern Lab-book.
Wednesday, 5 February 2014
Tuesday, 4 February 2014
Linux Tinyos example for patching a header file
I was having problems making a simple program for TinyOS using the command :-
make micaz
The micaz is the target device and can be other devices like iris , telos & tmote etc.
The error I got was:-
error: variable ‘McuSleepC__atm128PowerBits’ must be const in order to be put into read-only section by means of ‘__attribute__((progmem))’
From reading around the issue is documented here.
The patch is downloaded to the ~/tinyos-main/ directory and it patches the atm128const.h file to prevent the error messages.
The patch is applied using the following command:-
patch -p1 < tinyos-atm128-const-fix.patch
make micaz
The micaz is the target device and can be other devices like iris , telos & tmote etc.
The error I got was:-
error: variable ‘McuSleepC__atm128PowerBits’ must be const in order to be put into read-only section by means of ‘__attribute__((progmem))’
From reading around the issue is documented here.
The patch is downloaded to the ~/tinyos-main/ directory and it patches the atm128const.h file to prevent the error messages.
The patch is applied using the following command:-
patch -p1 < tinyos-atm128-const-fix.patch
Wednesday, 29 January 2014
Pentalobe Screwdriver Size Modification for the Macbook Air
Remember that using tools can be hazardous so wear eye protection and proceed with caution , if in doubt don't do it.
I had the annoying problem in that the Pentalobe screws for the Macbook Air I was repairing were too big for the Pentalobe screwdriver I had lying around , it was one supplied in a kit for replacing the LCD on an iPhone. I then realised that the head on this screwdriver has a stretched sort of taper so I basically ground the end of it with a grindstone fitted to my Dremel tool until it fitted the screw-head , testing the fit as I went. Job done , although the modified tool will now no longer fit the iPhone , that's not too much of a problem because iPhone replacement LCD's usually come with the tools required to do the job.![]() |
Ground Down Pentalobe |
Tuesday, 12 November 2013
Wireless Charging on a Star S7189 Mobile Phone
Warning: while soldering be careful of solder fumes, wear eye protection and don't burn yourself. Note that charging batteries can be dangerous especially Li-Ion but the work detailed here means we are effectively generating our own internal 5V supply in the phone and connecting this directly to the USB power connections as they come into the phone. It is the equivalent of connecting a micro USB cable to the phone from a 5V USB charger, only its wireless. You have been warned and I am not responsible for your actions.
S7189 Display |
This S7189 quad-core Android phone from Star was pretty cheap around £100 and it worked well. I found the front facing camera was not the best, but for the price I can live with it. Screen was also pretty good with a reasonable viewing angle. It was also pretty slick running any Apps I downloaded from Play with no signs of lagging.
Palm Internal Charging Circuit |
Palm Back Cover |
Circuit Cut Out of Plastic Cover |
Sticky Cover Preserved |
Stuck to Clear Film |
![]() |
S7189 Back with Cover Removed |
![]() |
Ground Connection |
![]() |
Routed Copper Tape |
![]() |
Palm Charge Circuit Added to S7189 Back Case |
![]() | ||
Phone Placed on Charger |
![]() |
Phone Now Charging |
Pure Evoke 1 Crackly Burbling Audio
Warning: while this radio is low voltage around 12V dc no mains voltage appears in the actual radio, so it is relatively safe to work on. The wall-wart power supply itself however is mains voltage ( in my case it's 230V AC ) so this needs to be treated with respect. Also while soldering be careful of solder fumes, wear eye protection and don't burn yourself. You have been warned, I am not responsible for your actions.
I have had this Pure Evoke 1 DAB radio for about 7 years but it started having problems. The audio became crackly and it also had an associated burbling noise. The signal quality displayed for the radio station I listen to normally which previously was 97 was now wavering between 40 up to about 70.
The first thing I tested was the most accessible thing the wall-wart power supply. This power supply seemed to be ok, measuring around 17.4 volts dc on my Fluke multimeter.
![]() |
Evoke 1 Amplifier Board |
So I started removing the capacitors on the amplifier board one-by-one to test them on my Peak capacitance and equivalent series resistance meter. All capacitors measured well within 10% of their marked values and low ESR apart from one capacitor, C7 a 100uF 16V electrolytic which is located very close to a regulator heatsink that runs very warm. Its value measured low and its ESR was higher than it should be so it appears that it is effectively being dried out over time.
![]() |
Faulty Capacitor C7 on the tester |
When I soldered the new capacitor into the board I bent the new capacitor body away from the offending 3.3 V regulator heat-sink to prevent the new capacitor being dried out with the heat.
![]() |
Capacitor bent away from heat-sink |
Job done. Thanks for reading and good luck if this is what has happened to your Pure Evoke 1.
Saturday, 21 September 2013
Use an ATTiny45 to auto-boot a NAS200 on power up
I make no guarantees for the information contained herein, I also cannot be held responsible for data loss as a result of your actions, we make our own decisions.
I needed a way of booting the Linksys NAS200 automatically when powered up. As standard from Linksys the NAS200 just stays off when powered up. The Power button on the back left hand side when looking at the rear of the NAS200 needs to be pressed to start the NAS. I often found that when I tried to connect to the NAS it was powered off usually due to a power outage that occurred through the night. I would then have to go upstairs to power it on and wait for it's disk check to finish before I could actually use it. So I set out to fix this inconvenient feature of the NAS200. First power off and disconnect the power supply then remove the hard drives so they don't get damaged. I numbered the drives 1 and 2 to match the bay they came out of before removal just to be sure they went back into the correct drive bay. I proceeded to open up the case of the NAS. This involved removing the silver painted base cover using a screwdriver to lift the plastic sprung pillars out and then slide the cover to the front of the NAS. Four screws included one covered by a warranty sticker ( only proceed if you are happy having no warranty and only if you are confident of success ) are removed. This allowed removal of drive bay 2, be careful of the power wires to PCB and SATA connector. Another four screws are removed to remove drive bay 1, again be careful of SATA and power cables. This will allow the main PCB to be accessed. Four screws are removed and this allows the PCB to be removed. An 8 pin socket was procured, pin 4 was soldered to the rear of one of the PCB mounted USB socket, pin 8 was connected to the 5V pin on the LM7805 voltage regulator see the picture below.
Pin 5 is connected to the conductor of the power push button at the rear of the PCB via a flexible insulated wire, I soldered it to the top of the push button.
The ATTiny45 was programmed using an Arduino Uno programmed with the ISP Sketch, it's in the Arduino IDE examples, remember to choose the correct board and serial port in the IDE. See my previous post on how to program the ATTiny45 with the Arduino Uno Board.
The AutoPowerON.ino sketch basically sets up the port pins we are using as inputs this gives us the high impedance state so the pins don't affect the NAS200 power up or switch off function using the button. After 10 seconds (just to be sure the power has settled) from power being applied the pins on the ATTiny45 being used are set as outputs and PB0 PB1 go low and high respectively for half a second. They then return to high impedance state, the NAS200 has begun booting. After this the program in the ATTiny45 is then caught in an infinite loop, this ensures the pins are only pulsed once for each power cycle.
Note* I only use pin 5 this is the active low output, pin 6 can be used for circuits that may need an active high 5V pulse.
Code I used is pasted below I saved it as AutoPowerON.ino :-
The programmed ATTiny45 is inserted into the socket carefully ensuring that pin 1 on the ATTiny45 goes into pin 1 on the Socket ( see the photo above ). The unit was tested by plugging in the power to the NAS, after 10 seconds the familiar boot beep with the flashing leds occurred. After the full boot the NAS was available on the network all without having to press the power button. :)
I needed a way of booting the Linksys NAS200 automatically when powered up. As standard from Linksys the NAS200 just stays off when powered up. The Power button on the back left hand side when looking at the rear of the NAS200 needs to be pressed to start the NAS. I often found that when I tried to connect to the NAS it was powered off usually due to a power outage that occurred through the night. I would then have to go upstairs to power it on and wait for it's disk check to finish before I could actually use it. So I set out to fix this inconvenient feature of the NAS200. First power off and disconnect the power supply then remove the hard drives so they don't get damaged. I numbered the drives 1 and 2 to match the bay they came out of before removal just to be sure they went back into the correct drive bay. I proceeded to open up the case of the NAS. This involved removing the silver painted base cover using a screwdriver to lift the plastic sprung pillars out and then slide the cover to the front of the NAS. Four screws included one covered by a warranty sticker ( only proceed if you are happy having no warranty and only if you are confident of success ) are removed. This allowed removal of drive bay 2, be careful of the power wires to PCB and SATA connector. Another four screws are removed to remove drive bay 1, again be careful of SATA and power cables. This will allow the main PCB to be accessed. Four screws are removed and this allows the PCB to be removed. An 8 pin socket was procured, pin 4 was soldered to the rear of one of the PCB mounted USB socket, pin 8 was connected to the 5V pin on the LM7805 voltage regulator see the picture below.
![]() |
NAS200 ATTiny45 in Socket |
Pin 5 is connected to the conductor of the power push button at the rear of the PCB via a flexible insulated wire, I soldered it to the top of the push button.
The ATTiny45 was programmed using an Arduino Uno programmed with the ISP Sketch, it's in the Arduino IDE examples, remember to choose the correct board and serial port in the IDE. See my previous post on how to program the ATTiny45 with the Arduino Uno Board.
The AutoPowerON.ino sketch basically sets up the port pins we are using as inputs this gives us the high impedance state so the pins don't affect the NAS200 power up or switch off function using the button. After 10 seconds (just to be sure the power has settled) from power being applied the pins on the ATTiny45 being used are set as outputs and PB0 PB1 go low and high respectively for half a second. They then return to high impedance state, the NAS200 has begun booting. After this the program in the ATTiny45 is then caught in an infinite loop, this ensures the pins are only pulsed once for each power cycle.
Note* I only use pin 5 this is the active low output, pin 6 can be used for circuits that may need an active high 5V pulse.
Code I used is pasted below I saved it as AutoPowerON.ino :-
/*
NOTE* This Sketch will pulse a Pin low on the ATiny45
This is to auto power up a NAS box to ensure it
is available after a power cut. It normally has to be
turned on by pressing the power button.
If using an Arduino to program these devices you need to
program the ISP Sketch found in the IDE onto the Arduino
first.
So the circuit will pulse a pin low after a
predetermined amount of time say 10 Seconds
This pin will be connected the same part of
the NAS box's push button circuit to simulate
a button press.
We only want to do this procedure once on every power up.
hence the capture while loop at the end of the loop function.
+5V---------------------+
Vcc|
+----------+
PB2 | 8 |PB4
+-----|7 3|----+
PB1 | ATTiny45 |PB3
+-----|6 2|----+
TO PB0 | |PB5
Push Button +-----|5 1|----+
| 4 |
+----------+
GND|
Ground-----------------+
(Wiring Diagram for Auto Power On Circuit)
By Jim Park jim (dot) buzz (at) gmail (dot) com
Coded :- 18/09/13
*/
int PowerPin = 0; // Pin 5 to power up the NAS if it's active Low
int PowerPinInv = 1; // Pin 6 to power up the NAS if it's active High
void setup() {
// declare pins as O/P's or I/P's
pinMode(PowerPin, INPUT); // HI-Z pin
pinMode(PowerPinInv, INPUT); // HI-Z pin
}
void loop() {
// Now delay for 10 Seconds
delay(10000); // 10 second delay to be sure power is stable
pinMode(PowerPin, OUTPUT); // Remove HI-Z state from pin
pinMode(PowerPinInv, OUTPUT); // Remove HI-Z state from pin
digitalWrite(PowerPin, LOW); // Active Low on Pin 5
digitalWrite(PowerPinInv, HIGH); // Active High on Pin 6
delay(500); // Half a second delay
pinMode(PowerPin, INPUT); // Back into HI-Z state
pinMode(PowerPinInv, INPUT); // Back into HI-Z state
while(true){} // Capture for ever......and..ever.........
}
The programmed ATTiny45 is inserted into the socket carefully ensuring that pin 1 on the ATTiny45 goes into pin 1 on the Socket ( see the photo above ). The unit was tested by plugging in the power to the NAS, after 10 seconds the familiar boot beep with the flashing leds occurred. After the full boot the NAS was available on the network all without having to press the power button. :)
Thursday, 5 September 2013
Programming ATTiny45 using an Arduino Uno
![]() |
Wiring of the Programmer |
The Arduino is programmed using the Arduino IDE and USB with the ArduinoISP sketch from the File Menu located in examples. Remember to choose the correct board and Serial port from the Tools menu, I was using an Uno. You have to set up the Arduino software to be able to program devices like the ATTiny45, I used the http://hlt.media.mit.edu/?p=1695 site to add the support. It was then just a matter of wiring up the Arduino as shown, putting an ATTiny45 in the 8 pin socket selecting the new board ATTiny45 (Internal 1MHz Clock) and programming the device with a sketch I wrote for this particular device.
Subscribe to:
Posts (Atom)
Defender 300tdi Lucas 10AS Alarm Immobiliser (Spider) Problems
We have a 1997 Landrover Defender 300tdi that has given immobiliser problems intermittently. I had initially fixed the fuel solenoid as we w...

-
Server failure This server failed with the error "E171F PCIE Fatal Err B0 D3 F0" during power up. Upon inspection it was found th...
-
I bricked my MR3220 router with an OpenWRT firmware upload. I did manage to get it back by soldering a 4 pin header on its pcb to allow conn...
-
I make no guarantees for the information contained herein, I also cannot be held responsible for data loss as a result of your actions, we m...