Language Selection

English French German Italian Portuguese Spanish

Devices: ROS, Taicenn, Mycroft Mark

Filed under
Linux
Hardware
  • Your first robot: The controller [3/5]

    This is the third blog post in this series about creating your first robot with ROS and Ubuntu Core. In the previous post you were introduced to the Robot Operating System (ROS), and got your robot moving by ROSifying one of the CamJam worksheets. Today we're going to move beyond the CamJam worksheets, and work toward having our robot remotely controlled by focusing on our wireless controller: getting data out of it and into ROS messages.

  • Tough, Atom-based box PC supports EtherCAT

    Taicenn’s Linux-ready “TBOX-4000” industrial box PC provides an Atom D2550, dual GbE ports with EtherCAT support, mSATA, optional wireless, and shock, vibration, and extended temperature resistance.

    Shenzhen based Taicenn Technology has launched a rugged industrial computer that runs Linux or Windows on an old school Intel Atom D2550 “Cedar Trail” processor with dual 1.86GHz cores, 640MHz Intel graphics, and a separate Intel NM10 controller chipset. The TBOX-4000’s D2550 chip has the advantage of being reasonably power efficient (10W TDP), leading to the computer’s under 20W total consumption. It’s also likely to make this computer more affordable than most, although no pricing was listed.

  • Developing an Open Source Voice Assistant: Interview with Mycroft AI’s Steve Penrod

    Mycroft is an industry first. Where Amazon Echo and Google Home are unsurprisingly closed-lipped about their data gathering, we know that recordings gathered from these devices are stored for later use (whatever that might be). Mycroft Mark II, by comparison, is an open source voice platform.

    This means that users of the Mycroft platform can opt into sharing their usage data and designers can then use that data to learn more about demographics, language, and voice recognition.

    On the other hand, users could choose to keep their data private.

    What we know about Mycroft Mark II's hardware is that it has a Xilinx quad-core processor, specifically a Zynq UltraScale+ EG MPSoC. It has an array of six far-field PDM-based MEMs microphones and has hardware acoustic echo cancellation (AEC) for beamforming and noise reduction. It has stereo sound with dual 2" drivers (10 Watts), a 4" IPS LCD touchscreen, BT 2.1+EDR and BLE 4.2 Bluetooth In, and single-band Wi-Fi (2.4 GHz).

More in Tux Machines

Browsing the web with Min, a minimalist open source web browser

Does the world need another web browser? Even though the days of having a multiplicity of browsers to choose from are long gone, there still are folks out there developing new applications that help us use the web. One of those new-fangled browsers is Min. As its name suggests (well, suggests to me, anyway), Min is a minimalist browser. That doesn't mean it's deficient in any significant way, and its open source, Apache 2.0 license piques my interest. Read more

Security: Patches, FUD and Voting Machines

  • libssh 0.8.4 and 0.7.6 security and bugfix release

    libssh versions 0.6 and above have an authentication bypass vulnerability in the server code. By presenting the server an SSH2_MSG_USERAUTH_SUCCESS message in place of the SSH2_MSG_USERAUTH_REQUEST message which the server would expect to initiate authentication, the attacker could successfully authentciate without any credentials.

  • A Cybersecurity Weak Link: Linux and IoT [Ed: Blaming "Linux" for companies that put default passwords on all their products? Windows has back doors.]
  • Undetectably bypass voting machines' anti-tamper mechanism with a bit of a soda-can

    But University of Michigan grad student Matt Bernhard has demonstrated that he can bypass the tamper-evident seals in seconds, using a shim made from a slice of a soda can. The bypass is undetectable and doesn't damage the seal, which can be resecured after an attacker gains access to the system.

  • Security Seals Used to Protect Voting Machines Can Be Easily Opened With Shim Crafted from a Soda Can

    Bernhard, who is an expert witness for election integrity activists in a lawsuit filed in Georgia to force officials to get rid of paperless voting machines used in that state, said the issue of security ties and seals came up in the lawsuit earlier this year when Fulton County Elections Director Richard Barron told the court that his Georgia county relies on tamper-evident metal and plastic ties to seal voting machines and prevent anyone with physical access to the machines from subverting them while they sit in polling places days before an election.

    [...]

    He noted that defeating ties and seals in non-tamper-evident ways isn’t the only method to wreak havoc on an election in Michigan. The state has a unique law that prohibits ballots from being used in a recount if the number of voters doesn't match the number of ballots cast at a precinct or if the seal on a ballot box is broken or has a different serial number than what it should have. Someone who wanted to wreak havoc on an election or alter an election outcome in Michigan could purposely tamper with ballot box seals in a way that is evident or simply replace them with a seal bearing a different serial number in order to get ballots excluded from a recount. The law came into sharp relief after the 2016 presidential election when Green Party candidate Jill Stein sought to get a statewide recount in Michigan and two other critical swing states and found that some precincts in Wayne County couldn't be recounted because the number of voters who signed the poll books—which get certified with a seal signed by officials—didn't match the number of ballots scanned on the voting machines.

OSS: Hedera Hashgraph, Service Providers, and Renaming the Bro Project

  • Hedera Hashgraph Distributed Ledger Technology Shares New Open-Source SDK [Ed: Hedera needs to delete GitHub, however, as the new head of GitHub killed Java projects like Hedera's]
    Hedera Hashgraph, one of the DApp facilitators within the blockchain industry recently announced that it has released its Software Development Kit (SDK) in Java.
  • Service Providers Should Adapt to Open Source World
    Finding differing opinions on open source with the telecom industry isn't hard to do, especially where orchestration is concerned. That's why a panel discussion on open source and MANO at the Light Reading NFV-Carrier SDN event in Denver seemed an odd place to find such outspoken agreement on that topic, but there it was. Four smart guys, none shy with their opinions, all seemed to agree on key points around open source, the need for standards, the role of vendors and the lack of internal software skills. But they also agreed that telecom service providers are struggling a bit to understand how to proceed in an open source world and still need some fundamental internal changes.
  • Renaming the Bro Project
    More than 20 years ago I chose the name "Bro" as "an Orwellian reminder that monitoring comes hand in hand with the potential for privacy violations", as the original Bro paper put it. Today that warning is needed more than ever ... but it's clear that now the name "Bro" is alas much more of a distraction than a reminder. On the Leadership Team of the Bro Project, we heard clear concerns from the Bro community that the name "Bro" has taken on strongly negative connotations, such as "Bro culture". These send a sharp, anti-inclusive - and wholly unintended and undesirable - message to those who might use Bro. The problems were significant enough that during BroCon community sessions, several people have mentioned substantial difficulties in getting their upper management to even consider using open-source software with such a seemingly ill-chosen, off-putting name.

Back End: Apache Kafka, 'Serverless'