Just finished my DIY project, dsox lan interface with usb console interface.
What I've to do next is to buy a 3D printer
Sweet!!!
Just finished my DIY project, dsox lan interface with usb console interface.
What I've to do next is to buy a 3D printer
Did you join the 2 pins on the 'finger connector' for auto detect - can't tell since it's the 'other side' of the picture you posted.
No 3D printer really needed... I cut my original back/cover plate to hold my diy lan card - works just fine. Though I'm sure you could still use it as an excuse to get a 3D printer
cheers,
george.
gamalot,
I have a DSOX2014A and am looking to make a dsox lan interface. I think I missed somewhere in this little thread why a usb console interface might be useful. Could you please illuminate me.
thanks
There 2 simple reasons to have a USB console interface:
1) the board looks empty if there is a LAN interface only
2) Just in case the LAN interface doesn't work
There 2 simple reasons to have a USB console interface:
1) the board looks empty if there is a LAN interface only
2) Just in case the LAN interface doesn't work
2) doesn't work on the PC side?
So it is just a USB to ethernet converter? Confused.
One more picture, no more confusion.
There 2 simple reasons to have a USB console interface:
1) the board looks empty if there is a LAN interface only
One more picture, no more confusion.Wow, your right, thats worth 1000 repliesThere 2 simple reasons to have a USB console interface:
1) the board looks empty if there is a LAN interface only
Looks are definitely important, even in test equipment! Your board is really beautifully designed. Have any extra you want to get rid of?
... Now the problem is when the oscilloscope power is off, I can not see the virtual serial port on my PC, I need to modify the design to fix this bug.
It would, but it would likely take too long to be useful. If you're using the console port you probably want to be able to send a break within a second or two of power on when the bootloader runs. That means the port needs to exist and the terminal program should be ready and waiting.
I would think that the STM32F072 could be programmed to put out the req'd characters at the appropriate time after it's boot. It could certainly beat a human. You would have to set some non-volatile variable to whether you wanted it to do so or not. It wouldn't have to wait for the terminal to come up, maybe just bit-banging the transmit pin before even starting the terminal would be the easiest
Think that more easy just feed STM from USB
Thought I'd look at my suggestion of a few posts ago. I don't have a STM32F072. Just for fun I tested an Arduino nano and a Teensy 3.6 to see how long it takes them after power up to put out a character. The nano 1.45 seconds, the Teensy 402ms. I'm not ready to try this inside my scope yet.
Made a scope trace:
Is it processor start time on UART side only? Or with USB wakeup and send some info from terminal app on PC? (but IMO USB response strongly depending from PC, OS etc)
This is just the time for his UART chip (which is really a 32 bit ARM microprocessor that contains a UART ) to boot up and serial.write(" ..") to the I/O pins. All the time is the normal boot stuff required for the chip to determine the voltages and clocks are stable enough to run. This would all happen before any USB comm is established. You just need to know what to print (spaces?) and when to print it to get the DSOX in the right state. You don't even care what the response is. After that you'd start the USB stuff and takeover the same I/O pins for the regular comm session.
I'm pretty sure the STM32F072 chip could do the same and beat the micro in the DSOX to the point the input is needed.
Can you kindly share the schematic and layout files of your network interface card? Thanks!
So - I've been a little busy, but as promised - the permanent mod for the 3000T series.
After some testing, I found out that the registry edits to the regdb wasn't needed and all the mod takes is a exe, that call the infiniivisionlauncher.exe with our commandlines.
As I am no programmer, I found a source code in the CE sdk to do the job, compiled a exe and deleted the lnk in the startup folder, placing the exe here and copying the full infiniivisionlauncher.exe to the secure folder, as all exe's in the startup folder will be launched and as a result creating the "bootloop" problem.
I have created a zipfile with the needed exe's, a readme file and a script to do the job of copying.
The script will also copy a backup of cal-data to the usb stick, as I had a incident during all this testing, where the scope reported it gone, sp just to be safe.
Use it at your own risk! - But I have done quite some testing using the script, after reflashing firmware and no problems.