For those new to message boards please try to follow a few simple rules when posting your question.
Choose the correct forum for your message. Posting a VB.NET question in the C++ forum will end in tears.
Be specific! Don't ask "can someone send me the code to create an application that does 'X'. Pinpoint exactly what it is you need help with.
Keep the subject line brief, but descriptive. eg "File Serialization problem"
Keep the question as brief as possible. If you have to include code, include the smallest snippet of code you can.
Be careful when including code that you haven't made a typo. Typing mistakes can become the focal point instead of the actual question you asked.
Do not remove or empty a message if others have replied. Keep the thread intact and available for others to search and read. If your problem was answered then edit your message and add "[Solved]" to the subject line of the original post, and cast an approval vote to the one or several answers that really helped you.
If you are posting source code with your question, place it inside <pre></pre> tags. We advise you also check the "Encode "<" (and other HTML) characters when pasting" checkbox before pasting anything inside the PRE block, and make sure "Use HTML in this post" check box is checked.
Be courteous and DON'T SHOUT. Everyone here helps because they enjoy helping others, not because it's their job.
Please do not post links to your question into an unrelated forum such as the lounge. It will be deleted. Likewise, do not post the same question in more than one forum.
Do not be abusive, offensive, inappropriate or harass anyone on the boards. Doing so will get you kicked off and banned. Play nice.
If you have a school or university assignment, assume that your teacher or lecturer is also reading these forums.
No advertising or soliciting.
We reserve the right to move your posts to a more appropriate forum or to delete anything deemed inappropriate or illegal.
(Apologies for the repeat --- I posted this in the Lounge yesterday, before someone pointed me to the proper forum)
For those in DIY electronics...
Exactly how good is USB for providing power to a device? I specifically mean devices that are not attached to a computer and use the USB cable strictly for power.
I've long felt that we need a standardized low-voltage DC power source coming right out of our walls, much in the manner that we currently have 120V (or 220V) AC coming out of our walls -- to eliminate the need of all those "brick" power adapters cluttering our power strips. The last time I discussed this publicly (about 10+ years ago), I was scoffed, with the reason being every device uses a different voltage. (I rejected that, as AC devices were able to adapt to use 110V, so DC devices could adapt to use the standardized voltage).
The real problem was that every device used it's own plug size (and selling the proprietary adapter was a profit center). However, now there's some movement to power things with USB cables.
So, the question for the electrically minded here: If all you had available to power your device was an USB cable, would that be viable?
I'm not really sure how to describe this, so bear with me...
I'm having this problem on my development PC.
HP ENVY Desktop - 795-0030 CTO
Intel Core i7-9700
Win 10 Pro
My PC is fairly new, probably a year 1/2 old.
Every few minutes I get what I can only describe as a "pause" that lasts for only a second or two. Everything stops - Mouse, Keyboard, music I'm listening to - everything. If I'm in the middle of typing, the key I last hit repeats across the page until the 'outtage' stops.
I have run the HP diagnostic tools on it and with no issues found. I don't see any problems in Hardware & Device manager, and no OS problems either that I can see. It almost seems like a USB problem, but I don't see anyting to confirm that.
So, I'm open to suggestion on this one.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
If the pause doesn't happen during diagnostics (looping continuously), then it may be a driver or problem in Windows, or some other hardware problem. Windows can pause if the kernel is busy doing or waiting for something, completely unable to service any other interrupts until the current interrupt/operation is complete.
An I/O problem with a USB device may also be gumming things up.
Make sure all drivers are updated and see what happens. If the problem still persists, start unplugging things, one at a time, until the problem goes away.
<pre>Hi Everyone. I have an issue and I would like you to help me. I own an ASUS N56JR laptop and I'm planning to upgrade from 8GB Memory to 16 GB (The manufacturer specifies this limit). What I did first was only taking out the original memory stick from its slot (let's say it's Slot 1) to check the reference and features. When I put the stick back in Slot 1, the computer didn't turn on. After blaming it on the electrical network, I decided to switch the stick to Slot 2. Then it booted normally. I couldn't just remain with the doubt, and put the stick back in Slot 1. This time the laptop did turn on, but the keyboard back-light and display didn't turn on, so I don't know if it was actually booting. My question is if there is any chance I screwed the slot or something else in my machine, so this is happening now. Thanks for your attention.
I am trying to access the GPIO of an embedded computer. The device was installed with Windows 10 Pro 20H2 x64 (not my decision). I installed the vendor specific drivers, and the GPIO device is shown with "Intel(R) Serial IO GPIO Host Controller - INT34BB" in the device manager.
I searched the internet and could find a “GpioTestTool” (https://github.com/ms-iot/samples/tree/develop/GpioTestTool) which I could compile on my development machine. After installing “Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019” (“VC_redist.x64.exe”) on the embedded machine, I could start the program.
It shows following error message:
“Error: GPIO is not available on this system”
This error message is also shown when I start the program as an administrator.
That is, the program fails to detect the GPIO.
Can you suggest any tools for trouble shooting?
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
My GLINK USB 2.0 extension cable isn't detecting External Hard Drive, though Pen drive is being detected. Plugging the EHD directly to the USB port of the CPU works fine. Only the extension cable isn't detecting it. How do I make the EHD work with the extension cable now? Or shall I try something else altogether? I'm running on Windows-7 32 bit. May I get some help, please?
I am thinking of FPGA for an algorithm of mine, but lack of any experience with FPGAs.
The activity is number crunching, no fancy IO or A/D conversion.
I send a very large number, it crunch, and I get answer as a single number. One can think of it as integer factorization.
Crunching is made of large additions, subtractions, shift operations (*2 and /2), increments/decrements and logical operation and bits testing.
May be an embedded ARM processor to handle communication and data conversion.
Algorithm can be adapted for treading.
It is for hobby, so no real budget.
What hardware/software would you recommend ?
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
Im currently making an app on windows forms trying to program a micro over UART. I can achieve it, although it is taking a long time to carry out the program. I have used stopwatches to determine it is my read function taking up the majority of the time. When i try to read the micros response from each command I have to wait for all of it, which is why im using a while loop in the code below, if the returned message size is not what i expect. What im wondering is, if there is any way to speed up this process. The response from the micro should be pretty fast, its running at a baudrate of 115200, meaning the whole 512 kb file should in theory take just over 30 seconds to complete, at the moment it is more than double that, at 80 seconds.
The response from the micro should be pretty fast, its running at a baudrate of 115200, meaning the whole 512 kb file should in theory take just over 30 seconds to complete, at the moment it is more than double that, at 80 seconds.
You missed a couple things:
- In serial communications, every byte is preceded by at least a start bit and a stop bit, other settings like parity can add other delay. This make at least 10 bits for a byte transmitted, this make sending 512kB just under 45 secondes at 100% efficient.
- Any operation like reading the 512kB from storage will add delay.
- Any one serious with serial communication, for such a file, will encapsulate the data within a communication protocol to ensure data is not corrupted on the other side. This imply mode data to transmit and some time to ensure data integrity.
So 80 secondes is not that bad.
“Everything should be made as simple as possible, but no simpler.” Albert Einstein